Relationship of MS cryptoAPI and PKCS #11

From: Lock (lhunyi@yahoo.com.sg)
Date: 02/07/03 

From: "Lock" <lhunyi@yahoo.com.sg>
Date: Fri, 7 Feb 2003 00:54:03 -0800

RSA has set a standard for CryptoAPI under PKCS #11. Does
MS CryptoAPI follow this standard? If so does it mean that
all the function mention in PKCS #11 is in MS CryptoAPI.
If not, what MS CryptoAPI standard is following and how is
it related to RSA PKCS #11.

Relevant Pages

  • Re: How "strong" are CryptoAPI RSA keypairs
    ... > specifically how the 2 RSA primes are derived in CryptoAPI implementation. ... >> Kelvin Yiu [MSFT] ...
    (microsoft.public.security)
  • Re: Sign w/ BSafe; Verify w/ MS Crypto; Error: Invalid Signature
    ... > Most of the standard CMS/PKCS#7 signature structures generated by ... handling in CryptoAPI, but anyway I don't understand, what kind of issue ... which specify how to read or write this or that structure or data ...
    (microsoft.public.platformsdk.security)
  • .net and CryptoAPI key information
    ... The following information may be useful to those with some CryptoAPI ... generates new RSA public/private transient key-pair each time invoked. ... constructor, a random key container name, prepended with "CLR" is persisted to ... The term "public key blob" is used a bit loosely in docs. ...
    (microsoft.public.platformsdk.security)
  • .NET and CryptoAPI key information
    ... The following information may be useful to those with some CryptoAPI ... generates new RSA public/private transient key-pair each time invoked. ... constructor, a random key container name, prepended with "CLR" is persisted to ... The term "public key blob" is used a bit loosely in docs. ...
    (microsoft.public.platformsdk.security)
  • .net and CryptoAPI key information
    ... The following information may be useful to those with some CryptoAPI ... generates new RSA public/private transient key-pair each time invoked. ... constructor, a random key container name, prepended with "CLR" is persisted to ... The term "public key blob" is used a bit loosely in docs. ...
    (microsoft.public.dotnet.security)