Chrome not proceeding with Web Integrity API deemed by many to be DRM
![](https://discuss.tchncs.de/pictrs/image/3d481700-2f7b-47a6-9569-f7c22ad4e7a4.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
![Chrome not proceeding with Web Integrity API deemed by many to be DRM](https://lemmy.world/pictrs/image/13cce0cd-9a02-4f44-924e-38530271646d.jpeg?format=jpg&thumbnail=256)
9to5google.com
The Chrome team says they're not going to pursue Web Integrity but...
it is piloting a new Android WebView Media Integrity API that’s “narrowly scoped, and only targets WebViews embedded in apps.”
They say its because the team "heard your feedback." I'm sure that's true, and I can wildly speculate that all the current anti-trust attention was a factor too.
You are viewing a single comment
I use Firefox on Mobile with the bitwarden addon. Works well for me. Plus you export all your saved Google passwords into bitwarden. I need to make the switch on my PC now.
But the add-on isn't sandboxed like in chrome. Like i remember, depending on if you use an external MAC like apparmor or not, where if you're runnimg in Linux and you're using Firefox, websites could steal your ssh keys from ~/.ssh/
Malicious addons or websites could easily do the same thing, and steal your bitwarden credentials. Unless you have the premium version, you can't put otp on it.