Re:Building fast.com
by corobo on Tuesday August 09, 2016 @06:24PM
(#12258140)
That'd actually be great. The moment there's any evidence towards that happening I'm adding a cron script to visit fast.com every 15 minutes.
[ Parent
| on HN ]
Make sure you update your user agent string to the latest Chrome every couple of weeks too. (I'm assuming any ISP doing this is already doing all kinds of sneaky things).
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.
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.
The DNS-Query or IP could be used to identify somebody accessing fast.com.
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.