From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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> <20140914062826.GB21586@muck> <201409150923.02817.thomas@thomaszander.se> Date: Mon, 15 Sep 2014 11:49:53 +0200 Message-ID: From: Melvin Carvalho To: Thomas Zander 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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


On 15 September 2014 09:23, Thomas Zander <thomas@thomaszander.se= > wrote:
O= n 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 tru= st 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,=C2=A0 you can probably infer = that the owner of the key and the original owner of bitcoin.org are one and the same ...
=C2=A0
=

--
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/gam= pad/clk?id=3D157508191&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--001a11c372bc815f790503178e53--