[Bug 1817950] Re: mokutil --sb-state reports SecureBoot enabled when it isn't

[Mathieu Trudel-Lapierre]

Reassigning to mokutil and marking Fix Released:

I fixed that a few weeks ago. Mokutil reports the state it knows how to,
and that was previously only checking the state of the SecureBoot-*
variable, which is separate from the state that can be toggled in shim.

Now, mokutil looks at SecureBoot, SetupMode, and the MokSBStateRT
variable (the one set by shim), and should display an appropriate
message depending on the exact state of the system.

** Package changed: grub2 (Ubuntu) => mokutil (Ubuntu)

** Changed in: mokutil (Ubuntu)
       Status: New => Fix Released

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

Title:
  mokutil --sb-state reports SecureBoot enabled when it isn't

Status in mokutil package in Ubuntu:
  Fix Released

Bug description:
  mokutil --sb-state

  says

  SecureBoot enabled

  But I've followed the instructions at https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS to disable SecureBoot and I get the message that I'm booting in insecure made at startup. In fact, running unsigned mainline kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-09 (79 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  Package: grub2 (not installed)
  Tags:  cosmic
  Uname: Linux 4.20.13-042013-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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