Runic.Platform.Linux.Polkit 0.13.0

Runic.Platform.Linux.Polkit

Declared privileged actions for Runic applications on Linux: the build generates a Polkit policy, and the application runs each action through pkexec with an argument vector, never a shell.

Preview API targeting .NET 10. The contract, IDesktopPrivilegedActions, is in Runic.Platform; on Windows and macOS PolkitPrivilegedActions.Create returns a provider that reports every request unavailable. The design, the per-platform decisions and the security review are in privileged operations.

Declare actions

Declare each action once, as an item in the application's project:

<ItemGroup>
  <PackageReference Include="Runic.Platform.Linux.Polkit" />
  <RunicPrivilegedAction Include="org.example.app.activate"
                         Program="$(RunicApplicationInstallPrefix)/libexec/example/example-helper"
                         Verb="activate"
                         Description="Activate a system configuration"
                         Message="Authentication is required to activate the system configuration."
                         PolkitIconName="system-software-update"
                         MaximumArguments="2"
                         ArgumentPattern="switch|boot|/nix/store/[a-z0-9]{32}-nixos-system-[A-Za-z0-9._+-]+" />
</ItemGroup>

The items, their shared metadata and the generated PrivilegedActions class come from Runic.Platform, which this package depends on; see Declare privileged actions. This package adds the Polkit policy and the metadata only Polkit reads, named with a Polkit prefix like WindowsProgram and MacProgram of the other platforms (PolkitIconName, PolkitAllowAny, PolkitAllowInactive, PolkitAllowActive and PolkitAllowGui).

RunicApplicationInstallPrefix is the prefix the application is installed under, /usr unless the build sets it. The Nix builder sets it to the package's $out, where the program is its wrapper $(RunicApplicationInstallPrefix)/bin/<executable>. A package installed elsewhere sets it in the project or on the command line, for example dotnet publish -p:RunicApplicationInstallPrefix=/opt/example; an environment variable of the same name works too. The policy and the generated class carry the path, so the build must name the prefix the package installs under.

Declare the actions in one project. When the privileged program is a separate project, give both projects the same items, for example from one imported .props file, and set RunicPolkitPolicyCopyEnabled to false in all but one of them, so exactly one policy file declares each action ID.

Each build writes, under obj/.../runic-privileged/:

