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
|
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 <pete@petertodd.org>) id 1XTZ1a-0006Vl-Ls
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Sep 2014 16:21:10 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.95 as permitted sender)
client-ip=62.13.148.95; envelope-from=pete@petertodd.org;
helo=outmail148095.authsmtp.com;
Received: from outmail148095.authsmtp.com ([62.13.148.95])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1XTZ1Y-0002oE-F0 for bitcoin-development@lists.sourceforge.net;
Mon, 15 Sep 2014 16:21:10 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s8FGKoPE022571;
Mon, 15 Sep 2014 17:20:50 +0100 (BST)
Received: from [10.101.31.17] ([185.13.106.86]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s8FGKkFF046699
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Mon, 15 Sep 2014 17:20:47 +0100 (BST)
User-Agent: K-9 Mail for Android
In-Reply-To: <CAAS2fgRXUZxHSPyCo-tNdFE8nSky5ocuaPp7Yo-SbTXinQOpNQ@mail.gmail.com>
References: <20140913135528.GC6333@muck>
<3E354504-0203-4408-85A1-58A071E8546A@gmail.com>
<3586037.E6tZxYPG6n@coldstorage> <3205491.XcafbkJRvW@crushinator>
<CAAS2fgRXUZxHSPyCo-tNdFE8nSky5ocuaPp7Yo-SbTXinQOpNQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
charset=UTF-8
From: Peter Todd <pete@petertodd.org>
Date: Mon, 15 Sep 2014 17:20:44 +0100
To: Gregory Maxwell <gmaxwell@gmail.com>, Matt Whitlock <bip@mattwhitlock.name>
Message-ID: <91006404-f6ac-4d46-b58e-1160d1cfe2ae@email.android.com>
X-Server-Quench: 4096ca36-3cf4-11e4-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwcUC1AEAgsB AmIbWlNeUl17XWs7 agJUcwRefEtOWRti
VldNRFdNFUsrCWp2 fUVoJBl2cQNPcTB3 Z0RqEHRbVUIpJEV7
X00HQ2kbZGY1bH1N U0leagNUcgZDfk5E bwQuUz1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCWoMEyV0 ThYTGjMiVU0MWSh7
Jho3Nl4dGklZO1l6 OF8lEUkZPBkfBkVU Dgl2CTNePFkACDFj NSxiFU0TAWo1
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 185.13.106.86/465
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1XTZ1Y-0002oE-F0
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
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 16:21:10 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 15 September 2014 17:10:14 BST, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>If the server could replace the public key, it could replace the
>signature in all the same places.
>
>Please, can this stuff move to another list? It's offtopic.
+1
My original post was OT really, although obviously this was the right venue to be sure the required audience saw it and settle the question.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCAA6BQJUFxHcMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhfCtCACLNgMrxRQ4YlX4Tkyt
CIlqRh4AOLVRXeh6ER+BJJhJA+hbunNfH6kkROIinpBsFxlRfoHwrv2ax6GIlegO
s1+MSLFAoOob3tLQY/LrVF0PMTbKybdQRqQopzu81hbLTCjpnrnN2sDpAOA/bDsV
xDTHNVbOWS7UapkZf7AjueDfuyW3yhvcgsq1Tuc4r7pdKCEQA/HjBzIqyFT2K9hp
uahaENzCfsCVsEiTmAu+p9EvXhLWmMRfRz15z7D/KtOBTI83/t/WR7UnWlSRHn4i
Xyhj/iDv+kPj/vsGXZClCUZ7T/64ovVvoeY9Pk+1fc6okWWXmTHsH+R72szkhgEu
O4QP
=C27J
-----END PGP SIGNATURE-----
|
