From owner-freebsd-questions@FreeBSD.ORG Mon Sep 17 13:38:22 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84EFF16A41A for ; Mon, 17 Sep 2007 13:38:22 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6B213C45B for ; Mon, 17 Sep 2007 13:38:22 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id EE1495193F for ; Mon, 17 Sep 2007 09:37:58 -0400 (EDT) Date: Mon, 17 Sep 2007 14:37:56 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070917143756.420b7b94@gumby.homeunix.com.> In-Reply-To: References: <20070916215550.65e09a71@gumby.homeunix.com.> X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: /dev/random question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2007 13:38:22 -0000 On Mon, 17 Sep 2007 02:20:17 -0700 "Ted Mittelstaedt" wrote: > > > > -----Original Message----- > > From: owner-freebsd-questions@freebsd.org > > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of RW > > Sent: Sunday, September 16, 2007 1:56 PM > > To: freebsd-questions@freebsd.org > > Subject: Re: /dev/random question > > > > > > That's a poor analogy because they haven't improved /dev/random so > > it doesn't block, they've taken a /dev/urandom implementation and > > renamed it. In terms of your analogy they've blocked off the road, > > diverted everyone onto the highway, and renamed it to main street. > > > > Using Yarrow for /dev/random is not an intrinsically bad idea, but > > it is controversial. > > I really don't see what the issue is here. If you really want a > /dev/urandom on your system then fine - symlink /dev/random > to /dev/urandom and be done with it. My point was that Yarrow is a good choice for /dev/urandom but a controversial choice for /dev/random, so it would have been nice to have a choice as to whether /dev/random uses Yarrow or a conventional pool-based implementation.