From owner-freebsd-current Sun Jul 30 11:26:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id D6F0537B706; Sun, 30 Jul 2000 11:26:14 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id UAA09292; Sun, 30 Jul 2000 20:26:16 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007301826.UAA09292@grimreaper.grondar.za> To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Brian Fundakowski Feldman "Sun, 30 Jul 2000 13:28:47 -0400." Date: Sun, 30 Jul 2000 20:26:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > EG, by having it such that Yarrow state perturbations happen often > > enough that each read is "guaranteed" to be associated with at least > > one and preferably more. > > Can you give me an idea how this would work, at least with e.g. > pseudocode annotation of the current code? I'm curious what you're > going to change that will allow reseeeding while a read is in > progress. I didn't say "reseed", I said "perturb". Same code, (improved reseed control), more harvesting calls. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message