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...
Question for anyone with more understanding of the implementation…
Doesn’t this still presume the browser tells the truth to the third party attester? Could we not build something that just straight up lies to the attester? Says I’m a good Google chrome user with no extensions please serve me ads sir?
This system would use cryptography and hardware to make sure that you are unable to lie about any of this. Basically, there is a chip inside your CPU that contains special keys installed by the manufacturer. However, this chip only activates itself when it detects that your device is running the approved software. Furthermore, it is made (almost) impossible to open this chip and retrieve the keys without destroying it.
Question for anyone with more understanding of the implementation…
Doesn’t this still presume the browser tells the truth to the third party attester? Could we not build something that just straight up lies to the attester? Says I’m a good Google chrome user with no extensions please serve me ads sir?
This system would use cryptography and hardware to make sure that you are unable to lie about any of this. Basically, there is a chip inside your CPU that contains special keys installed by the manufacturer. However, this chip only activates itself when it detects that your device is running the approved software. Furthermore, it is made (almost) impossible to open this chip and retrieve the keys without destroying it.
I dunno man, you can virtualise tpms, and if you can virtualise it, you can lie about it.
You can virtualize a TPM, but you can’t obtain a valid endorsement key.