> How often do you check your unauthenticated ESP and /boot for malware? I don't, because it's not something I so far cared about. But if I started caring abou

> How often do you check your unauthenticated ESP and /boot for malware? I don't, because it's not something I so far cared about. But if I started caring about these sorts of attacks, I would not rely on board firmware to check software on my disks:) > vast majority of people aren't competent computer owners or users. Vast majority of people don't read HN and are not interested in the boot process. Those that do are more relevant, and I suspect many of them don't welcome Mr. Poettering's agenda. > They don't know what to do on a technical level with malware in their boot process. I'm not suggesting they should. But Mr. Poettering does not discuss origins and possible ways to solve this problem, e.g. using free software from reliable sources only and auditing software and hardware we use. He presents his (an the secure boot complex's) preferred solution to a problem that is complex and probably will try to "gently push it" on distributions like he did with systemd (his words).