From: "Theodore Ts'o" <tytso@mit.edu>
To: Prarit Bhargava <prarit@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] random, Add user configurable get_bytes_random()
Date: Thu, 5 Sep 2013 15:49:07 -0400 [thread overview]
Message-ID: <20130905194907.GE23661@thunk.org> (raw)
In-Reply-To: <20130905190334.GC23661@thunk.org>
BTW, note the following article, published today:
http://www.nytimes.com/2013/09/06/us/nsa-foils-much-internet-encryption.html?pagewanted=all
"By this year, the Sigint Enabling Project had found ways inside some
of the encryption chips that scramble information for businesses and
governments, either by working with chipmakers to insert back doors...."
Relying solely and blindly on a magic hardware random number generator
which is sealed inside a CPU chip and which is impossible to audit is
a ***BAD*** idea.
- Ted
next prev parent reply other threads:[~2013-09-05 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 12:18 [PATCH] random, Add user configurable get_bytes_random() Prarit Bhargava
2013-09-05 14:48 ` Theodore Ts'o
2013-09-05 15:08 ` Prarit Bhargava
2013-09-05 19:03 ` Theodore Ts'o
2013-09-05 19:49 ` Theodore Ts'o [this message]
2013-09-06 12:08 ` Prarit Bhargava
2013-09-06 13:57 ` Theodore Ts'o
2013-09-12 17:40 ` Jörn Engel
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=20130905194907.GE23661@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
/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