Currently systemd-tpm2-setup will fail if NvPCR initialization doesn't succeed, either because the currently booted UKI carries no PCR public key, or it carries no appropriate signed policy (one with the "initrd" policy reference). In addition to this, systemd-pcrextend will subsequently fail because it also fails to initialize the NvPCR it is requested to extend. This makes systemd-tpm2-setup return EX_CONFIG in these scenarios, with this marked as a successful exit status in the service unit file. In addition to this, systemd-pcrextend is updated to only attempt NvPCR initialization from the initrd (the only place it will succceed), and when called with --graceful, to not exit with an error code if the target NvPCR is uninitialized, and can't be initialized because of a missing PCR public key or appropriate signed policy. When called via Varlink, it will return the existing "NoSuchNvPCR" error. Note that I also removed some NvPCR initialization specific exit status codes from systemd-tpm2-setup.service.in, as these can only be returned via systemd-tpm2-setup-early.service. This should address the issues in https://github.com/systemd/systemd/issues/43848. (cherry picked from commit e846bbad04d87e58ba9c3e30d8a1087141691715)
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
