Paul Meyer
76b62b0435
Previously, --load-credential / --set-credential were rejected outright under --coco=sev-snp because the SMBIOS type-11 transport isn't covered by the launch measurement. PID1 wouldn't have accepted those credentials anyway (import_credentials_smbios() refuses any SMBIOS-sourced credentials under a confidential VM). Instead, when SNP is in use and credentials are present, synthesize a newc cpio archive containing each credential at .extra/system_credentials/<id>.cred and append it to the initrd list. The existing merge_initrds() path then concatenates it into the single initrd file QEMU loads, which kernel-hashes=on covers in the SEV-SNP launch digest. PID1's import_credentials_boot() picks them up from the trusted /.extra/system_credentials/ path and routes them to the @system bucket, so units can consume them via LoadCredential= unchanged. Direct kernel boot (--linux=) is already required under SNP, so the initrd is always under our control here. The cpio synthesis happens after all internal machine_credential_add()/machine_credential_load() call sites so the archive captures the complete credential set (journal forwarding, vmm.notify_socket, ssh ephemeral keys, etc.). The cpio path is intentionally scoped to SNP: it requires a guest PID1 that knows about /.extra/system_credentials/, and we don't want to regress credential delivery for non-CoCo guests running older systemd versions in the guest. Consider switching when the new path is widely available. Signed-off-by: Paul Meyer <katexochen0@gmail.com>
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, and also repositories with packages built from the latest stable release