Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VOnNu-0000Z4-S2 for bitcoin-development@lists.sourceforge.net; Wed, 25 Sep 2013 11:35:58 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.54 as permitted sender) client-ip=209.85.215.54; envelope-from=melvincarvalho@gmail.com; helo=mail-la0-f54.google.com; Received: from mail-la0-f54.google.com ([209.85.215.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VOnNr-0004sL-C1 for bitcoin-development@lists.sourceforge.net; Wed, 25 Sep 2013 11:35:58 +0000 Received: by mail-la0-f54.google.com with SMTP id ea20so4800560lab.13 for ; Wed, 25 Sep 2013 04:35:48 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.72.229 with SMTP id g5mr29032606lbv.10.1380108948542; Wed, 25 Sep 2013 04:35:48 -0700 (PDT) Received: by 10.112.159.233 with HTTP; Wed, 25 Sep 2013 04:35:48 -0700 (PDT) In-Reply-To: References: <521298F0.20108@petersson.at> Date: Wed, 25 Sep 2013 13:35:48 +0200 Message-ID: From: Melvin Carvalho To: Mike Hearn Content-Type: multipart/alternative; boundary=001a11c238e8a11d7204e733a7c4 X-Spam-Score: 0.4 (/) 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 (melvincarvalho[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 1.0 FREEMAIL_REPLY From and body contain different freemails X-Headers-End: 1VOnNr-0004sL-C1 Cc: Bitcoin Dev , Andreas Schildbach 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2013 11:35:59 -0000 --001a11c238e8a11d7204e733a7c4 Content-Type: text/plain; charset=ISO-8859-1 On 25 September 2013 13:15, Mike Hearn wrote: > 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. > It depends on the attacker. I think a large entity such as a govt or big to medium size corporation *may* be able to MITM https, of course the incentive to do so is probably not there ... > > > > > 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 >> > >> > 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 >> > > wrote: >> > >> > On Tue, Sep 24, 2013 at 11:52 PM, Mike Hearn > > > 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 >> > > > > ------------------------------------------------------------------------------ > 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 > > --001a11c238e8a11d7204e733a7c4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 25 September 2013 13:15, Mike Hearn <mike@plan99.net> wrote:
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&#= 39;s potential for a MITM attack. If the request URL is HTTPS or a secured = Bluetooth connection then there's no such possibility.

It depends on the attacker.=A0 I think a l= arge entity such as a govt or big to medium size corporation *may* be able = to MITM https, of course the incentive to do so is probably not there ...
=A0




On Wed, Sep 25, 2= 013 at 12:28 PM, Andreas Schildbach <andreas@schildbach.de> wrote:
While it's good to save space, I'm a= t 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=3Dbob.com/r/aZgR <http://bob.com/r/aZgR>
>
> I think that's about as small as possible without re-using the pub= key 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:
>
> =A0 =A0 On Tue, Sep 24, 2013 at 11:52 PM, Mike Hearn <mike@plan99.net
> =A0 =A0 <mailto:mike@plan99.net>> wrote:
>
> =A0 =A0 =A0 =A0 BTW, on the "make qrcodes more scannable" fr= ont -- is it too
> =A0 =A0 =A0 =A0 late to change BIP 72 so the new param is just "r= " instead of
> =A0 =A0 =A0 =A0 "request"? Every byte helps when it comes to= qrcodes ...
>
>
> =A0 =A0 Not too late, assuming there are no objections. Smaller QR cod= es is
> =A0 =A0 a very good reason to change it.
>
> =A0 =A0 --
> =A0 =A0 --
> =A0 =A0 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 mo= st from
> the latest Intel processors and coprocessors. See abstracts and regist= er >
> http://pubads.g.doubleclick.net= /gampad/clk?id=3D60133471&iu=3D/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitco= in-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 fr= om
the latest Intel processors and coprocessors. See abstracts and register &g= t;
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D60133471&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


-----------------------------------------------------------= -------------------
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 fr= om
the latest Intel processors and coprocessors. See abstracts and register &g= t;
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D60133471&iu=3D/4140/ostg.clktrk
___________________= ____________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a11c238e8a11d7204e733a7c4--