<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>probability &#8211; Accidents Happen</title>
	<atom:link href="https://ah.thameera.com/tag/probability/feed/" rel="self" type="application/rss+xml" />
	<link>https://ah.thameera.com</link>
	<description>In the dark</description>
	<lastBuildDate>Thu, 08 Nov 2012 16:25:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">56521109</site>	<item>
		<title>The probability of SHA-1 collisions</title>
		<link>https://ah.thameera.com/the-probability-of-sha-1-collisions/</link>
					<comments>https://ah.thameera.com/the-probability-of-sha-1-collisions/#respond</comments>
		
		<dc:creator><![CDATA[thameera]]></dc:creator>
		<pubDate>Thu, 08 Nov 2012 16:25:25 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[birthday paradox]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[hash]]></category>
		<category><![CDATA[probability]]></category>
		<category><![CDATA[sha-1]]></category>
		<guid isPermaLink="false">http://noisythameera.wordpress.com/?p=228</guid>

					<description><![CDATA[Git uses SHA-1 hashes to identify its objects (commits, refs, blobs, etc). It assumes that if the SHA-1 hashes of two objects are equal, then the two objects themselves are equal, hence there&#8217;s no need to store both in the repo. In other words, if the hashes of two different objects turned out to be [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Git uses <a href="http://en.wikipedia.org/wiki/SHA-1" target="_blank">SHA-1 hashes</a> to identify its objects (commits, refs, blobs, etc). It assumes that if the SHA-1 hashes of two objects are equal, then the two objects themselves are equal, hence there&#8217;s no need to store both in the repo. In other words, if the hashes of two different objects turned out to be equal at some point, Git wouldn&#8217;t be able to handle that!</p>
<p>But what are the chance of such a SHA-1 collision? This was discussed in the Git mailing list today and a recent analysis on this problem was shed into light. This analysis has used the famous <a href="http://en.wikipedia.org/wiki/Birthday_paradox" target="_blank">Birthday Paradox</a> and come up with a formula to determine the probability. It <a href="http://news.ycombinator.com/item?id=4753198" target="_blank">quotes</a>,</p>
<blockquote><p>&#8220;Applying the formula for 160bit SHA-1 you need 1.7e23 objects to get a 1% chance of collision. The current Linus kernel repository has 2.7 million objects. So to get a collision you&#8217;d need a repository that&#8217;s 6e16 times larger. That should be plenty.</p>
<p>For some wacky perspective that&#8217;s 10 million kernel sized contributions for every man woman and child on earth together in a single repository. It would seem git will reach plenty of other bottlenecks before SHA-1 becomes a problem&#8230;&#8221;</p></blockquote>
<p>The probability is, of course, still non-zero. But don&#8217;t ever expect to witness such a collision before you die. </p>
]]></content:encoded>
					
					<wfw:commentRss>https://ah.thameera.com/the-probability-of-sha-1-collisions/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">228</post-id>	</item>
	</channel>
</rss>
