Does IBM have any feedback for us regarding the test kernel Andy provided? We have generated an online signing key to be included in db for OPAL. In the absence of feedback about whether 4096-bit keys are supported, we have generated a 2048-bit key.
Our current plan for secure delivery of the public key to IBM is to deliver the keys in person to George next month. Does this timeline fit IBM's needs for receipt of the public keys? Does it meet your expectations for a trust path for the keys, or is there another protocol that should be used? In your reply of August 1, you wrote: > However, in order to add a certificate to DB, the certificate should be > signed by any of the KEK entries. The PK will be used to authorize updates > to the KEK certificate list. 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? -- 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
