PCR 16 is intended for debugging purposes, and is the only PCR that can be reset by software. Let's prefer that for testing. PCR 11 has a purpose (i.e. kernel is measured there on UKI systems, as are the boot phases), hence let's not use that for testing. That should remove any interference of boot time ordering and testing our tpm code, as we will write to PCR 16 only, and reset it before we rely on it. This likely, kind of fixes #39582, but the issue mixes two things, PCR 11 issues on real-life hardware, and PCR 11 isues in our artificial tests. Only the latter is addressed by this PR, the other issue needs more debugging, but without logs we cannot do much.
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
