CSP FuncVerifyImage issue on Vista + IE

Hi all. Our CSP loads a DLL at runtime and verifies its signature with
the following piece of code:

if ( ! pVTable->FuncVerifyImage(szDllName, NULL) ) {
ok = FALSE;
goto endCPAcquireContext;

}

Where szDllName is the absolute path to the DLL. This works ok on
Windows XP.

In Vista, this piece of code works fine when CSP is called from
command line (it passes also CSP Test Suite). However when loaded from
Internet Explorer, this peace of code is not working.

Is there any issue related with IE and this function pointer?

When kernel debugger is attached to the machine all works fine (i
supose because of signature verification is not done).

Thanks in advance :-)

.

Relevant Pages

  • Re: how can I sign a CSP dll that Written By Myself?
    ... kernel debugger to use the CSP without a signature from ... > I am in China, I download CSPDK, I find cspsign.exe, I use> it to Sign my csp dll, but when I test it use TESTCSP.exe,> when test function CryptAcquireContext, always return> error 0x80090006, that meaning "The provider DLL signature> could not be verified. ...
    (microsoft.public.security)
  • Re: Custom CSP
    ... A valid CSP signature is 136 bytes long. ... The special internal resource has 8 bytes of header information, ... Link the DLL using the ...
    (microsoft.public.platformsdk.security)
  • RE: questions about CSP signature resource
    ... Look for the sample csp.rc and csp.sig in the CSPDK ... Microsoft will update the resource in your dll with the signature ...
    (microsoft.public.platformsdk.security)
  • Re: Custom CSP - Bad Signature Error
    ... For Windows 98, the signature of the CSP must be in the registry, and must ... Now to distribute your CSP to other systems, copy both the newly built .DLL ...
    (microsoft.public.platformsdk.security)
  • RE: Sign and Verify with Different CSPs
    ... Unlike an RSA signature, which is a BIG NUMBER - and, hence, byte order is ... the purpose of the program was to test my CSP. ... What still confuses me is that the hash my CSP produces is also in big ... As for the public key: when you use CAPI to export the public key, ...
    (microsoft.public.platformsdk.security)