[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C24C30.8030106@ahsoftware.de>
Date: Fri, 23 Jan 2015 14:27:12 +0100
From: Alexander Holler <holler@...oftware.de>
To: David Howells <dhowells@...hat.com>
CC: Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] modsign: provide option to automatically delete the key
after modules were installed
Am 23.01.2015 um 13:56 schrieb David Howells:
> One thing that you have to be careful of with your patch is that if you turn
> it on during development, this will drain the entropy pool from which you get
> random numbers.
Hmm, I wonder how often people are compiling kernels and how much one
turn drains the entropy pool.
I would suggest to just get better in coding (and reviewing before
compile testing) in order to not having to build kernels that often. Or
just use a different config for development. ;)
My primary use case is just what Linus described in his keynote. I'm
building and signing all my kernels whenever a new stable kernel
appears, throwing away the keys away immediately afterwards.
And the patch avoids that I have to type the rm, and, even more usefull,
it makes sure I don't forget to delete the keys, which would make
signing the modules useless for me (as my kernel build directories (and
thus the private keys) are usually residing on the machine the kernel is
deployed afterwards).
Regards,
Alexander Holler
--
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