summaryrefslogtreecommitdiff
path: root/cd/89cb09b0f27310f9f8864072f8d3b059434807
blob: 569b16f84c03635877518195b314dccfd6477db7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <thomas@thomaszander.se>) id 1XTYBR-0003ZC-G6
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 15:27:17 +0000
X-ACL-Warn: 
Received: from bouvier.getmail.no ([84.210.184.8])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1XTYBP-0000ao-2M for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 15:27:17 +0000
Received: from localhost (localhost [127.0.0.1])
	by bouvier.getmail.no (Postfix) with ESMTP id DAECA406CD
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 17:10:22 +0200 (CEST)
Received: from bouvier.getmail.no ([127.0.0.1])
	by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new,
	port 10032) with ESMTP id MsvnFjGtpwaK
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 17:10:22 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by bouvier.getmail.no (Postfix) with ESMTP id F1EE14035F
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 17:10:21 +0200 (CEST)
X-Virus-Scanned: amavisd-new at bouvier.get.c.bitbit.net
Received: from bouvier.getmail.no ([127.0.0.1])
	by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new,
	port 10026) with ESMTP id TT7A1hBGgSZ3
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 17:10:21 +0200 (CEST)
Received: from coldstorage.localnet (cm-84.208.97.23.getinternet.no
	[84.208.97.23])
	by bouvier.getmail.no (Postfix) with ESMTP id CF97140240
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 17:10:21 +0200 (CEST)
From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Date: Mon, 15 Sep 2014 17:10:21 +0200
Message-ID: <3586037.E6tZxYPG6n@coldstorage>
User-Agent: KMail/4.13.3 (Linux/3.14-2-amd64; KDE/4.14.0; x86_64; ; )
In-Reply-To: <3E354504-0203-4408-85A1-58A071E8546A@gmail.com>
References: <20140913135528.GC6333@muck>
	<CAJHLa0Owjs=6vhy_RSD+VSAZgBq2pSYv5HhCdA4-XCGgX=Z6dA@mail.gmail.com>
	<3E354504-0203-4408-85A1-58A071E8546A@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1XTYBP-0000ao-2M
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 15:27:17 -0000

The reason it is in fact geek wanking is because pgp tried to solve a problem 
that can't be solved.
It tried to provide distributed trust to a system of identity, while still 
depending on the local governments (i.e. centralization) for the upstream ID.

Its a marriage that has no benefits.

What we really want is a (decentralized) identity management that allows me to 
create a new anonymous ID and use that as something more secure when needed 
that I have to proof its me.

So for instance I start including a bitcoin public key in my email signature. 
I don't sign the emails or anything like that, just to establish that everyone 
has my public key many times in their email archives.
Then when I need to proof its me, I can provide a signature on the content 
that the requester wants me to sign.

All the overhead of PGP and the WoT is really completely unneeded and just 
means that less people use it.

Consider this; people create accounts on GitHub or Reddit and those have in 
fact more value than your pgp key!  Because they got the anonymous part right.


On Monday 15. September 2014 09.32.03 Brian Hoffman wrote:
> I would agree that the in person aspect of the WoT is frustrating, but to
> dismiss this as "geek wanking" is the pot calling the kettle.
> 
> The value of in person vetting of identity is undeniable. Just because your
> risk acceptance is difference doesn't make it wanking. Please go see if you
> can get any kind of governmental clearance of credential without in-person
> vetting. Ask them if they accept your behavioral signature.
> 
> I know there is a lot of PGP hating these days but this comment doesn't
> necessarily apply to every situation.
> > On Sep 15, 2014, at 9:08 AM, Jeff Garzik <jgarzik@bitpay.com> 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.