From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <jgarzik@bitpay.com>) id 1Xtd0h-000708-Ag for bitcoin-development@lists.sourceforge.net; Wed, 26 Nov 2014 13:51:59 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.223.173 as permitted sender) client-ip=209.85.223.173; envelope-from=jgarzik@bitpay.com; helo=mail-ie0-f173.google.com; Received: from mail-ie0-f173.google.com ([209.85.223.173]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Xtd0g-0000XG-6L for bitcoin-development@lists.sourceforge.net; Wed, 26 Nov 2014 13:51:59 +0000 Received: by mail-ie0-f173.google.com with SMTP id y20so2627999ier.4 for <bitcoin-development@lists.sourceforge.net>; Wed, 26 Nov 2014 05:51:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=serTvczi2XkMyOXRVaaMcI2dIpiOq1BHMC26qc10Q/o=; b=UPfFHZXIIzQtVyEz0uYIjzDQ2wdNKQftlOog+JglCiOycOOwMSeR869YXPwXmiUAGZ mXEALsSdyZ9nG5HYHMOM7lx43sjHBLZhIg8Lofis/iyCz2HDZarbkdsIjjooUyEZbxHY AD/P1IXx/uC4/v03h06aM7UKFZy1TFB8xxUZrMf1zNwu5TN65h/BkrxbqNbH6ezTFohG QuyIe/R9GusiUJguP86HXyaJ/UqCF5XY5KTOs10JKhFVzLEyH97L7CsarAj8pGkwcu0e K2+V/SBRfplesd3PgqNVpWGrLy4an3hAOcvKp1KE/+Mnbpn16g/A5Xcr8QiBei7Ijp+p v6pw== X-Gm-Message-State: ALoCoQnSmldi6pYfOphVQpptMkUPHmvug1281X/sYjt7ArY2060fomP3xoQ5Oyv3z4+JJrlf7ZhL X-Received: by 10.43.47.5 with SMTP id uq5mr1027961icb.30.1417009912386; Wed, 26 Nov 2014 05:51:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.151.143 with HTTP; Wed, 26 Nov 2014 05:51:31 -0800 (PST) In-Reply-To: <4E783164-B2DC-45BC-946C-8EA191F31193@me.com> References: <4E783164-B2DC-45BC-946C-8EA191F31193@me.com> From: Jeff Garzik <jgarzik@bitpay.com> Date: Wed, 26 Nov 2014 08:51:31 -0500 Message-ID: <CAJHLa0N6+hpwNECpHUSiKuj4-BYohh=Wr1DP=67Ff8xVBsi8-Q@mail.gmail.com> To: Jean-Paul Kogelman <jeanpaulkogelman@me.com> Content-Type: multipart/alternative; boundary=bcaec52e600578b1ea0508c35470 X-Spam-Score: -0.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 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 X-Headers-End: 1Xtd0g-0000XG-6L Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Deanonymisation of clients in Bitcoin P2P network paper X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Wed, 26 Nov 2014 13:51:59 -0000 --bcaec52e600578b1ea0508c35470 Content-Type: text/plain; charset=UTF-8 I don't recall being contacted directly, but the attack has been discussed. It relies on a number of conditions. For example, if you are over Tor, they try to kick the machine off Tor, _assuming_ that it will fall back to non-Tor. That's only true for dual stack nodes, which are not really 100% anonymous anyway -- you're operating from your public IP anyway. On Wed, Nov 26, 2014 at 2:47 AM, Jean-Paul Kogelman <jeanpaulkogelman@me.com > wrote: > This paper was just posted on reddit that describes how an attacker can > de-anonymize clients on the bitcoin network. It mentions that the core devs > were contacted prior to publication. I was just wondering, how many of > these issues have already been addressed? > > > Paper (University of Luxembourg): > http://orbilu.uni.lu/handle/10993/18679 > > > Kind regards, > > Jean-Paul > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ --bcaec52e600578b1ea0508c35470 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I don't recall being contacted directly, but the attac= k has been discussed.=C2=A0 It relies on a number of conditions.=C2=A0 For = example, if you are over Tor, they try to kick the machine off Tor, _assumi= ng_ that it will fall back to non-Tor.=C2=A0 That's only true for dual = stack nodes, which are not really 100% anonymous anyway -- you're opera= ting from your public IP anyway.<br><br></div><div class=3D"gmail_extra"><b= r><div class=3D"gmail_quote">On Wed, Nov 26, 2014 at 2:47 AM, Jean-Paul Kog= elman <span dir=3D"ltr"><<a href=3D"mailto:jeanpaulkogelman@me.com" targ= et=3D"_blank">jeanpaulkogelman@me.com</a>></span> wrote:<br><blockquote = class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid= ;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>This paper was = just posted on reddit that describes how an attacker can de-anonymize clien= ts on the bitcoin network. It mentions that the core devs were contacted pr= ior to publication. I was just wondering, how many of these issues have alr= eady been addressed?</div><div><br></div><div><br></div><div>Paper (Univers= ity of Luxembourg):</div><div><a href=3D"http://orbilu.uni.lu/handle/10993/= 18679" target=3D"_blank">http://orbilu.uni.lu/handle/10993/18679</a></div><= div><br></div><div><br></div><div>Kind regards,</div><div><br></div><div>Je= an-Paul</div></div><br>----------------------------------------------------= --------------------------<br> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server<br> from Actuate! Instantly Supercharge Your Business Reports and Dashboards<br= > with Interactivity, Sharing, Native Excel Exports, App Integration & mo= re<br> Get technology previously reserved for billion-dollar corporations, FREE<br= > <a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D157005751&iu= =3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam= pad/clk?id=3D157005751&iu=3D/4140/ostg.clktrk</a><br>__________________= _____________________________<br> Bitcoin-development mailing list<br> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo= pment@lists.sourceforge.net</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development= " target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment</a><br> <br></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail= _signature">Jeff Garzik<br>Bitcoin core developer and open source evangelis= t<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" targe= t=3D"_blank">https://bitpay.com/</a></div> </div> --bcaec52e600578b1ea0508c35470--