mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Xymoron <oxymoron@waste.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Jon Burgess <Jon_Burgess@eur.3com.com>,
	henrique@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: Problem with random.c and PPC
Date: Fri, 16 Aug 2002 19:29:29 -0500	[thread overview]
Message-ID: <20020817002929.GM5418@waste.org> (raw)
In-Reply-To: <3D5D6621.E33EA4BE@nortelnetworks.com>

On Fri, Aug 16, 2002 at 04:52:49PM -0400, Chris Friesen wrote:
> Oliver Xymoron wrote:
> 
> > There is little to no reliably unpredictable data in network
> > interrupts and the current scheme does not include for the mixing of
> > untrusted sources. It's very likely that an attacker can measure,
> > model, and control such timings down to the resolution of the PCI bus
> > clock on a quiescent system. This is more than good enough to defeat
> > entropy generation on systems without a TSC and given that the bus
> > clock is a multiple of the processor clock, it's likely possible to
> > extend this to TSC-based systems as well.
> 
> > Entropy accounting is very fickle - if you overestimate _at all_, your
> > secret state becomes theoretically predictable. I have some patches
> > that create an API for adding such hard to predict but potentially
> > observable data to the entropy pool without accounting it as actual
> > entropy, as well as cleaning up some other major accounting errors but
> > I'm not quite done testing them.
> 
> The problem is this.  If you have an embedded system that is
> headless, diskless, keyboardless, and mouseless, then your only
> remaining source of any interrupt-based entropy is the network.
> Also, if you add entropy to the pool without accounting it as
> entropy, then how does that help anything?

Yes, you _potentially_ improve the unpredictability of /dev/urandom
without throwing out the guarantees of /dev/random. There is exactly
one difference between urandom and random - guaranteed entropy (ignore
for the moment that it's currently completely buggered, I'm fixing
that.). If you need guaranteed entropy, then you _need_ an
unobservable entropy source. Period. Pretending network interrupts are
unpredictable is just pretending.

> For the general user, network-based interrupts are likely okay.

If that's really true, then /dev/urandom is okay too, _by
definition_. Use it. 

-- 
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.." 

  reply	other threads:[~2002-08-17  0:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 10:00 Jon Burgess
2002-08-16 19:52 ` Oliver Xymoron
2002-08-16 17:51   ` henrique
2002-08-16 21:21     ` Ruth Ivimey-Cook
2002-08-17  0:47       ` Oliver Xymoron
2002-08-17  0:45     ` Oliver Xymoron
2002-08-17  6:05       ` Andreas Dilger
2002-08-17  7:23         ` Oliver Xymoron
2002-08-17  9:09           ` Andreas Dilger
2002-08-17 16:56             ` Oliver Xymoron
2002-08-19  9:29           ` Marco Colombo
2002-08-19 14:02             ` Oliver Xymoron
2002-08-19 15:11               ` Marco Colombo
2002-08-19 15:29                 ` Oliver Xymoron
2002-08-19 16:20                   ` Marco Colombo
2002-08-19 16:33                     ` Oliver Xymoron
2002-08-19 20:23                       ` Marco Colombo
2002-08-22  3:16             ` David Wagner
2002-08-16 20:52   ` Chris Friesen
2002-08-17  0:29     ` Oliver Xymoron [this message]
2002-08-22  3:19     ` David Wagner
2002-08-22 15:40       ` Chris Friesen
2002-08-22 17:25       ` Remco Post
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15 16:10 henrique
2002-08-15 15:14 henrique
2002-08-15 18:25 ` Andreas Dilger
2002-08-15 19:03   ` Tom Rini
2002-08-15 19:59     ` Andreas Dilger
2002-08-15 21:04       ` Tom Rini
2002-08-16  1:50         ` H. Peter Anvin
2002-08-16 16:33           ` Oliver Xymoron
2002-08-16 16:28         ` Oliver Xymoron
     [not found]           ` <20020816170126.GD26993@opus.bloom.county>
2002-08-16 17:15             ` Oliver Xymoron

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=20020817002929.GM5418@waste.org \
    --to=oxymoron@waste.org \
    --cc=Jon_Burgess@eur.3com.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=henrique@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®