This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
That’s even worse. Websites will trust only Microsoft, Apple, and Google. Those of us who value our security enough to install Linux will be left out in the cold. We’ll be such a small minority that no one ever cares enough to give up on attestation. The pressure will cause our numbers to dwindle to nothing as people flee to proprietary platforms in order to avoid losing access to their bank/doctor/government. All hail the eternal compulsory corporate triopoly.
For now spec calls “holdbacks”, which are designed for this purpose. Attestors will fail randomly for a set percentage of the requests so this can’t be used as a whitelist. Surely this “holdbacks” will either be not implemented or dropped in no time by attestors.
That’s even worse. Websites will trust only Microsoft, Apple, and Google. Those of us who value our security enough to install Linux will be left out in the cold. We’ll be such a small minority that no one ever cares enough to give up on attestation. The pressure will cause our numbers to dwindle to nothing as people flee to proprietary platforms in order to avoid losing access to their bank/doctor/government. All hail the eternal compulsory corporate triopoly.
For now spec calls “holdbacks”, which are designed for this purpose. Attestors will fail randomly for a set percentage of the requests so this can’t be used as a whitelist. Surely this “holdbacks” will either be not implemented or dropped in no time by attestors.
Surely. Remote attestation is only useful if it always succeeds on an approved device.