On Thu, Sep 07, 2017 at 11:50:09PM -0000, bugproxy wrote: > ------- Comment From l...@us.ibm.com 2017-09-07 19:41 EDT------- > (In reply to comment #25) > > Does IBM have any feedback for us regarding the test kernel Andy provided?
> We're planning to test this month. We'll give feedback as soon as the > test is completed. The tentative target will be Sept. 29 or sooner. > > Can you please clarify if this means you are expecting the db entry to be > > delivered as an x509 certificate issued by the CA key listed in KEK, or if > > it should be delivered according to the format defined in the UEFI spec for > > authenticated variable updates? > Our team needs to have some discussions before finalizing the expected > format. We'll get back to you soon. Thanks! Thanks. Do you have a timeline for when you will have this decision? While we have procedures in place for signing/revoking keys whenever necessary in the event of a key compromise, ordinarily this KEK key is not available for signing. We have a window when we will be able to do this signing from September 25 to September 29 and after that we do not have a window scheduled until next year, so it would be good to know before then what format you need this signed key matter to be provided in. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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
