Reason for revert:
After further discussion, decided against taking this in 53
Original issue's description:
> Re-enable rate limiting for Windows Crashpad
>
> Chrome can get itself into crash loops that cause massive numbers of
> uploads. We'd like to have UMA to see what we're dropping, but for
> the time being, mitigate by re-instituting the Mac-style 1/hr upload
> limit.
>
> BUG=crashpad:23, 647464
>
> Review-Url: https://codereview.chromium.org/2332103002
> Cr-Commit-Position: refs/heads/master@{#418063}
> (cherry picked from commit d922b3cacfcee6958d71de501a8ced7c25801965)
>
> Committed: https://chromium.googlesource.com/chromium/src/+/c1490fd145eda148dd788e554426aa7cb7fde5b2
TBR=
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=crashpad:23, 647464
dbf71ae...
by
Alex Moshchuk <email address hidden>
Block top-level navigations to nested URLs with extension origins from non-extension processes.
Before this CL, it was possible for a web iframe with an unblessed
extension frame to exploit the renderer, create a blob: or filesystem:
URL in the extension frame context, then create a new top-level window
and navigate it to that URL, which could end up putting the new window
into a privileged extension process running attacker's code.
Chrome can get itself into crash loops that cause massive numbers of
uploads. We'd like to have UMA to see what we're dropping, but for
the time being, mitigate by re-instituting the Mac-style 1/hr upload
limit.
BUG=crashpad:23, 647464
Review-Url: https://codereview.chromium.org/2332103002
Cr-Commit-Position: refs/heads/master@{#418063}
(cherry picked from commit d922b3cacfcee6958d71de501a8ced7c25801965)
