<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fs-Verity on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/fs-verity/</link>
    <description>Recent content in Fs-Verity on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/fs-verity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Data Integrity Verification — dm-verity vs fs-verity vs dm-integrity</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-data-integrity-verification-dm-verity-fs-verity-dm-integrity-guide/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-data-integrity-verification-dm-verity-fs-verity-dm-integrity-guide/</guid>
      <description>&lt;p&gt;Data integrity verification ensures that stored data has not been tampered with or corrupted. Linux provides three complementary integrity mechanisms: &lt;strong&gt;dm-verity&lt;/strong&gt; (block-device verification), &lt;strong&gt;fs-verity&lt;/strong&gt; (file-level verification), and &lt;strong&gt;dm-integrity&lt;/strong&gt; (sector-level integrity with authentication). This guide compares their architectures, use cases, and deployment patterns for self-hosted servers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
