W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2014

Re: SRI and CORS

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 3 Jul 2014 15:58:03 +0200
Message-ID: <CADnb78gszHE11K+w3=DztRDYmqB2emSaAS=S-+h4XDE7dKP9FQ@mail.gmail.com>
To: Frederik Braun <fbraun@mozilla.com>
Cc: WebAppSec WG <public-webappsec@w3.org>
On Thu, Jul 3, 2014 at 3:52 PM, Frederik Braun <fbraun@mozilla.com> wrote:
> I can't think of an alternative solution. So, this means we can only
> safely have SRI for resources that are CORS-enabled or same-origin?

Yeah. It depends a bit on how we want the processing to work. E.g. either

  <img src=x integrity=hash(x)>

ignores integrity, fails if x returns a tainted response, or fails
because no crossorigin attribute was set in addition to integrity.


-- 
http://annevankesteren.nl/
Received on Thursday, 3 July 2014 13:58:30 UTC

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