Re: Hash value not correct in CryptVerifyDetachedMessageSignature
From: Pablo J. Royo (PabloJRoyo_at_discussions.microsoft.com)
Date: 08/13/04
- Next message: Jakub Gwozdz: "Re: Gina: WlxSasNotify during WlxDisplayLockedNotice triggers both WlxWkstaLockedSAS and WlxLoggedOnSAS"
- Previous message: Nathan D. Lee: "Re: GinaStub Development for Windows XP(not getting XP Themes)..."
- In reply to: Tariq: "Re: Hash value not correct in CryptVerifyDetachedMessageSignature"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 13 Aug 2004 07:11:02 -0700
Thank you very much Tarik.
> You might have to reverse the bytes returnd by hashing using CAPI in order
> to verify it with Hash calculated using OpenSSL.
But How do I have access to that bytes?
I suppose, the function I use does an internal hashing of the content pased
to it, so I have no access to that.
The function prototype is
BOOL WINAPI CryptVerifyDetachedMessageSignature(
PCRYPT_VERIFY_MESSAGE_PARA pVerifyPara,
DWORD dwSignerIndex,
const BYTE* pbDetachedSignBlob,
DWORD cbDetachedSignBlob,
DWORD cToBeSigned,
const BYTE* rgpbToBeSigned[],
DWORD* rgcbToBeSigned[],
PCCERT_CONTEXT* ppSignerCert
);
I suppose I must give the clear content to the fucntion, so it can check
its hash is the same contained in the signature passed in
pbDetachedSignBlob.But I could also pass a hash of a clear content already
computed by some othe ways...
Are this rgpbToBeSigned the hash or the clear content ?.
Thanks again.
- Next message: Jakub Gwozdz: "Re: Gina: WlxSasNotify during WlxDisplayLockedNotice triggers both WlxWkstaLockedSAS and WlxLoggedOnSAS"
- Previous message: Nathan D. Lee: "Re: GinaStub Development for Windows XP(not getting XP Themes)..."
- In reply to: Tariq: "Re: Hash value not correct in CryptVerifyDetachedMessageSignature"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|