Image builds create a key separate from the SecureBoot one for verity signing. Its certificate ships inside the image as the sysext trust anchor. `genkey` certs had a hardcoded "SecureBoot signing key on host <fqdn of the build machine>" CN, which describes neither that verity role nor a meaningful hostname. Make that name configurable with `SecureBootCertificateCommonName=`, like mkosi's `--genkey-common-name`. That allows image build tools to re-use `ukify genkey` for non-SB keys. Unlike the implicit truncation for the default name, a specified one which is too long is an error. Add a citation where that limit comes frm.
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
