[Webkit-unassigned] [Bug 206924] Content blocker: add an option to replace response with static content

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 20 08:19:08 PDT 2021


https://bugs.webkit.org/show_bug.cgi?id=206924

--- Comment #6 from Andrey Meshkov <am at adguard.com> ---
(In reply to Sam Sneddon [:gsnedders] from comment #5)

> Right; realistically if WebKit owns the set of possible replacement files
> then it doesn't matter if they are "empty" or not, but the real desire is to
> keep them static to avoid a malicious content blocker from being able to
> load different replacement resources per-user and therefore add a trivial
> fingerprinting mechanism (e.g., imagine generating different
> window.uniqueUser = 2314321 JS files as replacements).

I completely agree. Also, that's exactly how it works in the ad blockers I mentioned.

Each of them maintains a list of static replacements which then can be used in a declarative manner.

For instance, `||example.org^$replace=noopjs` is a rule that basically says "Replace example.org responses with the specified replacement resource called noopjs".

> I guess there'd be some concern about the set of files becoming massive, but it doesn't look like the current set in that repo is very large.

These "empty" static resources are indeed changed rarely and I doubt there'll be any massive change in the future.

There're also some more complicated replacement resources though (for instance, a stub for Google Analytics). Here's the full list of replacement resources we use at AdGuard: https://github.com/AdguardTeam/Scriptlets/blob/master/dist/redirects.yml

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210520/328381a8/attachment.htm>


More information about the webkit-unassigned mailing list