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
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. -- Joe Kaplan-MS MVP Directory Services Programming Co-author of "The .NET Developer's Guide to Directory Services Programming" http://www.directoryprogramming.net -- "Jesse Houwing" <jesse.houwing@newsgroup.nospam> wrote in message news:21effc9043ec78ca46059b7214d8@news.microsoft.com... > 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 > >
