<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://powershell.com/cs/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>Security</title><link>http://powershell.com/cs/media/g/security/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>Start-ProcessInteractive</title><link>http://powershell.com/cs/media/p/9660.aspx</link><pubDate>Tue, 15 Mar 2011 15:47:58 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:9660</guid><dc:creator>Tobias</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;illustrates how you can use the task scheduler to run a program or script remotely on behalf of someone else.&lt;/p&gt;
&lt;p&gt;Can be used to launch programs remotely visibly, so the logged on user can see and interact with the program you launched.&lt;/p&gt;
&lt;p&gt;Requires Windows Vista/Server 2008 or better, and you need to have local admin privileges on the target machine.&lt;/p&gt;</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.96.60/start_2D00_interactiveV5.ps1" length="2802" type="application/octet-stream" /></item><item><title>Launch PS Script as Scheduled Task Elevated</title><link>http://powershell.com/cs/media/p/8026.aspx</link><pubDate>Fri, 29 Oct 2010 09:05:58 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:8026</guid><dc:creator>Tobias</dc:creator><slash:comments>0</slash:comments><description>creates a scheduled task that runs a PS script in the context of some other user. The script is NTFS protected, and you get back a single line of PS code that any user can execute to run the script elevated. This way, a regular user can safely run a PS script elevated without having to know the admin password.</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.80.26/3bevhghw.ps1" length="3643" type="image/jpeg" /></item><item><title>Encrypt Own Password in Script</title><link>http://powershell.com/cs/media/p/7981.aspx</link><pubDate>Mon, 25 Oct 2010 09:27:39 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:7981</guid><dc:creator>Tobias</dc:creator><slash:comments>0</slash:comments><description>Enter password and username. The script autogenerates a script that encrypts the password with your access token (identity). So when you run the autogenerated script, you receive a valid credential object that you can use to authenticate yourself to remote systems. Other persons will not be able to retrieve the encrypted password. Only the person who encrypted the password can decrypt it. No separate secure key is needed because the secret is your identity.</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.79.81/zp0qajtc.ps1" length="664" type="image/jpeg" /></item><item><title>Encrypt Password in Script</title><link>http://powershell.com/cs/media/p/7968.aspx</link><pubDate>Fri, 22 Oct 2010 14:34:56 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:7968</guid><dc:creator>Tobias</dc:creator><slash:comments>0</slash:comments><description>Asks for a password and a username, then autogenerates a script than contains the password in encrypted form and creates a credential object from it. A &amp;quot;more&amp;quot; secure way of hard-coding passwords into scripts. The password is still not safe, a user could reverse engineer the credential object. The password is however effectively &amp;quot;obfuscated&amp;quot; so a user can no longer easily identify and reuse a hard coded password.</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.79.68/2nlpslni.ps1" length="810" type="image/jpeg" /></item><item><title>Create shares with share permissons</title><link>http://powershell.com/cs/media/p/2535.aspx</link><pubDate>Sun, 17 May 2009 19:52:54 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:2535</guid><dc:creator>Gerry Bammert</dc:creator><slash:comments>2</slash:comments><description>&lt;p&gt;Create one or several shares with share permissions in a domain environment.&lt;/p&gt;</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.25.35/Create_2D00_Shares.ps1" length="6107" type="application/octet-stream" /></item><item><title>Get-HotFix</title><link>http://powershell.com/cs/media/p/2315.aspx</link><pubDate>Tue, 28 Apr 2009 10:49:51 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:2315</guid><dc:creator>Aleksandar</dc:creator><slash:comments>0</slash:comments><description>The Get-HotFix function gets the quick-fix engineering (QFE) updates that have been applied to the local computer or to remote computers and filter those hotfixes named &amp;quot;file 1&amp;quot;. There is Get-HotFix cmdlet in PowerShell V2. This is my attempt to bring similar functionality to V1.</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.23.15/Get_2D00_HotFix_5F00_za-blog-post.ps1" length="1969" type="image/jpeg" /></item><item><title>Read-MBSALogs</title><link>http://powershell.com/cs/media/p/1699.aspx</link><pubDate>Wed, 04 Mar 2009 22:16:02 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:1699</guid><dc:creator>Richard Giles</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;The following script iterates over each file in the directory, parses the file and looks for the count. This information is dynamically entered into an Excel spreadsheet.&lt;/p&gt;
&lt;p&gt;Attributed To: FatBeard&lt;/p&gt;
&lt;p&gt;URL: &lt;a target="_blank" href="http://fatbeards.blogspot.com/2009/01/powershell-mbsa-logs.html"&gt;http://fatbeards.blogspot.com/2009/01/powershell-mbsa-logs.html&lt;/a&gt;&lt;/p&gt;</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.16.99/Read_2D00_MBSALogs.ps1" length="2322" type="application/octet-stream" /></item><item><title>Set-Folderpermission.ps1</title><link>http://powershell.com/cs/media/p/1644.aspx</link><pubDate>Fri, 27 Feb 2009 15:52:07 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:1644</guid><dc:creator>Niklas Goude</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;This script sets the permissions on a folder.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.powershell.nu/2009/02/13/set-folder-permissions-using-a-powershell-script/"&gt;Read 
more about it here &amp;gt;&amp;gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;goude@powershell.nu&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.powershell.nu"&gt;www.powershell.nu&lt;/a&gt;&lt;/p&gt;</description><enclosure url="http://www.powershell.nu/wp-content/uploads/2009/02/setfolderpermission.ps1" length="2939" type="text/plain" /></item><item><title>Change file ownership</title><link>http://powershell.com/cs/media/p/377.aspx</link><pubDate>Tue, 25 Nov 2008 12:10:22 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:377</guid><dc:creator>Tobias Weltner</dc:creator><slash:comments>1</slash:comments><description>Demonstrates how to assign a new owner to a file by manipulating the file security descriptor. Assigning a new owner requires Admin privileges.</description></item><item><title>Load persisted password from disk and launch process with alternate credentials</title><link>http://powershell.com/cs/media/p/249.aspx</link><pubDate>Sat, 15 Nov 2008 07:49:33 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:249</guid><dc:creator>Tobias Weltner</dc:creator><slash:comments>1</slash:comments><description>This script shows how to load a previously persisted secret password from disk, then convert it to a securestring and a PSCredential object. This can be used to authenticate against a number of services. In the example, the loaded password is used to launch a process with alternate credentials. Note that only the person which persisted the secret password can retrieve it.</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.02.49/loadpassword.ps1" length="698" type="image/jpeg" /></item><item><title>Encrypt a password and save it to disk</title><link>http://powershell.com/cs/media/p/248.aspx</link><pubDate>Sat, 15 Nov 2008 07:45:07 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:248</guid><dc:creator>Tobias Weltner</dc:creator><slash:comments>1</slash:comments><description>encrypts a password with the current users identity and saves it to disk as file. The password can then be re-loaded from other scripts and used for authentication but only the user who originally saved the password can decrypt. To enable more than one person to decrypt, use the -key parameter while converting the string to a securestring.</description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.02.48/savepassword1.PS1" length="403" type="image/jpeg" /></item><item><title>Check for Administrative Privileges</title><link>http://powershell.com/cs/media/p/200.aspx</link><pubDate>Mon, 10 Nov 2008 18:14:12 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:200</guid><dc:creator>Tobias Weltner</dc:creator><slash:comments>0</slash:comments><description>Function isAdmin() checks whether a script runs with full Admin privileges. </description><enclosure url="http://powershell.com/cs/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.02.00/isAdmin.PS1" length="284" type="image/jpeg" /></item></channel></rss>
