this post was submitted on 13 Aug 2023
364 points (93.8% liked)
Technology
59237 readers
4230 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One thing I don't understand about all of this WEI: can't we just use a user agent switcher / spoofer to 'look' like chrome or any other browser and OS to counter this?
This isn't about a user agent. In basic terms there is supposed to be some kind of software that attests that the browser is actually what it claims to be. On the other side, a server can trust this "attester" or not. So even if you wrote software that always attests what the browser claims to be, Netflix for example could say "nah, I don't trust you bro".
On Android this attestation would be done by the Google play services (afaik). On desktop, the OSs would need to implement this attestation.
Please someone correct me if I'm wrong on this.
While I haven't seen data to back this up, another Lemmy user called out that Intel chips may have support for running secure code the user cannot modify. The results are signed by an encryption key on the motherboard/CPU that cannot be extracted to fake the signature.
So let's say Chrome asks this hardware module to hash the executable code and some state for itself currently in RAM and sign it with Intel's private key on the motherboard/CPU. The "some state" portion ensures the hash is always unique. Maybe it is just a timestamp. Regardless, this helps the attestation server know Chrome has not been modified because the hash is unique and cannot simply be captured in flight once and then replayed/faked over and over like a user-agent string.