Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XLGIo-0003qY-6H for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 18:44:38 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f181.google.com; Received: from mail-ob0-f181.google.com ([209.85.214.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XLGIX-0001mp-As for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 18:44:38 +0000 Received: by mail-ob0-f181.google.com with SMTP id va2so9276655obc.26 for ; Sat, 23 Aug 2014 11:44:15 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.33.33 with SMTP id o1mr12146749obi.24.1408819455832; Sat, 23 Aug 2014 11:44:15 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.82.34 with HTTP; Sat, 23 Aug 2014 11:44:15 -0700 (PDT) In-Reply-To: References: <53F3DFF7.9070709@jrn.me.uk> <1569765.oHsHtFYAhh@1337h4x0r> <53F8C656.6010200@riseup.net> <20140823175038.GU22640@nl.grid.coop> Date: Sat, 23 Aug 2014 20:44:15 +0200 X-Google-Sender-Auth: 72l6ZXln3_Fo74vdA6QquLr0QGk Message-ID: From: Mike Hearn To: William Yager Content-Type: multipart/alternative; boundary=001a11c1fe1e37baa405015057c1 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XLGIX-0001mp-As Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal: Encrypt bitcoin messages X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 18:44:38 -0000 --001a11c1fe1e37baa405015057c1 Content-Type: text/plain; charset=UTF-8 > > Not to mention encrypting basically non-sensitive inter-node traffic is > almost completely worthless in providing anonymity anyway... > Recall that P2P connections carry Bloom filters too, which are not public information. --001a11c1fe1e37baa405015057c1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Not to mention encrypting basically non-sensitive inte= r-node traffic is almost completely worthless in providing anonymity anyway= ...=C2=A0

Recall that P2P connections carry Bloom filters too, which are not public = information.
--001a11c1fe1e37baa405015057c1--