<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux-System-Administration on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/linux-system-administration/</link>
    <description>Recent content in Linux-System-Administration on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/linux-system-administration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Privilege Escalation Management: sudo vs doas vs polkit</title>
      <link>https://www.pistack.xyz/posts/2026-05-25-self-hosted-linux-privilege-escalation-sudo-vs-doas-vs-polkit-guide/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-25-self-hosted-linux-privilege-escalation-sudo-vs-doas-vs-polkit-guide/</guid>
      <description>&lt;p&gt;When managing self-hosted Linux servers, controlling who can execute privileged commands is a foundational security requirement. The default root account should never be used directly for day-to-day administration. Instead, privilege escalation tools provide audited, configurable, and constrained access to elevated permissions. Three dominant approaches have emerged in the Linux ecosystem: &lt;strong&gt;sudo&lt;/strong&gt;, the ubiquitous standard; &lt;strong&gt;doas&lt;/strong&gt;, the minimalist alternative from OpenBSD; and &lt;strong&gt;polkit&lt;/strong&gt; (PolicyKit), the desktop-focused authorization framework that has found its way into server workflows.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
