<?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 Nalar</title>
    <link>https://nalar.dev/tags/fs-verity/</link>
    <description>Recent content in Fs-Verity on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 04 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/fs-verity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>fs-verity Verifies Read-Only Files as They Are Read</title>
      <link>https://nalar.dev/fs-verity-verifies-read-only-files-as-they-are-read/</link>
      <pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/fs-verity-verifies-read-only-files-as-they-are-read/</guid>
      <description>&lt;h1 id=&#34;fs-verity-verifies-read-only-files-as-they-are-read&#34;&gt;fs-verity Verifies Read-Only Files as They Are Read&lt;/h1&gt;&#xA;&lt;p&gt;A conventional file hash is often checked before a file is trusted. Linux fs-verity moves part of that integrity work into the filesystem. Once verity is enabled for a regular file on a supporting filesystem, the file becomes read-only and its data is checked against a persisted Merkle tree as data is read.&lt;/p&gt;&#xA;&lt;p&gt;The mechanism has a deliberately narrow boundary. fs-verity can detect data that no longer matches the digest enforced for a verity file. Authenticating that digest against a trusted identity or release policy is a separate decision. The distinction prevents an integrity primitive from being mistaken for a complete software-trust policy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
