<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: GnuPG / PGP</title>
	<link>http://secure2s.net/tools/2006/06/23/gnupg-pgp/</link>
	<description>Secure2S Security Tool Sets Blog</description>
	<pubDate>Sun, 12 Oct 2008 23:48:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: ha.ckers.org security lab - Archive &#187; MD5 isn&#8217;t really broken - sorta</title>
		<link>http://secure2s.net/tools/2006/06/23/gnupg-pgp/#comment-2</link>
		<author>ha.ckers.org security lab - Archive &#187; MD5 isn&#8217;t really broken - sorta</author>
		<pubDate>Sat, 24 Jun 2006 23:12:36 +0000</pubDate>
		<guid>http://secure2s.net/tools/2006/06/23/gnupg-pgp/#comment-2</guid>
					<description>[...] Rainbow crack really is a great tool, but it has one major flaw in it.  It takes a LOT of time to calculate every known hash of every password and worse yet, a lot of space to keep them all organized.  Passwords are generally less than 8 characters, but even still, I&#8217;ve seen passwords that can get up to dozens of chars long (like GnuPG or PGP passphrases, for instance).  What about long strings, like cookies?  Cookies are arbitrary things that can be any lenght (well, in reality they must total less than 4k otherwise Internet Explorer can&#8217;t deal with them in JavaScript space).  So let&#8217;s just use 4k as a hard stop. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Rainbow crack really is a great tool, but it has one major flaw in it.  It takes a LOT of time to calculate every known hash of every password and worse yet, a lot of space to keep them all organized.  Passwords are generally less than 8 characters, but even still, I&#8217;ve seen passwords that can get up to dozens of chars long (like GnuPG or PGP passphrases, for instance).  What about long strings, like cookies?  Cookies are arbitrary things that can be any lenght (well, in reality they must total less than 4k otherwise Internet Explorer can&#8217;t deal with them in JavaScript space).  So let&#8217;s just use 4k as a hard stop. [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
