I am using Firefox too. However I also consume lots and lots of general purpose websites which in time probably become not consumable if you are not compliant. Which in turn either render FF not usable, or adopt the unfortunate standards.
Even if it does implement WEI, it still won't pass validation. Each website will have its own list of approved software configurations, and you'll be lucky if your bank/doctor/government even allows you to use a Mac, let alone your favorite distro's builds of Firefox and Linux.
I rechecked the current spec. It does not fully cover what a user agent can ask to the attestor ( "content binding" to be defined). So we can assume this attestation spec is defined at the attestor.
Of course this does not mean attestor can not have different profiles to attest for.
So your comment even though is possible, just not defined yet. Which we can - I believe - rightfully assume will be in the final spec or implementation.
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.
![[wei] Ensure Origin Trial enables full feature ยท chromium/chromium@6f47a22](https://forkk.me/pictrs/image/9f5d02b2-782e-453e-8fe9-c6195ee3f0ce.png?format=jpg&thumbnail=256)
I am using Firefox too. However I also consume lots and lots of general purpose websites which in time probably become not consumable if you are not compliant. Which in turn either render FF not usable, or adopt the unfortunate standards.
Even if it does implement WEI, it still won't pass validation. Each website will have its own list of approved software configurations, and you'll be lucky if your bank/doctor/government even allows you to use a Mac, let alone your favorite distro's builds of Firefox and Linux.
I rechecked the current spec. It does not fully cover what a user agent can ask to the attestor ( "content binding" to be defined). So we can assume this attestation spec is defined at the attestor.
Of course this does not mean attestor can not have different profiles to attest for.
So your comment even though is possible, just not defined yet. Which we can - I believe - rightfully assume will be in the final spec or implementation.
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.