This adds a new cloud IMDS client, that can cover AWS, Azure, GCP, Hetzner imds to varying degrees. Each cloud has this and it's very basic functionality, hence I think it makes sense to add this to systemd. Since the clouds are all different this tries hard to do the abstract common logic in code, but encode the endpoint details, and well-known keys in hwdb, attached to the DMI id device. Why all this? * Efficiency: we can schedule this in the initrd, at the earliest points possible, without unnecessary delays * Robustness: imds is typically slow and/or heavily rate-limited: systemd-imdsd as single entrypoint can deal with that, and provide a reliable, cached interface * Security: the idea is that systemd-imdsd is the only service behing able to access the IMDS HTTP, and the host carries a blackhole route for it otherwise. That way sensitive info can be kept away from clients, and requires polkit auth for access * Simplicity: extraction of systemd's system credentials from IMDS userdata happens with systemd's own infra, and for many usecases that should already be enough. * Measurements: before accepting the IDMS userdata, it can be measured into a PCR, as any other configuration input for the system Fixes: #40763
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
