Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Xu9gl-0002w5-D9 for bitcoin-development@lists.sourceforge.net; Fri, 28 Nov 2014 00:45:35 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.65 as permitted sender) client-ip=209.85.215.65; envelope-from=misterbg6@gmail.com; helo=mail-la0-f65.google.com; Received: from mail-la0-f65.google.com ([209.85.215.65]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Xu9gk-0002Lz-Iw for bitcoin-development@lists.sourceforge.net; Fri, 28 Nov 2014 00:45:35 +0000 Received: by mail-la0-f65.google.com with SMTP id hs14so33304lab.0 for ; Thu, 27 Nov 2014 16:45:28 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.189.10 with SMTP id ge10mr40749845lbc.23.1417135528230; Thu, 27 Nov 2014 16:45:28 -0800 (PST) Received: by 10.25.30.13 with HTTP; Thu, 27 Nov 2014 16:45:28 -0800 (PST) Date: Fri, 28 Nov 2014 01:45:28 +0100 Message-ID: From: Mistr Bigs To: Bitcoin Development Content-Type: multipart/alternative; boundary=001a11c37016c244f50508e0933d X-Spam-Score: -0.3 (/) 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 (misterbg6[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (misterbg6[at]gmail.com) 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: 1Xu9gk-0002Lz-Iw 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2014 00:45:35 -0000 --001a11c37016c244f50508e0933d Content-Type: text/plain; charset=UTF-8 That's what I was trying to say... The researchers are deanonymizing transactions from non-Tor connected hosts. So why are we talking about Tor limitations in response to this? Shouldn't we be discussing how to address the issues in Bitcoin proper? M On 11/27/2014 9:30 PM, Gregory Maxwell wrote: On Thu, Nov 27, 2014 at 5:44 PM, wrote: I might be mistaken, but it seems to me this paper discusses unintended ways of obtaining the IP addresses of clients involved in transactions on the core Bitcoin network. You're mistaken. :) If a node is used exclusively via tor it effectively doesn't have a IP address. (short of bugs of a class that aren't discussed here) The paper is about fingerprinting approaches that probabilistically connect transactions to hosts that you can already identify their IPs. --001a11c37016c244f50508e0933d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That's what I was trying to say... The researcher= s are deanonymizing transactions from non-Tor connected hosts. So why are w= e talking about Tor limitations in response to this? Shouldn't we be di= scussing how to address the issues in Bitcoin proper?

M
On 11/27/2014 9:30 PM, Gregory Maxwell wrote:
On Thu, Nov 27, 2014 at 5:44 PM, <misterbg6@gmail.com> wrote:

I might be mistaken, but it seems to me th=
is paper discusses unintended ways
of obtaining the IP addresses of clients involved in transactions on the
core Bitcoin network.

You're mistaken. :)

If a node is used exclusively via tor it effectively doesn't have a IP =
address.

(short of bugs of a class that aren't discussed here)

The paper is about fingerprinting approaches that probabilistically
connect transactions to hosts that you can already identify their IPs.

--001a11c37016c244f50508e0933d--