Public bug reported:
[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.
** Affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680279
Title:
attach secureboot state files to shim-signed apport reports
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1680279/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
