[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-cryptoapi
Subject:    Re: Default key container
From:       Peter Batim <pbatim () HOTMAIL ! COM>
Date:       2001-05-28 7:40:22
[Download RAW message or body]


Hello Carlos,

I would like to add a comment..

CryptoAPI has big number of various flags - some of them are not described
in any publicly available documentation (e.g. MSDN Library).
How about defining (and documenting of course;) new flags that would help
solve the problem (I mean managing default containers in any removable
token)?

For example:
CRYPT_DEFAULTKEYSET would create default keyset when used with
CRYPT_NEWKEYSET in CryptAcquireContext call.

PP_DEFAULTKESEY could be used to get/set provider’s default keyset name by
CryptGetProvParam/CryptSetProvParam calls.

What do you think about that? Makes it sense?

Thanks,

-pb-


-----Original Message-----
Richard is correct an application calling CryptAcquireContext should
never use NULL for the container unless they are using the
CRYPT_VERIFYCONTEXT flag.

In your case, you are writing the smartcard CSP so the situation is not
quite the same.  You want to have more than one container on the
smartcard for different uses.

The problem is, how does your CSP know what container to use and the
unfortunate answer is you really can't know.

If anyone else would like to add a comment please do so.

Carlos


_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

----------------------------------------------------------------
Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:CryptoAPI-signoff-request@DISCUSS.MICROSOFT.COM

[prev in list] [next in list] [prev in thread] [next in thread]