From: "Theodore Ts'o" <tytso@mit.edu>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Jörn Engel" <joern@logfs.org>, "H. Peter Anvin" <hpa@zytor.com>,
"Linux Kernel Developers List" <linux-kernel@vger.kernel.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
dave.taht@gmail.com, blogic@openwrt.org, andrewmcgr@gmail.com,
smueller@chronox.de, "Geert Uytterhoeven" <geert@linux-m68k.org>,
tg@mirbsd.de
Subject: Re: [PATCH,RFC] random: collect cpu randomness
Date: Mon, 3 Feb 2014 17:44:38 -0500 [thread overview]
Message-ID: <20140203224438.GD22856@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.10.1402032149530.3940@eddie.linux-mips.org>
On Mon, Feb 03, 2014 at 09:54:22PM +0000, Maciej W. Rozycki wrote:
>
> Can we be sure we don't leak information this way? Just being
> paranoid...
The register information will be mixed pretty thoroughly by the time
it gets to the entropy pool, and then we don't ever expose the entropy
pool to userspace. So no, I don't think we need to worry about
leaking information.
- Ted
next prev parent reply other threads:[~2014-02-03 22:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 20:36 [PATCH,RFC] random: collect cpu randomness Jörn Engel
2014-02-02 21:25 ` Stephan Mueller
2014-02-03 1:24 ` Jörn Engel
2014-02-03 1:28 ` H. Peter Anvin
2014-02-03 13:36 ` Stephan Mueller
2014-02-03 1:39 ` Theodore Ts'o
2014-02-03 3:35 ` Jörn Engel
2014-02-03 12:54 ` Thorsten Glaser
2014-02-03 13:06 ` Stephan Mueller
2014-02-03 15:50 ` Jörn Engel
2014-02-03 16:37 ` Theodore Ts'o
2014-02-03 18:48 ` Jörn Engel
2014-03-23 18:00 ` [PATCH] random: mix all saved registers into entropy pool Jörn Engel
2014-02-03 21:54 ` [PATCH,RFC] random: collect cpu randomness Maciej W. Rozycki
2014-02-03 22:44 ` Theodore Ts'o [this message]
2014-02-06 22:20 ` Kees Cook
2014-02-06 22:21 ` Dave Taht
2014-02-07 7:44 ` Jörn Engel
2014-02-20 9:50 ` Paolo Bonzini
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=20140203224438.GD22856@thunk.org \
--to=tytso@mit.edu \
--cc=andrewmcgr@gmail.com \
--cc=blogic@openwrt.org \
--cc=dave.taht@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=smueller@chronox.de \
--cc=tg@mirbsd.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.