public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, tytso@mit.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Replace /dev/random input mix polynomial with Brent's xorgen?
Date: 15 Dec 2013 23:22:47 -0500	[thread overview]
Message-ID: <20131216042247.9826.qmail@science.horizon.com> (raw)
In-Reply-To: <20131215221948.GA6773@thunk.org>


On Sun, Dec 15, 2013 at 03:34:59AM -0500, George Spelvin wrote:
>> You're describing standard key-recovery attacks.  For /dev/random,
>> just knowing the *ciphertext* constitutes a successful attack.

> Um, no.  The *ciphertext* is the output.  The attacker can get all of
> the ciphertext he or she wants by reading /dev/random (although we'd
> probably do some folding as we currently do so the attacker won't even
> get all of the ciphertext).  What the attacker has to be able to do is
> given some of the ciphertext bits, be able to predict future
> ciphertext bits given some construction which uses AES as the basis.

The attack I was thinking of was figuring out (without breaking root and
using ptrace) what some *other* process on the same machine is reading
from /dev/random.

In other words, reading someone else's output.

  reply	other threads:[~2013-12-16  4:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14  9:06 Replace /dev/random input mix polynomial with Brent's xorgen? George Spelvin
2013-12-14 19:23 ` Theodore Ts'o
2013-12-14 21:55   ` George Spelvin
2013-12-15  2:21     ` Theodore Ts'o
2013-12-15  8:34       ` George Spelvin
2013-12-15 22:19         ` Theodore Ts'o
2013-12-16  4:22           ` George Spelvin [this message]
2013-12-16  6:43             ` Theodore Ts'o
2013-12-16  6:49               ` Theodore Ts'o
2013-12-16 15:03               ` George Spelvin
2013-12-15 20:03   ` Greg Price
2013-12-15 22:09     ` George Spelvin
2013-12-16  0:32       ` Greg Price
2013-12-16  6:53         ` George Spelvin

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=20131216042247.9826.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=linux-kernel@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