Menu
I'm currently porting a piece of code written in .NET 3.5 to 2.0. At some point in the code (heavy load) the AesManaged class is being used, are there any performance gains from this implementation compared to RijndaelManaged, and should there be any risk when changing from AesManaged to RijndaelManaged concerning heavy load?
481
The RijndaelManaged class is not FIPS certified at all. The AesCryptoServiceProvider class (which uses the Rijndael algorithm for block encryption) uses the Windows' Cryptographic Service Provider API.
The Rijndael and RijndaelManaged types are marked as obsolete, starting in . NET 6.
AES is a variant of Rijndael, with a fixed block size of 128 bits, and a key size of 128, 192, or 256 bits. By contrast, Rijndael per se is specified with block and key sizes that may be any multiple of 32 bits, with a minimum of 128 and a maximum of 256 bits.
The Rijndael algorithm, in conjunction with safe configuration values (i.e. AES ), is very robust and secure. The only true measure of an encryption algorithm's security is its consistent and long-lived exposure to cryptanalysis and attempts to defeat it by many cryptographers.
Actually there is one very subtle difference: Block size.
Rijndael supports block sizes of 128, 192, 256 bits. AES supports only 128 bit block sizes.
56
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
