a38b4c39ff
`systemd-analyze security --user foo.service` currently flags units without `User=` as running as root. For user manager instances this is impossible: per systemd.exec(5), switching user identity is not permitted there, so the service always runs under the calling user's UID. Track the runtime scope inside SecurityInfo and short-circuit security_info_runs_privileged() and assess_user() for RUNTIME_SCOPE_USER, so that User=/DynamicUser=, SupplementaryGroups= and RemoveIPC= are no longer marked as if the service ran as root in both the bus-backed and --offline paths. Fixes #40292 Signed-off-by: Shihao Ren <renshihao.rsh@bytedance.com>
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release