Posted Sep 13, 2012 19:10 UTC (Thu) by iabervon (subscriber, #722)
Parent article: LSS: Secure Boot
It seems to me that, if a user can install their own key in the shim, they could run all sorts of malware, like Windows 8 (once Windows 9 comes out), simply by signing it. So the assumption has to be that, if the user has put their key in the shim, the shim is off the hook as far as anything that further that gets run is concerned, so long as it is, in fact, signed by the user's key. As such, all of the kernel changes aren't actually important for Secure Boot itself, but rather that, if you buy Secure Boot's premise and want to enforce those policies, you'll want to have a kernel that doesn't violate them, and you probably want a configuration option that keeps you from accidentally enabling something that isn't trying to enforce them.