Request for Mozilla Position on an Emerging Web Specification Specification Title: Web Environment Integrity API Specification or proposal URL (if available): https://rupertbenwiser.github.io/Web-E...
Ads. To be precise this on it’s own provides a way for servers to be certain of the environment the pages run (browser, plugins, os). Protecting ads or other functions come from servers refusing unattested configurations or configurations they don’t like (i.e. running adblock, running firefox, running linux).
It should be noted that “being certain of the environment the pages run” requires controlling the client software being executed which requires preventing the user from modifying said executable which requires the browser to either be closed source or, more effectively, controlling the user’s hardware via blackbox verification chips (e.g. TPM DRM). It’s not just advertisers that would benefit but any website that wants to DRM content.
if chrome fully adapts this, this might well be a full blown commerical by chrome for people to switch to firefox. i have been only using chrome only to run our projects locally and test it out.
and what kinda of thing does this protect?
I’d guess it’s first gonna be used for streaming TV shows and such. After that it’ll probably be used for absurd things
I thought they were already being protected by DRM.
Kinda, but it doesn’t work very well. Using video download manager you can download pretty much every video from the web
Malware, malware encrypts its code so researchers cant crack into it and antivirus cant anilize it. Google is accedentally sponsoring malware
Ads. To be precise this on it’s own provides a way for servers to be certain of the environment the pages run (browser, plugins, os). Protecting ads or other functions come from servers refusing unattested configurations or configurations they don’t like (i.e. running adblock, running firefox, running linux).
It should be noted that “being certain of the environment the pages run” requires controlling the client software being executed which requires preventing the user from modifying said executable which requires the browser to either be closed source or, more effectively, controlling the user’s hardware via blackbox verification chips (e.g. TPM DRM). It’s not just advertisers that would benefit but any website that wants to DRM content.
if chrome fully adapts this, this might well be a full blown commerical by chrome for people to switch to firefox. i have been only using chrome only to run our projects locally and test it out.