Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of mmocny@google.com designates
 209.85.220.173 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CABiQX1U=srqaf65atCq+DcE7MTFD+xkK7PDjH06ZcTcCALMu=g@mail.gmail.com>
References: 
 <CABiQX1WEhoOyXngbHmyhqLHK_yfbMv3RKH=g8ms-KLy8ZKs6QA@mail.gmail.com>
 <CAEeF2TdXe8=UCsomQyBMBOpnQ+RbXpi=0WGk79Zn8T+1oi4aOg@mail.gmail.com>
 <CABiQX1U=srqaf65atCq+DcE7MTFD+xkK7PDjH06ZcTcCALMu=g@mail.gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Tue, 3 Mar 2015 13:06:13 -0500
Message-ID: 
 <CAEeF2TfitRUCja2XErjPyzGT7CeQEjVLm=TE=5QnZK9G=N=fLA@mail.gmail.com>
Subject: Re: Android's new Whitelist Plugins
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=089e01633feaeb48870510663107

--089e01633feaeb48870510663107
Content-Type: text/plain; charset=UTF-8

Ah, the bit about <access> being mostly useful for pre-kitkat was context I
was missing.  Seems important to note at the start of the section.  I'll
update the README.

On Tue, Mar 3, 2015 at 1:02 PM, Andrew Grieve <agrieve@chromium.org> wrote:

> Like your ideas a lot. Updating the project template makes a lot of sense.
>
> Tried to make it clear in the README, so if any part was not clear please
> fix it. But, the CSP tag is the more important bit, since <access> can't
> actually block all requests. The only reason to even leave <access> in
> there is to support pre-kitkat webviews, where no CSP support exists. CSP
> is also used to set a navigation whitelist for subframes, which the native
> side is not able to do.
>
> On Tue, Mar 3, 2015 at 11:22 AM, Michal Mocny <mmocny@chromium.org> wrote:
>
> > My thoughts:
> >
> > - The split between <allow-navigation>, <allow-intent>, and <access>:
> Like
> > it a lot.
> > - I think the defaults *for the plugin* are very reasonable.  However, we
> > may want to provide a default set of tags for the hello world app.  A
> year
> > or so ago we added a default access * whitelist and I think maybe we
> should
> > continue that.  (on the other hand, I've gotten used to explicitly
> > whitelisting every url as part of chrome packaged app development and its
> > not so bad).
> >   - Additionally, that means this plugin should be installed by default.
> > As we discussed this morning, with the new plugin --save functionality we
> > could just add this to the helloworld config.xml, I think!
> > - Do you really need a CSP meta tag *and* <access> declarations?   Thats
> > what the README.md implies, but I would assume CSP trumps?
> >
> > -Michal
> >
> > On Mon, Mar 2, 2015 at 9:38 PM, Andrew Grieve <agrieve@chromium.org>
> > wrote:
> >
> > > I've tried to explain it in the plugin's readme:
> > >
> > > https://github.com/apache/cordova-plugins/tree/master/url-policy
> > >
> > > Some points for discussion:
> > > - What should the default behaviour be for the three whitelists (what
> > > should happen if not whitelist plugin is installed).
> > >   - right now it can't open external URLs
> > >   - and can't do XHRs to http(s)
> > > - Is the plugin name decent ("url-policy"). We should make a dedicated
> > git
> > > repo for it (as well as for legacy-whitelist plugin)
> > >
> >
>

--089e01633feaeb48870510663107--