3 ms·
This seems... kind of pointless? You'd expect the fingerprint to be fully determined by the OS/browser combination, since TLS is implemented entirely in softwar
by gruez 5y ago
This seems... kind of pointless? You'd expect the fingerprint to be fully determined by the OS/browser combination, since TLS is implemented entirely in software. But you can already get both pieces of information through the user-agent, so what's the point?
- foxfluff 5y agoThe point is that there are many many ways to fingerprint even if people spoof their user agent.
- jonatron 5y agoIt can be used to detect scrapers/bots that don't use a browser.
- zamadatix 5y agoFor those exposing a lot of fingerprintable data it doesn't help much but that's not really a problem since there is already plenty of fingerprintable data. For those trying to hide/fake fingerprintable data the mismatch between spoofed user agent and detected browser/OS combo creates a strong fingerprint in itself. This is the general premise of fingerprinting: if you throw enough data points at it trying to escape fingerprinting itself creates a unique fingerprint.
- citrin_ru 5y ago> determined by the OS/browser combination And by browser settings; at least Firefox has quite a few TLS related knobs in about:config (and settings like spdy disable affect TLS hello too).
- richardwhiuk 5y agoYou can observe it without being the server.
- DeadBeatDad 5y ago> But you can already get both pieces of information through the user-agent This is why I have the `resistFingerprinting` flag set to `true` in Firefox