<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Hashing on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/hashing/</link>
		<description>Recent content in Hashing on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Fri, 18 Sep 2026 19:31:07 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/hashing/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Encryption vs Hashing vs Encoding: What Is the Difference?</title>
				<link>https://www.compilemymind.com/posts/encryption-vs-hashing-vs-encoding/</link>
				<pubDate>Fri, 18 Sep 2026 19:31:07 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/encryption-vs-hashing-vs-encoding/</guid>
				<description>&lt;p&gt;A developer opens a support ticket and finds an API credential that looks like this:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;c2VjcmV0LWtleS0xMjM=&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;It looks scrambled, so someone calls it encrypted. A few seconds later, another person decodes it as Base64 and reads &lt;code&gt;secret-key-123&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Nothing was cracked. There was no key to steal and no cryptographic weakness to exploit. The data was merely written in a different alphabet.&lt;/p&gt;&#xA;&lt;p&gt;That small vocabulary mistake points to a much larger engineering problem. Encryption, hashing, and encoding can all turn readable input into output that looks meaningless, but appearance is where the similarity ends. They make different promises, solve different problems, and fail in different ways.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
