From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Thomas Zander <thomas@thomaszander•se>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Does anyone have anything at all signed by Satoshi's PGP key?
Date: Mon, 15 Sep 2014 11:49:53 +0200 [thread overview]
Message-ID: <CAKaEYhKH1cO1-vTAf_g_bhfPV4rxf7MECyFkn1cgs5428G9x+w@mail.gmail.com> (raw)
In-Reply-To: <201409150923.02817.thomas@thomaszander.se>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2303 bytes --]
next prev parent reply other threads:[~2014-09-15 9:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 13:55 Peter Todd
2014-09-13 14:03 ` Jeff Garzik
2014-09-14 6:28 ` Peter Todd
2014-09-15 7:23 ` Thomas Zander
2014-09-15 9:49 ` Melvin Carvalho [this message]
2014-09-15 13:08 ` Jeff Garzik
2014-09-15 13:32 ` Brian Hoffman
2014-09-15 14:33 ` Jeff Garzik
2014-09-15 14:49 ` Brian Hoffman
2014-09-15 14:55 ` Pieter Wuille
2014-09-15 14:38 ` ThomasZander.se
2014-09-15 15:10 ` Thomas Zander
2014-09-15 15:51 ` Matt Whitlock
2014-09-15 16:07 ` Thomas Zander
2014-09-15 16:10 ` Gregory Maxwell
2014-09-15 16:20 ` Peter Todd
2014-09-15 14:44 ` Venzen
2014-09-15 18:06 ` Justus Ranvier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKaEYhKH1cO1-vTAf_g_bhfPV4rxf7MECyFkn1cgs5428G9x+w@mail.gmail.com \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=thomas@thomaszander$(echo .)se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox