Hi guys:
I am surprised (actually disappointed) to see RSACryptoServiceProvider (&
some others like TripleDES) class(es) in WSE2.0
(Microsoft.Web.Services2.Security.Cryptography ).
Why would they be needed ?. These classes are part of .NET Framework.... I
did some comparison and WSE one's does not extend the functionality (at
least not mentioned in documentation) of
one in core .NET framework
if anyone from MSFT could throw a light on these it would be really great.
Regards
Kapil
casey chesnut - 28 Jun 2004 01:52 GMT
i did see some differences when i was looking at TripleDES in particular.
WSE adds TripleDESKeyExchangeFormatter and TripleDESEncryptionFormatter.
TripleDESKeyExchangeFormatter is much different then the
TripleDESCryptoServiceProvider of .NET.
it uses a standardized IV, and has a couple layers of encyrption.
and TripleDESEncryptionFormatter provides Encrypt and Decrypt methods,
instead of having to use CryptoStreams.
so i definitely think both of those make sense being in WSE 2.0.
Thanks,
casey
http://www.brains-N-brawn.com
> Hi guys:
>
[quoted text clipped - 10 lines]
> Regards
> Kapil
Kapil Sachdeva - 28 Jun 2004 21:45 GMT
Thanks casey .... i agree for tripleDES ... but for RSACryptoServiceProvider
did you see any difference
Regards & Thanks
Kapil
> i did see some differences when i was looking at TripleDES in particular.
> WSE adds TripleDESKeyExchangeFormatter and TripleDESEncryptionFormatter.
[quoted text clipped - 22 lines]
> > Regards
> > Kapil
casey chesnut - 28 Jun 2004 23:21 GMT
from a quick look, there seems to be less difference with that one.
all i see is some slightly different methods for encrypting and signing.
the main thing is the constructor overloads supporting IntPtr's to a
CertificateContext.
that will certainly be useful for working with X509 certs.
Thanks,
casey
http://www.brains-N-brawn.com
> Thanks casey .... i agree for tripleDES ... but for RSACryptoServiceProvider
> did you see any difference
[quoted text clipped - 31 lines]
> > > Regards
> > > Kapil
Byron Kim - 01 Jul 2004 00:49 GMT
System RSACryptoService Provider has a well-known long delay prolbem for a
certain certificate..
If the ceritificate does not have provider information(e.g. MakeCert
generated Certificate), WSE ask to the system go find it. It talkes very
long time.
So, WSE team developed for fixing this issue.
thanks
Byron KIM
> Hi guys:
>
[quoted text clipped - 10 lines]
> Regards
> Kapil