linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] random: add random_initialized command line param
Date: Mon, 18 May 2015 14:42:09 -0400	[thread overview]
Message-ID: <20150518184209.GA2871@thunk.org> (raw)
In-Reply-To: <4206400.x843ypJTc1@tachyon.chronox.de>

On Mon, May 18, 2015 at 06:25:25PM +0200, 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.
> 
> CC: Ted Tso <tytso@mit.edu>
> Signed-off-by: Stephan Mueller <smueller@chronox.de>

How much does 125 vs 112 vs 128 bits really matter?  Is the cost of
waiting the extra 16 bits (the difference between 112 and 128 bits)
really that high?  I'm not entirely convincd that adding Yet Another
Tuning parameter is really worth it.  If we stick with 128 bits, we
will satisfy SOGIS, BSI, NIST, etc., and I would find it difficult to
believe that someone would want 132, 147, etc., bits.

	     	     	   	     	  - Ted

  reply	other threads:[~2015-05-18 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 16:25 [PATCH] random: add random_initialized command line param Stephan Mueller
2015-05-18 18:42 ` Theodore Ts'o [this message]
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
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=20150518184209.GA2871@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smueller@chronox.de \
    /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;
as well as URLs for NNTP newsgroup(s).