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
128
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jouke@bitonic.nl>) id 1WfBOb-0008Fh-DC
for bitcoin-development@lists.sourceforge.net;
Tue, 29 Apr 2014 17:00:41 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitonic.nl
designates 178.22.57.41 as permitted sender)
client-ip=178.22.57.41; envelope-from=jouke@bitonic.nl;
helo=mail.entix.nl;
Received: from mail.entix.nl ([178.22.57.41])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WfBOZ-0003ye-Gj for bitcoin-development@lists.sourceforge.net;
Tue, 29 Apr 2014 17:00:41 +0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.entix.nl (Postfix) with ESMTP id 874141843C5
for <bitcoin-development@lists.sourceforge.net>;
Tue, 29 Apr 2014 18:43:59 +0200 (CEST)
Received: from mail.entix.nl ([178.22.57.41])
by localhost (entix.nl [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id emisxYHwtDhC
for <bitcoin-development@lists.sourceforge.net>;
Tue, 29 Apr 2014 18:43:58 +0200 (CEST)
Received: from [192.168.178.25] (a83-163-138-228.adsl.xs4all.nl
[83.163.138.228])
by mail.entix.nl (Postfix) with ESMTPSA id C9DFA1843BF
for <bitcoin-development@lists.sourceforge.net>;
Tue, 29 Apr 2014 18:43:58 +0200 (CEST)
Message-ID: <535FD6DC.8000002@bitonic.nl>
Date: Tue, 29 Apr 2014 18:44:12 +0200
From: Jouke Hofman <jouke@bitonic.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CABsx9T2v=oX5eR9yoBULPVceZFD2_d+xMF7jQJACHYP=FgWK-A@mail.gmail.com>
In-Reply-To: <CABsx9T2v=oX5eR9yoBULPVceZFD2_d+xMF7jQJACHYP=FgWK-A@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: 1WfBOZ-0003ye-Gj
Subject: Re: [Bitcoin-development] Proposal to change payment protocol
signing
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: Tue, 29 Apr 2014 17:00:41 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We have BIP70 already in use (over a hundred paid requests).
Could you elaborate on why this needs changing?
On 28-04-14 14:39, Gavin Andresen wrote:
> There is a discussion about clarifying how BIP70 signs payment
> requests here: https://github.com/bitcoin/bips/pull/41
>
> The issue is what to do with the signature field before signing.
> The code Mike and I initially wrote does this:
>
> request.set_signature(string(""));
>
> (sets signature to the empty string)
>
> I think that is a mistake; it should be:
>
> request.clear_signature();
>
> (clears signature field, so it is not serialized at all).
>
> So: if you are implementing, or have implemented, the payment
> protocol, please chime in. I'd like to change the spec and the
> reference implementation NOW, while BIP70 is still a 'Draft'.
>
> Because this type of "hey, I'm implementing your standard and it
> doesn't work the way I think it should" mistake is exactly why BIPs
> take a while before being declared 'Final.'
>
>
>
>
> ------------------------------------------------------------------------------
>
>
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing
> platform available. Simple to use. Nothing to install. Get started
> now for free." http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTX9bcAAoJELhWickZBkAlKqcH/RVFAr6vGgDjJvYah46StMHy
ZhKwpV1oqFCslOts6MyO+bZp9uDRlmYtnAy02CTPmlico3IyK85/+CGCGEdyiGo1
AEI2Ixr5FJs9t8uAVLyUKwOQddUFEJuZuiKXd1Wl9GqfG/z8gwdSxd08Wrq57lSH
JdwUnWOG1xBwyhgm7stqFoXgTrrnFNcE97vwsk6QMIzJG/v0suw7Lp42q7bKYaA/
J9xWSQ1cRKSPdsmu4K45oxXriqUmiqz3EouaTSQqC80OO7y8sfa96DqiHR83Vy3w
KUna5enjGqhhberWCokg3x5lCiH/IfLPrgK23iib4cg6Vm70jSQ2S2Xh/NuoDaM=
=JA5K
-----END PGP SIGNATURE-----
|
