|
I have problem on ms windows server 2003 with hotfix KB 938397. I try sign with certificate which is in old sha1 format. If i sign with SHA1 everything go ok. But if i try sign with SHA256 it produce exception with message "Unable to access the private key (0x80092004)". Where can be problem. If i try it on my MS Vista it works OK. |
|
It turned out you were using The reason for this is that different CryptoAPI calls have to be done for SHA-2 because a different CryptoAPI provider than the one associated with the certificate's provate key has to be used. We might try to address this in one of the future releases. In the meantime, if you need to use SHA-2, please make sure to initialize the
|
|
Windows Server 2003 with KB938397 hotfix is not sufficiently tested platform and we are not entirely sure whether the hotfix is supposed to make signature generation work - there is a ver similar KB968730 hotfix that is newer and addresses a similar problem, so installing it first might be a good idea. To help us in analyzing this, could you please run the following program and let us know what output it displays?
We will try to test this ourselves as well in the next few days. I'am so sorry, but i'am ill. Ill try it maybye tomorrow.
(23 Feb '10, 16:14)
Daniel Spurny
Result from your code: Accessible: True HardwareDevice: False KeyContainerName: {CFCFBE30-6919-48E1-B96B-671826A89927} KeyNumber: Exchange MachineKeyStore: False Protected: False ProviderName: Microsoft Enhanced Cryptographic Provider v1.0 ProviderType: 1 UniqueKeyContainerName: 56e8c5d2dd4118ee7b9a885912117c35_131747bf-ce21-4b0c-baaf-f2fdacc6f8ef
(24 Feb '10, 10:38)
Daniel Spurny
Thanks! Nothing extraordinary in there. We modified our code to use a different approach for accessing private keys. I will send you a link to the current build shortly to our e-mail address.
(25 Feb '10, 16:52)
Lukas Pokorny ♦♦
|