<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ECB vs CBC Encryption</title>
	<atom:link href="http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: Peter G.</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-124256</link>
		<dc:creator>Peter G.</dc:creator>
		<pubDate>Thu, 21 Feb 2013 11:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-124256</guid>
		<description><![CDATA[Is it possible to get a visual feedback from a DES / T-DES OR DESX encryption as well?]]></description>
		<content:encoded><![CDATA[<p>Is it possible to get a visual feedback from a DES / T-DES OR DESX encryption as well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Toponce</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-117085</link>
		<dc:creator>Aaron Toponce</dc:creator>
		<pubDate>Sun, 28 Oct 2012 14:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-117085</guid>
		<description><![CDATA[Well, first all the commands are already in the post. You just need to reverse them. Second, because I took a bitmap header (54 bytes worth), and placed it on the encrypted data to create the image, there is irreversible data corruption on the encrypted data. For ECB, this won&#039;t be a problem. For CBC, it will.]]></description>
		<content:encoded><![CDATA[<p>Well, first all the commands are already in the post. You just need to reverse them. Second, because I took a bitmap header (54 bytes worth), and placed it on the encrypted data to create the image, there is irreversible data corruption on the encrypted data. For ECB, this won&#8217;t be a problem. For CBC, it will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shailja</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-117084</link>
		<dc:creator>Shailja</dc:creator>
		<pubDate>Sun, 28 Oct 2012 09:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-117084</guid>
		<description><![CDATA[Can you tell me how to decrypt this image , because I tried but it shows some bad magic no
Please reply asap with the command

Thanks]]></description>
		<content:encoded><![CDATA[<p>Can you tell me how to decrypt this image , because I tried but it shows some bad magic no<br />
Please reply asap with the command</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Klaas</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116893</link>
		<dc:creator>Marcus Klaas</dc:creator>
		<pubDate>Sat, 08 Sep 2012 16:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116893</guid>
		<description><![CDATA[Great post that explained EBC vs CBC really well. Thanks :-)]]></description>
		<content:encoded><![CDATA[<p>Great post that explained EBC vs CBC really well. Thanks <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116807</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Mon, 09 Jul 2012 02:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116807</guid>
		<description><![CDATA[This is a great demonstration, but I wonder if it might be made more accurate if the first 54 bytes of ubuntu.bmp were not included in the encryption. In the given example, the first 54 bytes are used in encryption, but then thrown away for visualization. It might be better to dd ubuntu.bmp to ubuntu-sans-header.bmp with bs=1 and skip=54. Perform encryption on ubuntu-sans-header.bmp and then append the 54 bytes from ubuntu.bmp as per the current example.]]></description>
		<content:encoded><![CDATA[<p>This is a great demonstration, but I wonder if it might be made more accurate if the first 54 bytes of ubuntu.bmp were not included in the encryption. In the given example, the first 54 bytes are used in encryption, but then thrown away for visualization. It might be better to dd ubuntu.bmp to ubuntu-sans-header.bmp with bs=1 and skip=54. Perform encryption on ubuntu-sans-header.bmp and then append the 54 bytes from ubuntu.bmp as per the current example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Toponce</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116560</link>
		<dc:creator>Aaron Toponce</dc:creator>
		<pubDate>Mon, 04 Jun 2012 21:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116560</guid>
		<description><![CDATA[Yes. You&#039;re absolutely correct. I&#039;ll update the post. Thanks!]]></description>
		<content:encoded><![CDATA[<p>Yes. You&#8217;re absolutely correct. I&#8217;ll update the post. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martins Mozeiko</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116559</link>
		<dc:creator>Martins Mozeiko</dc:creator>
		<pubDate>Sun, 03 Jun 2012 23:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116559</guid>
		<description><![CDATA[AES-256 doesn&#039;t operate on 256-bit blocks at time. AES-128, 192 and 256 all operate on 128-bit blocks at time.
Only difference is in key size. That means expanded key size will be bigger and AES will use more rounds for AES-192/256 than for AES-128. 128 has 10 rounds, 192 has 12 rounds and 256 has 14 rounds]]></description>
		<content:encoded><![CDATA[<p>AES-256 doesn&#8217;t operate on 256-bit blocks at time. AES-128, 192 and 256 all operate on 128-bit blocks at time.<br />
Only difference is in key size. That means expanded key size will be bigger and AES will use more rounds for AES-192/256 than for AES-128. 128 has 10 rounds, 192 has 12 rounds and 256 has 14 rounds</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116455</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Sun, 26 Feb 2012 18:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116455</guid>
		<description><![CDATA[Fascinating.  ECB looks like a terrible idea that should never be used to encrypt anything, as it makes no proper attempt to encrypt &quot;whitespace&quot;, or repeated runs of the same data in the input.  The BMP clearly shows the effect, but other datasets (documents, audio, whatever) would be affected too.]]></description>
		<content:encoded><![CDATA[<p>Fascinating.  ECB looks like a terrible idea that should never be used to encrypt anything, as it makes no proper attempt to encrypt &#8220;whitespace&#8221;, or repeated runs of the same data in the input.  The BMP clearly shows the effect, but other datasets (documents, audio, whatever) would be affected too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Toponce</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116444</link>
		<dc:creator>Aaron Toponce</dc:creator>
		<pubDate>Thu, 23 Feb 2012 02:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116444</guid>
		<description><![CDATA[Tiao- You need a browser that supports viewing bitmaps.]]></description>
		<content:encoded><![CDATA[<p>Tiao- You need a browser that supports viewing bitmaps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tiao</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116443</link>
		<dc:creator>Tiao</dc:creator>
		<pubDate>Thu, 23 Feb 2012 01:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116443</guid>
		<description><![CDATA[I cannot see the images in my bada phone.]]></description>
		<content:encoded><![CDATA[<p>I cannot see the images in my bada phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Toponce</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116439</link>
		<dc:creator>Aaron Toponce</dc:creator>
		<pubDate>Wed, 22 Feb 2012 12:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116439</guid>
		<description><![CDATA[shalombi- Yes, this isn&#039;t a one-size-fits-all solution. And ECB definitely performs better than CBC in most cases. However, it is important to understand that patterns will emerge from the underlying data if you use ECB. It&#039;s simple enough to do this same exercise on binary executables or text files, and see patterns emerge.

Regardless, the illustration with images is to help you understand what is happening with the different block modes.]]></description>
		<content:encoded><![CDATA[<p>shalombi- Yes, this isn&#8217;t a one-size-fits-all solution. And ECB definitely performs better than CBC in most cases. However, it is important to understand that patterns will emerge from the underlying data if you use ECB. It&#8217;s simple enough to do this same exercise on binary executables or text files, and see patterns emerge.</p>
<p>Regardless, the illustration with images is to help you understand what is happening with the different block modes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shalombi</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116437</link>
		<dc:creator>shalombi</dc:creator>
		<pubDate>Wed, 22 Feb 2012 07:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116437</guid>
		<description><![CDATA[ECB does preserve block structure which in the case of images reveals part of the information encrypted.
However this isn&#039;t so much an issue with other types of data where the value lies in the data rather than the structure.

As explained CBC solves this by chaining the encryption but this comes with a performance hit.
So IMHO CBC isn&#039;t a blanket solution but must be chosen carefully in regard with the task at hand.

http://www.cse.wustl.edu/~jain/cse567-06/ftp/encryption_perf/index.html#6]]></description>
		<content:encoded><![CDATA[<p>ECB does preserve block structure which in the case of images reveals part of the information encrypted.<br />
However this isn&#8217;t so much an issue with other types of data where the value lies in the data rather than the structure.</p>
<p>As explained CBC solves this by chaining the encryption but this comes with a performance hit.<br />
So IMHO CBC isn&#8217;t a blanket solution but must be chosen carefully in regard with the task at hand.</p>
<p><a href="http://www.cse.wustl.edu/~jain/cse567-06/ftp/encryption_perf/index.html#6" rel="nofollow">http://www.cse.wustl.edu/~jain/cse567-06/ftp/encryption_perf/index.html#6</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116436</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Wed, 22 Feb 2012 04:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116436</guid>
		<description><![CDATA[Very clever! Thanks for posting.]]></description>
		<content:encoded><![CDATA[<p>Very clever! Thanks for posting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Toponce : Randomize First, Then Encrypt Your Block Device</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116426</link>
		<dc:creator>Aaron Toponce : Randomize First, Then Encrypt Your Block Device</dc:creator>
		<pubDate>Mon, 20 Feb 2012 22:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116426</guid>
		<description><![CDATA[[...] blog post is in continuation of the previous post, where I showed why you should not use ECB when encrypting your data. Well, when putting down an [...]]]></description>
		<content:encoded><![CDATA[<p>[...] blog post is in continuation of the previous post, where I showed why you should not use ECB when encrypting your data. Well, when putting down an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://pthree.org/2012/02/17/ecb-vs-cbc-encryption/#comment-116423</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Sat, 18 Feb 2012 15:45:07 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=2264#comment-116423</guid>
		<description><![CDATA[Thanks for this illustration. That&#039;s why some time ago i changed for IRC encryption from FiSH to mircryption which supports CBC]]></description>
		<content:encoded><![CDATA[<p>Thanks for this illustration. That&#8217;s why some time ago i changed for IRC encryption from FiSH to mircryption which supports CBC</p>
]]></content:encoded>
	</item>
</channel>
</rss>
