Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 588548" data-attributes="member: 32260"><p><strong>I have done some research about signed scripts.</strong></p><p></p><p><em><strong>Windows Script Host</strong></em> JS,JSE,VBS,VBE,WSF,WSH scripts:</p><p>Registry settings for running only signed scripts (the second key is for 32Bit Windows Script Host in 64Bit system):</p><p>***********************************************************************</p><p>Windows Registry Editor Version 5.00</p><p></p><p>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings]</p><p>"UseWINSAFER"="0"</p><p>"Enabled"=dword:00000001</p><p>"TrustPolicy"=dword:00000002</p><p></p><p>HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Script Host\Settings</p><p>"UseWINSAFER"="0"</p><p>"Enabled"=dword:00000001</p><p>"TrustPolicy"=dword:00000002</p><p>***********************************************************************</p><p>In Windows 64Bit there are two Windows Script Hosts (32Bit and 64Bit).</p><p>If UseWINSAFER is set to 1 (default value), Windows will ignore the TrustPolicy setting.</p><p>If UseWINSAFER is set to 0 Windows Script Host will not call into Software Restriction Policies to apply software restriction policies to scripts that are being run. So, the above scripts can be blocked only by extension like for example PowerShell scripts (no big issue for home users).</p><p>All system 'Windows Script Host' scripts are not signed (gatherNetworkInfo.vbs , slmgr.vbs, SyncAppvPublishingServer.vbs, winrm.vbs, manage-bde.wsf).</p><p>Most scripts (maybe all) from Microsoft Script Center (<a href="https://gallery.technet.microsoft.com/scriptcenter/" target="_blank">Powershell, VB Script, SQL and JavaScript - TechNet IT Pro's and Scripting Guys</a>) are not signed.</p><p>The local scripts can be signed by hash in SRP.</p><p>I think that an advantage of using signed scripts may be evident only in enterprises.</p><p></p><p><strong><em>PowerShell Scripts.</em></strong></p><p>Registry settings for running only signed scripts (the second key is for 32Bit Powershell in 64Bit system):</p><p>************************************************************************************</p><p>Windows Registry Editor Version 5.00</p><p></p><p>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell]</p><p>"ExecutionPolicy"="AllSigned"</p><p></p><p>[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell]</p><p>"ExecutionPolicy"="AllSigned"</p><p>************************************************************************************</p><p>In Windows 64Bit there are two PowerShell Hosts (32Bit and 64Bit).</p><p>All numerous (c:\Windows\diagnostics\) system PowerShell scripts are signed.</p><p>Most scripts from Microsoft Script Center (<a href="https://gallery.technet.microsoft.com/scriptcenter/" target="_blank">Powershell, VB Script, SQL and JavaScript - TechNet IT Pro's and Scripting Guys</a>) are not signed.</p><p>The local scripts can be signed by hash in SRP.</p><p>There's an advantage of using signed scripts, while doing system maintenance.</p><p>Which is better: RemoteSigned or AllSigned, that is the question.</p><p>RemoteSigned blocks only unsigned scripts downloaded from the Internet (added 'Mark of the Web'), and does not touch local scripts.</p><p></p><p>Any ideas would be welcomed.</p><p></p><p>@WindowsSecurity, thanks for pointing out the potential usability of signed scripts option.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 588548, member: 32260"] [B]I have done some research about signed scripts.[/B] [I][B]Windows Script Host[/B][/I] JS,JSE,VBS,VBE,WSF,WSH scripts: Registry settings for running only signed scripts (the second key is for 32Bit Windows Script Host in 64Bit system): *********************************************************************** Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings] "UseWINSAFER"="0" "Enabled"=dword:00000001 "TrustPolicy"=dword:00000002 HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Script Host\Settings "UseWINSAFER"="0" "Enabled"=dword:00000001 "TrustPolicy"=dword:00000002 *********************************************************************** In Windows 64Bit there are two Windows Script Hosts (32Bit and 64Bit). If UseWINSAFER is set to 1 (default value), Windows will ignore the TrustPolicy setting. If UseWINSAFER is set to 0 Windows Script Host will not call into Software Restriction Policies to apply software restriction policies to scripts that are being run. So, the above scripts can be blocked only by extension like for example PowerShell scripts (no big issue for home users). All system 'Windows Script Host' scripts are not signed (gatherNetworkInfo.vbs , slmgr.vbs, SyncAppvPublishingServer.vbs, winrm.vbs, manage-bde.wsf). Most scripts (maybe all) from Microsoft Script Center ([URL='https://gallery.technet.microsoft.com/scriptcenter/']Powershell, VB Script, SQL and JavaScript - TechNet IT Pro's and Scripting Guys[/URL]) are not signed. The local scripts can be signed by hash in SRP. I think that an advantage of using signed scripts may be evident only in enterprises. [B][I]PowerShell Scripts.[/I][/B] Registry settings for running only signed scripts (the second key is for 32Bit Powershell in 64Bit system): ************************************************************************************ Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell] "ExecutionPolicy"="AllSigned" [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell] "ExecutionPolicy"="AllSigned" ************************************************************************************ In Windows 64Bit there are two PowerShell Hosts (32Bit and 64Bit). All numerous (c:\Windows\diagnostics\) system PowerShell scripts are signed. Most scripts from Microsoft Script Center ([URL='https://gallery.technet.microsoft.com/scriptcenter/']Powershell, VB Script, SQL and JavaScript - TechNet IT Pro's and Scripting Guys[/URL]) are not signed. The local scripts can be signed by hash in SRP. There's an advantage of using signed scripts, while doing system maintenance. Which is better: RemoteSigned or AllSigned, that is the question. RemoteSigned blocks only unsigned scripts downloaded from the Internet (added 'Mark of the Web'), and does not touch local scripts. Any ideas would be welcomed. @WindowsSecurity, thanks for pointing out the potential usability of signed scripts option. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
