<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ptrace on Nalar</title>
    <link>https://nalar.dev/tags/ptrace/</link>
    <description>Recent content in Ptrace 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/ptrace/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PR_SET_DUMPABLE Changes Linux Process Inspection Boundaries</title>
      <link>https://nalar.dev/pr-set-dumpable-changes-linux-process-inspection-boundaries/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/pr-set-dumpable-changes-linux-process-inspection-boundaries/</guid>
      <description>&lt;p&gt;A service receives credentials into process memory, drops privileges, and continues running under an ordinary account. Another same-account process may still be able to inspect it through interfaces intended for debugging. Linux places an additional process attribute, commonly called &lt;code&gt;dumpable&lt;/code&gt;, into several of these access decisions.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;prctl(PR_SET_DUMPABLE, 0)&lt;/code&gt; marks the calling process non-dumpable. The effect is broader than suppressing a core file: Linux also incorporates dumpable state into ptrace access checks and changes ownership behavior for files under &lt;code&gt;/proc/&amp;lt;pid&amp;gt;&lt;/code&gt;. These effects form related boundaries, but they are not a single universal ban on process observation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
