Christian Brauner
9bb5d21c15
Right now RestrictFileSystemAccess= checks that a file comes from a trusted dm-verity device, but it doesn't guard against mapping that file and making use of COW modifications. So a MAP_PRIVATE mapping of a trusted binary can be made writable, modified, and executed, while the vma still points to the trusted file and the pages are attacker-controlled anonymous copies. Enforce W^X: deny any mapping that is writable and executable at once, and refuse to make a private file mapping executable once it has been modified through copy-on-write. Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
System and Service Manager
Details
Most documentation is available on systemd's website.
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