News for hackers. Stuff that matters.

A comment on Building fast.com. Parent comment

Re:Building fast.com by scrollaway on Tuesday August 09, 2016 @07:19PM (#12258354)
Since fast.com is https, the headers are encrypted. Correct me if I'm wrong, but unless the ISP has the CAs private keys they wouldn't be able to tell your user agent.
[ Parent | on HN ]
Re:Building fast.com by MertsA on Wednesday August 10, 2016 @07:33AM (#12260855)
The CAs private keys can't be used to decrypt https. All the CA does is sign your public key in a certificate that shows validity and the domain name.
[ Parent | on HN ]
Re:Building fast.com by kekub on Tuesday August 09, 2016 @07:50PM (#12258496)
The DNS-Query or IP could be used to identify somebody accessing fast.com.
[ Parent | on HN ]
Re:Building fast.com by detaro on Tuesday August 09, 2016 @08:02PM (#12258562)
That still doesn't allow the ISP to tell the difference between e.g. wget and a browser via a current User-Agent-String, thanks to HTTPS.

The domain is exposed over various ways, yes, but that's the point of the idea to connect to fast.com regularly to trick theoretical shaping based on it.

[ Parent | on HN ]
Re:Building fast.com by pornel on Tuesday August 09, 2016 @08:34PM (#12258700)
List of supported ciphers is unencrypted and very UA-specific.
[ Parent | on HN ]