linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Stephan Mueller <smueller@chronox.de>
Cc: Oleksij Rempel <linux@rempel-privat.de>, "Pan\,
	Miaoqing" <miaoqing@qti.qualcomm.com>,
	"linville\@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>, Theodore Ts'o <tytso@mit.edu>,
	linux-crypto@vger.kernel.org, nhorman@tuxdriver.com
Subject: Re: [PATCH 2/2] ath9k: export HW random number generator
Date: Fri, 31 Jul 2015 10:08:42 +0300	[thread overview]
Message-ID: <8738043ith.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <3945775.m5HblJPgiO@tauon.atsec.com> (Stephan Mueller's message of "Mon, 27 Jul 2015 13:01:46 +0200")

Stephan Mueller <smueller@chronox.de> writes:

>>-rw-rw-r-- 1 lex lex 2564096 Jul 27 11:36 hwrng.out
>>-rw-rw-r-- 1 lex lex 2468394 Jul 27 11:36 hwrng.out.bz2
>>
>>Do i understand it correctly, in case of hwrng bzip was able to find
>>enough pattern to compressed the data? Even with format overhead?
>>
>>I'm no an expert, help of an expert would be welcome, added some more
>>people to CC
>
> This one does not look good for a claim that the RNG produces white noise. An 
> RNG that is wired up to /dev/hwrng should produce white noise. Either by 
> having an appropriate noise source or by conditioning the output of the noise 
> source.
>
> When conditioning the output, you have to be careful about the entropy claim. 
> For example, you cannot state that the data stream from your noise source has 
> close to one bit of entropy for each obtained bit. Thus, the conditioner must 
> ensure that the data from the noise source is collected and its entropy is 
> maintained and accumulated.
>
> However, the hwrandom framework does not provide any conditioning logic. And I 
> would say that such conditioner logic should not reside in a driver either. I 
> would say that the discussed RNG does not seem fit for hooking it up with the 
> hwrandom framework.

Based on the discussion I'm going to revert this patch, at least for
now.

-- 
Kalle Valo

  parent reply	other threads:[~2015-07-31  7:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  7:54 [PATCH 1/2] ath9k: Fix register definitions for QCA956x miaoqing
2015-07-15  7:54 ` [PATCH 2/2] ath9k: export HW random number generator miaoqing
2015-07-26  7:41   ` Oleksij Rempel
2015-07-27  6:50     ` Pan, Miaoqing
2015-07-27 10:45       ` Oleksij Rempel
2015-07-27 11:01         ` Stephan Mueller
2015-07-28 17:41           ` Sandy Harris
2015-07-29  6:33             ` Stephan Mueller
2015-07-31  7:08           ` Kalle Valo [this message]
2015-07-31  8:39             ` Pan, Miaoqing
2015-11-07 23:39               ` Nick Kossifidis
2015-11-07 23:59                 ` Nick Kossifidis
2015-11-25  9:16                 ` Kalle Valo
2015-07-21 14:30 ` [PATCH 1/2] ath9k: Fix register definitions for QCA956x Kalle Valo
2015-07-21 15:04 ` [1/2] " Kalle Valo

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=8738043ith.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=linville@tuxdriver.com \
    --cc=miaoqing@qti.qualcomm.com \
    --cc=nhorman@tuxdriver.com \
    --cc=smueller@chronox.de \
    --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).