From owner-freebsd-current Mon Jul 17 23: 3:45 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 64A8E37B9AE for ; Mon, 17 Jul 2000 23:03:38 -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 IAA03329; Tue, 18 Jul 2000 08:04:37 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007180604.IAA03329@grimreaper.grondar.za> To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007180145.VAA00554@whizzo.transsys.com> In-Reply-To: <200007180145.VAA00554@whizzo.transsys.com> ; from "Louis A. Mamakos" "Mon, 17 Jul 2000 21:45:52 -0400." Date: Tue, 18 Jul 2000 08:04:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, you could really use this in ntpd(8), rather than just ntpdate. > You could crank in the offset and delay samples for each packet > received from an NTP peer; this will have the effect of adding into > the entropy pool the "noise" in the latency of the path between you > and each of your NTP peers. This varies over time with each sample, > and in fact, NTP goes to considerable effort in it's sample filtering > to exclude the noisy samples. We need to get that date before it's > discarded and contribute it to the entropy cause. You forget; a snooper watching your (ether)net has access to nearly all of this information. 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