4 ms·
To be charitable, he could be talking about the implementation of SCT auditing in Chrome, but it has never uploaded all the sites you visit. There are thre
by charcircuit 3y ago
To be charitable, he could be talking about the implementation of SCT auditing in Chrome, but it has never uploaded all the sites you visit.
There are three possible states:
No Safe Browsing protections -> no SCT auditing
Default Safe Browsing protections -> SCT auditing logic selects a small proportion of TLS connections and performs a k-anonymous lookup on an SCT. If that privacy-preserving SCT lookup reveals that the SCT is not known to Google but should be, the client uploads the certificate, SCTs, and hostname to Google (but no other information).
Enhanced Safe Browsing protections -> SCT auditing logic selects a small proportion of TLS connections and uploads the certificate, SCTs, and hostname to Google (but no other information).
https://groups.google.com/a/chromium.org/g/ct-policy/c/FddjjCNIrLo https://groups.google.com/a/chromium.org/g/ct-policy/c/Fddjj...
- aaomidi 3y agoGot it. Just for reference for others, SCT Auditing is different from SCT validation. I was talking about the validation side. SCT Auditing basically helps ensure that the logs are keeping their promise by letting the root program (Chrome, and Apple) see what certificates are flowing on the internet and if the merkle tree structure is valid.