Messages in this thread | | | Date | Thu, 13 Mar 2014 10:12:35 +0000 | From | One Thousand Gnomes <> | Subject | Re: Trusted kernel patchset for Secure Boot lockdown |
| |
On Thu, 13 Mar 2014 20:33:06 +1100 (EST) James Morris <jmorris@namei.org> wrote:
> On Wed, 12 Mar 2014, Kees Cook wrote: > > > On Wed, Mar 12, 2014 at 10:01 PM, Matthew Garrett > > <matthew.garrett@nebula.com> wrote: > > > On Fri, 2014-02-28 at 14:03 +1100, James Morris wrote: > > > > > >> Ok, which tree should take this? I'm happy to, although most of it is > > >> outside security/ . > > > > > > Should I be looking for someone else to take them instead? :) > > > > Andrew, is this series[1] something you'd be okay taking? It touches > > many different areas, so you might be best for it. > > I'll take it, but there's unanswered review feedback (your response to the > first question), and Alan raised some doubts about the patches which I'm > not sure have been resolved.
I have a series of doubts about their completeness which didn't get any answer at all, and one on the misleading use of the term "secure" as opposed to "measured" 8)
I don't think it's reasonable to have a policy of refusing them until they cover all cases. It's not like it can be dropped into staging and refined.
So other than the usual moan about people naming things "security" being like putting "i-" and "e-" on the front of stuff to make it sound cool when it isn't what it says I'm fine 8)
I would prefer it did the revocation of CAP_SYS_RAWIO or at least documented the absolute requirement.
Alan
| |