<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stickybit on Linux Security</title><link>https://linuxtransfer.com/tags/stickybit/</link><description>Recent content in Stickybit on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 23 Oct 2026 08:11:43 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/stickybit/index.xml" rel="self" type="application/rss+xml"/><item><title>Resolving “Permission denied” When Moving Files Into a Sticky‑Bit Directory Using ACLs</title><link>https://linuxtransfer.com/post/2026-10-23-resolving-permission-denied-when-moving-files/</link><pubDate>Fri, 23 Oct 2026 08:11:43 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-10-23-resolving-permission-denied-when-moving-files/</guid><description>&lt;h2 id="stickybit-directories-and-acls-why-permission-denied-still-happens">Sticky‑Bit Directories and ACLs: Why “Permission denied” Still Happens&lt;/h2>
&lt;p>When you try to move a file into a directory that has the sticky bit set, the kernel first checks the directory’s owner and the user’s write permission. If the directory is owned by someone else, the sticky bit forces it to also check the file’s owner. ACLs can grant write access to a group or user, but the sticky‑bit logic still requires the file’s owner to match the directory’s owner unless the moving user has the &lt;em>write&lt;/em> permission on the file itself. That subtle rule is the source of a lot of “Permission denied” errors that only surface when ACLs are involved.&lt;/p></description></item></channel></rss>