Can anyone answer:

1] Does this vulnerability apply when the UEFI is operating in "legacy
boot" mode instead of "secure boot" mode? I recall that when I was
originally setting up my only UEFI-equipped device that there were
differences between the two modes in how I needed to set up the
partition table.

2] If this vulnerability is exploited, is there a JTAG fix? I haven't
looked at my particular motherboard, but many have a physical access
JTAG connector with which to directly access/debug/modify firmware on
the board.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0