diff options
| author | João Paulo Rechi Vita <jprvita@endlessos.org> | 2021-03-09 14:07:05 -0800 |
|---|---|---|
| committer | Peter Jones <pjones@redhat.com> | 2021-03-10 15:59:07 -0500 |
| commit | 4df8ed30f1a306b496ceffbce6ec21505122c962 (patch) | |
| tree | 44592904a2e00e34ab5f9c2a773a857fd5d900ba /Cryptlib/OpenSSL/crypto/md32_common.h | |
| parent | 426c5a1e8ada8b8a4374ba37bcb8be16c2ea1d71 (diff) | |
| download | efi-boot-shim-4df8ed30f1a306b496ceffbce6ec21505122c962.tar.gz efi-boot-shim-4df8ed30f1a306b496ceffbce6ec21505122c962.zip | |
fallback: Consider all Boot* vars when checking for duplicates
Some firmware implementations like the one on the Acer TravelMate
P449-G2-MG completely ignore the value of BootOrder set by fallback, and
overwrite it with a value of its own. On this particular machine, the
boot entry created by fallback on the previous boot is not included by
the firmware on this new BootOrder, so it is not considered when
checking for duplicates.
This problem is agravated by the fact that such firmware does not give
the user the possibility to manually boot from any entry created outside
of the firmware setup program -- the only way to boot a distro that
deploys "the fallback ESP layout" and no \EFI\BOOT\grubx64.efi with this
firmware is through \EFI\BOOT\BOOTX64.EFI. The side effect here is
having a new boot entry created by fallback on every boot.
This commit makes fallback try every Boot* variable when checking for
duplicates, not only the ones listed in BootOrder, so it can find the
duplicate Boot entry and re-use it instead of creating a new one.
https://phabricator.endlessm.com/T15481
Signed-off-by: João Paulo Rechi Vita <jprvita@endlessos.org>
Diffstat (limited to 'Cryptlib/OpenSSL/crypto/md32_common.h')
0 files changed, 0 insertions, 0 deletions