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

CSP2: Drop 'unsafe-redirect'.

From: Mike West <mkwst@google.com>
Date: Wed, 1 Jul 2015 16:12:09 +0200
Message-ID: <CAKXHy=d9nLDX6Pcm-Di9rXGcwyMJmOJC6pzJkUeAxAQEx2L3xA@mail.gmail.com>
To: "public-webappsec@w3.org" <public-webappsec@w3.org>, Wendy Seltzer <wseltzer@w3.org>
Cc: Brad Hill <hillbrad@gmail.com>, Dan Veditz <dveditz@mozilla.com>
Neither Chrome nor Firefox have implemented the `unsafe-redirect` bits of
CSP2 (see 1.2 of http://www.w3.org/TR/CSP2/#changes-from-level-1).
Experimentation locally on internal sites leads me to believe that it's not
going to be web compatible: I didn't find any Google property that used CSP
which the new behavior wouldn't break in some way.

Moreover, statistics from Chrome show that about 0.7% of page views would
be affected (trending upwards), which is significantly above the bar that
Blink has for breaking changes:

We didn't declare it as "at risk" in the CSP2 CR, though we probably should
have. I think this means that removing the source expression and associated
behavior is likely a "substantive change"[1], which I think means that we
need to revise and republish the CR. Wendy, can you confirm that?

(Note to self: next time, mark the whole spec as "at risk" to make
deletions take less than a month and a half. :) )

[1]: http://www.w3.org/2014/Process-20140801/#substantive-change
[2]: http://www.w3.org/2014/Process-20140801/#revised-cr

Mike West <mkwst@google.com>, @mikewest

Google Germany GmbH, Dienerstrasse 12, 80331 München,
Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der
Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)
Received on Wednesday, 1 July 2015 14:12:57 UTC

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