<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://hackepedia.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Roy</id>
	<title>Hackepedia - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://hackepedia.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Roy"/>
	<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Special:Contributions/Roy"/>
	<updated>2026-05-08T16:27:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://hackepedia.org/index.php?title=Hashcash&amp;diff=1846</id>
		<title>Hashcash</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Hashcash&amp;diff=1846"/>
		<updated>2005-10-10T05:01:07Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Hashcash]] is a &amp;quot;proof of work&amp;quot; system originally designed as an anti-spam measure.  [[Hashcash]] tokens are &amp;quot;minted&amp;quot; by finding a [[hash collision]] for a unique input string.  The result is included in the header of an email message as &amp;quot;proof&amp;quot; that the sender has done a certain amount of work to &amp;quot;pay for&amp;quot; the delivery of the message.  A 20-bit collision may take only a fraction of a second to compute, depending on the computer system.  25 bits on the same system would take 11 seconds, and 30 bits would take over 6 minutes.  The recipient determines how much work is required to pay for delivery.&lt;br /&gt;
&lt;br /&gt;
The idea behind [[hashcash]] is that a legitimate email sender can easily afford a few seconds to mint a stamp for an outgoing email, but spammers who want to send millions of emails would be bogged down.&lt;br /&gt;
&lt;br /&gt;
The [[hashcash]] project may be found [http://www.hashcash.org here].&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=Hash_collision&amp;diff=378</id>
		<title>Hash collision</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Hash_collision&amp;diff=378"/>
		<updated>2005-10-10T04:49:04Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&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&#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&#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>
	<entry>
		<id>https://hackepedia.org/index.php?title=One_way_hash&amp;diff=396</id>
		<title>One way hash</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=One_way_hash&amp;diff=396"/>
		<updated>2005-10-10T04:35:04Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A [[One way hash]] is a mathematical way to create a (usually smaller) unique representation of a given set of data.  It&#039;s sometimes referred to as a &amp;quot;fingerprint&amp;quot;. It&#039;s called &amp;quot;One Way&amp;quot; because while it&#039;s easy to create the hash value from the input data, it is, for all intents and purposes, impossible to reconstruct the original data from the hash value.  [[MD5]] is perhaps the most well-known [[One way hash]].  [[SHA]], the Secure Hashing Algorithm, is widely used today to replace [[MD5]].&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=Md5&amp;diff=633</id>
		<title>Md5</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Md5&amp;diff=633"/>
		<updated>2005-10-10T04:33:34Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[MD5]] is a cryptographic one-way hashing algorithm first described in [[RFC]] 1321 back in 1992.&lt;br /&gt;
&lt;br /&gt;
[[MD5]] is no longer recommended for use, following a presentation at the 2004 Crypto Conference that revealed [[hash collision]] problems with the algorithm.&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=One_way_hash&amp;diff=184</id>
		<title>One way hash</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=One_way_hash&amp;diff=184"/>
		<updated>2005-10-10T04:28:18Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A [[One Way Hash]] is a mathematical way to create a (usually smaller) unique representation of a given set of data.  It&#039;s sometimes referred to as a &amp;quot;fingerprint&amp;quot;. It&#039;s called &amp;quot;One Way&amp;quot; because while it&#039;s easy to create the hash value from the input data, it is, for all intents and purposes, impossible to reconstruct the original data from the hash value.  [[MD5]] is perhaps the most well-known [[One Way Hash]].  [[SHA]], the Secure Hashing Algorithm, is widely used today to replace [[MD5]].&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=Rot13&amp;diff=1841</id>
		<title>Rot13</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Rot13&amp;diff=1841"/>
		<updated>2005-10-10T04:13:44Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Rot13 rotates all 26 letters of the alphabet by 13 positions rolling over to position 1 after position 26.  A sample display of how rot13 &amp;quot;encrypts&amp;quot; is shown below:&lt;br /&gt;
&lt;br /&gt;
 $ echo A B C D E F G H I J K L M N O P Q R S T U V W X Y Z | rot13&lt;br /&gt;
        N O P Q R S T U V W X Y Z A B C D E F G H I J K L M&lt;br /&gt;
&lt;br /&gt;
So you see A becomes N and N becomes A. This encryption can be found in many places online, such as Usenet and geocaching.com.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;But wait!&amp;quot;, you say.  &amp;quot;My system, has no &#039;rot13&#039; program!&amp;quot;  Fear not.  It is but one line of Perl:&lt;br /&gt;
&lt;br /&gt;
 #!/usr/bin/perl -p&lt;br /&gt;
 y/A-Za-z/N-ZA-Mn-za-m/;&lt;br /&gt;
&lt;br /&gt;
(OK, two lines, if you count the shellexec header).  rot13 is also found in the BSD games package.&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=Rot13&amp;diff=183</id>
		<title>Rot13</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Rot13&amp;diff=183"/>
		<updated>2005-10-10T04:13:29Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Rot13 rotates all 26 letters of the alphabet by 13 positions rolling over to position 1 after position 26.  A sample display of how rot13 &amp;quot;encrypts&amp;quot; is shown below:&lt;br /&gt;
&lt;br /&gt;
 $ echo A B C D E F G H I J K L M N O P Q R S T U V W X Y Z | rot13&lt;br /&gt;
        N O P Q R S T U V W X Y Z A B C D E F G H I J K L M&lt;br /&gt;
&lt;br /&gt;
So you see A becomes N and N becomes A. This encryption can be found in many places online, such as Usenet and geocaching.com.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;But wait!&amp;quot;, you say.  &amp;quot;My system, has no &#039;rot13&#039; program!&amp;quot;  Fear not.  It is but one line of Perl:&lt;br /&gt;
&lt;br /&gt;
 #!/usr/bin/perl -p&lt;br /&gt;
 y/A-Za-z/N-ZA-Mn-za-m/;&lt;br /&gt;
&lt;br /&gt;
(OK, two lines, if you count the shellexec header)  rot13 is also found in the BSD games package.&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
	<entry>
		<id>https://hackepedia.org/index.php?title=Rot13&amp;diff=182</id>
		<title>Rot13</title>
		<link rel="alternate" type="text/html" href="https://hackepedia.org/index.php?title=Rot13&amp;diff=182"/>
		<updated>2005-10-10T04:02:17Z</updated>

		<summary type="html">&lt;p&gt;Roy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Rot13 rotates all 26 letters of the alphabet by 13 positions rolling over to position 1 after position 26.  A sample display of how rot13 &amp;quot;encrypts&amp;quot; is shown below:&lt;br /&gt;
&lt;br /&gt;
 $ echo A B C D E F G H I J K L M N O P Q R S T U V W X Y Z | rot13&lt;br /&gt;
        N O P Q R S T U V W X Y Z A B C D E F G H I J K L M&lt;br /&gt;
&lt;br /&gt;
So you see A becomes N and N becomes A. This encryption can be found in many places online, such as Usenet and geocaching.com.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;But wait!&amp;quot;, you say.  &amp;quot;My system, has no &#039;rot13&#039; program!&amp;quot;  Fear not.  It is but one line of Perl:&lt;br /&gt;
&lt;br /&gt;
 #!/usr/bin/perl -p&lt;br /&gt;
 y/A-Za-z/N-ZA-Mn-za-m/;&lt;br /&gt;
&lt;br /&gt;
(OK, two lines, if you count the shellexec header)&lt;/div&gt;</summary>
		<author><name>Roy</name></author>
	</entry>
</feed>