Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <melvincarvalho@gmail.com>) id 1XTSv9-0007XR-3e
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 09:50:07 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.48 as permitted sender)
	client-ip=209.85.215.48; envelope-from=melvincarvalho@gmail.com;
	helo=mail-la0-f48.google.com; 
Received: from mail-la0-f48.google.com ([209.85.215.48])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XTSv5-0004xy-HB
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 09:50:06 +0000
Received: by mail-la0-f48.google.com with SMTP id ty20so4225494lab.21
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 02:49:53 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.35.138 with SMTP id h10mr24309059lbj.65.1410774593525;
	Mon, 15 Sep 2014 02:49:53 -0700 (PDT)
Received: by 10.112.13.99 with HTTP; Mon, 15 Sep 2014 02:49:53 -0700 (PDT)
In-Reply-To: <201409150923.02817.thomas@thomaszander.se>
References: <20140913135528.GC6333@muck>
	<CAJHLa0MaE3Ki5Hs4Tu4dQNBW-EL-857N2kf-fVxYcXM6OO-84w@mail.gmail.com>
	<20140914062826.GB21586@muck>
	<201409150923.02817.thomas@thomaszander.se>
Date: Mon, 15 Sep 2014 11:49:53 +0200
Message-ID: <CAKaEYhKH1cO1-vTAf_g_bhfPV4rxf7MECyFkn1cgs5428G9x+w@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Thomas Zander <thomas@thomaszander.se>
Content-Type: multipart/alternative; boundary=001a11c372bc815f790503178e53
X-Spam-Score: -0.6 (/)
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
	(melvincarvalho[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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: 1XTSv5-0004xy-HB
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Does anyone have anything at all signed
 by Satoshi's PGP key?
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: Mon, 15 Sep 2014 09:50:07 -0000

--001a11c372bc815f790503178e53
Content-Type: text/plain; charset=UTF-8

On 15 September 2014 09:23, Thomas Zander <thomas@thomaszander.se> wrote:

> On Sunday 14. September 2014 08.28.27 Peter Todd wrote:
> > Do we have any evidence Satoshi ever even had access to that key? Did he
> > ever use PGP at all for anything?
>
> Any and all PGP related howtos will tell you that you should not trust or
> sign
> a formerly-untrusted PGP (or GPG for that matter) key without seeing that
> person in real life, verifying their identity etc.
>
> I think that kind of disqualifies pgp for identity purposes wrt Satoshi :-)
>

But I presume that if the key is on bitcoin.org,  you can probably infer
that the owner of the key and the original owner of bitcoin.org are one and
the same ...


>
> --
> Thomas Zander
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--001a11c372bc815f790503178e53
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 15 September 2014 09:23, Thomas Zander <span dir=3D"ltr">&lt;<a href=
=3D"mailto:thomas@thomaszander.se" target=3D"_blank">thomas@thomaszander.se=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">O=
n Sunday 14. September <a href=3D"tel:2014%2008.28.27" value=3D"+1201408282=
7">2014 08.28.27</a> Peter Todd wrote:<br>
&gt; Do we have any evidence Satoshi ever even had access to that key? Did =
he<br>
&gt; ever use PGP at all for anything?<br>
<br>
</span>Any and all PGP related howtos will tell you that you should not tru=
st or sign<br>
a formerly-untrusted PGP (or GPG for that matter) key without seeing that<b=
r>
person in real life, verifying their identity etc.<br>
<br>
I think that kind of disqualifies pgp for identity purposes wrt Satoshi :-)=
<br></blockquote><div><br></div><div>But I presume that if the key is on <a=
 href=3D"http://bitcoin.org">bitcoin.org</a>,=C2=A0 you can probably infer =
that the owner of the key and the original owner of <a href=3D"http://bitco=
in.org">bitcoin.org</a> are one and the same ...<br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Thomas Zander<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Want excitement?<br>
Manually upgrade your production database.<br>
When you want reliability, choose Perforce<br>
Perforce version control. Predictably reliable.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D157508191&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D157508191&amp;iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div></div>

--001a11c372bc815f790503178e53--