<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cryptsetup on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cryptsetup/</link>
    <description>Recent content in Cryptsetup on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cryptsetup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Encrypted Swap: LUKS dm-crypt vs Plain dm-crypt vs zram Encryption</title>
      <link>https://www.pistack.xyz/posts/2026-06-03-self-hosted-encrypted-swap-luks-dm-crypt-zram-guide/</link>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-03-self-hosted-encrypted-swap-luks-dm-crypt-zram-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Swap space is a fundamental component of Linux memory management, but its security implications are often overlooked. When a server runs low on RAM, the kernel writes memory pages to swap — including pages that may contain encryption keys, authentication tokens, database connection strings, and other sensitive data. If an attacker gains physical access to the storage device or compromises a cloud provider&amp;rsquo;s disk snapshot feature, unencrypted swap becomes a goldmine of credentials and secrets.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
