That's probably the best bet. The .NET framework calls down into the
unmanaged CryptoAPI for its 3DES implementation, so you can't even use
Reflector to see anything useful.
I'm curious why this is needed though.
Joe K.

Signature
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
> Hello!
> You wrote on Mon, 25 Feb 2008 08:27:02 -0800:
[quoted text clipped - 11 lines]
> http://www.SecureBlackbox.com - the comprehensive component suite for
> network security
Jesse Houwing - 25 Feb 2008 19:39 GMT
Hello Joe,
> That's probably the best bet. The .NET framework calls down into the
> unmanaged CryptoAPI for its 3DES implementation, so you can't even use
> Reflector to see anything useful.
>
> I'm curious why this is needed though.
I guess it wouldn't be needed, but the CryptoAPI is a well known API which
is certified by a number of government organisations. It was probably easier
to re-use it as it's guaranteed to be available on any Windows PC.
--
Jesse Houwing
jesse.houwing at sogeti.nl
Joe Kaplan - 25 Feb 2008 20:15 GMT
If you just want to be sure you are using the CryptoAPI for 3DES, then using
the TripleDESCryptoServiceProvider class should take care of you.
Joe K.

Signature
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
> Hello Joe,
>
[quoted text clipped - 11 lines]
> Jesse Houwing
> jesse.houwing at sogeti.nl