Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WeJuJ-00075L-Sq for bitcoin-development@lists.sourceforge.net; Sun, 27 Apr 2014 07:53:51 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.176 as permitted sender) client-ip=209.85.160.176; envelope-from=kgreenek@gmail.com; helo=mail-yk0-f176.google.com; Received: from mail-yk0-f176.google.com ([209.85.160.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WeJuJ-00057v-1n for bitcoin-development@lists.sourceforge.net; Sun, 27 Apr 2014 07:53:51 +0000 Received: by mail-yk0-f176.google.com with SMTP id 19so4716593ykq.21 for ; Sun, 27 Apr 2014 00:53:45 -0700 (PDT) X-Received: by 10.236.125.12 with SMTP id y12mr28030044yhh.42.1398585225553; Sun, 27 Apr 2014 00:53:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.75.213 with HTTP; Sun, 27 Apr 2014 00:53:25 -0700 (PDT) In-Reply-To: <535BF056.6080804@jrn.me.uk> References: <535ABD5D.7070509@jrn.me.uk> <535BF056.6080804@jrn.me.uk> From: Kevin Greene Date: Sun, 27 Apr 2014 00:53:25 -0700 Message-ID: To: Ross Nicoll Content-Type: multipart/alternative; boundary=20cf303a36a18eaa8d04f8017f4c 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 (kgreenek[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: 1WeJuJ-00057v-1n Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Error handling in payment protocol (BIP-0070 and BIP-0072) 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, 27 Apr 2014 07:53:52 -0000 --20cf303a36a18eaa8d04f8017f4c Content-Type: text/plain; charset=UTF-8 Keep in mind that links don't always come embedded in html. Think of native mobile apps. On Sat, Apr 26, 2014 at 10:43 AM, Ross Nicoll wrote: > I'd be very cautious of security implications of embedding files into > the payment request. Even file formats one would presume safe, such as > images, have had security issues (i.e. > https://technet.microsoft.com/library/security/ms11-006 ) > > Longer term I was wondering about embedding the PaymentRequest into web > pages directly via the tag, which could eliminate need for > BIP0072 and potentially improve user interface integration that way. > Obviously this would require browser plugins, however. > > Ross > > On 26/04/14 18:36, Mike Hearn wrote: > >> PaymentRequests are limited to 50,000 bytes. I can't think of a reason > why > >> Payment messages would need to be any bigger than that. Submit a pull > >> request to the existing BIP. > >> > > In future it might be nice to have images and things in the payment > > requests, to make UIs look prettier. But with the current version 50kb > > should be plenty indeed. > > > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --20cf303a36a18eaa8d04f8017f4c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Keep = in mind that links don't always come embedded in html. Think of native = mobile apps.
=


On Sat,= Apr 26, 2014 at 10:43 AM, Ross Nicoll <jrn@jrn.me.uk> wrote:
I'd be very cautious of security implications of embedding files into the payment request. Even file formats one would presume safe, such as
images, have had security issues (i.e.
https://technet.microsoft.com/library/security/ms11-006 )
Longer term I was wondering about embedding the PaymentRequest into web
pages directly via the <object> tag, which could eliminate need for BIP0072 and potentially improve user interface integration that way.
Obviously this would require browser plugins, however.

Ross

On 26/04/14 18:36, Mike Hearn wrote:
>> PaymentRequests are limited to 50,000 bytes. I can't think of = a reason why
>> Payment messages would need to be any bigger than that. Submit a p= ull
>> request to the existing BIP.
>>
> In future it might be nice to have images and things in the payment > requests, to make UIs look prettier. But with the current version 50kb=
> should be plenty indeed.
>


-----------------------= -------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.n= et/sfu/ExoPlatform
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--20cf303a36a18eaa8d04f8017f4c--