-
Story
-
Resolution: Done-Errata
-
Major
-
rhel-9.3.0
-
None
-
systemd-252-27.el9
-
None
-
-
rhel-sst-cs-plumbers
-
ssg_core_services
-
26
-
13
-
Dev ack
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
Pass
-
-
Automated
-
None
Support for remote (when only public key from the target TPM is available) secret sealing and consumption of the remotely sealed data was added to systemd-cryptsetup/systemd-cryptenroll, see https://github.com/systemd/systemd/pull/28519 and its pre-requisites:
- https://github.com/systemd/systemd/pull/29234
- https://github.com/systemd/systemd/pull/29183
- https://github.com/systemd/systemd/pull/29426
- https://github.com/systemd/systemd/pull/29427
The functionality is needed for RHEL on Confidential VMs on Azure where root volume is pre-encrypted by Azure infrastructure. Currently, RHEL uses a downstream-only solution:
- https://gitlab.com/vkuznets/tpm2-luks-import
which we'd like to get rid of.
- is duplicated by
-
RHEL-16266 Remote volume key sealing with standard systemd tools
- Closed
- links to
-
RHSA-2023:125388 systemd bug fix and enhancement update
- mentioned on
(1 links to, 1 mentioned on)