The owner of the system should always be able to load arbitrary code into the kernel, and the solution we've implemented permits that. Arbitrary privileged userspace shouldn't be able to load arbitrary code into the kernel unless the owner of the system has explicitly permitted that.
Power management, mobile and firmware developer on Linux. Security developer at nvidia. Ex-biologist. Content here should not be interpreted as the opinion of my employer. Also on Mastodon and Bluesky.
Re: Secure Boot is subverting security itself
Date: 2013-12-04 08:09 pm (UTC)