Signed version of grub will result in failure of boot without a separated non-encrypted boot partition

Bug #1850978 reported by Pejman Rezaei
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
New
Undecided
Unassigned
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi

I use Ubuntu 18.04.3
Further than the 1727956 bug, ubiquity installs the signed version of grub. If I want to install Ubuntu with just two partitions (ESP and a luks container which includes the root partition) and don't create any separated boot partition (neither encrypted nor non-encrypted), the signed version of grub will result in a non bootable system and is not compatible with this config. I checked all needed configs (crypttab, luks module in /etc/default/grub) and installed non-signed version of grub which is compatible with this config and working correctly. Also tested on other Linux distros.

Here the problem is the signed version of grub. For more info on this scenario, you can take a look at this page which approves this problem.

http://www.chinnodog.com/ubuntu/ubuntu-fde-boot/

Pejman Rezaei (pejmanrz)
summary: Signed version of grub will result in failure of boot without a
- separated non-encrypted boot boot partition
+ separated non-encrypted boot partition
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.