From: Stephan Mueller <smueller@chronox.de>
To: Sandy Harris <sandyinchina@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Theodore Ts'o <tytso@mit.edu>,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] random: add random_initialized command line param
Date: Wed, 20 May 2015 08:29:19 +0200 [thread overview]
Message-ID: <3005024.K2tYVGR0qE@tauon> (raw)
In-Reply-To: <CACXcFmnZw9eS1EuokG54OYgCXnju2iD2q2o9miWmQMab5SJmDQ@mail.gmail.com>
Am Dienstag, 19. Mai 2015, 18:40:20 schrieb Sandy Harris:
Hi Sandy,
>
>When we do do it, I see no reason to support anything other than 128
>and 256, and I am not sure about retaining 128. Nor do I see any
>reason this should be a command-line option rather than just a
>compile-time constant.
I would hazard to guess that a compile time option is a bit difficult for
distributions which typically only want one kernel for all their user base. As
that user base is typically large, they would potentially be unable to please
everybody with a compile time option.
But I see that such a change may not be warranted at this point. Though, I see
that discussion may rise again in the future when such new requirements for
256 bit keys (not only AES, thanks Sandy for mentioning :-) ) are commonly
raised.
So, let us disregard the patch until hard requirements are coming up.
Ciao
Stephan
next prev parent reply other threads:[~2015-05-20 6:29 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
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 [this message]
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=3005024.K2tYVGR0qE@tauon \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).