Re:Deconstructing Google’s excuses on tracking protection
by vengefulduck on Friday August 23, 2019 @10:10PM
(#20784741)
Except the extension could just inject a script into the webpage and exfiltrate data that way.
Re:Deconstructing Google’s excuses on tracking protection
by rndgermandude on Saturday August 24, 2019 @12:49AM
(#20785293)
That requires some different permissions to the webRequest permission in question.
But yeah, a bad actor would probably just switch away from webRequest to <all_urls> + webNavigation permissions and siphon off data with content scripts. So google's argument that is is a privacy issue and thus they just HAVE TO cripple their webRequest APIs doesn't get any better.
Re:Deconstructing Google’s excuses on tracking protection
by shawnz on Saturday August 24, 2019 @08:01AM
(#20786643)
That is still possible with Chrome's new declarative model too, so the parent's idea is strictly an improvement.
Re:Deconstructing Google’s excuses on tracking protection
by sfink on Tuesday August 27, 2019 @04:46PM
(#20814256)
Blocking is itself a communications channel. You have some data to exfiltrate from extension to server. The page embeds a bunch of URLs to your ad server, you selectively block based on the data to exfiltrate, the server gets 1 bit per URL.
Any additional blocking capabilities (reordering, delaying, selective header stripping) increase the number of bits.
It took me less than 2mins of thinking (and I am hardly the smartest guy ever) about it to figure out that you can solve the potential privacy hazard that webRequest poses (extensions siphoning off request data) by introducing a special kind of content script, let's call it a request-script, that is input-only/one-way-communication except for a limited set of request manipulation and only when asked by the browser. Such as blocking requests. Of course, the devil is in the details here of what to allow and not allow.
The input-only nature still allows for it to be feed new/updates instructions, and it being a script it can still implement rules that cannot be implemented with a fixed rule list like google proposes. But it cannot make web requests and exfiltrate data like that, it cannot communicate back to the host extension and exfiltrate that like that, it cannot exfiltrate data, period. It only ever is allowed to perform certain (not all) request modifications and only when asked by the browser itself.
That leaves the "performance issues" google claims are a major problem. And indeed, there is a chance a misbehaving extension might obliterate performance. But you can do a lot of things in this space, too. "You" are the browser after all and any extension or any request script is at the mercy of what you're allowing it to do anyway. A low hanging fruit here would be to enforce that a request-script has to give an answer in a sane amount of time. Or warn users when an extension slows down requests too much.
And ultimately users will decide if a e.g. 100ms delay for each request is preferable over downloading a few megabytes of video ads for them or not. That is if google was really interested in protecting their users and improving their experience and did not have other motives...