Files
keru/privilege-elevation.html
T
Astral 4a32fab414
Deploy website to GitHub Pages / deploy (push) Failing after 3s
migrate website from KeruOS web to its own repo
2026-09-01 12:06:36 +02:00

53 lines
3.0 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Privilege elevation — Keru OS</title>
<meta name="description" content="How you gain root with Keru: doas, sudo, opendoas, or su. You decide.">
<link rel="stylesheet" href="assets/css/style.css">
<link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><text y='.9em' font-size='90'>ける</text></svg>">
</head>
<body>
<nav class="top" data-nav></nav>
<header class="pagehead">
<p class="crumbs"><a href="index.html">home</a> / <a href="swappables.html">swappables</a> / privilege elevation</p>
<h1>Privilege elevation</h1>
<p>How you become root. Your choice.</p>
</header>
<section>
<div class="wrap">
<div class="prose">
<p>Even "sudo" isn't sacred in Keru. How you elevate privileges is a swappable — the question of which <code>su</code>-style tool runs your privileged commands is settled by you, at install, alongside everything else.</p>
</div>
<div class="grid grid-4" style="margin-top:30px">
<div class="card"><span class="h">doas</span><p>The default. OpenBSD's elegant, minimal replacement for sudo — small config, fewer lines, no surprise policies.</p></div>
<div class="card"><span class="h">sudo</span><p>The familiar heavyweight. Fine-grained policies (<code>sudoers</code>), broad ecosystem familiarity.</p></div>
<div class="card"><span class="h">opendoas</span><p>A portable, independently-maintained doas implementation for Linux — the doas philosophy with a maintained port.</p></div>
<div class="card"><span class="h">su</span><p>The classic. No added abstraction — switch user and run what you need, as basic as it gets.</p></div>
</div>
<div class="prose" style="margin-top:34px">
<h3>Why this is on the list</h3>
<p>Privilege elevation touches everything an admin does, and it's usually a foregone conclusion: "you get sudo." Keru treats it as what it is — a tool with tradeoffs — and lets you pick the flavor. If you believe in two-line configs, <code>doas</code>. If you need <code>sudoers</code> granularity, <code>sudo</code>. If you want zero abstraction, <code>su</code>.</p>
<p>Whichever you choose gets built in stage 2 as part of your profile, alongside your kernel and init. Nothing preinstalled, nothing assumed.</p>
<div class="callout">Small opinion, stated plainly: <code>doas</code> is the default because two lines of config beats two hundred. But it's a default, not a dogma — swap it freely.</div>
<p><a href="swappables.html">← All swappables</a></p>
</div>
</div>
</section>
<footer data-footer></footer>
<noscript><div style="text-align:center;padding:16px">See the <a href="sitemap.html">sitemap</a> for all pages.</div></noscript>
<script src="assets/js/include.js" data-base="."></script>
</body>
</html>