mirror of
https://git.proxmox.com/git/grub2
synced 2025-10-23 22:43:56 +00:00
Fix setup on Secure Boot systems where cryptodisk is in use
On full-encrypted systems, including /boot, the current code omits cryptodisk commands needed to open the drives if Secure Boot is enabled. This prevents grub2 from reading any further configuration residing on the encrypted disk. This patch fixes this issue by adding the needed "cryptomount" commands in the load.cfg file that is then copied in the EFI partition. Bug-Debian: https://bugs.debian.org/917117 Last-Update: 2019-02-10 Patch-Name: uefi-secure-boot-cryptomount.patch
This commit is contained in:
parent
b5148a7311
commit
ec85b3d37c
@ -1502,6 +1502,23 @@ main (int argc, char *argv[])
|
||||
|| uefi_secure_boot)
|
||||
{
|
||||
char *uuid = NULL;
|
||||
|
||||
if (uefi_secure_boot && config.is_cryptodisk_enabled)
|
||||
{
|
||||
if (grub_dev->disk)
|
||||
probe_cryptodisk_uuid (grub_dev->disk);
|
||||
|
||||
for (curdrive = grub_drives + 1; *curdrive; curdrive++)
|
||||
{
|
||||
grub_device_t dev = grub_device_open (*curdrive);
|
||||
if (!dev)
|
||||
continue;
|
||||
if (dev->disk)
|
||||
probe_cryptodisk_uuid (dev->disk);
|
||||
grub_device_close (dev);
|
||||
}
|
||||
}
|
||||
|
||||
/* generic method (used on coreboot and ata mod). */
|
||||
if (!force_file_id && grub_fs->uuid && grub_fs->uuid (grub_dev,
|
||||
&uuid))
|
||||
|
Loading…
Reference in New Issue
Block a user