On Thu, Mar 26, 2020 at 1:33 PM Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > As a straw-man approach: make the rule that we never call EFI after secure launch. Instead we write out any firmware variables that we want to change on disk somewhere. When we want to commit those changes, we reboot, commit the changes, and re-launch. Or we deactivate the kernel kexec-style, seal the image against PCRs, blow away PCRs, call EFI, relaunch, unseal the PCRs, and continue on our merry way. That breaks the memory overwrite protection code, where a variable is set at boot and cleared on a controlled reboot. We'd also need to read every variable and pass those values to the kernel in some way so the read interfaces still work. Some platforms may also expect to be able to use the EFI reboot call. As for the second approach - how would we verify that the EFI code hadn't modified any user pages? Those wouldn't be measured during the second secure launch. If we're calling the code at runtime then I think we need to assert that it's trusted. > I’m not sure how SMM fits in to this whole mess. SMM's basically an unsolved problem, which makes the whole DRTM approach somewhat questionable unless you include the whole firmware in the TCB, which is kind of what we're trying to get away from. > If we insist on allowing EFI calls and SMM, then we may be able to *measure* our exposure to potentially malicious firmware, but we can’t eliminate it. I personally trust OEM firmware about as far as I can throw it.
