From: Stephan Mueller <smueller@chronox.de>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Ted Tso <tytso@mit.edu>,
herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
Kalle Valo <kvalo@codeaurora.org>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [v2] RANDOM: ATH9K RNG delivers zero bits of entropy
Date: Tue, 27 Sep 2016 17:17:02 +0200 [thread overview]
Message-ID: <1477295.yC8zZtqI66@tauon.atsec.com> (raw)
In-Reply-To: <2ba03f89daee4f09a88a1238943eb49d@euamsexm01a.eu.qualcomm.com>
Am Dienstag, 27. September 2016, 16:44:16 CEST schrieb Kalle Valo:
Hi Kalle,
> Stephan Mueller <smueller@chronox.de> wrote:
> > The ATH9K driver implements an RNG which is completely bypassing the
> > standard Linux HW generator logic.
> >
> > The RNG may or may not deliver entropy. Considering the conservative
> > approach in treating entropy with respect to non-auditable sources, this
> > patch changes the delivered entropy value to zero. The RNG still feeds
> > data into the input_pool but it is assumed to have no entropy.
> >
> > When the ATH9K RNG changes to use the HW RNG framework, it may re-enable
> > the entropy estimation considering that a user can change that value at
> > boot and runtime.
> >
> > Reviewed-by: Jason Cooper <jason@lakedaemon.net>
> > Signed-off-by: Stephan Mueller <smueller@chronox.de>
>
> Based on the discussion I'm dropping this patch. But the discussion was
> hard to follow so please let me know if I misunderstood.
I guess the rejection is appropriate, but something needs to be done:
add_hwgenerator_randomness should not be used in this scenario.
>
> Patch set to Rejected.
Ciao
Stephan
prev parent reply other threads:[~2016-09-27 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 15:08 [RFC][PATCH] " Stephan Mueller
2016-08-06 19:45 ` Jason Cooper
2016-08-06 20:03 ` Stephan Mueller
2016-08-06 20:16 ` Jason Cooper
2016-08-07 9:36 ` [PATCH v2] " Stephan Mueller
2016-08-08 2:03 ` Pan, Miaoqing
2016-08-08 6:41 ` Stephan Mueller
2016-08-08 17:29 ` Jason Cooper
2016-08-08 22:04 ` Jason Cooper
2016-08-09 6:30 ` Pan, Miaoqing
2016-08-09 11:56 ` Theodore Ts'o
2016-08-09 14:04 ` Jason Cooper
2016-08-10 23:44 ` Theodore Ts'o
2016-08-14 18:11 ` Jason Cooper
2016-08-15 11:01 ` Kalle Valo
2016-09-27 14:44 ` [v2] " Kalle Valo
2016-09-27 15:17 ` Stephan Mueller [this message]
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=1477295.yC8zZtqI66@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=herbert@gondor.apana.org.au \
--cc=jason@lakedaemon.net \
--cc=kvalo@codeaurora.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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®