prijon.net

Create a self signed - code signing certificate

Admin — Wed, 06 Feb 2008 20:19:20 +0000

Using “makecert.exe”, whic is a part of Windows SDK, or download it here.
This tool is suitable for testing purposes only!

To create the root certificate:
Open Windows SDK CMD Shell (or Command Prompt and go to the makecert.exe location)
Run this command
makecert -n “CN=PowerShell Root Certificate” -a sha1 -eku 1.3.6.1.5.5.7.3.3 -r -sv root.pvk root.cer -ss Root -len 1024 -sr localMachine

To create a user certificate (with the private key):
Open Windows SDK CMD Shell (or Command Prompt and go to the makecert.exe location)
Run this command

makecert -pe -n “CN=PowerShell User Certificate” -ss MY -a sha1 -eku 1.3.6.1.5.5.7.3.3 -iv root.pvk -ic root.cer

Note that the number 1.3.6.1.5.5.7.3.3 indicates that a certificate can be used for code signing.

More info for Makecert: http://msdn2.microsoft.com/en-us/library/aa386968(VS.85).aspx

Execute a Powershell script on Windows Vista

Admin — Thu, 24 Jan 2008 21:37:20 +0000

script.ps1 is not digitally signed. The script will not execute on the system. Please see “get-help about_signing” for more details.

To solve the problem, you can just change the Execution policy to “RemoteSigned” with the folowing command (as Administrator):
Set-ExecutionPolicy RemoteSigned - Note that this option is not recomanded!

The more secure way is to digitaly sign the script.

Navigate to the location of your code signing certificate (like “Set-Location cert:\CurrentUser\my\” for Personal certificates).
Type Get-CilldItem to get a list of all certificates in thihs location and copy the Thumbprint of the right certificate.
Set the ”$cert” with the certificate location:

$cert = Get-Childitem -Path cert:\CurrentUser\My\A4309AD8067D6AC70E36B578A890A1EFC3FB -CodeSigningCert

4. Now with the folowing command digitaly sign the file
(ex.: Powershell profile)

Set-AuthenticodeSignature -FilePath C:\…\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 -cert $cert

Create a Powershell profile

Admin — Thu, 24 Jan 2008 20:45:15 +0000

If you want that Powershell remember your aliases (and other commands) like “gh for Get-Help”,
you can create a Powershell profile script, which is automaticali executed at Powershell startup

First test if a profile exist with the folowing command:
test-path $profile
If the resulte is false, use the folowing command to create a new profile
new-item -path $profile -itemtype file -force
Type notepad $profile to edit the pprofile
Now you can write down all yours commands (ex. Set-Alias gh Get-Help)

To view the location of the profile script type $profile