Bug 2182653 - Add a new cert for signing UKI
Summary: Add a new cert for signing UKI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: redhat-release
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Release Engineering Bug Triage
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-29 08:57 UTC by Vitaly Kuznetsov
Modified: 2023-05-02 19:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-02 19:04:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELBLD-12547 0 None None None 2023-03-29 08:58:52 UTC
Red Hat Issue Tracker RHELPLAN-153396 0 None None None 2023-03-29 08:58:57 UTC

Description Vitaly Kuznetsov 2023-03-29 08:57:09 UTC
Unified Kernel Image (UKI) was added to RHEL9.2 and Fedora/ARK recently (kernel-uki-virt package). The image is currently signed with the same SecureBoot certificate as our standard kernel (vmlinuz) and we'd like to change that. The main motivation for creating a new certificate for UKI is to make it possible to distinguish between standard vmlinuz and UKI in PCR measurements, namely PCR7. 

Currently, for Azure Confidential VMs we seal root volume key against PCR4+PCR7 and this is suboptimal as PCR4 changes with every UKI update. We'd like to switch to sealing against PCR7 only but in that case measurements for standard vmlinuz and for UKI must differ and this is not the case with the current signing scheme.

We need to introduce a new certificate for signing UKIs and export its public part in redhat-sb-certs to be able to switch to in in the kernel specfile. We also want to do the same change in Fedora/ARK.

(I may be missing some details on how new SB certs are added, hope the BZ is the right starting point)

Comment 3 Lisa S 2023-05-02 19:04:33 UTC
Closing this as a redhat-release component bug, as it needs to be filed with the ProdSec team (and they are not in Bugzilla).


Note You need to log in before you can comment on or make changes to this bug.