From owner-freebsd-questions@FreeBSD.ORG Fri Sep 26 20:25:05 2008 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 47F96106569B for ; Fri, 26 Sep 2008 20:25:05 +0000 (UTC) (envelope-from fbsd06+2E=28e05097@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id 199318FC0A for ; Fri, 26 Sep 2008 20:25:05 +0000 (UTC) (envelope-from fbsd06+2E=28e05097@mlists.homeunix.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in1.mxes.net (Postfix) with ESMTP id B07751643A8 for ; Fri, 26 Sep 2008 16:13:44 -0400 (EDT) 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 B2551D05AF for ; Fri, 26 Sep 2008 16:13:42 -0400 (EDT) Date: Fri, 26 Sep 2008 21:13:39 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080926211339.70c03147@gumby.homeunix.com.> In-Reply-To: <48DBE78E.70101@FreeBSD.org> References: <18648.30321.369520.631459@jerusalem.litteratus.org> <20080923224057.46955938@gumby.homeunix.com.> <48DBE78E.70101@FreeBSD.org> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: using /dev/random 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: Fri, 26 Sep 2008 20:25:05 -0000 On Thu, 25 Sep 2008 20:33:34 +0100 Kris Kennaway wrote: > RW wrote: > > On Tue, 23 Sep 2008 11:52:07 -0400 > > kern.random.sys.seeded is just a flag that gets set to 1 on each > > reseed. IIRC it's also initialized to 1 so it doesn't actually do > > anything very useful. > > Except tell you that the kernel random number generator has finished > seeding ;) Not if it's initialized to 1. I'm not really sure if this is a bug, or whether the developers simply gave-up on starting the device blocked - rc.d/initrandom would unblock it anyway. The checks in rc.d/sshd are pointless.