From: Mistr Bigs <misterbg6@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Deanonymisation of clients in Bitcoin P2P network paper
Date: Fri, 28 Nov 2014 01:45:28 +0100 [thread overview]
Message-ID: <CABssiCpUE=3GhC+Scd3htzVb9+gmLeZ0mEO5LY-zxywvguZ--w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
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, <misterbg6@gmail•com> 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.
[-- Attachment #2: Type: text/html, Size: 1216 bytes --]
next reply other threads:[~2014-11-28 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 0:45 Mistr Bigs [this message]
2014-11-28 5:30 ` Gregory Maxwell
2014-12-11 11:51 ` Isidor Zeuner
-- strict thread matches above, loose matches on Subject: below --
2014-11-27 17:44 Mistr Bigs
2014-11-27 20:30 ` Gregory Maxwell
2014-11-26 7:47 Jean-Paul Kogelman
2014-11-26 13:51 ` Jeff Garzik
2014-11-26 17:13 ` odinn
2014-11-27 2:09 ` Isidor Zeuner
2014-11-27 2:22 ` Gregory Maxwell
2014-11-27 11:06 ` Mike Hearn
2014-11-27 11:27 ` Wladimir
2014-12-08 16:15 ` Isidor Zeuner
2014-12-08 16:59 ` Mike Hearn
2015-01-22 0:44 ` Isidor Zeuner
2015-01-22 13:20 ` Mike Hearn
2014-12-15 13:25 ` Isidor Zeuner
2014-12-01 10:42 ` Isidor Zeuner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABssiCpUE=3GhC+Scd3htzVb9+gmLeZ0mEO5LY-zxywvguZ--w@mail.gmail.com' \
--to=misterbg6@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox