linux-kernel - Re: RFC: sign the modules at install time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <877gqoo0tp.fsf@rustcorp.com.au>
Date:	Thu, 18 Oct 2012 15:04:26 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <gregkh@...uxfoundation.org>
Cc:	David Howells <dhowells@...hat.com>,
	David Miller <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	jwboyer@...hat.com, pjones@...hat.com
Subject: Re: RFC: sign the modules at install time

Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Wed, Oct 17, 2012 at 5:54 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>>>
>>> One of the main sane use-cases for module signing is:
>>>
>>>  - CONFIG_CHECK_SIGNATURE=y
>>>  - randomly generated one-time key
>>>  - "make modules_install; make install"
>>>  - "make clean" to get rid of the keys.
>>>  - reboot.
>>
>> I want that too, but right now 'make clean' leaves the keys around,
>> which seems a bit dangerous to me.
>
> Oh, yes, we should make sure the key file gets cleaned up at "make clean".

I left it at distclean, figuring the temporary key is a bit like the
.config.  But it's trivial to change if people think that's unnatural.

Cheers,
Rusty.
--
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/