[Bug 1680279] Re: attach secureboot state files to shim-signed apport reports

[Mathieu Trudel-Lapierre]

Verification-done for xenial; using shim-signed 1.32~17.04.1:

The right elements now include a human-readable content (which is what
the latest SRU changes) in the apport-generated crash files
(specifically, MokSBStateRT values if present, along with SecureBoot
state).

** Tags removed: verification-needed verification-needed-yakkety verification-needed-zesty
** Tags added: verification-done-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1680279

Title:
  attach secureboot state files to shim-signed apport reports

Status in shim-signed package in Ubuntu:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed
Status in shim-signed source package in Yakkety:
  Fix Committed
Status in shim-signed source package in Zesty:
  Fix Committed

Bug description:
  [SRU Justification]
  I'm asking the same questions repeatedly of bug submitters about the state of secureboot on their systems, so we should just include these files in the apport hook.  Since shim-signed changes in stable releases for policy reasons, this should be SRUed back in as well.

  [Test case]
  1. Install the shim-signed package from -proposed
  2. Run apport-bug shim-signed
  3. Confirm that the apport collection succeeds
  4. Verify that the report to be sent includes keys for two files under /sys/firmware/efi/efivars and for /proc/sys/kernel/moksbstate_disabled

  [Regression potential]
  If I done messed up, we could fail to get bug reports about shim that we really need.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1680279/+subscriptions