[Bug 2036812] Re: No MOK enrolment for a secure boot installation

[Dan Bungert]

There are two angles on this:

1. It's OK that it doesn't always prompt for MOK enrollment
2. But we probably want to actually do MOK enrollment sometimes.

I understand that item 1 is a change from Ubiquity, but in some cases
that's OK.  Just because we search for drivers to install doesn't mean
there actually are any that match the hardware, so that case does not
require MOK enrollment.  And other cases like the nvidia (which are non-
DKMS) drivers also do not require MOK enrollment today.  Really this is
about DKMS drivers, which means that this report is the same as LP:
#2008142.

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

Title:
  No MOK enrolment for a secure boot installation

Status in subiquity package in Ubuntu:
  New

Bug description:
  Testing Ubuntu Budgie 23.10 beta

  Virtualbox 7- EFI + Secure boot chosen.

  I chose the proprietary graphics/wifi option.

  I noted that no screen was offered to select an enrolment password.

  After installation on reboot that was confirmed that no MOK enrolment
  was requested.

  I repeated this with the legacy ISO.  This time ubiquity asked for an
  enrolment password and on install/reboot a MOK enrolment option was
  requested by VirtualBox EFI

  Not sure if this is actually two issues or one - maybe ubuntu-desktop-
  provision for the missing password and subiquity for the lack of MOK
  enrolment ? or is it ubuntu-desktop-provision not passing the right
  options to subiquity?

  Attached is the /var/log/installer that has been tar'd

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