zlacker

Well, I think this move by google will divide the chromium project in 2 versions: one with and one without this "feature".

>>elforc+(OP)
It doesn't matter. It's a DRM. If your version of the software doesn't contain the right keys none of this will work correctly.

Kinda like how Widevine works. No keys means lower quality.

>>elforc+(OP)
Google will degrade their services for non-DRM browsers. They have a long history of "oops" with UA sniffs and serving slow buggy alternatives to Chrome-only JS.

You'll be filling in captchas 10 times a day, getting randomly locked out of your Google account in the name of security, and whatever new feature they add to their services, they'll find an excuse to require the DRM for it.

>>elforc+(OP)
That doesn't make any difference. There will be websites that will only allow people using approved browsers to access them. Instead of whatever you expect, you'll get a link to download Chrome (or whatever), and possibly install $COMPANY's attestation software.

Then, people will DDOS the attestation endpoints because why not.

>>pornel+22
Cloudflare will happily help Google with displaying captchas to everyone not using Chrome.

>>Wirele+w1
Don't you think people will inevitably crack the software side of things (as has been done with the lower levels of Widevine)?

The end game is probably integration with a TPM that produces the token, or at least whatever part of it verifies that the chrome binary is genuine and that there is no forbidden software running on the client machine.

>>elforc+(OP)
Yes, just like you can still use Android phones that don't pass SafetyNet. But good luck doing anything useful with them.

>>codedo+54
endless captcha loops

>>Spaghe+K8
The end game is probably integration with a TPM that produces the token, or at least whatever part of it verifies that the chrome binary is genuine and that there is no forbidden software running on the client machine.

That is exactly the goal of this, and why it needs to be opposed fiercely.