lkml.org 
[lkml]   [2015]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Should we automatically generate a module signing key at all?
Dne 20.5.2015 v 05:47 Jiri Kosina napsal(a):
> On Tue, 19 May 2015, David Howells wrote:
>
>> That wouldn't very convenient for building our kernels in our build farm
>> - we have a lot of machines and all of them would have to be equiped
>> with the key. Besides, we *want* to discard the private key where
>> possible as soon as possible because then we can't leak it and we can't
>> be forced to disclose it.
>
> You can still have a dedicated machine that's used just for signing the
> binaries. That machine wouldn't be connected to the network, would be
> physically secured, and would sign through a serial line or so.

Right, that's what CONFIG_MODULE_SIG_ALL=n is meant for -- build the
public key into the kernel, but sign the modules later, outside of the
build system. So you still have to trust the build machine to build what
you ask it to build, but you do not have to trust it not to leak your
private key.

Michal


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