Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QpK7Q-0000JO-LH for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 13:07:16 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=andyparkins@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QpK7Q-0007FX-0e for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 13:07:16 +0000 Received: by wwf25 with SMTP id 25so73900wwf.10 for ; Fri, 05 Aug 2011 06:07:09 -0700 (PDT) Received: by 10.227.19.195 with SMTP id c3mr1814248wbb.98.1312549629825; Fri, 05 Aug 2011 06:07:09 -0700 (PDT) Received: from dvr.localnet (mail.360visiontechnology.com [92.42.121.178]) by mx.google.com with ESMTPS id eo18sm2281152wbb.63.2011.08.05.06.07.07 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Aug 2011 06:07:08 -0700 (PDT) From: Andy Parkins To: bitcoin-development@lists.sourceforge.net Date: Fri, 5 Aug 2011 14:07:05 +0100 User-Agent: KMail/1.13.6 (Linux/2.6.38-2-686; KDE/4.6.3; i686; ; ) References: <201108041038.47396.luke@dashjr.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5973170.lotD1xUgr4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201108051407.06216.andyparkins@gmail.com> X-Spam-Score: -1.6 (-) 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 (andyparkins[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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 0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service -0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QpK7Q-0007FX-0e Subject: Re: [Bitcoin-development] Blitcoin? (Black Hat 2011) 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: Fri, 05 Aug 2011 13:07:16 -0000 --nextPart5973170.lotD1xUgr4 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On 2011 August 05 Friday, Gavin Andresen wrote: > "As reported, I've got a BitCoin deanonymization mechanism. It's not > complicated. >=20 > Connect to every node in the cloud, discoverable via sweeping/IRC/get_pee= rs > messages. The first IP to consistently relay transactions for a given > identity, is the given identity. Transaction forwarding could be randomised slightly, by randomising the=20 outgoing relay order; and adding a random delay between each forward. Even= =20 the massively connected monitor can't represent _all_ the connections on ev= ery=20 real node, so it would have no way of knowing whether it got any transactio= n=20 from the originator or because it got a fast path through the first N nodes= to=20 receive it. Andy =2D-=20 Dr Andy Parkins andyparkins@gmail.com --nextPart5973170.lotD1xUgr4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk476voACgkQwQJ9gE9xL220CACeOeJTNlTle1JcoLmZrkDcldKi QwMAnRYlOVD/OXQrZi01fU4pWOiQnJ3C =8M/g -----END PGP SIGNATURE----- --nextPart5973170.lotD1xUgr4--