Product: PowerShell Studio 2024 (64 Bit)
Build: v5.8.237
OS: Windows 11.0.22631
PS Version(s): 5.1.22621.1, 7.2.18
I am using a code signing token and when I attempt to package a script when I have overlooked loading the token, PSS continues to package the executable unsigned.
I would much prefer that it fails, otherwise I could end up distributing an executable that I think is code signed when in fact, it isnt.
I do have a post build executable I run that I could modify to perform "Get-AuthenticodeSignature" as a test. Is this the best approach?
Build: v5.8.237
OS: Windows 11.0.22631
PS Version(s): 5.1.22621.1, 7.2.18
I am using a code signing token and when I attempt to package a script when I have overlooked loading the token, PSS continues to package the executable unsigned.
I would much prefer that it fails, otherwise I could end up distributing an executable that I think is code signed when in fact, it isnt.
I do have a post build executable I run that I could modify to perform "Get-AuthenticodeSignature" as a test. Is this the best approach?
Statistics: Posted by owinsloe — Mon Jan 22, 2024 6:35 pm