SignedCms in VS.2005 is very slow, signed data is not compatible with CAPICOM 2

Hello, Did some body used VS 2005(c#) to sign data or verify signature functions ?
I tried sign a data and verify signature sample on MSDN (Signing a Message by One Signer ), it seems this sample is very slow, I used CAPICOM SignedData function to sign 10M string, it used 1 second on my computer, but SignedCms (convert to byte[]), it used 29 seconds.
also the signature I get from this function can not be verified (convert to base64 string) by CAPICOM. If I used CAPICOM signedData sign some data, SignedCms.CheckSignature can not verify signature from CAPICOM.

It seems that EnvolopedCms worked very good with CAPICOM, results are compatible.

[694 byte] By [jimmyshu] at [2008-2-7]
# 1
Jim, we'd need more data to accurately diagnose this issue, I've never heard of it before. Feel free to contact me directly: kitg@microsoft.com

Kit

KitG at 2007-9-8 > top of Msdn Tech,.NET Development,Common Language Runtime...
# 2

capicom is bad, because it is not compatible with cryptoapi and .NET 2.x. And capicom is'nt able to support certificates on smart cards. Only the first certificate of the card is used. So be careful in using capicom.

Klaus-Dieter Brinkmann

Klaus-Dieter at 2007-9-8 > top of Msdn Tech,.NET Development,Common Language Runtime...

.NET Development

Site Classified