From: "Theodore Ts'o" <tytso@mit.edu>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: short read from /dev/urandom
Date: Fri, 14 Jan 2005 18:21:54 -0500 [thread overview]
Message-ID: <20050114232154.GB18479@thunk.org> (raw)
In-Reply-To: <41E833F4.8090800@redhat.com>
On Fri, Jan 14, 2005 at 01:04:52PM -0800, Ulrich Drepper wrote:
> I'm concerned that there is isgnificant code out there relying on the
> no-short-read promise. And perhaps more importantly, other
> implementations promise the same.
>
> The code in question comes from a crypto library which is in wide use
> (http://www.cryptopp.com) and it is using urandom under this assumption.
> I fear there is quite a bit more code like this out there. Changing
> the ABI after the fact is no good and dangerous in this case.
>
> I know this is making the device special, but I really think the
> no-short-reads property should be perserved for urandom.
Good point. The fact that there are other implementations out there
which are doing this is a convincing argument.
I am still a bit concerned still that a stupidly written program that
opens /dev/urandom (perhaps unwittingly) and tries to read a few
hundred megabytes will become uninterruptible until the read
completes, but I'm not sure it's worth it to but in some kludge that
says "break if there's a signal and count > 1 megabyte --- otherwise
we'll return soon enough".
- Ted
next prev parent reply other threads:[~2005-01-14 23:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 4:54 short read from /dev/urandom 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 [this message]
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
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=20050114232154.GB18479@thunk.org \
--to=tytso@mit.edu \
--cc=drepper@redhat.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 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.