2 ms·
Because then your trust path includes the userspace insmod utility and every library and system service it depends on, all of which would themselves need signat
by JoshTriplett 14y ago
Because then your trust path includes the userspace insmod utility and every library and system service it depends on, all of which would themselves need signature verification and hardening against things like LD_LIBRARY_PATH (even from root).
Otherwise, you can easily construct a harmful payload consisting of the distro-signed Shim, that kernel, and a modified userspace that loads an arbitrary module which takes over the kernel and runs arbitrary code in ring 0. And then that distro's Secure Boot signing key gets revoked.