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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1URGNr-0001DQ-6y
for bitcoin-development@lists.sourceforge.net;
Sun, 14 Apr 2013 06:25:51 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.58 as permitted sender)
client-ip=62.13.149.58; envelope-from=pete@petertodd.org;
helo=outmail149058.authsmtp.co.uk;
Received: from outmail149058.authsmtp.co.uk ([62.13.149.58])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1URGNp-0002lN-GT for bitcoin-development@lists.sourceforge.net;
Sun, 14 Apr 2013 06:25:51 +0000
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
by punt14.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r3E6PgEA005756;
Sun, 14 Apr 2013 06:25:42 GMT
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r3E6PZgi085206
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Sun, 14 Apr 2013 07:25:38 +0100 (BST)
Date: Sun, 14 Apr 2013 02:25:35 -0400
From: Peter Todd <pete@petertodd.org>
To: Alan Reiner <etotheipi@gmail.com>
Message-ID: <20130414062535.GA3310@savin>
References: <20130414050958.GA11142@savin>
<516A3CD1.20704@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn"
Content-Disposition: inline
In-Reply-To: <516A3CD1.20704@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 1fb77d67-a4cc-11e2-b10b-0025903375e2
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdwYUGUUGAgsB AmUbW1NeUlh7Wms7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqAmkH ZnRJCxl6cgdGfjB3 bE9nEHENDkN9IUB6
Xx9QRj4bZGY1an1N UUAKagNUcgZDfhxG bVUqVj1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCXwlNWx0 SgAeEDMjVVYESCM2
Igc9I1ERW1gcKEQ8 IF4sQkkRPBJaFgo8 V3kXOw8RIkQFWysw DAwy
X-Authentic-SMTP: 61633532353630.1019:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
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: 1URGNp-0002lN-GT
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to
P2SH multisig
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: Sun, 14 Apr 2013 06:25:51 -0000
--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Apr 14, 2013 at 01:21:21AM -0400, Alan Reiner wrote:
> If we're going to extend/expand message signing, can we please add a
> proper ASCII-armored format for it? Really, anything that encodes the
> signed message next to the signature, so that there's no ambiguities
> about what was signed. You can keep the "bare signatures" as an option
> for backwards compatiblity, but offer this as the primary one.
>=20
> What we really want is to have the user copy an ASCII-armored block of
> text into the client (or we could have a URI-extension for this), and
> the app pops up with a window that says "The following message has a
> valid signature from address 1XKjf32kJbf...: <message>". =20
I already looked into ASCII-armoring PGP style for a different project.
(timestamping) Basically you'd want to follow RFC2440, section 7
"Cleartext signature framework":
-----BEGIN BTC SIGNED MESSAGE-----
Hello world!
-----BEGIN BTC SIGNATURE-----
IKBeCbxXHvD1TJh8ZlMySo26w5z6YZQD1xqKgbhsvlhEgcFD+kvKx4LzUz1yxg/8
IdYdBnzez77VDq3odHrVftg=3D
-----END BTC SIGNATURE-----
Pretty simple really and doesn't need to be done prior to other
signmessage changes. There may be an issue passing \r's through the RPC
interface; the RFC specifies CRLF line endings.
--=20
'peter'[:-1]@petertodd.org
--x+6KMIRAuhnl3hBn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJRakveAAoJEH+rEUJn5PoEzUwH/0stgYrluWvqDAfLLKsWKZqF
LJ6Gh4YWeLt2PcQgpg0pNEmddOl1o5L8GMe7wTtZBQbs1QH5arPMV4gXB2iBvj/0
NR2m4lRoSDMJ/f5YH23wOiVSKX5CZybYfJRfQ9/LtfPcrPkA/dZDNhLV5uXtjTbK
unHAxaQD9dIWas//1qnhweiBj2esE+1o7r2IgSgzNqLOfE1ySByd+M32+ORWi0s2
AcVWbVlzE6Yq733hSa7WkqDWUkMsBGOCh08n+CxNiqchbgaZkWhMY0LffYCxcrMC
BdoSw7UUIJGuTnZMJfFDd1m+SC6fWS8uW9PLRKenWqK/c/3xgTAITBmZNhH/VMM=
=ZOoR
-----END PGP SIGNATURE-----
--x+6KMIRAuhnl3hBn--
|
