From owner-freebsd-current Fri Oct 20 1:19:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 2420337B4D7; Fri, 20 Oct 2000 01:19:23 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA41140; Fri, 20 Oct 2000 01:19:02 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Fri, 20 Oct 2000 01:19:02 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: Udo Schweigert Cc: Andrej Cernov , current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: entropy reseeding is totally broken In-Reply-To: <20001020075809.A20959@alaska.cert.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Oct 2000, Udo Schweigert wrote: > On Fri, Oct 20, 2000 at 08:48:46 +0400, Andrej Cernov wrote: > > In very recent -current, my entropy file writted and readed sucessfully, > > but I got the same fortune quote again and again right after reboot! > > > > It means that anything writted to /dev/random not reseed it but _reset_ it > > to the same default state. > > > > How do you shutdown your machine: > > a) reboot or halt > b) shutdown -r now C-A-D usually works too, as does 'init 6'. One of the oft-agreed on topics at the con is that we need a _consistent_ schedule of events for all forms of shutdown that are not explicitly "fast" shutdown paths that for whatever reason we don't want to schedule things like rc.shutdown and sync for. Expect to see conversation about this on -arch sometime soon. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message