LUKS2 supports built-in integrity checking which may come very handy to mitigate partial rollback attacks on the storage when only some specific parts are restored to some old encrypted state. Specific use-cases like Confidential VMs may want to mandate the usage of feature e.g. on the root volume. Introduce "encryptedwithintegrity" image policy to support that. Note, due to the current libcryptsetup limitations, checking whether the feature is enabled or not for the 'file' case (e.g. DDI image as a raw file) requires setting up a loop device. To avoid that and keep dissect fully functional when working unpriviliged, implement a minimal custom LUKS header parser.
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
