MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
Precedence: list

--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&#39;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&#39;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&#39;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--