From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Tggsk-0007Qi-M9 for bitcoin-development@lists.sourceforge.net; Thu, 06 Dec 2012 19:13:14 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.169 as permitted sender) client-ip=209.85.212.169; envelope-from=gavinandresen@gmail.com; helo=mail-wi0-f169.google.com; Received: from mail-wi0-f169.google.com ([209.85.212.169]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Tggsi-0003bR-TH for bitcoin-development@lists.sourceforge.net; Thu, 06 Dec 2012 19:13:14 +0000 Received: by mail-wi0-f169.google.com with SMTP id hq12so757289wib.4 for ; Thu, 06 Dec 2012 11:13:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.103.106 with SMTP id fv10mr4206704wib.19.1354821186812; Thu, 06 Dec 2012 11:13:06 -0800 (PST) Received: by 10.194.27.136 with HTTP; Thu, 6 Dec 2012 11:13:06 -0800 (PST) In-Reply-To: References: <20121128233619.GA6368@giles.gnomon.org.uk> <20121129170713.GD6368@giles.gnomon.org.uk> <20121129185330.GE6368@giles.gnomon.org.uk> <50C03BDA.6010600@petersson.at> Date: Thu, 6 Dec 2012 14:13:06 -0500 Message-ID: From: Gavin Andresen To: Mike Hearn Content-Type: multipart/alternative; boundary=f46d0443049c92f98204d033e3ec X-Spam-Score: -0.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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1Tggsi-0003bR-TH Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts 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: Thu, 06 Dec 2012 19:13:14 -0000 --f46d0443049c92f98204d033e3ec Content-Type: text/plain; charset=ISO-8859-1 On Thu, Dec 6, 2012 at 12:55 PM, Mike Hearn wrote: > Re: the newest spec. Rather than make the signature over the > "concatenation of", why not just make it a signature over the > serialized protobuf minus the signature field (as I did in my demo > code). Otherwise it seems like we'd need more code than really > necessary. We can state explicitly tags must be ordered if you want, > even though all implementations should do that already. OK. I want to keep the signature field required, though, so how about: signature: digital signature over a protocol buffer serialized variation of the SignedPaymentRequest message where signature is a zero-byte array and fields are serialized in numerical order (all current protocol buffer implementations serialize fields in numerical order), using the public key in pki_data. -- -- Gavin Andresen --f46d0443049c92f98204d033e3ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Dec 6, 2012 at 12:55 PM, Mike Hearn <mike@plan99.net> wrote:
Re: the newest spec. Rather than make the signature over the
"concatenation of", why not just make it a signature over the
serialized protobuf minus the signature field (as I did in my demo
code). Otherwise it seems like we'd need more code than really
necessary. We can state explicitly tags must be ordered if you want,
even though all implementations should do that already.
OK. I want to keep the signature field required, though, so ho= w about:

signature: digital signature over a proto= col buffer serialized variation of the SignedPaymentRequest message where s= ignature is a zero-byte array and fields are serialized in numerical order = (all current protocol buffer implementations serialize fields in numerical = order), using the public key in pki_data.

--
--
Gavin Andresen

--f46d0443049c92f98204d033e3ec--