This bug was fixed in the package shim-signed - 1.33.1~16.04.4 --------------- shim-signed (1.33.1~16.04.4) xenial; urgency=medium
* 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-2ubuntu11.5~) since we're changing the behavior of update-secureboot-policy. -- Mathieu Trudel-Lapierre <cypher...@ubuntu.com> Mon, 28 Jan 2019 10:22:31 -0500 ** Changed in: shim-signed (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs