lkml.org 
[lkml]   [2015]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFD] linux-firmware key arrangement for firmware signing
On 15-05-20 23:14:53, Greg Kroah-Hartman wrote:
>
> Ok, but how do we know "where"? Who is going to start signing and attesting
> to the validity of all of the firmware images in the linux-firmware tree
> suddenly? Why is it the kernel's job to attest this "where"? Shouldn't your
> distro/manufacturer be doing that as part of their "put this file on this
> disk" responsibilities (i.e. the package manager?)

I did not say the kernel should care about signatures. This is entirely user's
choice. You care about authenticity, you require signature and verify it
against "known good" certificate. s/you/distro/

I'm just saying that it would be nice to have this feature in case somebody need
it. Luckily IMA has this functionality, although you'll have to work hard to
get to use it. :)

> What is verifying a firmware image signature in the kernel attesting that
> isn't already known in userspace?

The kernel is a lot better place to keep certificates and keys safe, compared to
userland.


Petko


\
 
 \ /
  Last update: 2015-05-21 17:21    [W:2.046 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site