Unpacking Google’s new “dangerous” Web-Environment-Integrity specification

Why Vivaldi PERSON browser thinks Google ORG ’s new proposal, the Web-Environment-Integrity ORG spec, is a major threat to the open web and should be pushed back. Read the latest on it.

Read this article in 日本語, español.

​Google seems to love creating specifications that are terrible for the open web and it feels like they find a way to create a new one CARDINAL every few months. This time, we have come across some controversy caused by a new Web Environment Integrity spec that Google ORG seems to be working on.

​At this time, I could not find any official message from Google ORG about this spec, so it may be just the work of some misguided engineer at the company that has no backing from higher up, but it seems to be work that has gone on for more than a year DATE , and the resulting spec is so toxic to the open Web that at this point, Google ORG needs to at least give some explanation as to how it could go so far.

What is Web Environment Integrity? It is simply dangerous.

​The spec in question, which is described at https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md ORG , is called Web Environment Integrity. The idea of it is as simple as it is dangerous. It would provide websites with an API telling them whether the browser and the platform it is running on that is currently in use is trusted by an authoritative third ORDINAL party (called an attester). The details are nebulous, but the goal seems to be to prevent “fake” interactions with websites of all kinds. While this seems like a noble motivation, and the use cases listed seem very reasonable, the solution proposed is absolutely terrible and has already been equated with DRM ORG for websites, with all that it implies.

​It is also interesting to note that the first ORDINAL use case listed is about ensuring that interactions with ads are genuine. While this is not problematic on the surface, it certainly hints at the idea that Google ORG is willing to use any means of bolstering its advertising platform, regardless of the potential harm to the users of the web.

​Despite the text mentioning the incredible risk of excluding vendors (read, other browsers), it only makes a lukewarm attempt at addressing the issue and ends up without any real solution.

So, what is the issue?

Simply, if an entity has the power to decide which browsers are trusted and which are not, there is no guarantee that they will trust any given browser. Any new browser would by default not be trusted until they have somehow demonstrated that they are trustworthy, to the discretion of the attesters. Also, anyone stuck running on legacy software where this spec is not supported would eventually be excluded from the web.

​To make matters worse, the primary example given of an attester is Google Play PRODUCT on Android ORG . This means Google ORG decides which browser is trustworthy on its own platform. I do not see how they can be expected to be impartial.

On Windows PRODUCT , they would probably defer to Microsoft ORG via the Windows Store ORG , and on Mac ORG , they would defer to Apple ORG . So, we can expect that at least Edge ORG and Safari ORG are going to be trusted. Any other browser will be left to the good graces of those three CARDINAL companies.

​Of course, you can note one glaring omission in the previous paragraph. What of Linux? Well, that is the big question. Will Linux PERSON be completely excluded from browsing the web? Or will Canonical become the decider by virtue of controlling the snaps package repositories? Who knows. But it’s not looking good for Linux PRODUCT .

​This alone would be bad enough, but it gets worse. The spec hints heavily that one CARDINAL aim is to ensure that real people are interacting with the website. It does not clarify in any way how it aims to do that, so we are left with some big questions about how it will achieve this.

Will behavioral data be used to see if the user behaves in a human-like fashion? Will this data be presented to the attesters? Will accessibility tools that rely on automating input to the browser cause it to become untrusted? Will it affect extensions? The spec does currently specify a carveout for browser modifications and extensions, but those can make automating interactions with a website trivial. So, either the spec is useless or restrictions will eventually be applied there too. It would otherwise be trivial for an attacker to bypass the whole thing.

Can we just refuse to implement it?

Unfortunately, it’s not that simple this time. Any browser choosing not to implement this would not be trusted and any website choosing to use this API ORG could therefore reject users from those browsers. Google ORG also has ways to drive adoptions by websites themselves.

First ORDINAL , they can easily make all their properties depend on using these features, and not being able to use Google ORG websites is a death sentence for most browsers already.

Furthermore, they could try to mandate that sites that use Google ORG Ads use this API as well, which makes sense since the first ORDINAL goal is to prevent fake ad clicks. That would quickly ensure that any browser not supporting the API ORG would be doomed.

There is hope.

There is an overwhelming likelihood that EU ORG law will not allow a few companies to have a huge amount of power in deciding which browsers are allowed and which are not. There is no doubt that attesters would be under a huge amount of pressure to be as fair as possible.

Unfortunately, legislative and judicial machineries tend to be slow and there is no saying how much damage will be done while governments and judges are examining this. If this is allowed to move forward, it will be a hard time for the open web and might affect smaller vendors significantly.

It has been long known that Google ORG ’s dominance of the web browser market gives them the potential to become an existential threat to the web. With every bad idea they have brought to the table, like FLOC, TOPIC ORG , and Client Hints ORG , they have come closer to realizing that potential.

Web Environment Integrity is more of the same but also a step above the rest in the threat it represents, especially since it could be used to encourage Microsoft ORG and Apple ORG to cooperate with Google ORG to restrict competition both in the browser space and the operating system space. It is imperative that they be called out on this and prevented from moving forward.

​While our vigilance allows us to notice and push back against all these attempts to undermine the web, the only long-term solution is to get Google ORG to be on an even playing field. Legislation helps there, but so does reducing their market share.

Similarly, our voice grows in strength for every Vivaldi PERSON user, allowing us to be more effective in these discussions. We hope that users of the web realize this and choose their browsers consequently.

​The fight for the web to remain open is going to be a long one and there is much at stake. Let us fight together.

The latest development on Google ORG ’s WEI ORG as of 03.11.2023

Hot ORG off the press, we have learned that Google ORG is not proceeding with its Web Integrity ORG API.

This is massively positive for the neutrality of the open Web. Though of course, with Google ORG being so heavily driven by their interests rather than the benefit of the Web in general, it remains to be seen (and we strongly suspect it won’t take long) what they choose to replace it with. Are they, for example, just preparing a seemingly less obnoxious spec that is actually just as harmful to users (as they did with FLOC and Topics)? It also seems highly suspicious that it coincides with their very recent announcement to move from pay-per-click to pay-per-impression for ads.

Generally, Google ORG hasn’t shown itself to be a trustworthy custodian of the web and we can’t let this apparent victory lure us into resting on our laurels. As always, a strong diversity of browsers and browser engines is going to be crucial to counteract any future attempt by a single party to dictate the future of the web.

​Last edited on 11.10 CARDINAL am on 03.11.2023 ORG .

Connecting to blog.lzomedia.com... Connected... Page load complete