systemd is not responsible for allowing kernel code that I wrote to destroy your shitty firmware. I think you get to blame me instead.
@mjg59 Well most users don't have the luxury of open implementations. Running firmware code with kernel privs compromises their security.
-
-
@RichFelker Running on closed hardware compromises security. We all make choices about what level of risk we accept.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker@mjg59 1. You don't have a choice if you're reconfiguring the firmware; 2. the firmware is in SMM, you're already compromised -
@oshepherd@mjg59 Reconfiguring firmware and running a system for normal/production use are completely different operations & shouldn't mix. -
@RichFelker@mjg59 Then don't write to your EFI vars. But the kernel still needs to read some at boot, and also occasionally use some others -
@oshepherd@mjg59 Should be read by bootloader, passed to kernel as a device tree blob, & EFI/BIOS should be completely unmapped @ runtime. -
@RichFelker@oshepherd But that's not how things work, and so entirely irrelevant to solving the current problem
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.