<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Once upon a time, silvioprog said:<br>
</div>
<blockquote
cite="mid:CAKq_V2KtgtEejQ3VexWObPWhuuzVnW+oTajwyV1A7cch2SjonQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">2013/12/11 Ewald <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:ewald@yellowcouch.org" target="_blank">ewald@yellowcouch.org</a>></span><br>
</div>
<div><br>
</div>
<div>Go to: <a moz-do-not-send="true"
href="http://md5decryption.com/">http://md5decryption.com</a></div>
<div>In "Please input the MD5 hash that you would like to be
decrypted:" field, put: 7db4a8dae498d1b4686ebd1f79326602</div>
<div>See the result in "Decrypted Text:" field.</div>
</div>
</div>
</blockquote>
Yes, I've seen the site, what they probably do is a reverse lookup
in a table, but it cannot be called `decryption`. Encryption is two
way: an output can be converted back to the original input. This is
not the case with a hashing function. Take for example a very simple
function that xor's all input bytes together (with MD5 it boils down
to the same, albeit a bit more complex). If I give you the output
$F0, how do you know what was the original input? The answer is you
don't. It could be [$80 $70] as well as it could have been [$C0 $FF
$30 $FF]...<br>
<br>
While both algorithm types (encryption and hashing) are related (the
above xor example classified as a checksum, whereas xor encryption
also exists), they are definitly not the same.<br>
<pre class="moz-signature" cols="72">--
Ewald
</pre>
</body>
</html>