<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permission Management on ByF (BaiFan) · Daily Deep Think</title><link>https://blog.baifan.site/en/tags/permission-management/</link><description>Recent content in Permission Management on ByF (BaiFan) · Daily Deep Think</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF (BaiFan))</managingEditor><webMaster>blog@baifan.site (ByF (BaiFan))</webMaster><copyright>CC BY-NC 4.0</copyright><lastBuildDate>Wed, 20 May 2026 09:00:00 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/permission-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Permissions and Real Security Boundaries: Sandboxes, System Calls, and Approval Escape</title><link>https://blog.baifan.site/en/claude-code-permissions-security/</link><pubDate>Wed, 20 May 2026 09:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/claude-code-permissions-security/</guid><description>&lt;p&gt;Any AI agent permission system running in userspace that relies on model self-discipline and application-level regex filtering does not constitute an enforceable security boundary from the perspective of the operating system kernel. Claude Code&amp;rsquo;s 5-level permission model and interactive approval workflow operate as flow-control protocols to mitigate developer mistakes, lacking sandbox containment against adversarial attacks.&lt;/p&gt;&#10;&lt;!-- more --&gt;&#10;&lt;p&gt;Granting an AI coding assistant filesystem write access and terminal execution rights under the belief that confirmation prompts preserve a safety perimeter is a fundamental category error. Confusing interactive human approval with privileged access control collapses into a cosmetic barrier when confronted with supply-chain poisonings, indirect prompt injections, and shell parser differentials.&lt;/p&gt;</description></item></channel></rss>