From owner-freebsd-security Wed May 3 11: 9:47 2000 Delivered-To: freebsd-security@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id DD23937B7D6 for ; Wed, 3 May 2000 11:09:42 -0700 (PDT) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (1109 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Wed, 3 May 2000 13:06:09 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Wed, 3 May 2000 13:06:04 -0500 (CDT) From: James Wyatt To: Matthew Dillon Cc: "Andrew J. Korty" , security@FreeBSD.ORG Subject: Re: Cryptographic dump(8) In-Reply-To: <200005031718.KAA63329@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 3 May 2000, Matthew Dillon wrote: [ losts stuff deleted ] > Also, putting a random number in each block is important if each block > is separately encrypted, for the same reason. > > Using /dev/random to obtain your random numbers is considered to be > acceptable. How can you tell how much entropy is in the 'pool' for /dev/random and it's about to start being not-so-random? Pull a sample once in a while and Chi test it? I like being able to know. - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message