W3C home > Mailing lists > Public > public-webappsec@w3.org > April 2015

Re: HTML Imports and CSP

From: Jeffrey Yasskin <jyasskin@google.com>
Date: Tue, 7 Apr 2015 10:04:34 -0700
Message-ID: <CANh-dXkYg8bfMmXz+gvPM8ei4eREtC4rr4tkA8Zqwoy5c412Gw@mail.gmail.com>
To: Mike West <mkwst@google.com>
Cc: Dimitri Glazkov <dglazkov@google.com>, Devdatta Akhawe <dev.akhawe@gmail.com>, Brad Hill <hillbrad@gmail.com>, Joel Weinberger <jww@google.com>, Justin Schuh <jschuh@google.com>, Nathan Sobo <nathan@github.com>, Justin Fagnani <justinfagnani@google.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On Tue, Apr 7, 2015 at 9:53 AM, Mike West <mkwst@google.com> wrote:
> On Tue, Apr 7, 2015 at 5:43 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
>>> On Tue, Apr 7, 2015 at 1:39 PM, Mike West <mkwst@google.com> wrote:
>>>> After thinking about this a bit more over the holidays, I think I'm more
>>>> in agreement with you than I thought, Dev. :)
>>>> What do you think about this:
>>>> 1. Move imports to `import-src` (we'll need to measure usage in Chrome,
>>>> but assuming this is mostly an extension thing at this point, it should be
>>>> doable).
>>>> 2. Give imports their own policy (that is, no longer inherit from the
>>>> containing document) like Workers and frames, which would enable them to
>>>> either whitelist `unsafe-inline` themselves, or use nonces/hashes whatever.
>> This seems encouraging. What is the bottom line for developers using CSP?
>> What is the least that they need to do in order to make HTML Imports usable?
> The very least? Nothing at all. No CSP, no problem, right?
> The least they should do to maintain the security invariants they had before
> is add an `imports-src` directive to their policy that allows Imports from a
> set of sources. We'd almost certainly want to change Chrome extension/app's
> default CSP to include such a directive.
> Maybe `import-src` would even default to `script-src`, in the same way (the
> deprecated) `frame-src` defaults to `child-src` (which defaults to
> `default-src`)? We've avoided these chains in the past, but it might make
> sense here, as Imports can and do execute script, and the vast majority of
> sites wouldn't know that they should think about restricting them.

Further, they should put a CSP on the HTML Imports themselves, right?
Otherwise the Import can pull scripts from bad places and be XSS'ed
itself. If the HTML Import contains inline script blocks, they'll also
need to enable those, probably with hashes since unsafe-inline enables
too much. Has anyone written a build step for grunt/gulp/etc that
generates hashes for a static file? What needs to be done to serve
those hashes from most CDNs?

Received on Tuesday, 7 April 2015 17:05:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:48 UTC