feat: rootless su for pebble - #25
Open
hpidcock wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pebble service layers can specify
user/user-idandgroup/group-idtorun a service as a different Linux user. Today, switching user requires Pebble
itself to be running as root (UID 0): the service is started with
setresuid(2)/setresgid(2)applied betweenfork(2)andexecve(2),and the kernel only honours those calls for privileged callers.
Pebble is often run as a non-root user inside a container (security best
practice; rootless Podman / Kubernetes
runAsNonRoot), but the workloadstill needs to drop further to a different unprivileged uid (e.g.
nobody,an app-specific user).
yuzuis a prototype privilege-delegation tool built to handleexactly this Pebble use case. It is a setuid-per-profile helper that lets an unprivileged
Pebble process exec a command as another user, with authorisation governed by a config
file written at image-build time rather than by host-level privilege.
This spec proposes that, when Pebble is not running as root and the
yuzubinary is available on
PATH, Pebble starts services that request a useror group switch by exec'ing them through
yuzuinstead of callingsetresuid/setresgiddirectly.