<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permissions on Linux Security</title><link>https://linuxtransfer.com/tags/permissions/</link><description>Recent content in Permissions on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 07 Aug 2026 10:15:25 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/permissions/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Shared Directory Chaos with Setgid, Sticky Bits, and ACLs</title><link>https://linuxtransfer.com/post/2026-08-07-taming-shared-directory-chaos-with-setgid-sti/</link><pubDate>Fri, 07 Aug 2026 10:15:25 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-08-07-taming-shared-directory-chaos-with-setgid-sti/</guid><description>&lt;h2 id="introduction-to-shared-directory-management">Introduction to Shared Directory Management&lt;/h2>
&lt;p>I&amp;rsquo;ve seen shared directory management become a nightmare on Linux systems, especially when dealing with complex permission scenarios. Luckily, Linux provides some useful tools to simplify this process, including setgid, sticky bits, and Access Control Lists (ACLs). These features give you fine-grained control over file and directory permissions, ensuring that users and groups have the necessary access without compromising security.&lt;/p>
&lt;h2 id="setgid-and-sticky-bits">Setgid and Sticky Bits&lt;/h2>
&lt;p>Setgid and sticky bits are special permission bits that can be set on directories. The real trick is understanding how they work together. The setgid bit, when set on a directory, ensures that all files created within that directory inherit the group ownership of the directory. This is particularly useful in shared directories where multiple users need to collaborate on files. Don&amp;rsquo;t bother with the setgid bit if you&amp;rsquo;re working with single-user directories, though. The sticky bit, on the other hand, prevents users from deleting or renaming files they do not own, even if they have write permission to the directory.&lt;/p></description></item><item><title>Troubleshooting Broken Permissions on Shared Directories with setgid and ACLs</title><link>https://linuxtransfer.com/post/2026-06-21-troubleshooting-broken-permissions-on-shared-/</link><pubDate>Sun, 21 Jun 2026 10:09:46 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-06-21-troubleshooting-broken-permissions-on-shared-/</guid><description>&lt;h2 id="introduction-to-shared-directory-permissions">Introduction to Shared Directory Permissions&lt;/h2>
&lt;p>When working with shared directories in Linux, permissions can quickly become a complex issue. I&amp;rsquo;ve seen this go wrong when multiple users need to collaborate on the same project, and suddenly, nobody can access the files they need. The &lt;code>setgid&lt;/code> bit and Access Control Lists (ACLs) are two powerful tools for managing these permissions. In this article, we&amp;rsquo;ll explore how to troubleshoot broken permissions on shared directories using &lt;code>setgid&lt;/code> and ACLs.&lt;/p></description></item></channel></rss>