PowerShell Requires Chilkat v11.7.0+
PowerShell
Authenticode Sign a PowerShell Script (.ps1, .psm1, .psd1)
See more Code Signing Examples
Demonstrates how to Authenticode sign a PowerShell script. PowerShell scripts (.ps1), modules (.psm1) and data files (.psd1) can be signed starting in Chilkat v11.7.0. The signature is appended to the file as a comment block, and the file keeps its text encoding.Chilkat PowerShell Downloads
Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"
$success = $false
# This example requires the Chilkat API to have been previously unlocked.
# See Global Unlock Sample for sample code.
# Signing PowerShell files requires Chilkat v11.7.0 or later.
# The same code signs a script (.ps1), a module (.psm1), or a data file (.psd1).
# Load the code signing certificate. It must have access to its private key.
$cert = New-Object Chilkat.Cert
$success = $cert.LoadPfxFile("C:/someDir/myCodeSigningCert.pfx","pfx password")
if ($success -eq $false) {
$($cert.LastErrorText)
exit
}
# Sign with SHA256, and ask a timestamp authority for a timestamp. A timestamp lets the
# signature continue to validate after the code signing certificate has expired.
#
# {
# "hashAlg": "sha256",
# "timestampToken": {
# "enabled": true,
# "tsaUrl": "http://timestamp.digicert.com",
# "requestTsaCert": true,
# "hashAlg": "sha256"
# }
# }
$json = New-Object Chilkat.JsonObject
$json.UpdateString("hashAlg","sha256")
$json.UpdateBool("timestampToken.enabled",$true)
$json.UpdateString("timestampToken.tsaUrl","http://timestamp.digicert.com")
$json.UpdateBool("timestampToken.requestTsaCert",$true)
$json.UpdateString("timestampToken.hashAlg","sha256")
$scriptPath = "C:/someDir/Deploy.ps1"
$signer = New-Object Chilkat.CodeSign
# The script is modified in place. The signature is appended to the end of the file as a comment block:
#
# # SIG # Begin signature block
# # MIIoKgYJKoZIhvcNAQcCoIIoGzCCKBcCAQExDzANBglghkgBZQMEAgEFADB5Bgor
# # ...
# # SIG # End signature block
#
# The text encoding of the file (UTF-8, UTF-8 with BOM, or UTF-16) is kept.
# If the script is already signed, the new signature block replaces the existing one.
$success = $signer.AddSignature($scriptPath,$cert,$json)
if ($success -eq $false) {
$($signer.LastErrorText)
exit
}
$("Signed the PowerShell script.")
# Verify the signature that was just added.
# Any change made to the script after it is signed, even to a comment, invalidates the signature.
$sigInfo = New-Object Chilkat.JsonObject
$valid = $signer.VerifySignature($scriptPath,$sigInfo)
if ($valid -eq $false) {
$($signer.LastErrorText)
exit
}
$("The signature is valid.")