[186] in The Cryptographic File System users list

home help back first fref pref prev next nref lref last post

gathering randomness (was are there many active users...)

daemon@ATHENA.MIT.EDU (Brian Edmonds)
Wed May 24 11:33:05 2000

From owner-cfs-users@nsa.research.att.com Wed May 24 15:33:05 2000
Return-Path: <owner-cfs-users@nsa.research.att.com>
Delivered-To: cfs-mtg@CHARON2.mit.edu
Received: (qmail 13074 invoked from network); 24 May 2000 15:33:05 -0000
Received: from mail-blue.research.att.com (135.207.30.102)
  by charon2.mit.edu with SMTP; 24 May 2000 15:33:05 -0000
Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 1F8314CE18; Wed, 24 May 2000 11:33:05 -0400 (EDT)
Received: from nsa.research.att.com (majordomo@nsa.research.att.com [135.207.24.155])
	by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id LAA19877;
	Wed, 24 May 2000 11:32:54 -0400 (EDT)
Received: (from majordomo@localhost) by nsa.research.att.com (8.7.3/8.7.3) id LAA19024 for cfs-users-list; Wed, 24 May 2000 11:30:10 -0400 (EDT)
X-Authentication-Warning: nsa.research.att.com: majordomo set sender to owner-cfs-users@nsa.research.att.com using -f
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103]) by nsa.research.att.com (8.7.3/8.7.3) with ESMTP id LAA19020 for <cfs-users@nsa.research.att.com>; Wed, 24 May 2000 11:30:08 -0400 (EDT)
Received: by mail-green.research.att.com (Postfix)
	id 5000B1E00C; Wed, 24 May 2000 11:32:41 -0400 (EDT)
Delivered-To: cfs-users@research.att.com
Received: from lios.gweep.bc.ca (a3a17164.sympatico.bconnected.net [209.53.11.73])
	by mail-green.research.att.com (Postfix) with ESMTP id BE6B41E00F
	for <cfs-users@research.att.com>; Wed, 24 May 2000 11:32:40 -0400 (EDT)
Received: (from uucp@localhost)
	by lios.gweep.bc.ca (8.9.3/8.9.1) with UUCP id IAA13030
	for cfs-users@research.att.com; Wed, 24 May 2000 08:32:40 -0700
Received: by yuri.gweep.bc.ca (Postfix, from userid 500)
	id 02C6F56B39; Wed, 24 May 2000 08:31:59 -0700 (PDT)
To: cfs-users@research.att.com
Subject: gathering randomness (was are there many active users...)
References: <m3wvklxpxu.fsf@yuri.gweep.bc.ca> <392AD9DA.BDCA74D@insta.com>
From: Brian Edmonds <brian@gweep.bc.ca>
Date: 24 May 2000 08:31:59 -0700
In-Reply-To: "Stephen D. Williams"'s message of "Tue, 23 May 2000 15:19:54 -0400"
Message-ID: <m31z2sezgw.fsf_-_@yuri.gweep.bc.ca>
Lines: 25
User-Agent: Gnus/5.0806 (Gnus v5.8.6) XEmacs/21.1 (Bryce Canyon)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-cfs-users@research.att.com
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Stephen D. Williams" <sdw@insta.com> writes:
> This is a bit confusing.  There should be a kernel message in syslog
> to warn about extended waits.  I believe that the problem is that
> /dev/random in Linux is very stringent about gathering enough true
> randomness before returning.

Is this a newer version than 1.4.0beta2 that has been distributed only
to the list?  That was the newest version I could find out on the net,
and it knows nothing of /dev/[u]random.  It does randomness gathering
with some itimer/setjmp/longjmp hack that I'm sure is way cool, but lost
me entirely. :)

Brian.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iD8DBQE5K/XucCEFQUX5+OwRAgCyAKCfeKwE81jDkRIiofa2Bwy3FWssHACdFsC8
LRZUtPM/qgyJdDq8VDT0KOo=
=SmoA
-----END PGP SIGNATURE-----


home help back first fref pref prev next nref lref last post