<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Acl on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/acl/</link>
    <description>Recent content in Acl on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 24 May 2026 10:19:31 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/acl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming the Chaos of Shared Directories with ACLs and Sticky Bits</title>
      <link>https://linuxeries.org/post/2026-05-24-taming-the-chaos-of-shared-directories-with-a/</link>
      <pubDate>Sun, 24 May 2026 10:19:31 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-24-taming-the-chaos-of-shared-directories-with-a/</guid>
      <description>&lt;h2 id=&#34;introduction-to-shared-directories-and-acls&#34;&gt;Introduction to Shared Directories and ACLs&lt;/h2&gt;&#xA;&lt;p&gt;When managing shared directories on a Linux system, I&amp;rsquo;ve seen this go wrong when accessibility and security aren&amp;rsquo;t balanced. One way to achieve this balance is by utilizing Access Control Lists (ACLs) and sticky bits. ACLs provide a more fine-grained access control mechanism than traditional Unix permissions, allowing you to set specific permissions for users and groups. Sticky bits, on the other hand, prevent users from deleting or renaming files they don&amp;rsquo;t own in a shared directory.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
