From owner-freebsd-current Wed Oct 25 21:29:12 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 C708837B479 for ; Wed, 25 Oct 2000 21:29:10 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA10663; Wed, 25 Oct 2000 21:28:32 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39F7B2EF.6DCC868D@gorean.org> Date: Wed, 25 Oct 2000 21:28:31 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-102 i386) X-Accept-Language: en MIME-Version: 1.0 To: Wesley Morgan Cc: Mark Murray , " =?iso-8859-1?Q?=E1=CE=C4=D2=C5=CA=20=FE=C5=D2=CE=CF=D7?=" , current@FreeBSD.ORG Subject: Re: entropy reseeding is totally broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wesley Morgan wrote: > > I'm not knocking anyone or any code, especially considering this IS > -current... BUT... I don't need to read the code to know that I am seeing > the same fortunes on first login after reboot more often than I can > attribute to random chance. Maybe nanotime is being harvested, but it > seems that there is a time lag between system startup and reaching a state > of "true pseudo-entropy". Also, every reboot has entropy caching failing > to work. I don't know if this is a product of the broken reseeding or > what, because the /etc/rc files seem to be fine. How exactly are you rebooting? If you're using the 'reboot' command, that explains why entropy reseeding is not working. As has been discussed several times on -current, you only run rc.shutdown if you use another method, like 'shutdown -r now', 'init 6', or even the trust three-finger salute. Good luck, 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