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?
My understanding was that the browser vendor itself would be the attester. So if Google says it’s Google Chrome, it probably is. Unless you somehow reverse engineer how Google decides that it’s Google Chrome and spoof that or something…
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?
My understanding was that the browser vendor itself would be the attester. So if Google says it’s Google Chrome, it probably is. Unless you somehow reverse engineer how Google decides that it’s Google Chrome and spoof that or something…