From: Stephan Mueller <smueller@chronox.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Ted Tso <tytso@mit.edu>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] random: add random_initialized command line param
Date: Tue, 23 Jun 2015 23:47:33 +0200 [thread overview]
Message-ID: <3810058.lSGD55uyzM@myon.chronox.de> (raw)
In-Reply-To: <20150623204411.GB30826@amd>
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?
> u-boot-SPL does DRAM calibration, for example, and I guess that may
> provide some rather hard to guess values...
>
> [I initialy misread parameter below as "random_initize=" and thought
> it does exactly this...]
> Pavel
>
> > + random_initialized= [KNL] Set the threshold in bits at which the
> > + Linux random number generator considers an output
> > + entropy pool initialized.
> > + Format: <int> (must be >= 112 and <= size of output
> > + entropy pool in bits)
> > + Default: 128
> > +
--
Ciao
Stephan
next prev parent reply other threads:[~2015-06-23 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 16:25 Stephan Mueller
2015-05-18 18:42 ` Theodore Ts'o
2015-05-18 19:16 ` Stephan Mueller
2015-05-18 22:58 ` Herbert Xu
2015-05-19 22:40 ` Sandy Harris
2015-05-20 6:29 ` Stephan Mueller
2015-05-20 15:06 ` Theodore Ts'o
2015-05-20 16:18 ` Stephan Mueller
2015-06-23 20:44 ` Pavel Machek
2015-06-23 21:47 ` Stephan Mueller [this message]
2015-06-24 8:45 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3810058.lSGD55uyzM@myon.chronox.de \
--to=smueller@chronox.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®