Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.115 as permitted sender)
	client-ip=62.13.149.115; envelope-from=pete@petertodd.org;
	helo=outmail149115.authsmtp.co.uk; 
Date: Sat, 23 Aug 2014 18:51:38 -0400
From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>
Message-ID: <20140823225138.GB18381@savin.petertodd.org>
References: <CA+8=xuJ+YDTNjyDW7DvP8KPN_nrFWpE68HvLw6EokFa-B-QGKw@mail.gmail.com>
	<CAG8oi1O0RzEmnPg+t1GONnpmmEFucB_Ux35Ca8Y6g0TZf6CiCQ@mail.gmail.com>
	<CANEZrP1a_WNBJBKASfAngMU0HzgJ7as6Wec5x69dpBSO-vK0+Q@mail.gmail.com>
	<201408231902.57017.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb"
Content-Disposition: inline
In-Reply-To: <201408231902.57017.luke@dashjr.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: Encrypt bitcoin messages
Precedence: list


--mxv5cy4qt+RJ9ypb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Aug 23, 2014 at 07:02:55PM +0000, Luke Dashjr wrote:
> On Saturday, August 23, 2014 6:44:15 PM Mike Hearn wrote:
> > > Not to mention encrypting basically non-sensitive inter-node traffic =
is
> > > almost completely worthless in providing anonymity anyway...
> >=20
> > Recall that P2P connections carry Bloom filters too, which are not publ=
ic
> > information.
>=20
> As soon as you tell it to an unknown/public peer, it is public informatio=
n.

Mike is correct here: It *might* be public information, and probably
won't be. We already can give weak assurance that it probably won't be
against many weaker attackers, simply because getting lots of IP
addresses is moderately expensive, and in the future additional methods
will be developed and deployed.

--=20
'peter'[:-1]@petertodd.org
0000000000000000239344fc532bbad8a679e3fc30e8900772523a10c4720a0c

--mxv5cy4qt+RJ9ypb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJT+Rr1XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxNjI2NGM5NjViZWY5NmE1ZTI1ODhjOGQ5OWQxZDA1OWMx
OWY2ZWE1OWUwMjVkZGUvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfs7iQf/YcKwKjFrW7W3293mxbhLPuPr
1i8bmK+PVSyIQ3ufzSNsbdSyWaCnj3y1sdG3caUtbsuHiBVwoQQ/9tIvhJwL7Ztz
1/a78cg6Jq839HlRWK6RPd+jdP8cWpYK1qiOsPnq/6m6czgDlAiIhj8TCjcPgk63
5THiKB+x/SGgRjYY3xh4iNuIbQROgcEr+RmDeVDKEqow7T9Roc/Zziu8k5smNTfC
/O1mIDGNjK2izyNOnfm9qt1oq0ZcfXZKGcXp+ynwWRfS6ErBSHg9OveT3024Z2IS
s1IhJExHkKE5K3P/Oq6/Hxu6SbRdRxaBEIM1k8gQdGPgPrF/qXnHHjSQhUrB+A==
=sk55
-----END PGP SIGNATURE-----

--mxv5cy4qt+RJ9ypb--