From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1URRcT-0005X6-Bo for bitcoin-development@lists.sourceforge.net; Sun, 14 Apr 2013 18:25:41 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.53 as permitted sender) client-ip=209.85.216.53; envelope-from=etotheipi@gmail.com; helo=mail-qa0-f53.google.com; Received: from mail-qa0-f53.google.com ([209.85.216.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1URRcS-000211-6J for bitcoin-development@lists.sourceforge.net; Sun, 14 Apr 2013 18:25:41 +0000 Received: by mail-qa0-f53.google.com with SMTP id p6so197764qad.19 for ; Sun, 14 Apr 2013 11:25:34 -0700 (PDT) X-Received: by 10.229.125.205 with SMTP id z13mr3798116qcr.110.1365963934559; Sun, 14 Apr 2013 11:25:34 -0700 (PDT) Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net. [76.111.96.126]) by mx.google.com with ESMTPS id ed8sm26789396qeb.7.2013.04.14.11.25.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 14 Apr 2013 11:25:33 -0700 (PDT) Message-ID: <516AF462.1020400@gmail.com> Date: Sun, 14 Apr 2013 14:24:34 -0400 From: Alan Reiner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Peter Todd References: <20130414050958.GA11142@savin> <516A3CD1.20704@gmail.com> <20130414062535.GA3310@savin> In-Reply-To: <20130414062535.GA3310@savin> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (etotheipi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1URRcS-000211-6J 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 18:25:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/14/2013 02:25 AM, Peter Todd wrote: > 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. >> >> 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...: ". > > 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= > -----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. > Perfect. That was the spec I was looking for but too lazy to find it. I guess I'll lead by example and just do it in Armory. I'll let users pressure the other devs to follow :) - -Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFq9GIACgkQYdHIW5RKKv1A2gCeMfdttPylmPqPqemo0Q2uACEt eAcAn21a7sYy+TNIinRR3SlVgm4VbJPh =qGlo -----END PGP SIGNATURE-----