[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150624084550.GB22179@amd>
Date: Wed, 24 Jun 2015 10:45:50 +0200
From: Pavel Machek <pavel@....cz>
To: Stephan Mueller <smueller@...onox.de>
Cc: Ted Tso <tytso@....edu>, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] random: add random_initialized command line param
On Tue 2015-06-23 23:47:33, Stephan Mueller wrote:
> Am Dienstag, 23. Juni 2015, 22:44:11 schrieb Pavel Machek:
>
> Hi Pavel,
>
> > On Mon 2015-05-18 18:25:25, Stephan Mueller wrote:
> > > Make the threshold at which the output entropy pools are considered to
> > > be initialized configurable via a kernel command line option. The
> > > current integer value of 128 bits is a good default value. However, some
> > > user groups may want to use different values. For example, the SOGIS
> > > group now requires 125 bits at least (BSI, the participant at that group
> > > used to require 100 bits). NIST moved from 80 bits to 112 bits starting
> > > with 2014.
> > >
> > > It is therefore to be expected that in the future, this threshold may
> > > increase for different user groups.
> >
> > Speaking of random and kernel parameters... should we add random=<hex
> > digits> parameter to pass entropy from bootloader to the kernel?
>
> Everybody can see that string. How do you think that way of providing entropy
> is protected?
Only local users, not remote attackers. And yes, we should probably
"censor" the command line for this use.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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