From owner-freebsd-current Mon Jul 17 9:31:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E82C337B5CC; Mon, 17 Jul 2000 09:31:39 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA33104; Mon, 17 Jul 2000 09:35:15 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200007171635.JAA33104@troutmask.apl.washington.edu> Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <39731FC5.34D3074D@FreeBSD.org> from Maxim Sobolev at "Jul 17, 2000 06:01:25 pm" To: Maxim Sobolev Date: Mon, 17 Jul 2000 09:35:15 -0700 (PDT) Cc: Mark Murray , "Louis A. Mamakos" , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: [Charset koi8-r unsupported, filtering to ASCII...] > Mark Murray wrote: > > > Agreed. I have already committed a "persistent" entropy cache that > > reseeds the random device on reboot. > > You may also want to extend /etc/crontab to periodically save entropy. > This would help if something unexpected like halt(8) or panic(9) happened. > I thought about a reseed daemon periodically saving entropy to, say, /var/log/entropy. But, a crontab entry would work just as well. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message