<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OverlayFS on Nalar</title>
    <link>https://nalar.dev/tags/overlayfs/</link>
    <description>Recent content in OverlayFS on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/overlayfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OverlayFS Stashed Credentials Separate Overlay Access from Backing Filesystem Access</title>
      <link>https://nalar.dev/overlayfs-stashed-credentials-separate-overlay-access-from-backing-filesystem-access/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/overlayfs-stashed-credentials-separate-overlay-access-from-backing-filesystem-access/</guid>
      <description>&lt;h1 id=&#34;overlayfs-stashed-credentials-separate-overlay-access-from-backing-filesystem-access&#34;&gt;OverlayFS Stashed Credentials Separate Overlay Access from Backing Filesystem Access&lt;/h1&gt;&#xA;&lt;p&gt;A process opens a path through an OverlayFS mount and appears to access one ordinary filesystem object. The kernel may actually consult an upper layer, a lower layer, or both, and a write can trigger copy-up before the requested operation proceeds. That indirection creates an authorization problem: the caller must be permitted to use the object as exposed by the overlay, while the internal access to the backing filesystems must also run under a defined security identity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
