1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <misterbg6@gmail.com>) id 1Xu37i-0003fl-HQ
for bitcoin-development@lists.sourceforge.net;
Thu, 27 Nov 2014 17:44:58 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.193 as permitted sender)
client-ip=209.85.217.193; envelope-from=misterbg6@gmail.com;
helo=mail-lb0-f193.google.com;
Received: from mail-lb0-f193.google.com ([209.85.217.193])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Xu37h-00042v-Ff
for bitcoin-development@lists.sourceforge.net;
Thu, 27 Nov 2014 17:44:58 +0000
Received: by mail-lb0-f193.google.com with SMTP id w7so720627lbi.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 27 Nov 2014 09:44:51 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.152.27.73 with SMTP id r9mr37705004lag.33.1417110291121;
Thu, 27 Nov 2014 09:44:51 -0800 (PST)
Received: by 10.25.30.13 with HTTP; Thu, 27 Nov 2014 09:44:51 -0800 (PST)
Date: Thu, 27 Nov 2014 18:44:51 +0100
Message-ID: <CABssiCqwF_JFLfnSd5Hhh6oN6w2YzOVhjmWD3oMznLpvmvQNsw@mail.gmail.com>
From: Mistr Bigs <misterbg6@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0160c274828d0e0508dab327
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: 1Xu37h-00042v-Ff
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: Thu, 27 Nov 2014 17:44:58 -0000
--089e0160c274828d0e0508dab327
Content-Type: text/plain; charset=UTF-8
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.
Tor was mentioned only insofar as it might be one's first thought of how to
mitigate this risk, yet Bitcoin over Tor has its own problems that prevent
this from being effective.
But the primary "issues" mentioned in the paper are regarding a Bitcoin
node in default operation, no?
"In their new study, researchers at the Laboratory of Algorithmics,
Cryptology and Security of the University of Luxembourg have shown that
Bitcoin does not protect user's IP address and that it can be linked to the
user's transactions in real-time."
"The basic idea behind these findings is that Bitcoin entry nodes, to which
the user's computer connects in order to make a transaction, form a unique
identifier for the duration of user's session. This unique pattern can be
linked to a user's IP address. Moreover, transactions made during one
session, even those made via unrelated pseudonyms, can be linked together.
With this method, hackers can reveal up to 60 percent of the IP addresses
behind the transactions made over the Bitcoin network."
"'This Bitcoin network analysis combined with previous research on
transaction flows shows that the level of anonymity in the Bitcoin network
is quite low,' explains Dr. Alex Biryukov."
M
--089e0160c274828d0e0508dab327
Content-Type: text/html; charset=UTF-8
<div dir="ltr">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.<br>
Tor was mentioned only insofar as it might be one's first thought of how
to mitigate this risk, yet Bitcoin over Tor has its own problems that
prevent this from being effective.<br>
But the primary "issues" mentioned in the paper are regarding a Bitcoin node in default operation, no?<br>
<br>
"In their new study, researchers at the Laboratory of Algorithmics,
Cryptology and Security of the University of Luxembourg have shown that
Bitcoin does not protect user's IP address and that it can be linked to
the user's transactions in real-time."<br>
<br>
"The basic idea behind these findings is that Bitcoin entry nodes, to
which the user's computer connects in order to make a transaction, form a
unique identifier for the duration of user's session. This unique
pattern can be linked to a user's IP address. Moreover, transactions
made during one session, even those made via unrelated pseudonyms, can
be linked together. With this method, hackers can reveal up to 60
percent of the IP addresses behind the transactions made over the
Bitcoin network."<br>
<br>
"'This Bitcoin network analysis combined with previous research on
transaction flows shows that the level of anonymity in the Bitcoin
network is quite low,' explains Dr. Alex Biryukov."<br>
<br>
M</div>
--089e0160c274828d0e0508dab327--
|
