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

List:       ms-cryptoapi
Subject:    Re: CALG_SSL3_SHAMD5
From:       "John Banes (Exchange)" <jbanes () EXCHANGE ! MICROSOFT ! COM>
Date:       1999-11-29 19:31:40
[Download RAW message or body]


The CALG_SSL3_SHAMD5 hash type must be implemented by all CSPs that hope to
be used for SSL client authentication. This includes CSPs of type
PROV_RSA_FULL and PROV_RSA_SIGN as well as PROV_RSA_SCHANNEL.

CSPs implement the CPSignHash function by taking the 36-byte hash value
(obtained from CPSetHashParam) and signing it normally. The only difference
is that there is no OID placed in the signature block, just the hash value
and a bunch of FFs.

-John


-----Original Message-----
From: Marcus Lee [mailto:cklee@CSIS.HKU.HK]
Sent: Wednesday, November 24, 1999 7:43 PM
To: CryptoAPI@DISCUSS.MICROSOFT.COM
Subject: CALG_SSL3_SHAMD5


Hi,

It is said that CSPs for PROV_RSA_SCHANNEL must support the
CALG_SSL3_SHAMD5 hash that is compatible with the Microsoft Base
Cryptographic Provider. However, what are the actual functionality that
must be implemented? If that hash is signed with an RSA private key,
what OID should be place in it? It seems that
http://msdn.microsoft.com/library/psdk/cryptcsp/cspref_8jdx.htm does not
contain sufficient information.

Regards,
ML

----------------------------------------------------------------
Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
contains important info including how to unsubscribe.  Save time, search
the archives at http://discuss.microsoft.com/archives/index.html

----------------------------------------------------------------
Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
contains important info including how to unsubscribe.  Save time, search
the archives at http://discuss.microsoft.com/archives/index.html

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