From: Venzen <venzen@mail•bihthai.net>
To: 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 21:44:05 +0700 [thread overview]
Message-ID: <5416FB35.1060700@mail.bihthai.net> (raw)
In-Reply-To: <CAJHLa0Owjs=6vhy_RSD+VSAZgBq2pSYv5HhCdA4-XCGgX=Z6dA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Funny that you should describe WoT that way. According to some
psycho-analysts the act of making love to a partner is actually a
realization of our subconscious desire to make love to ourselves.
So, in this sense, WoT geeks are indeed masturbating, but it's with
the good purpose of ensuring that it's being done via the intended
recipient and not some imposter or unsuspecting bystander.
That's a valid concern, especially as Bitcoin development ranks grow
and branch beyond a small core team.
On 09/15/2014 08:08 PM, Jeff Garzik wrote:
> On Mon, Sep 15, 2014 at 3:23 AM, Thomas Zander
> <thomas@thomaszander•se> wrote:
>> 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.
>
> Such guidelines are a perfect example of why PGP WoT is useless
> and stupid geek wanking.
>
> A person's behavioural signature is what is relevant. We know how
> Satoshi coded and wrote. It was the online Satoshi with which we
> interacted. The online Satoshi's PGP signature would be fine...
> assuming he established a pattern of use.
>
> As another example, I know the code contributions and PGP key
> signed by the online entity known as "sipa." At a bitcoin conf I
> met a person with photo id labelled "Pieter Wuille" who claimed to
> be sipa, but that could have been an actor. Absent a laborious and
> boring signed challenge process, for all we know, "sipa" is a
> supercomputing cluster of 500 gnomes.
>
> The point is, the "online entity known as Satoshi" is the relevant
> fingerprint. That is easily established without any in-person
> meetings.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUFvsyAAoJENQRrA3m8xlAwkAH/iRekS+Q0jIzaMPFJjD9Qh2e
TTpnQ5MyceeWaEQ9BIS9Lp92k/KlhYUmdaHRmmgOuUQZ6VlOmLSyveMe2qpX3igb
jZX3ydZe2hs1D3Z48MFyNBz06eufApSi5LC8BvN4bYotOD+/qrrxag+jaU3NjDu3
yCaSF563ZQ9xXkfh5JoZ3SGBcRmR5bS6QAoR29OQXBubriPwJuVxUBB37cfaL2Nf
rc67q2KgpU/vOyucxMFZgoP0vDjxUzXTc2ONrEHGJUfdypMADFwXjxeA8ikOt4ik
GIB69wMGQiMeE5e3H337yJxYaZJK4R1KnrSLF0j+Vkl3Yy25duBYAbFUGayeTw0=
=xR8K
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-09-15 14:44 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
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 [this message]
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=5416FB35.1060700@mail.bihthai.net \
--to=venzen@mail$(echo .)bihthai.net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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