* update-secureboot-policy: (LP: #1748983)
- Backport update-secureboot-policy changes to generate a MOK and guide
users through re-enabling validation and automatically signing DKMS
modules.
* debian/shim-signed.postinst:
- When triggered, explicitly try to enroll the available MOK.
* debian/shim-signed.install, openssl.cnf: Install some default configuration
for creating our self-signed key.
* debian/shim-signed.dirs: make sure we have a directory where to put a MOK.
* debian/templates: update templates for update-secureboot-policy changes.
* debian/control: Breaks dkms (<< 2.2.0.3-1.1ubuntu5.14.04.10~) since we're
changing the behavior of update-secureboot-policy.
This bug was fixed in the package shim-signed - 1.33.1~14.04.4
---------------
shim-signed (1.33.1~14.04.4) trusty; urgency=medium
* update- secureboot- policy: (LP: #1748983) secureboot- policy changes to generate a MOK and guide shim-signed. postinst: shim-signed. install, openssl.cnf: Install some default configuration shim-signed. dirs: make sure we have a directory where to put a MOK. secureboot- policy changes. 1.1ubuntu5. 14.04.10~ ) since we're secureboot- policy.
- Backport update-
users through re-enabling validation and automatically signing DKMS
modules.
* debian/
- When triggered, explicitly try to enroll the available MOK.
* debian/
for creating our self-signed key.
* debian/
* debian/templates: update templates for update-
* debian/control: Breaks dkms (<< 2.2.0.3-
changing the behavior of update-
-- Mathieu Trudel-Lapierre <email address hidden> Mon, 28 Jan 2019 11:02:00 -0500