Sujet : Re: F2FS On USB Sticks?
De : dwhodgins (at) *nospam* nomail.afraid.org (David W. Hodgins)
Groupes : comp.os.linux.miscDate : 23. Mar 2025, 16:58:32
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <op.23vdbuaoa3w0dxdave@hodgins.homeip.net>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14
User-Agent : Opera Mail/12.16 (Linux)
On Sun, 23 Mar 2025 09:57:33 -0400, Carlos E.R. <
robin_listas@es.invalid> wrote:
<snip>
UEFI, on the other hand, is designed to boot multiple systems. Having
the boot signed is a different thing.
I used to use the gag boot loader on the mbr, grub (legacy) on each linux partition boot record,
so that a problem with one install had no impact on another install. Each install was isolated
except for a data partition shared between them.
With grub2, I changed to one disk per install in order to keep one install from impacting another.
While grub2 can be installed on the pbr, most installers will only install it on an mbr.
With uefi, while it's still possible to have multiple installs, it is not possible to keep them isolated
from each other. Any install can break all installs. The only way to keep each install isolated is
to have one install per machine.
uefi is a mini operating system developed primarily for the purpose of making it harder for other
operating systems to be used, and to boost pc sales. The attack surface it exposes allows
undetectable root kits to be installed, or machines to be easily bricked just by deleting the
efivars from the nvram.
uefi is marketed as improving security. While it may block amateur attackers, it is a security
nightmare. The only possible way to ensure a uefi computer does not have a stealth rootkit
already installed is to remove it's nvram and use a reader attached to another system. In most
cases the nvram is soldered onto the motherboard.
Regards, Dave Hodgins