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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D792286
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Aug 2015 17:31:13 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f169.google.com (mail-yk0-f169.google.com
[209.85.160.169])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 345CDEE
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Aug 2015 17:31:13 +0000 (UTC)
Received: by ykdt205 with SMTP id t205so133549386ykd.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Aug 2015 10:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=UszyVVtbdE/QvaRokU6eQ4nAaIW8O9odARhOEtrui+8=;
b=bj3Np7de+FbtIeXIrEDvhlPU54CEew5knAiHdZKnh/njJ20Clu67il+rzD/L13dIDP
Qa6ryj6yPUJSMgJqtjQrQpVuKoUUqQRJ1ggXJNxR2GO9PzdvBndaHb33T70wckPpHTTQ
HV7BRHHb3BbsBilfYwvp0d2+eMS7qHSl1i+pRd/eC/6yZbFjmbEHibBR2ie7aTOlNGTg
3zaYc/osDcYKkaj7nIkEm76CixO4Js8vxEePMeV7nNMT0JV0Q5znQ6+5AevAtanB+AOU
AueqmD+ZWxM3pQdSw/zyMtwc77jGMNGFm07XTDHwiFbkwjAVCXvNMrFDm7fYmBuQ6W2r
hq9A==
X-Received: by 10.13.247.3 with SMTP id h3mr2763039ywf.142.1439832672445; Mon,
17 Aug 2015 10:31:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.94.132 with HTTP; Mon, 17 Aug 2015 10:30:53 -0700 (PDT)
In-Reply-To: <CABm2gDpLB+hBy0AA3oPseOjq03k7c9KNCSHkyq+Tz72fGcsvUA@mail.gmail.com>
References: <6EC9DDF352DC4838AE9B088AB372428A25E1F42A@DS04>
<55D1C81D.4070402@olivere.de>
<CABm2gDrQTSyJUDWzO5FEy8GD76+coN7tM--8rhC7i0vfmUf0Qw@mail.gmail.com>
<55D1CAAF.6010400@olivere.de>
<CABm2gDqNUzqXNjih0TkCyAxUjWTcdHFsdYJYT9wriy7wDx3teg@mail.gmail.com>
<55D21356.4010302@olivere.de>
<CABm2gDpLB+hBy0AA3oPseOjq03k7c9KNCSHkyq+Tz72fGcsvUA@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Mon, 17 Aug 2015 18:30:53 +0100
Message-ID: <CADJgMzuUgX1AqqZkmDpKed422Z3OZz0eboRWi5+kRhk5DrRQDQ@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=94eb2c0802a0fa2b20051d852aee
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2015 17:31:13 -0000
--94eb2c0802a0fa2b20051d852aee
Content-Type: text/plain; charset=UTF-8
For the record I would like to share my technical analysis of the Satoshi
email which I wrote in a pastebin (http://pastebin.com/Ct5M8fa2) a few days
ago.
1. The email is the one used by Satoshi to announce Bitcoin in the first
place.
http://www.metzdowd.com/pipermail/cryptography/2008-October/014810.html
2. The email was not spoofed, it actually originated from vistomail's
server. The email headers show the email originated from 190.97.163.93 and
the SPF records show this as an authorised sender for the email. This does
not prove the account wasn't hacked of course, or that the account might
have expired and be re-registered by someone else (vistomail is a paid for
email provider).
3. While the email is not signed, and there are a number of PGP keys listed
on key servers for him (to vary addresses), he didnt sign any emails with
any PGP keys.
It is therefore not possible to outright dismiss the email's authenticity
as the email originates from an authentic source. The only questions is
whether the webmail service was hacked or commandeered somehow.
--94eb2c0802a0fa2b20051d852aee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">For the record I would like to =
share my technical analysis of the Satoshi email which I wrote in a pastebi=
n (<a href=3D"http://pastebin.com/Ct5M8fa2">http://pastebin.com/Ct5M8fa2</a=
>) a few days ago.</div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">1. The email is the one used by Satoshi to announce Bitcoin in=
the first place.=C2=A0</div><div class=3D"gmail_extra"><a href=3D"http://w=
ww.metzdowd.com/pipermail/cryptography/2008-October/014810.html">http://www=
.metzdowd.com/pipermail/cryptography/2008-October/014810.html</a></div><div=
class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">2. The email wa=
s not spoofed, it actually originated from vistomail's server. The emai=
l headers show the email originated from=C2=A0<span style=3D"color:rgb(0,0,=
0);white-space:pre-wrap">190.97.163.93 and the SPF records show this as an =
authorised sender for the email</span>. This does not prove the account was=
n't hacked of course, or that the account might have expired and be re-=
registered by someone else (vistomail is a paid for email provider).</div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">3. While the=
email is not signed, and there are a number of PGP keys listed on key serv=
ers for him (to vary addresses), he didnt sign any emails with any PGP keys=
.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">It i=
s therefore not possible to outright dismiss the email's authenticity a=
s the email originates from an authentic source. The only questions is whet=
her the webmail service was hacked or commandeered somehow.</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div></div>
--94eb2c0802a0fa2b20051d852aee--
|
