[Bug 1641793] [NEW] Invalid Signature detected -- must uncheck secure boot

Steve Langasek steve.langasek at canonical.com
Tue Nov 22 00:02:47 UTC 2016


On Tue, Nov 15, 2016 at 02:20:11AM -0000, TedM wrote:

> I executed a suggested command "bcdedit /set {bootmgr} path
\EFI\ubuntu\grubx64.efi"

As noted, this is a bad suggestion.  I have proposed an edit to the
askubuntu.com answer to fix this.

On Mon, Nov 21, 2016 at 10:01:46PM -0000, TedM wrote:
> Thanks for your explanation.  I am satisfied with the way my system
> works now.  I get the grub menu and can start either Ubuntu or Windows.
> I do not have the secure boot, but I never had it in previous systems.
> Is there really any advantage of having secure boot?

It protects your firmware from malware attacks launched from under the OS. 
I certainly recommend using Secure Boot whenever feasible.

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

Title:
  Invalid Signature detected -- must uncheck secure boot

Status in shim package in Ubuntu:
  Incomplete

Bug description:
  This occurred after a fresh install of 16.04 on an Acer Desktop.  At the start only Windows would boot -- no Grub2 screen appeared.  I made a number of attempts following "https://help.ubuntu.com/community/UEFI"  Nothing worked and they suggested trying "http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-windows-10-with-uefi"
  I executed a suggested command "bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi"
  This gave the Grub2 menu but only in unsecure boot mode.
  The same document says to send a bug report if an invalid signature is detected.  I am doing that.  However in doing so i note that the bug report is sent to "shim".  But the instructions said to set the path to "grub64.efi" and not "shimx64.efi" which was also available in the /boot/EFI folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: shim 0.8-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 14 20:47:37 2016
  Dependencies:
   
  EFIBootMgr:
   BootCurrent: 0001
   Timeout: 2 seconds
   BootOrder: 0001,0000
   Boot0000  ubuntu	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
   Boot0001* Windows Boot Manager	HD(1,GPT,a30e4f73-c41a-4d41-8b33-8bc3beb73cc0,0x800,0x32000)/File(\EFI\ubuntu\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...}................
  InstallationDate: Installed on 2016-11-12 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  SourcePackage: shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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



More information about the foundations-bugs mailing list