[187] in The Cryptographic File System users list

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

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

daemon@ATHENA.MIT.EDU (Charles@Schwieters.org)
Wed May 24 11:44:49 2000

From owner-cfs-users@nsa.research.att.com Wed May 24 15:44:49 2000
Return-Path: <owner-cfs-users@nsa.research.att.com>
Delivered-To: cfs-mtg@CHARON2.mit.edu
Received: (qmail 13156 invoked from network); 24 May 2000 15:44:49 -0000
Received: from h-135-207-30-103.research.att.com (HELO mail-green.research.att.com) (135.207.30.103)
  by charon2.mit.edu with SMTP; 24 May 2000 15:44:49 -0000
Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32])
	by mail-green.research.att.com (Postfix) with ESMTP
	id A96111E00B; Wed, 24 May 2000 11:44:47 -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 LAA20268;
	Wed, 24 May 2000 11:44:37 -0400 (EDT)
Received: (from majordomo@localhost) by nsa.research.att.com (8.7.3/8.7.3) id LAA19056 for cfs-users-list; Wed, 24 May 2000 11:41:59 -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-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by nsa.research.att.com (8.7.3/8.7.3) with ESMTP id LAA19052 for <cfs-users@nsa.research.att.com>; Wed, 24 May 2000 11:41:57 -0400 (EDT)
Received: by mail-blue.research.att.com (Postfix)
	id 0008E4CE2F; Wed, 24 May 2000 11:44:30 -0400 (EDT)
Delivered-To: cfs-users@research.att.com
Received: from argo.cit.nih.gov (argo.cit.nih.gov [165.112.92.24])
	by mail-blue.research.att.com (Postfix) with ESMTP id 45E674CE21
	for <cfs-users@research.att.com>; Wed, 24 May 2000 11:44:29 -0400 (EDT)
Received: from bach.cit.nih.gov (bach.cit.nih.gov [165.112.92.28])
	by argo.cit.nih.gov (8.9.3/8.9.3) with ESMTP id LAA29659;
	Wed, 24 May 2000 11:42:40 -0400 (EDT)
From: Charles@Schwieters.org
Received: by bach.cit.nih.gov (980427.SGI.8.8.8) id LAA07189; Wed, 24 May 2000 11:42:40 -0400 (EDT)
Date: Wed, 24 May 2000 11:42:40 -0400 (EDT)
Message-Id: <200005241542.LAA07189@bach.cit.nih.gov>
To: cfs-users@research.att.com
In-reply-to: <m31z2sezgw.fsf_-_@yuri.gweep.bc.ca> (message from Brian Edmonds
	on 24 May 2000 08:31:59 -0700)
Subject: Re: gathering randomness (was are there many active users...)
Cc: Charles@Schwieters.org
References: <m3wvklxpxu.fsf@yuri.gweep.bc.ca> <392AD9DA.BDCA74D@insta.com> <m31z2sezgw.fsf_-_@yuri.gweep.bc.ca>
Sender: owner-cfs-users@research.att.com
Precedence: bulk


guys--

  I also ran into problems with the cfs random number generator - on
linux 2.2.12. I also patched it by using /dev/random, which should be
better anyway. I previously posted my patch at

http://schwieters.org/cfs-1.4.0.beta2cds.patch.gz

The patch also fixes ccat and ccname to work with the latest 
cfs formats.

Charles

>  
>   -----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.


-- 
Charles Schwieters     email: Charles.Schwieters@nih.gov
		       www:   http://www.hec.utah.edu/~schwitrs
phone: (301) 402-4914  FAX:   (301) 402-2867

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