Date: Fri, 26 Sep 2008 21:13:39 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: using /dev/random 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 25 Sep 2008 20:33:34 +0100 Kris Kennaway <kris@FreeBSD.org> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080926211339.70c03147>