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; 
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)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to
 P2SH multisig
Precedence: list


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