<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>PowerShell’s Security Guiding Principles</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx</link><description>One of most common issues we face with PowerShell comes from users or ISVs misunderstanding PowerShell’s security guiding principles. At a high-level, it seems to all make sense – execution policies help ensure that you only run scripts that you trust</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: PowerShell’s Security Guiding Principles</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx#8970720</link><pubDate>Wed, 01 Oct 2008 00:11:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970720</guid><dc:creator>martin.zugec</dc:creator><description>&lt;p&gt;Hi Lee,&lt;/p&gt;
&lt;p&gt;-ExecutionPolicy Bypass is supported only in v2??&lt;/p&gt;
&lt;p&gt;This could solve a huge problem we have. Running PS scripts in w2k8 environment is not very easy and there are already people asking if we could just use cmd batches instead (PS from SCCM). I understand that Unrestricted will ask you if you wanted to run downloaded script - however you got the same if you run script from network share in secured environment (UNC paths are automatically considered unsecured) :(&lt;/p&gt;
&lt;p&gt;Martin&lt;/p&gt;</description></item><item><title>re: PowerShell’s Security Guiding Principles</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx#8970753</link><pubDate>Wed, 01 Oct 2008 00:37:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970753</guid><dc:creator>PowerShellTeam</dc:creator><description>&lt;p&gt;Correct. It is only supported in V2.&lt;/p&gt;
&lt;p&gt;Some machines are configured to treat UNC paths as the same security zone as the internet (as opposed to the intranet.) This is Internet Explorer's &amp;quot;Enhanced Security Configuration.&amp;quot; In this case, PowerShell responds the same as the Explorer Shell when it runs scripts from a UNC path: “While scripts from the internet can be useful, this script can potentially harm your computer. Do you want to run &amp;lt;script&amp;gt;?” &lt;/p&gt;
&lt;p&gt;One way to fix this is by adding the source server to Internet Explorer’s Trusted Sites, or changing the “UncAsIntranet” configuration property (&lt;a rel="nofollow" target="_new" href="http://technet.microsoft.com/en-us/library/bb457150.aspx"&gt;http://technet.microsoft.com/en-us/library/bb457150.aspx&lt;/a&gt;). This is also covered on page 341 of the (my) PowerShell Cookbook. &lt;/p&gt;
&lt;p&gt;Lee&lt;/p&gt;
</description></item><item><title>re: PowerShell’s Security Guiding Principles</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx#8970852</link><pubDate>Wed, 01 Oct 2008 02:02:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970852</guid><dc:creator>Frank-Peter Schultze</dc:creator><description>&lt;p&gt;#&lt;/p&gt;
&lt;p&gt;# Add a 'fileserver' to the trusted sites&lt;/p&gt;
&lt;p&gt;#&lt;/p&gt;
&lt;p&gt;$RegPath = &amp;quot;HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\fileserver&amp;quot;&lt;/p&gt;
&lt;p&gt;$RegValue = &amp;quot;file&amp;quot;&lt;/p&gt;
&lt;p&gt;$RegType = &amp;quot;DWord&amp;quot;&lt;/p&gt;
&lt;p&gt;$RegData = 2&lt;/p&gt;
&lt;p&gt;New-Item -Path $RegPath&lt;/p&gt;
&lt;p&gt;New-ItemProperty -Path $RegPath -Name $RegValue -PropertyType $RegType -Value $RegData&lt;/p&gt;
&lt;p&gt;#&lt;/p&gt;
&lt;p&gt;#&lt;/p&gt;
&lt;p&gt;#&lt;/p&gt;</description></item><item><title>re: PowerShell’s Security Guiding Principles</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx#8971627</link><pubDate>Wed, 01 Oct 2008 17:06:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8971627</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;New tagline:&lt;/p&gt;
&lt;p&gt;&amp;quot;Ultimately, if bad code has the ability to run this code, it already has control of the machine.&amp;quot;&lt;/p&gt;</description></item><item><title>Confusion about PowerShell Script Signing</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx#9484596</link><pubDate>Tue, 17 Mar 2009 22:49:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9484596</guid><dc:creator>James Kovacs</dc:creator><description>&lt;p&gt;I’ve been having fun writing about my adventures in PowerShell. I would like to thank everyone for their&lt;/p&gt;
</description></item><item><title>Confusion about PowerShell Script Signing</title><link>http://blogs.msdn.com/powershell/archive/2008/09/30/powershell-s-security-guiding-principles.aspx#9487026</link><pubDate>Wed, 18 Mar 2009 17:56:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9487026</guid><dc:creator>Community Blogs</dc:creator><description>&lt;p&gt;I’ve been having fun writing about my adventures in PowerShell. I would like to thank everyone for their&lt;/p&gt;
</description></item></channel></rss>