I am now experiencing the same problem, and wondered if anyone can shed any light on this?
Basically we’re building and signing code using an ‘ant script’ and I get the following error:
SignTool Error: ISignedCode::Sign returned error: 0x80092006
[exec] No provider was specified for the store or object.
[exec] SignTool Error: An error occurred while attempting to sign: drivername.sys
[exec] Issued by: VeriSign Class 3 Code Signing 2004 CA
[exec] Expires: 26/06/2008 00:59:59
[exec] SHA1 hash: E9577972CB986CADE324AF3AF8FE34D4E1CXXXXX
(I’ve changed the driver name and SHA1 Hash, because it seems the right thing to do in a public forum!)
I should add that this particular machine has been able to build and sign this same code in the past without any issues. I’m not aware of any environmental changes having occured since the last successful build.
The URL below does not seem to work. In any case, your best bet is to channel Gianluca. He hasn’t been around much recently, but
he knows a lot more about code signing that probably would like to.
I am now experiencing the same problem, and wondered if anyone can shed any light on this?
Basically we’re building and signing code using an ‘ant script’ and I get the following error:
SignTool Error: ISignedCode::Sign returned error: 0x80092006
[exec] No provider was specified for the store or object.
[exec] SignTool Error: An error occurred while attempting to sign: drivername.sys
[exec] Issued by: VeriSign Class 3 Code Signing 2004 CA
[exec] Expires: 26/06/2008 00:59:59
[exec] SHA1 hash: E9577972CB986CADE324AF3AF8FE34D4E1CXXXXX
(I’ve changed the driver name and SHA1 Hash, because it seems the right thing to do in a public forum!)
I should add that this particular machine has been able to build and sign this same code in the past without any issues. I’m not aware of any environmental changes having occured since the last successful build.
(2) Found with “signtool sign /?”:
/f Specify the signing cert in a file. If this file is a PFX with a password, the password may be supplied with the “/p” option. If the file does not contain private keys, use the “/csp” and “/k” options to specify the CSP and container name of the private key.
=> CSP = Cryptographic Service Provider
(3) This is our signtool invocation (added line breaks for legibility):
Note that both certicifates are already loaded in the cert store. The /ac is the Microsoft recommendation to ensure cross-certification.
> I should add that this particular machine has been able to build and > sign this same code in the past without any issues. I’m not aware of > any environmental changes having occured since the last successful > build.
Did any certificate expire in the mean time? Not only yours, but also the cross-certificate need to be checked.