<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://hackepedia.org/index.php?action=history&amp;feed=atom&amp;title=Hash_collision</id>
	<title>Hash collision - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://hackepedia.org/index.php?action=history&amp;feed=atom&amp;title=Hash_collision"/>
	<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Hash_collision&amp;action=history"/>
	<updated>2026-05-08T17:44:21Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://hackepedia.org/index.php?title=Hash_collision&amp;diff=1845&amp;oldid=prev</id>
		<title>Frankk at 04:33, 27 October 2005</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Hash_collision&amp;diff=1845&amp;oldid=prev"/>
		<updated>2005-10-27T04:33:28Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 21:33, 26 October 2005&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l1&quot;&gt;Line 1:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 1:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;The desirable property of a [[One way hash]] algorithm is that for any given input, the output is unique.  Given that the hash output is almost always smaller than the input, this property can&amp;#039;t be achieved completely.  When two sets of input data result in the same hash output, it is called a [[hash collision]].&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;The desirable property of a [[One way hash]] algorithm is that for any given input, the output is unique.  Given that the hash output is almost always smaller than the input, this property can&amp;#039;t be achieved completely.  When two sets of input data result in the same hash output, it is called a [[hash collision]].&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;−&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Hash collisions aren&#039;t always a problem.  Some techniques, like [[hashcash]], rely on finding collisions as a &quot;proof of work&quot;.  The problems arise when similar data sets collide.  This is the basis of the [&lt;del style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;[&lt;/del&gt;MD5&lt;del style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;]] &lt;/del&gt;collision paper presented at Crypto 2004.  Further research has produced a method of creating quite similar documents that have the same [[MD5]] hash value.  When the two documents are, for example, slightly different versions of a contract, and the [[MD5]] hash value is used to attest that the original document has not been altered, the [[hash collision]] problem becomes obvious.&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Hash collisions aren&#039;t always a problem.  Some techniques, like [[hashcash]], rely on finding collisions as a &quot;proof of work&quot;.  The problems arise when similar data sets collide.  This is the basis of the [&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;http://eprint.iacr.org/2004/199.pdf &lt;/ins&gt;MD5 collision paper&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;] &lt;/ins&gt;presented at Crypto 2004.  Further research has produced a method of creating quite similar documents that have the same [[MD5]] hash value.  When the two documents are, for example, slightly different versions of a contract, and the [[MD5]] hash value is used to attest that the original document has not been altered, the [[hash collision]] problem becomes obvious.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>Frankk</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=Hash_collision&amp;diff=378&amp;oldid=prev</id>
		<title>Roy at 04:49, 10 October 2005</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Hash_collision&amp;diff=378&amp;oldid=prev"/>
		<updated>2005-10-10T04:49:04Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The desirable property of a [[One way hash]] algorithm is that for any given input, the output is unique.  Given that the hash output is almost always smaller than the input, this property can&amp;#039;t be achieved completely.  When two sets of input data result in the same hash output, it is called a [[hash collision]].&lt;br /&gt;
&lt;br /&gt;
Hash collisions aren&amp;#039;t always a problem.  Some techniques, like [[hashcash]], rely on finding collisions as a &amp;quot;proof of work&amp;quot;.  The problems arise when similar data sets collide.  This is the basis of the [[MD5]] collision paper presented at Crypto 2004.  Further research has produced a method of creating quite similar documents that have the same [[MD5]] hash value.  When the two documents are, for example, slightly different versions of a contract, and the [[MD5]] hash value is used to attest that the original document has not been altered, the [[hash collision]] problem becomes obvious.&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
</feed>