Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Windows Script Host
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Security concerns== Windows applications and processes may be automated using a script in Windows Script Host. Viruses and malware could be written to exploit this ability. Thus, some suggest disabling it for security reasons.<ref>{{cite web|url=http://www.norman.com/Virus/Articles/Articles_previous_years/25780/en|title=Norman - Antivirus & Security Software for Home & Business|website=AVG.com|access-date=30 April 2018|url-status=live|archive-url=https://web.archive.org/web/20060221140139/http://www.norman.com/Virus/Articles/Articles_previous_years/25780/en|archive-date=21 February 2006}}</ref> Alternatively, antivirus programs may offer features to control .vbs and other scripts which run in the WSH environment. Since version 5.6 of WSH, scripts can be [[digital signature|digitally signed]] programmatically using the ''Scripting.Signer'' object in a script itself, provided a valid [[public key certificate|certificate]] is present on the system. Alternatively, the signcode tool from the Platform SDK, which has been extended to support WSH filetypes, may be used at the command line.<ref>{{cite web|url=http://msdn.microsoft.com/en-us/library/ms974604.aspx|title=Providing a Secure eXPerience|first=Tara Meyer (Aquent|last=LLC)|website=msdn.microsoft.com|date=30 June 2006 |access-date=30 April 2018|url-status=live|archive-url=https://web.archive.org/web/20171110234926/https://msdn.microsoft.com/en-us/library/ms974604.aspx|archive-date=10 November 2017}}</ref> By using ''Software Restriction Policies'' introduced with Windows XP, a system may be configured to execute only those scripts which are stored in trusted locations, have a known MD5 hash, or have been digitally signed by a trusted publisher, thus preventing the execution of untrusted scripts.<ref>[http://msdn.microsoft.com/msdnmag/issues/02/05/wsh/ Windows Script Host 5.6 Boasts Windows XP Integration, Security, New Object Model] {{webarchive|url=https://web.archive.org/web/20080218162807/http://msdn.microsoft.com/msdnmag/issues/02/05/wsh/ |date=2008-02-18 }}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)