Error when code signing VBS script

Post by **dlethe** » Wed Feb 14, 2007 2:17 am

I can't get primalscript to sign a VBS script. The error message is "Could not load the specified certificate".

I am using a verisign-generated code signing cert. As primalscript doesn't like .SPC and .PVK files, I used the standard microsoft utility pvkimprt to incorporate both keys into a .pfx file. The certificate has been imported into my certificate store, and it doesn't show any errors, and the certificate certainly hasn't expired.

If I leave the tools->options->wsh certificate field blank, then it says I must enter the .PFX file before signing, so at least I know it is trying to look at this file.

I also imported the certificate into my default store.

My development PC is Windows XP 64, is that a problem?

Post by **jhicks** » Wed Feb 14, 2007 4:01 am

Under Options - Script Settings - Script Security, when you click View Certificates do you see your certificate under the Personal tab? The certificate needs to be installed in the personal or user store.

Post by **dlethe** » Wed Feb 14, 2007 5:20 am

Yes ... It reports under Personal
Issued To: SANtools, Inc.
Issued BY: Verisign Class 3 Code Signing
Experiation date 9/13/2007
Friendly Name <None>
Nothing unexpected in the Genera/Details area if I inspect it, other than it says I have a private key that corresponds to this certificate.
The Certification Path is
Verisign Class 3 Public Primary CA -> Verisign Class 3 Code Signing 2004 CA -> SANtools, Inc.

Certificate Status reports: "This certificate is OK"

Post by **jhicks** » Wed Feb 14, 2007 5:37 am

Under Options, where it says Certificate, type in SANtools, Inc. click OK and then try signing a script.

Post by **Alexander Riedel** » Wed Feb 14, 2007 5:40 am

PrimalScript uses Microsoft's Script Signer component to sign scripts. It is not impossible that this simply does not work under a 64bit OS.

Try to run the script used in this article:

http://msdn.microsoft.com/library/defau ... 2a262e.asp

Alex

Post by **dlethe** » Wed Feb 14, 2007 6:09 am

No luck, but hopefully problem is with input parameters.
I stripped it down to a 2-line VBS script called TestSigner.VBS

If I enter "cscript TestSigner.VBS" using code below then it works fine on my WinXP64 system.

Set objSigner = WScript.CreateObject("Scripting.Signer")objSigner.SignFile "C:ScratchScriptTosign.vbs", "SANtools, Inc.", "my"
So this points to some incompatibility with the .PFX file ? When I used the MSFT utility to build a PFX cert out of my .SPC / .PVK files it did give me a few choices. Do you have specifics of what responses I should say?
Otherwise, any way to just read it out of the certificate store?

Post by **Alexander Riedel** » Wed Feb 14, 2007 6:15 am

Does the script still work when you leave the last parameter off?

Set objSigner = WScript.CreateObject("Scripting.Signer")objSigner.SignFile "C:ScratchScriptTosign.vbs", "SANtools, Inc."

Post by **dlethe** » Wed Feb 14, 2007 6:26 am

Yes, it works. Not only that, but if I truncate "SANtools, Inc." to just "SANtools" then it works. (If I remove this parameter completely, then I get error msg about wrong number of parameters.

Post by **dlethe** » Wed Feb 14, 2007 6:33 am

Re:

If I just enter "SANtools, Inc." as certificate name in tools->options, then it gives me the error message below when I attempt to sign it via PrimalScript

An exception occured when signing the script".
dlethe2007-02-14 14:35:03

Post by **jhicks** » Wed Feb 14, 2007 7:01 am

So if "SANtools" works with the script signer object, then use that name as the certificate.

SAPIEN Technologies