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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VOn43-0008EH-QE
for bitcoin-development@lists.sourceforge.net;
Wed, 25 Sep 2013 11:15:27 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.50 as permitted sender)
client-ip=209.85.214.50; envelope-from=mh.in.england@gmail.com;
helo=mail-bk0-f50.google.com;
Received: from mail-bk0-f50.google.com ([209.85.214.50])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VOn40-0001gk-7o
for bitcoin-development@lists.sourceforge.net;
Wed, 25 Sep 2013 11:15:27 +0000
Received: by mail-bk0-f50.google.com with SMTP id mz11so2294383bkb.9
for <bitcoin-development@lists.sourceforge.net>;
Wed, 25 Sep 2013 04:15:17 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.204.60.66 with SMTP id o2mr27545815bkh.22.1380107717736;
Wed, 25 Sep 2013 04:15:17 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.204.237.74 with HTTP; Wed, 25 Sep 2013 04:15:17 -0700 (PDT)
In-Reply-To: <l1udst$uos$1@ger.gmane.org>
References: <CABsx9T0Ly67ZNJhoRQk0L9Q0-ucq3e=24b5Tg6GRKspRKKtP-g@mail.gmail.com>
<521298F0.20108@petersson.at>
<CABsx9T3b--tfUmaxJxsXyM2f3Cw4M1oX1nX8o9WkW_haBmLctA@mail.gmail.com>
<CANEZrP2BOWk4FOUx4eVHvXmdSgx3zo_o18J8YBi2Uc_WkBAXKA@mail.gmail.com>
<CANEZrP0H9TVfQ3AGv6aBmS1DUa6MTWhSFAN1Jo4eimBEBQhPZw@mail.gmail.com>
<CABsx9T0TQ6Gg=muNP-rCZxan8_nAqeJt6ErYVOfnLJKrsLs81w@mail.gmail.com>
<CANEZrP2V72+-m-FOCsW3C2GBO7+=-0casKadeHncmNTYjyqJRA@mail.gmail.com>
<l1udst$uos$1@ger.gmane.org>
Date: Wed, 25 Sep 2013 13:15:17 +0200
X-Google-Sender-Auth: jq9i03pt1FLeQ5Ad36gQvsIBs_I
Message-ID: <CANEZrP03KsGHvGqcNT1Qs6qkJ4i050CPjwvGqTRRhbdkgMf_dA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=001a11c376fc44acbd04e7335e4e
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1VOn40-0001gk-7o
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72
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: Wed, 25 Sep 2013 11:15:28 -0000
--001a11c376fc44acbd04e7335e4e
Content-Type: text/plain; charset=UTF-8
It won't fit. But I don't see the logic. A URI contains instructions for
making a payment. If that instruction is "pay to this address" or "download
this file and do what you find there", it's no different unless there's
potential for a MITM attack. If the request URL is HTTPS or a secured
Bluetooth connection then there's no such possibility.
On Wed, Sep 25, 2013 at 12:28 PM, Andreas Schildbach
<andreas@schildbach.de>wrote:
> While it's good to save space, I'm at the moment not convinced that
> taking a de-route via an URL is a good idea to begin with.
>
> The main problem is trust. If you scan a QR code from a foreign phone,
> you trust that that phone is owned by the one you want to send money to.
> By adding the HTTP request that trust is voided.
>
> As soon as there is a BIP70 implementation, I will begin playing with
> putting the payment request directly into the QR code.
>
>
> On 09/25/2013 11:27 AM, Mike Hearn wrote:
> > We could also say that if protocol part (https://) is missing, it's
> > implied automatically. So just:
> >
> > bitcoin:1abc........?r=bob.com/r/aZgR <http://bob.com/r/aZgR>
> >
> > I think that's about as small as possible without re-using the pubkey as
> > a token in the url.
> >
> >
> > On Wed, Sep 25, 2013 at 1:35 AM, Gavin Andresen <gavinandresen@gmail.com
> > <mailto:gavinandresen@gmail.com>> wrote:
> >
> > On Tue, Sep 24, 2013 at 11:52 PM, Mike Hearn <mike@plan99.net
> > <mailto:mike@plan99.net>> wrote:
> >
> > BTW, on the "make qrcodes more scannable" front -- is it too
> > late to change BIP 72 so the new param is just "r" instead of
> > "request"? Every byte helps when it comes to qrcodes ...
> >
> >
> > Not too late, assuming there are no objections. Smaller QR codes is
> > a very good reason to change it.
> >
> > --
> > --
> > Gavin Andresen
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > October Webinars: Code for Performance
> > Free Intel webinars can help you accelerate application performance.
> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> > the latest Intel processors and coprocessors. See abstracts and register
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> >
> >
> >
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c376fc44acbd04e7335e4e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">It won't fit. But I don't see the logic. A URI con=
tains instructions for making a payment. If that instruction is "pay t=
o this address" or "download this file and do what you find there=
", it's no different unless there's potential for a MITM attac=
k. If the request URL is HTTPS or a secured Bluetooth connection then there=
's no such possibility.<div>
<br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">On Wed, Sep 25, 2013 at 12:28 PM, Andreas Schildbach <spa=
n dir=3D"ltr"><<a href=3D"mailto:andreas@schildbach.de" target=3D"_blank=
">andreas@schildbach.de</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">While it's good to save space, I'm a=
t the moment not convinced that<br>
taking a de-route via an URL is a good idea to begin with.<br>
<br>
The main problem is trust. If you scan a QR code from a foreign phone,<br>
you trust that that phone is owned by the one you want to send money to.<br=
>
By adding the HTTP request that trust is voided.<br>
<br>
As soon as there is a BIP70 implementation, I will begin playing with<br>
putting the payment request directly into the QR code.<br>
<div class=3D"im"><br>
<br>
On 09/25/2013 11:27 AM, Mike Hearn wrote:<br>
> We could also say that if protocol part (https://) is missing, it'=
s<br>
> implied automatically. So just:<br>
><br>
</div>> bitcoin:1abc........?r=3D<a href=3D"http://bob.com/r/aZgR" targe=
t=3D"_blank">bob.com/r/aZgR</a> <<a href=3D"http://bob.com/r/aZgR" targe=
t=3D"_blank">http://bob.com/r/aZgR</a>><br>
<div class=3D"im">><br>
> I think that's about as small as possible without re-using the pub=
key as<br>
> a token in the url.<br>
><br>
><br>
> On Wed, Sep 25, 2013 at 1:35 AM, Gavin Andresen <<a href=3D"mailto:=
gavinandresen@gmail.com">gavinandresen@gmail.com</a><br>
</div><div class=3D"im">> <mailto:<a href=3D"mailto:gavinandresen@gma=
il.com">gavinandresen@gmail.com</a>>> wrote:<br>
><br>
> =C2=A0 =C2=A0 On Tue, Sep 24, 2013 at 11:52 PM, Mike Hearn <<a href=
=3D"mailto:mike@plan99.net">mike@plan99.net</a><br>
</div><div class=3D"im">> =C2=A0 =C2=A0 <mailto:<a href=3D"mailto:mik=
e@plan99.net">mike@plan99.net</a>>> wrote:<br>
><br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 BTW, on the "make qrcodes more scanna=
ble" front -- is it too<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 late to change BIP 72 so the new param is =
just "r" instead of<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 "request"? Every byte helps when=
it comes to qrcodes ...<br>
><br>
><br>
> =C2=A0 =C2=A0 Not too late, assuming there are no objections. Smaller =
QR codes is<br>
> =C2=A0 =C2=A0 a very good reason to change it.<br>
><br>
> =C2=A0 =C2=A0 --<br>
> =C2=A0 =C2=A0 --<br>
> =C2=A0 =C2=A0 Gavin Andresen<br>
><br>
><br>
><br>
><br>
</div>> ----------------------------------------------------------------=
--------------<br>
> October Webinars: Code for Performance<br>
> Free Intel webinars can help you accelerate application performance.<b=
r>
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the mo=
st from<br>
> the latest Intel processors and coprocessors. See abstracts and regist=
er ><br>
> <a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60133471&am=
p;iu=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net=
/gampad/clk?id=3D60133471&iu=3D/4140/ostg.clktrk</a><br>
<div class=3D"im">><br>
><br>
><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
><br>
<br>
<br>
<br>
</div>---------------------------------------------------------------------=
---------<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr=
om<br>
the latest Intel processors and coprocessors. See abstracts and register &g=
t;<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60133471&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60133471&iu=3D/4140/ostg.clktrk</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--001a11c376fc44acbd04e7335e4e--
|
