linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Droneaud <ydroneaud@opteya.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	Sandy Harris <sandyinchina@gmail.com>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
	labbott@redhat.com
Subject: Re: [PATCH] random: addu a config option to trust the CPU's hwrng
Date: Thu, 19 Jul 2018 22:17:03 +0200	[thread overview]
Message-ID: <437d334a02acf3eff96a4f4da6079829f1de1197.camel@opteya.com> (raw)
In-Reply-To: <20180718173621.GC30706@thunk.org>

Hi,

Le mercredi 18 juillet 2018 à 13:36 -0400, Theodore Y. Ts'o a écrit :

> For those people who are super paranoid and want a "true random
> number generator" (and the meaning of that is hazy) because a
> CRNG is Not Enough, my recommendation these days is that they get
> something like an open hardware RNG solution, such as ChaosKey from
> Altus Metrum[1].
> 
> [1] https://altusmetrum.org/ChaosKey/
> 

I could suggest "Infinite Noise" [1] keys which are also open hardware.
They use a different design, based on "modular multiplication" which
should be immune to most RF noise, 

The original model is currently sold out[2] but a fork exists[3].

One can also have a look at OneRNG [4][5] which uses a more usual
design but adds a nice EMI shield protection.

[1] https://github.com/waywardgeek/infnoise
[2] https://www.tindie.com/products/WaywardGeek/infinite-noise-true-random-number-generator/
[3] https://www.tindie.com/products/manueldomke/infinite-noise-trng-true-random-number-generator/
[4] http://onerng.info/
[5] http://moonbaseotago.com/onerng/

Regards.

-- 
Yann Droneaud
OPTEYA


  parent reply	other threads:[~2018-07-19 20:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  1:43 [PATCH] random: add a config option to trust the CPU's hwrng Theodore Ts'o
2018-07-18  1:51 ` Theodore Y. Ts'o
2018-07-18 15:14   ` Sandy Harris
2018-07-18 17:36     ` [PATCH] random: addu " Theodore Y. Ts'o
2018-07-18 20:22       ` Sandy Harris
2018-07-19 14:21         ` Theodore Y. Ts'o
2018-07-19 20:17       ` Yann Droneaud [this message]
2018-07-18 17:36   ` [PATCH] random: add " Ken Moffat
2018-07-19  0:19     ` Ken Moffat
2018-07-18  5:09 ` Randy Dunlap
2018-07-18  6:46 ` Jeffrey Walton
2018-07-18  7:22 ` Yann Droneaud
2018-07-18 14:26   ` Theodore Y. Ts'o
2018-07-18 15:29     ` Yann Droneaud
2018-07-18 19:17       ` Theodore Y. Ts'o
2018-08-04 21:52     ` Pavel Machek
2018-08-05  0:25       ` Theodore Y. Ts'o
2018-08-05  0:28         ` Theodore Y. Ts'o
2018-08-05  9:44         ` Pavel Machek
2018-07-20 19:09 ` Laura Abbott

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=437d334a02acf3eff96a4f4da6079829f1de1197.camel@opteya.com \
    --to=ydroneaud@opteya.com \
    --cc=labbott@redhat.com \
    --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).