<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx</link><description>When you need to write managed code that encrypts or decrypts data according to the AES standard, most people just plug the RijndaelManaged class in and go on their way. After all, Rijndael was the winner of the NIST competition to select the algorithm</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#814101</link><pubDate>Tue, 10 Oct 2006 23:02:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:814101</guid><dc:creator>Peter Ritchie</dc:creator><description>&lt;p&gt;You block size for AES-256 in your table should be 128 not 228. &amp;nbsp;Feel free to delete this if it no longer applies...&lt;/p&gt;
</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#814331</link><pubDate>Wed, 11 Oct 2006 00:01:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:814331</guid><dc:creator>shawnfa</dc:creator><description>&lt;p&gt;Yep, stupid typoo. &amp;nbsp;Thanks, I've fixed it now!&lt;/p&gt;
&lt;p&gt;-Shawn&lt;/p&gt;
</description></item><item><title>re: The Differences Between Rijndael and AES (FIPS compliance?)</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#822580</link><pubDate>Fri, 13 Oct 2006 21:04:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:822580</guid><dc:creator>David</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I'm curious, why doesn't Rijndael work when the system cryptography FIPS compliance security setting is enabled?&lt;/p&gt;
&lt;p&gt;Since it's the successor to DES, and since FIPS 197 is the official standard for it, I guess I kind of expected it to work.&lt;/p&gt;
&lt;p&gt;Has it just not yet been through compliance testing, or is there some reason that it will never be compliant?&lt;/p&gt;
&lt;p&gt;David&lt;/p&gt;</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#823274</link><pubDate>Sat, 14 Oct 2006 00:11:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:823274</guid><dc:creator>shawnfa</dc:creator><description>&lt;p&gt;Hi David,&lt;/p&gt;
&lt;p&gt;You hit the nail on the head -- the reason that RijndaelManaged doesn't work in FIPS mode is that it has not been certified.&lt;/p&gt;
&lt;p&gt;That being said, we have heard the feedback to provide an AES algorithm which will work when FIPS is turned on, so we are looking at that for our next release.&lt;/p&gt;
&lt;p&gt;-Shawn&lt;/p&gt;
</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#1453513</link><pubDate>Fri, 12 Jan 2007 05:36:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1453513</guid><dc:creator>christian</dc:creator><description>&lt;p&gt;Sorry AES crypto ignorant question here.&lt;/p&gt;
&lt;p&gt;What about cipher mode and initialization vector?&lt;/p&gt;
&lt;p&gt;As you said above like most people I just got RijnDaelManaged and went, when I got the request to encrypt using AES. Wouldn't you need to agree on a cipher mode and exchange init vectors with the deciphering party, in addition to exchanging keys?&lt;/p&gt;
&lt;p&gt;Or is CBC what people use when they say AES?&lt;/p&gt;
&lt;p&gt;And initVector is not used, or rather all 0?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;</description></item><item><title>New Crypto Algorithms in Orcas</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#1484427</link><pubDate>Wed, 17 Jan 2007 21:21:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1484427</guid><dc:creator>.Net Security Blog</dc:creator><description>&lt;p&gt;The January CTP of Orcas is now available , and with it comes a total of 12 new cryptography algorithm&lt;/p&gt;
</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#1484514</link><pubDate>Wed, 17 Jan 2007 21:35:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1484514</guid><dc:creator>shawnfa</dc:creator><description>&lt;p&gt;Hi Christian,&lt;/p&gt;
&lt;p&gt;You're correct that both sides of the encrypted conversation will need to agree on all of the parameters to successfully communicate. &amp;nbsp;AES does not restrict either IV or the cipher mode, however as I mention in the blog post there is a bug in RijndaelManaged which makes CFB and OFB dangerous to use if you need to work with AES. &amp;nbsp;In practice most people just default to CBC.&lt;/p&gt;
&lt;p&gt;As for the IV, that's not technically protected information, so one practice is to just send it in plaintext before the beginning of the encrypted conversation.&lt;/p&gt;
&lt;p&gt;-Shawn&lt;/p&gt;
</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#1932505</link><pubDate>Thu, 22 Mar 2007 21:58:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1932505</guid><dc:creator>Matt</dc:creator><description>&lt;p&gt;Is it cryptographically dangerous to simply agree that the IV will be the first (or last) 128 bits of the key? (Is the answer the same for all key sizes?)&lt;/p&gt;
&lt;p&gt;I'm thinking there are plenty of other things that need to be agreed upon (mode, feedback, padding, block size, etc) so why not the IV too?&lt;/p&gt;</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#1989578</link><pubDate>Thu, 29 Mar 2007 20:26:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1989578</guid><dc:creator>shawnfa</dc:creator><description>&lt;p&gt;Hi Matt,&lt;/p&gt;
&lt;p&gt;Generally the IV is not considered a secret, so saying that part of the key is the IV would not be a good idea (since the IV could be transmitted in plain-text, which means that the first portion of your key would be known to attackers). &amp;nbsp;Instead, you can just generate a random IV and send it to the other party to use along with the ciphertext.&lt;/p&gt;
&lt;p&gt;-Shawn&lt;/p&gt;
</description></item><item><title>re: The Differences Between Rijndael and AES</title><link>http://blogs.msdn.com/shawnfa/archive/2006/10/09/The-Differences-Between-Rijndael-and-AES.aspx#2258488</link><pubDate>Tue, 24 Apr 2007 12:31:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2258488</guid><dc:creator>P Dawson, Doncaster, United Kingdom</dc:creator><description>&lt;p&gt;The best solution is to encrypt IV with a perminent (persistent) key previously agreed with the other party, so that only you (plural) know how to decode it. cf. The enigma machine during WWII which had day settings (keys)preknown and the message keys which were encrypted using the day keys.&lt;/p&gt;
&lt;p&gt;In CBC the PT is XORed with the previous CT, thus ensuring that any changes made to the CT stream will propagate in the decrypted PT.&lt;/p&gt;
&lt;p&gt;However, this otherwise gives no better security than ECB except for the matter that no repetitions of PT (and CT) can appear.&lt;/p&gt;</description></item></channel></rss>