[Bug 1590668] [NEW] Shim now reports "booting in insecure mode" regardless of BIOS setting

[Broadsworde]

Public bug reported:

I just installed a nice fresh Ubuntu 16.04 on my Samsung Series 5
Laptop, and noted the new option in the install screens that required a
password to disable secure mode booting - I unsuspectingly choose that
option, as I wanted to install the 3rd party support options. So then on
reboot it takes me through my new secure boot password (random letters)
and hey presto I'm now booting insecurely... and get this 2 to 3 second
message telling me so (slowing down the boot process). Further research
showed me that all the OS needs is for Secure Booting to be turned off
in BIOS, so, erm... why didn't they just get the user to do that ahead
of time, or at least give a fulsome explanation for those who need to
dual-boot.

Anyway, my question: Now that I have this "Booting in insecure mode"
message in my boot process, how do I get rid of it. I have of course
tried reinstalling a number of times with Secure Boot in BIOS on and
off.

I have subsequently found out this is a SHIM issue, which is why I'm
posting this bug.

Your assistance would be very much appreciated.

** Affects: shim (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  Shim now reports "booting in insecure mode" regardless of BIOS setting

Status in shim package in Ubuntu:
  New

Bug description:
  I just installed a nice fresh Ubuntu 16.04 on my Samsung Series 5
  Laptop, and noted the new option in the install screens that required
  a password to disable secure mode booting - I unsuspectingly choose
  that option, as I wanted to install the 3rd party support options. So
  then on reboot it takes me through my new secure boot password (random
  letters) and hey presto I'm now booting insecurely... and get this 2
  to 3 second message telling me so (slowing down the boot process).
  Further research showed me that all the OS needs is for Secure Booting
  to be turned off in BIOS, so, erm... why didn't they just get the user
  to do that ahead of time, or at least give a fulsome explanation for
  those who need to dual-boot.

  Anyway, my question: Now that I have this "Booting in insecure mode"
  message in my boot process, how do I get rid of it. I have of course
  tried reinstalling a number of times with Secure Boot in BIOS on and
  off.

  I have subsequently found out this is a SHIM issue, which is why I'm
  posting this bug.

  Your assistance would be very much appreciated.

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