4 ms·
Kind reminder Google broke almost all TCP fingerprints (i.e. JA3) when introducing grease values and other stuff such as random order in the ciphers in Chromium
by luth0r 3y ago
Kind reminder Google broke almost all TCP fingerprints (i.e. JA3) when introducing grease values and other stuff such as random order in the ciphers in Chromium. I work in a bot detection company and we put a lot effort on it, currently have an advanced implementation that ignores some extensions, order the fields, remove the grease values etc.
- _lvbh 3y agoI have an open source implementation of normalized JA3 fingerprinting at https://github.com/fidraC/canary https://github.com/fidraC/canary (Includes CreepJS and other stuff to be added / WIP) it’s not very complicated but I did waste some time before realizing that grease was everywhere, not just extensions. Note: That is my secondary account for school. I’m not stealing someone else’s work. I use a different name as a sort of mental compartmentalization between different spheres of my life.
- mike_d 3y agoGoogle's plan is to break every type of client fingerprinting and then funnel everyone into using their browser attestation. iOS isn't any better and already sends a unique "Private Access Token" with requests to Cloudflare.