Thursday, 19 September 2013

Signed powershell script not signed after source control

Signed powershell script not signed after source control

I'm trying to set up some powershell build scripts. I've got a self-signed
certificate that I can use to sign the script and get it to run with
AllSigned. The problem is, this doesn't carry across our scm (git).
Whenever I try to clone and run the script, or change it and revert, I get
the error that the file is unsigned.
File <> cannot be loaded. The file <> is not digitally signed. The script
will not execute on the system. ...
If I re-sign the script, the signature block changes and I can run it again.
Is there any way to either preserve the signing?

No comments:

Post a Comment