[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140226222151.78854cd8@alan.etchedpixels.co.uk>
Date: Wed, 26 Feb 2014 22:21:51 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Kees Cook <keescook@...omium.org>
Cc: Matthew Garrett <matthew.garrett@...ula.com>,
LKML <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
James Morris <jmorris@...ei.org>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: Re: Trusted kernel patchset for Secure Boot lockdown
> > kernel was trusted - untrusted userspace could have set it on an untrusted
> > kernel, but by the same metric an untrusted kernel could just set it itself.
> >
> > If people object to this name then I swear to god that I will open a poll
> > on Phoronix to decide the next attempt and you will like that even less.
Go on open the poll - I dare you. But don't be shocked if it ends up
being called "Eric" or "Icanhazsigs" 8)
> For the Chrome OS use-case, it might be better described as "untrusted
> userspace", but that seems unfriendly. :) The "trusted kernel" name
> seems fine to me.
Trusted is rather misleading. It's not trusted, it's *measured*.
It's the same bits you had when you made it, and when you booted it
before. Whether you trust them is a different and quite unrelated
question. You may have reasons to do either.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists