<?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 *scratch*</title>
    <link>https://www.scrivano.org/tags/fs-verity/</link>
    <description>Recent content in Fs-Verity on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 10 Jul 2026 10:41:24 +0200</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/fs-verity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Image sealing with composefs</title>
      <link>https://www.scrivano.org/posts/2026-06-05-sealing-with-composefs/</link>
      <pubDate>Fri, 05 Jun 2026 08:00:00 +0000</pubDate>
      <guid>https://www.scrivano.org/posts/2026-06-05-sealing-with-composefs/</guid>
      <description>&lt;p&gt;Composefs achieves whole-filesystem integrity verification through &lt;em&gt;image sealing&lt;/em&gt;: a single cryptographic digest authenticates an entire filesystem, covering both file contents and metadata (directory structure, permissions, ownership, symlinks, and xattrs). This goes further than fs-verity alone, which can only verify individual file contents, and avoids the fixed-partition requirement of dm-verity. The mechanism combines an EROFS image for metadata, a content-addressed object store for file data, and overlayfs with &lt;code&gt;verity=require&lt;/code&gt; to enforce integrity checks on every file access at the kernel level.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
