4be269563d
let's skip over credentials we cannot decode when they are found with ImportCredential=. When installing an OS on some disk and using that disk on a different machine than assumed we'll otherwise end up with a broken boot, because the credentials cannot be decoded when starting systemd-firstboot. Let's handle this somewhat gracefully. This leaves handling for LoadCredential=/SetCredential= as it is (i.e. failure to decrypt results in service failure), because it is a lot more explicit and focussed as opposed to ImportCredentials= which looks everywhere, uses globs and so on and is hence very vague and unfocussed. Fixes: #34740
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