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

Re: webappsec-ISSUE-51: How to handle externally defined <element> with <link rel=import>

From: Adam Barth <w3c@adambarth.com>
Date: Sat, 27 Apr 2013 08:43:05 -0700
Message-ID: <CAJE5ia955Vkmfd5F5ivxL+KW93iJ6frVVNRznag84sTVsNHqqw@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, Web Application Security Working Group <public-webappsec@w3.org>
Done: https://dvcs.w3.org/hg/content-security-policy/rev/5c5a663f67f1

On Sat, Apr 27, 2013 at 8:34 AM, Dimitri Glazkov <dglazkov@google.com> wrote:
> I think that's reasonable. In my mental model, <link rel=import> falls
> roughly into that same bucket as script.
>
> :DG<
>
>
> On Sat, Apr 27, 2013 at 7:07 AM, Adam Barth <w3c@adambarth.com> wrote:
>>
>> On Thu, Apr 25, 2013 at 4:16 PM, Anne van Kesteren <annevk@annevk.nl>
>> wrote:
>> > On Thu, Apr 25, 2013 at 10:49 PM, Web Application Security Working
>> > Group Issue Tracker <sysbot+tracker@w3.org> wrote:
>> >> Create a new directive, e.g. import-src for allowing custom elements to
>> >> be imported from an external source?
>> >
>> > Last I checked this can do the same as script, so you probably want to
>> > restrict via the same mechanism.
>>
>> Yeah, we'll probably need to restrict <link rel=import> with
>> script-src so that it's not an XSS vector for existing web sites that
>> use CSP.
>>
>> Adam
>
>
Received on Saturday, 27 April 2013 15:44:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:01 UTC