[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXn1xcFpVFUxukAPpM7x6Z5hfyS0PvUXSQnNao5q26gig@mail.gmail.com>
Date: Sat, 10 Dec 2011 10:49:52 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>,
linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
linux-kernel@...r.kernel.org, dmitry.kasatkin@...el.com,
zohar@...ux.vnet.ibm.com, alan@...rguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing
On Fri, Dec 9, 2011 at 15:20, Arjan van de Ven <arjan@...ux.intel.com> wrote:
>> I wonder what the best way to deal with that is... I guess make
>> allyesconfig and make allmodconfig are going to break otherwise.
>
> the best way to deal is to have KBUILD generate a key on demand ;-)
Or provide a default key with the kernel, cfr. all the other "*.shipped" files?
No entropy source needed.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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