summaryrefslogtreecommitdiff
path: root/4a/03a4678936e1500a4215047934c3df0fdc7f72
blob: b3765f4035ae713a2a5eb969ed639bc5fcaf226c (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <thomas@thomaszander.se>) id 1XTQwp-0007Rh-OZ
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 07:43:43 +0000
X-ACL-Warn: 
Received: from mail1.bemta5.messagelabs.com ([195.245.231.147])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1XTQwo-0000v7-7N
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 07:43:43 +0000
Received: from [85.158.136.83:4723] by server-11.bemta-5.messagelabs.com id
	C5/95-11011-9D396145; Mon, 15 Sep 2014 07:23:05 +0000
X-Env-Sender: thomas@thomaszander.se
X-Msg-Ref: server-16.tower-36.messagelabs.com!1410765785!8607101!1
X-Originating-IP: [83.145.56.68]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29630 invoked from network); 15 Sep 2014 07:23:05 -0000
Received: from unknown (HELO mail.infront.no) (83.145.56.68)
	by server-16.tower-36.messagelabs.com with AES128-SHA encrypted SMTP;
	15 Sep 2014 07:23:05 -0000
Received: from SE8EX13-MBX04.osl.infront.as (10.234.180.16) by
	SE8TMG.osl.infront.as (10.234.180.35) with Microsoft SMTP Server (TLS)
	id 14.3.158.1; Mon, 15 Sep 2014 09:23:05 +0200
Received: from SE8EX13-CAS.osl.infront.as (10.234.180.10) by
	SE8EX13-MBX04.osl.infront.as (10.234.180.16) with Microsoft SMTP Server
	(TLS) id 15.0.775.38; Mon, 15 Sep 2014 09:23:04 +0200
Received: from debian.localnet (10.234.92.22) by SE8EX13-CAS.osl.infront.as
	(10.234.180.11) with Microsoft SMTP Server (TLS) id 15.0.775.38 via
	Frontend Transport; Mon, 15 Sep 2014 09:23:04 +0200
From: Thomas Zander <thomas@thomaszander.se>
To: <bitcoin-development@lists.sourceforge.net>
Date: Mon, 15 Sep 2014 09:23:02 +0200
User-Agent: KMail/1.13.7 (Linux/3.2.0-4-486; KDE/4.8.4; i686; ; )
References: <20140913135528.GC6333@muck>
	<CAJHLa0MaE3Ki5Hs4Tu4dQNBW-EL-857N2kf-fVxYcXM6OO-84w@mail.gmail.com>
	<20140914062826.GB21586@muck>
In-Reply-To: <20140914062826.GB21586@muck>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-ID: <201409150923.02817.thomas@thomaszander.se>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [195.245.231.147 listed in list.dnswl.org]
	-0.0 SPF_HELO_PASS          SPF: HELO matches SPF record
	0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
	lines
X-Headers-End: 1XTQwo-0000v7-7N
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 07:43:43 -0000

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 :-)

-- 
Thomas Zander