Deployment to production seems successful.  I have uploaded a modified
kernel to a PPA and built a signed kernel image from that.  I am
attaching that signed kernel and the public key component of the signing
key for it.  NOTE: this key is _not_ a final official canonical key it
is a key for a PPA and for testing only.

There are two files:

  vmlinux-4.11.0-13-generic.opal.signed -- this is the bootable signed binary
  opal.x509 -- the DER format public key with which this binary is signed

Any testing, review appreciated.  Please report back to this bug.

** Also affects: linux-signed (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux-signed (Ubuntu)
       Status: New => In Progress

** Changed in: linux-signed (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-signed (Ubuntu)
   Importance: Critical => High

** Changed in: linux-signed (Ubuntu)
     Assignee: (unassigned) => Andy Whitcroft (apw)

** Attachment added: "opal.x509"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1696154/+attachment/4932055/+files/opal.x509

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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

Reply via email to