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

Re: Trimming the SecurityPolicy DOM interface

From: Alex Russell <slightlyoff@google.com>
Date: Sat, 27 Apr 2013 19:31:17 +0100
Message-ID: <CANr5HFXHFY8e2pPhbLNz7i-t+abHyOf6YKu6G7pawa5fT--_UQ@mail.gmail.com>
To: Adam Barth <w3c@adambarth.com>
Cc: public-webappsec@w3.org, Mike West <mkwst@google.com>, "www-tag@w3.org List" <www-tag@w3.org>
I object to these changes in the strongest possible terms. If it is not
possible to implement CSP policy enforcement on top of your API, it is not
sufficient.
On Apr 27, 2013 5:46 PM, "Adam Barth" <w3c@adambarth.com> wrote:

> As discussed at the face-to-face meeting, I've trimmed the
> SecurityPolicy DOM interface to just the first four attributes:
>
> https://dvcs.w3.org/hg/content-security-policy/rev/f338192860c5
>
> At the meeting, we discussed that these attribute have strong use
> cases, but we couldn't think of any strong use cases for the remaining
> DOM interfaces.
>
> If folks come up with strong use cases, we should consider adding back
> the removed interfaces (or adding new interfaces that better address
> those use cases).
>
> Note: At the face-to-face, we discussed making some of these attribute
> writable in some circumstances, but I haven't made that change yet
> because it probably deserves more discussion.
>
> Adam
>
>
Received on Saturday, 27 April 2013 18:31:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 13:26:32 UTC