Re: Usage of CRYPT_VERIFYCONTEXT with Smart Cards
From: Skybird Le (skybird_lgf_at_sina.com)
Date: 09/27/03
- Next message: Skybird Le: "questions with CryptImportKey and CryptExportKey"
- Previous message: Eric Perlin [MS]: "Re: Help with CTRL+ALT+DEL"
- In reply to: Milton Kuo: "Usage of CRYPT_VERIFYCONTEXT with Smart Cards"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 27 Sep 2003 11:50:50 +0800
yes, there are more difference between MSDN and other documents of MS.
The pszContainer can be NULL or NON-NULL when dwFlags is set to
CRYPTO_VERIFYCONTEXT in CryptAcquireContext.
If pszContainer is NULL , the csp can operate without your smart card,
application can only acquire the usual information, such as it's
capabilities. If pszContainer is non-NULL, the csp can access to public key
portion of persistent public/private key pair on smart card.
I don't know when MS can bring them to same , i hope soon.
"Milton Kuo" <milton.kuo@microsoft.com> > There is a discrepancy between the
Platform SDK and the CSPDK in how
> CRYPT_VERIFYCONTEXT is used in calls to CryptAcquireContext.
Specifically,
> the PSDK states that pszContainer must be NULL if the CRYPT_VERIFYCONTEXT
> flag is set. However, the CSPDK states that pszContainer can be non-NULL
if
> CRYPT_VERIFYCONTEXT is set.
>
> Which of the two documents, if any :), is correct? Also, if the CSPDK is
> correct, when can we expect to see the information in the CSPDK merged
into
> the PSDK?
>
> Thanks,
> Milton
>
>
- Next message: Skybird Le: "questions with CryptImportKey and CryptExportKey"
- Previous message: Eric Perlin [MS]: "Re: Help with CTRL+ALT+DEL"
- In reply to: Milton Kuo: "Usage of CRYPT_VERIFYCONTEXT with Smart Cards"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
