<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Cryptography on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/cryptography/</link>
		<description>Recent content in Cryptography on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 24 Sep 2026 22:30:28 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/cryptography/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Symmetric vs Asymmetric Encryption: What Is the Difference?</title>
				<link>https://www.compilemymind.com/posts/symmetric-vs-asymmetric-encryption/</link>
				<pubDate>Thu, 24 Sep 2026 22:30:28 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/symmetric-vs-asymmetric-encryption/</guid>
				<description>&lt;p&gt;A team encrypts its nightly backup with one secret key. The protection works—until a second system needs to restore the data.&lt;/p&gt;&#xA;&lt;p&gt;Should the team copy the secret key to that system? Send it over the network? Give every service its own copy? And if one copy leaks, how many backups and systems must be treated as exposed?&lt;/p&gt;&#xA;&lt;p&gt;This is the problem hidden inside most explanations of encryption. Turning plaintext into ciphertext is only half the design. The other half is deciding &lt;strong&gt;who holds which keys, how those keys arrive safely, and what a key is allowed to do&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
