On Thu, Oct 05, 2017 at 01:52:46AM -0000, bugproxy wrote: > ------- Comment From gcwil...@us.ibm.com 2017-10-04 17:33 EDT------- > I have received the KEK from Emily in person.
> ------- Comment From gcwil...@us.ibm.com 2017-10-04 18:16 EDT------- > BTW, I learned from Emily that Canonical plans to issue Power keys/certs > separately from those for the x86 UEFI shim. So moving from SHA-512 to > SHA-256 may not be much of a priority from a reuse point of view. If we > need any key changes, it would be good to send them before or during next > week while Emily will be in NY meeting with vorlon. Yes, if you need the hash changed from SHA512 to SHA256 on the 2048-bit db key, please let us know this week so that we can arrange to have a new ESL signed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1696154 Title: [17.10 FEAT] Sign POWER host/NV kernels Status in Launchpad itself: Fix Committed Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-signed package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
