mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Matt Mackall <mpm@selenic.com>, "Theodore Ts'o" <tytso@mit.edu>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: short read from /dev/urandom
Date: Sun, 16 Jan 2005 14:23:40 +0100	[thread overview]
Message-ID: <20050116132340.GA8163@pclin040.win.tue.nl> (raw)
In-Reply-To: <41E9E65F.1030100@redhat.com>

On Sat, Jan 15, 2005 at 07:58:23PM -0800, Ulrich Drepper wrote:

> Matt Mackall wrote:
> >_Neither_ case mentions signals and the "and will return as many bytes
> >as requested" is clearly just a restatement of "does not have this
> >limit". Whoever copied this comment to the manpage was a bit sloppy
> >and dropped the first clause rather than the second:
> 
> It still means the documented API says there are no short reads.

No. It says that /dev/urandom "contains" an unlimited amount
of bits - you can read as many bits from there as you want,
while /dev/random "contains" a limited amount of information -
you can exhaust it.

That is information about the device. There is no suggestion at all
about some special property that would guarantee that the normal
read() system call has special behavior in connection with /dev/urandom.

There is no special documented API. Now that this misunderstanding
occurred I suppose a clarifying sentence will be added.
Nothing special with /dev/urandom.

Applications that make special assumptions are broken.

Andries

      parent reply	other threads:[~2005-01-16 13:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14  4:54 Ulrich Drepper
2005-01-14  5:56 ` David Wagner
2005-01-14  6:54   ` Ulrich Drepper
2005-01-14 19:55     ` David Wagner
2005-01-14 19:10 ` Theodore Ts'o
2005-01-14 21:04   ` Ulrich Drepper
2005-01-14 23:21     ` Theodore Ts'o
2005-01-15  2:36       ` H. Peter Anvin
2005-01-16  2:51         ` Matt Mackall
2005-01-16  3:18           ` H. Peter Anvin
2005-01-15  2:34     ` H. Peter Anvin
2005-01-19 15:48     ` Pavel Machek
2005-01-16  2:44 ` Matt Mackall
2005-01-16  3:58   ` Ulrich Drepper
2005-01-16  4:58     ` Matt Mackall
2005-01-16 13:23     ` Andries Brouwer [this message]

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=20050116132340.GA8163@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --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

all inboxes | Powered by JetHome®