News for hackers. Stuff that matters.
Re:Web Environment Integrity API by keepamovin on Friday July 21, 2023 @10:12PM (#36822494)
I was kind of worried about this while reading it, as it seems to be able to exclude people using remote browser isolation because, by definition, that's a browser running on some other environment than the device, likely on a server.

At BrowserBox we do this with headless chrome, and so it's unlikely it would be "approved" by this attestation.

I was worried about this for my business, but then I realized that, if it really came down to browsing being unusable through BrowserBox because of this, we could just create a fork of chromium that removes this attestation, modifies it to always be valid, or requests a valid token from the human's connecting device and then sends that on from the remote browser, essentially acting as a agent (a true user agent) to the requesting web page.

Thankfully we're open source so this is something that people can contribute to in a collective and distributed way, if they want it. It's not just a browser company versus individuals, it's what a browser company wants versus the whole might of open source and what people actually want.

Dosyago is technically a "browser company" too, but we get around needing to fund it with ads, by selling the browsing as first class product. If you want to get involved in these efforts, of "securing the web against its own 'best interests'", and "protecting the web from itself", come and check us out and contribute at: https://github.com/dosyago/BrowserBoxPro

There are no comments on this comment yet.