<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory Files on Nalar</title>
    <link>https://nalar.dev/tags/memory-files/</link>
    <description>Recent content in Memory Files 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/memory-files/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Memfd Seals Turn Mutable Anonymous Files into Explicit Handoff Objects</title>
      <link>https://nalar.dev/memfd-seals-turn-mutable-anonymous-files-into-explicit-handoff-objects/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/memfd-seals-turn-mutable-anonymous-files-into-explicit-handoff-objects/</guid>
      <description>&lt;p&gt;A process prepares a binary payload in memory, passes a file descriptor to another process, and expects the bytes to remain stable after validation. A plain descriptor does not create that guarantee. If some holder still has write authority, the object can change after a consumer has inspected it, and pathname permissions offer no useful boundary when the object has no ordinary filesystem name.&lt;/p&gt;&#xA;&lt;p&gt;Linux &lt;code&gt;memfd_create()&lt;/code&gt; provides an anonymous file backed by memory-like filesystem storage, and file seals can constrain later changes to that file. The useful security property is not anonymity by itself. It is the ability to construct a mutable object, apply irreversible restrictions to that object, then hand out descriptors whose backing file can no longer be changed in the prohibited ways.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
