You’re relying on the device to provide a signal of authenticity with this model. Firefox can simply say it’s authentic. However this will just lead to any signals from Firefox being ignored by any site… So Firefox would actually just need to spoof whatever signals Chrome is using… And thanks to Chromium being open source that shouldn’t be too hard. If it’s a device ID or mac address that’s being used to show uniqueness, that can be randomized and presented to sites…
I haven’t looked at the spec… and from my understanding the Spec isn’t even finalized yet… I could be wrong. But It’s certainly not going to be a case that each webhost has a complete list of ssl certs from every client… That’s never going to happen. It could be that a cert is issued to Apple and Google, and they sub-cert out to individual devices for identities. Not sure what would stop firefox from just pulling a glut of certs and rotating them out regularly.
If it could be spoofed easily, wouldn’t that defeat the point?
I mean you can’t just “spoof” a ssl cert or private ssh key, I have to assume this is at least that good.
You’re relying on the device to provide a signal of authenticity with this model. Firefox can simply say it’s authentic. However this will just lead to any signals from Firefox being ignored by any site… So Firefox would actually just need to spoof whatever signals Chrome is using… And thanks to Chromium being open source that shouldn’t be too hard. If it’s a device ID or mac address that’s being used to show uniqueness, that can be randomized and presented to sites…
I haven’t looked at the spec… and from my understanding the Spec isn’t even finalized yet… I could be wrong. But It’s certainly not going to be a case that each webhost has a complete list of ssl certs from every client… That’s never going to happen. It could be that a cert is issued to Apple and Google, and they sub-cert out to individual devices for identities. Not sure what would stop firefox from just pulling a glut of certs and rotating them out regularly.