TechPulseTechPulse
Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

75% Positive

Analyzed from 219 words in the discussion.

Trending Topics

#tpm#key#chrome#secure#enclave#device#fortress#read#private#write

Discussion (6 Comments)Read Original on HackerNews

shim__•4 minutes ago
How is that any different from an TPM backed passkey?
maratc•about 1 hour ago
If Chrome can write into TPM/Secure Enclave it's like the best fingerprinting ever?
coffe2mug•about 1 hour ago
> If Chrome can write into TPM/Secure Enclave it's like the best fingerprinting ever?

Please. Hatred for tech is stupid.

Read the specs before commenting. Even any free AI would have told you better.

Chrome is not writing into TPM or secure enclave.

maratc•about 1 hour ago
From the article:

> The new Chrome protection is known as device-bound session credentials (DBSCs). The measure stores a unique encryption key in a silicon-resident fortress that’s built into the device running the browser. On Windows machines, this fortress is called a TPM, short for Trusted Platform Module. On macOS and iOS, it’s known as a secure enclave. Other platforms have differing names. Recently released versions of Chrome for Windows and macOS generate a key that’s stored in this fortress.

coffe2mug•30 minutes ago
article poorly written (may be by AI).

> generate a key that’s stored in this fortress.

It refers to the private key that is resident inside SecureEnclave. (During manufacturing)

See further. Dont just read one or two lines.

“The attacker can’t steal the private key from the device because the TPM / Secure Enclave will not release it. That is the core protection here,” Scott Helme, a researcher and founder of Report URI who blogged about the new protections on Tuesday, told Ars. “The attacker can steal the cookie, but they can’t answer a DBSC challenge by signing it with the private key, which is still safe on your device.”

Read https://support.apple.com/en-gb/guide/security/sec59b0b31ff/...