From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f171.google.com (mail-iy0-f171.google.com [209.85.210.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 3BF96200ABA for ; Thu, 22 Sep 2011 10:34:04 -0700 (PDT) Received: by iagv1 with SMTP id v1so5456849iag.16 for ; Thu, 22 Sep 2011 10:34:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/26efiqNC3YPEDi0gMaIasLB+3q5GpDxl+bkHmCvTmQ=; b=RNTNVsc1bfze3R8emu8SQ1rRAzOlUQStWK/1C0NQ67j6/8ZM6Ne9WXen8o5+8Akiqf T+Dbq3IX30kCSAYBeKlZ/ZXdFuBlq3wnQZbvDUmfKLYLUyZS+El0AG1CIKz7tLPcG+TY D9I/dnxpzu1txDUOcQv1xuFJEjpCeOLwYCDac= MIME-Version: 1.0 Received: by 10.42.174.9 with SMTP id t9mr2554823icz.183.1316712843314; Thu, 22 Sep 2011 10:34:03 -0700 (PDT) Received: by 10.43.132.8 with HTTP; Thu, 22 Sep 2011 10:34:03 -0700 (PDT) In-Reply-To: <4E7B6D48.2040205@hp.com> References: <20110921230205.2275820C2E5@snark.thyrsus.com> <20110922021137.GB21302@thyrsus.com> <4E7B6D48.2040205@hp.com> Date: Thu, 22 Sep 2011 10:34:03 -0700 Message-ID: Subject: Re: Preliminary results of using GPS to look for clock skew From: Dave Taht To: Rick Jones Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: esr@thyrsus.com, Eric Raymond , bloat-devel@lists.bufferbloat.net X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 17:34:04 -0000 On Thu, Sep 22, 2011 at 10:15 AM, Rick Jones wrote: > >> >> One thing that surprised me of late is >> http://www.bufferbloat.net/issues/271 >> >> while not related, surprises are the last thing we need as regards to >> time. >> > > The decision to stop letting networking contribute to entropy goes back a > few years actually :) I wasn't paying attention then. > In another context, also where running-out of entropy was a problem, some= one > mentioned there are RNGs on USB keys that can be used to provide > randomness/entropy/whatnot. =A0The one mentioned in that discussion was t= he > "Entropy Key" from these folks: http://www.entropykey.co.uk/ While I would like RNGs to be on-chip, the lack of randomness in a system that supposedly does a lot of WPA encryption does concern me. https://dev.openwrt.org/ticket/9631 Secondly, routers at least have multiple interfaces to get randomness from which would be hard to spoof all at the same time. and wireless routers have more noise sources and interfaces... so while I find the decision to eliminate networking as a source of randomn= ess makes some sense in a device with only one interface, I find it indefensibl= e to have nearly no entropy pool at all as a result for devices with multiple interfaces. > rick jones > --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://the-edge.blogspot.com