[Bug 1384973] Re: shim prints "Booting in insecure mode" when booting without SecureBoot enabled

[Steve Langasek]

On Fri, Jul 22, 2016 at 08:58:53PM -0000, Mark wrote:
> I triggered this situation when trying to install a proprietary NVIDIA
> driver.  This driver cannot be loaded into the kernel.  First must its key
> being registered in the bios.  During install of the driver I'm asked to
> switch off UEFI secure boot and then reboot.  On reboot a blue screen
> appears with MOK management.  The process is failing, the driver is not
> installed correctly and also brings this problem with "Booting in insecure
> mode".

This bug was about shim printing a warning about booting in insecure mode
when SecureBoot was not enabled in your firmware.  That is not why you are
seeing this message.  You are seeing this message because *you have
configured your system to boot in insecure mode*, overriding SecureBoot in
MOK, which is a prerequisite for newer kernels to load unsigned modules
(such as the nvidia driver).

If you are seeing this message on boot, *and* the nvidia driver is not
loading for you, then there is a bug somewhere other than shim and you
should file a new bug report about this.

-- 
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/1384973

Title:
  shim prints "Booting in insecure mode" when booting without SecureBoot
  enabled

Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in shim source package in Vivid:
  Fix Released
Status in shim-signed source package in Vivid:
  Fix Released

Bug description:
  shim 0.7 has an unfortunate bug where when booting with SecureBoot
  disabled (i.e., in setup mode), it will print the message "Booting in
  insecure mode" and pause for two seconds before booting.

  This has been corrected upstream in commit
  d95b24bd02cf41cca9adebd95f10609d6424d2b3, which postdates 0.7.  We
  will include this fix in the next upload of shim (dependent on a
  Microsoft round-trip for signing).

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