So far, when we tried to match a component to eent log entries we skipped those components if they were outside of our location window. That however is too aggressive, since it means any components that are already in the logs, but outside of the location window will be considered unrecognized in the logs, and thus removed from the PCR policy. Change things around: always try to match up all components, regardless if inside the location window or outside, but then make it non-fatal we can't find a component outside of the location window. Fixes: #36079
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