• PrivilegedActions.g.cs (from Runic.Platform's targets): an internal PrivilegedActions class in the root namespace with one PrivilegedActionDeclaration property per action and All. Both the application and the privileged program use it.
• <RunicPolkitPolicyName>.policy, copied to the output and publish directories at share/polkit-1/actions/. Install it in /usr/share/polkit-1/actions. The Nix builder installs it in $out/share/polkit-1/actions, which NixOS links into the system's actions directory when the package is in environment.systemPackages (the NixOS module does that). Without it, pkexec falls back to its generic org.freedesktop.policykit.exec action and asks for an administrator with a generic message.

Invalid declarations are build errors RUNICPA001 to RUNICPA013: Runic.Platform reports the shared ones first, then this package RUNICPA010, RUNICPA012 and RUNICPA013, and the warning RUNICPA014. A project that still sets a former name, RunicPolkitPolicy or the metadata AllowAny, AllowInactive, AllowActive, AllowGui or IconName, fails with RUNICPA108, which names the replacement; the old names no longer apply. They are described in the diagnostics catalog.

Run an action

IDesktopPrivilegedActions actions = PolkitPrivilegedActions.Create(PrivilegedActions.All);

var result = await actions.RunAsync(
    new PrivilegedActionRequest(PrivilegedActions.Activate, ["switch", storePath])
    {
        Output = line => log.Append(line.Channel, line.Text),
    },
    cancellationToken);

switch (result)
{
    case PlatformResult<PrivilegedActionCompletion>.Success(var completion) when completion.Succeeded: /* done */ break;
    case PlatformResult<PrivilegedActionCompletion>.Success(var completion): /* the program failed: completion.ExitCode */ break;
    case PlatformResult<PrivilegedActionCompletion>.Failed { Code: PlatformFailureCode.PermissionDenied }: /* policy refused */ break;
    case PlatformResult<PrivilegedActionCompletion>.Failed { Code: PlatformFailureCode.UserDismissed }: /* dialog closed */ break;
    case PlatformResult<PrivilegedActionCompletion>.Unavailable: /* no polkit, no agent, no pkexec */ break;
    case PlatformResult<PrivilegedActionCompletion>.Failed failed: /* failed.Code, failed.Diagnostic */ break;
}

A request whose action the provider was not created with, or whose arguments are outside the declaration, throws ArgumentException before anything runs. Check untrusted input first with PrivilegedActionDeclaration.AcceptsArguments.

Output receives lines from standard output and standard error as they arrive, one call at a time on a worker thread. The program waits while the callback runs, so output never piles up in memory. Lines from the two streams are not ordered relative to each other; a line longer than 16 KiB arrives in parts. An exception from the callback stops further calls and is rethrown after the program exits.

Cancellation while pkexec waits for authorization stops it, closes the dialog and throws OperationCanceledException. Once the program runs as root, the application can no longer signal it: cancellation closes the program's standard input and the result reports how the program ended. An application that itself runs as root (under sudo) cannot tell pkexec from the program, so it never kills: it always closes the input and waits. pkexec is signalled through a pidfd where the kernel has one (Linux 5.3), so a reused process ID is never hit.

pkexec exits with 126 and 127 when authorization was dismissed or refused, and otherwise with the program's code. A program that exits with 126 or 127, or prints pkexec's messages, is reported as dismissed, denied or unavailable although it ran. For an action that is not idempotent, check the system's state before concluding that nothing happened.

pkexec gets a minimal environment: the locale, TERM, DISPLAY and XAUTHORITY, and PATH=/usr/sbin:/usr/bin:/sbin:/bin. In particular it gets no SHELL, because pkexec refuses a SHELL that /etc/shells does not list, such as the store path a nix develop shell sets.

By default pkexec gets --disable-internal-agent, so an application without a graphical authentication agent reports unavailable rather than prompting on a terminal. PolkitOptions.AllowTerminalAuthentication lets a command-line tool prompt on its controlling terminal. PolkitOptions.PkexecPath selects pkexec; by default the provider looks in /run/wrappers/bin, /usr/bin and /bin, never PATH, and uses only a setuid-root binary.

Write the privileged program

pkexec runs the program as root with any arguments any local user passes, as far as the policy allows. The program must check them again; the application's check only catches mistakes early.

// Match first resets the process state and fails closed when this is not root for a pkexec caller.
if (PolkitHelper.Match(PrivilegedActions.All, args, out var arguments) is not { } action)
    return 2;
var caller = PolkitHelper.GetCallerUserId();
var stop = PolkitHelper.WatchCancellation(); // cancelled when the application cancels or dies
// Then check positions and meaning yourself: resolve each path with realpath(3), check the resolved
// path (a NixOS system with bin/switch-to-configuration) and use only the resolved path from then on.

• ArgumentPattern applies to every argument. Positional rules, such as "first a mode, then a store path", can be declared as commands (RunicPrivilegedCommand, see Commands under one action), which Match checks; the program then switches on the command name, the first of arguments. Checks against the system belong in the program. Resolve paths (realpath), check the resolved path again and use only it. A store-path pattern is not a trust boundary: any user can create /nix/store/<hash>-nixos-system-x by building it, so an action that activates a system must stay auth_admin.
• PolkitHelper.Initialize, which Match calls, resets what pkexec takes over from the caller: the working directory becomes / (pkexec --keep-cwd keeps the caller's), the umask 022 and the nice value 0; signals the caller ignored are default again (except SIGPIPE, which .NET ignores itself); the signal mask is emptied; core dumps are off; the CPU time, address space, data and file size limits are lifted; at least 1024 open files are allowed; and oom_score_adj is 0. The scheduling policy, CPU affinity and stack limit stay as the caller set them.
• The signal mask is per thread: Initialize empties the calling thread's, and threads and processes started from it later inherit that, but threads the runtime started before keep the caller's mask. Call Match (or Initialize) first in Main, before starting threads or processes, and start child processes from that thread or threads created after it.
• Initialize returns false, and Match null, when the process is not root (as when pkexec ran with --user and another user; --user root is accepted), is a 32-bit process, or a reset fails. pkexec always sets PKEXEC_UID.
• pkexec clears the environment; PATH is a fixed list (root's system profile on NixOS). Call tools by absolute path and read nothing from the caller's environment; PKEXEC_UID names the caller.
• Do not exit with 126 or 127: pkexec uses them for dismissed and refused authorization.
• When the application dies, nothing signals the program: the kernel clears pkexec's parent-death signal when pkexec becomes root. Standard input reaches its end, so a program using WatchCancellation stops, and one that ignores its input runs on. Its own writes to standard output go nowhere (.NET's console drops them), and the tools it starts get write errors or SIGPIPE. Run steps that must finish, such as switch-to-configuration, with redirected output or in their own systemd unit (systemd-run), as nixos-rebuild does.
• Install the whole application root-owned and unwritable by others: the program, its directory, its runtime and any wrapper script's targets. The provider's check of the program path only catches deployment mistakes. Prefer a NativeAOT build for the privileged program, which loads no runtime or assemblies from elsewhere.