If we are asked to come up with our own name for the namespace to allocate (because client enabled "mangle"), then we so far created a randomized name if shortening what was proposed didn't work. This broke polkit authorization however, because when polkit is in the mix, we process method calls twice, submitting the polkit request on the first and then assuming a response is known on the second invocation. But if we generate a randomized name for the two checks we'll not be ablet to match up the requests because it's going to be different. Let's fix that by not using a randomized name, but one hashed from the socket connection we are processing mixed with the client provided name. This will ensure that for the same method call we'll generate the same name, but different calls (i.e. calls with different names on the same socket, or with any name on any socket) we'll end up with different names, minimizing chance of collision. This ensures PK starts to work with nsresourced userns registration when a bad or no name is specified, which previously would end up in a PK query loop.
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
