linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: David Schwartz <davids@webmaster.com>
Cc: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: /dev/random: really secure?
Date: Mon, 18 Dec 2000 21:38:01 +0100	[thread overview]
Message-ID: <20001218213801.A19903@pcep-jamie.cern.ch> (raw)
In-Reply-To: <20001217225057.A8897@atrey.karlin.mff.cuni.cz> <NCBBLIEPOCNJOAEKBEAKKEFEMIAA.davids@webmaster.com>
In-Reply-To: <NCBBLIEPOCNJOAEKBEAKKEFEMIAA.davids@webmaster.com>; from davids@webmaster.com on Sun, Dec 17, 2000 at 04:18:31PM -0800

David Schwartz wrote:
> The code does its best to estimate how much actual entropy it is gathering.

A potential weakness.  The entropy estimator can be manipulated by
feeding data which looks random to the estimator, but which is in fact
not random at all.

-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-18 21:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-17 21:50 /dev/random: really secure? Karel Kulhavy
2000-12-18  0:18 ` David Schwartz
2000-12-18  8:21   ` Karel Kulhavy
2000-12-18 20:38   ` Jamie Lokier [this message]
2000-12-18 21:33     ` Theodore Y. Ts'o
2000-12-18 22:15       ` Andreas Dilger
2000-12-19  9:27         ` Daniel Stone
2000-12-19 11:49       ` Kurt Garloff
2000-12-19 12:48         ` Peter Samuelson
2000-12-19 16:51         ` Theodore Y. Ts'o
2000-12-19 17:39         ` Pavel Machek
2000-12-18 21:58     ` David Schwartz
2000-12-18  8:49 ` David Feuer
2000-12-18  9:22 ` Martin Mares
2000-12-19  6:49 ` Philipp Rumpf
2000-12-20  3:41 Bernd Eckenfels
2000-12-20 17:58 ` Jamie Lokier
2000-12-20  3:49 Bernd Eckenfels

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=20001218213801.A19903@pcep-jamie.cern.ch \
    --to=lk@tantalophile.demon.co.uk \
    --cc=clock@atrey.karlin.mff.cuni.cz \
    --cc=davids@webmaster.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;
as well as URLs for NNTP newsgroup(s).