> The fanciest tracking trick is I feel like this changes all the time; I was recently surprised to discover 'TLS Client Channel ID' (my nomenclature is a bit

> The fanciest tracking trick is I feel like this changes all the time; I was recently surprised to discover 'TLS Client Channel ID' (my nomenclature is a bit fuzzy - an RFC for automatic client certs "for security") and would love to learn more about the extent of its current implementation in Chrome. https://news.ycombinator.com/item?id=15753648 https://news.ycombinator.com/item?id=15753648 >londons_explore: In Chrome, it also uses the TLS Client Channel ID, which is a persistent unique identifier established between a browser and a server which (on capable platforms) is derived from a key stored in a hardware security module, making it hard to steal. Ie. if you clone the hard drive of a computer, when you use the clone, Google will know you are a suspicious person, even though you have all the right cookies. https://en.wikipedia.org/wiki/Transport_Layer_Security_Channel_ID https://en.wikipedia.org/wiki/Transport_Layer_Security_Chann... http://www.browserauth.net/channel-bound-cookies http://www.browserauth.net/channel-bound-cookies