7 ms·
According to the paper the most useful attributes for browser fingerprinting are: - User agent - List of Plugins - Screen resolution and color depth - Canva
by wongarsu 8y ago
According to the paper the most useful attributes for browser fingerprinting are:
- User agent
- List of Plugins
- Screen resolution and color depth
- Canvas
- WebGL Renderer (~GPU Model)
Maybe Canvas can be fixed to a degree, but the others feel like things that will inherently be different. Firefox with the privacy.resistfingerprinting setting solves all of these at least partially (and more), but not without some usability tradeoffs.
- thejohnconway 8y agoSurely user agents could give out way less information (virtually none in fact?).
- Fnoord 8y agoYes, but it will break functionality because servers use it to apply hacks on the website before the content is served. WebRTC is another one which you can disable. JavaScript, in general, as well, requiring uMatrix. Chrome leaks the extensions you use, Firefox does not (AFAIK). As for blocking canvas, see [1] To test your fingerprinting I can recommend IPleak [2] The problem of this all is, its a usability nightmare. [1] https://addons.mozilla.org/en-US/android/addon/canvasblocker/ https://addons.mozilla.org/en-US/android/addon/canvasblocker... [2] https://www.ipleak.net https://www.ipleak.net
- Jonnax 8y agoYes it really should. Chrome on Android reports your phone model and build number. If you're using a lessor known phone with a carrier specific ROM, then you're in a really tiny population.
- zaarn 8y agoNot without breaking Grandma's favorite online banking website.
- wongarsu 8y agoYou can't get around giving nearly the entirey of the User Agent string simply thorugh feature detection (well, except for the phone model when on mobile). Canvas and WebGL can be fixed by limiting their functionality, or at least that's what Firefox does in the aforementioned mode. Canvas could conceivably be fixed to just behave the same everywhere, but for WebGL you have to limit it to some common denominator to hide the GPU model, so privacy nessesitates less functionality. The list of plugins can be spoofed to be empty. Screen resolution (or more importantly, window size) has to be somewhat accurate because lots of websites use it for responsive design. Firefox can round the window size to the nearest multiple of 200x100 which doesn't break too many things, but that's still far from giving the same value for everyone. https://wiki.mozilla.org/Security/Fingerprinting https://wiki.mozilla.org/Security/Fingerprinting
- zzzcpan 8y ago> Canvas could conceivably be fixed to just behave the same everywhere, but for WebGL you have to limit it to some common denominator to hide the GPU model You can just measure performance of those things then.
- bartimus 8y agoUnless two browsers are identical there's almost always a way to detect some particularity.
- wongarsu 8y agoJust giving the same value for everyone on the latest version of Firefox using Windows 10 with a maximized window on a 1920p display would seriously hamper fingerprinting. It can still be enough when used with other information (IP, visited sites etc), but at least it would dilute the signal a lot.
- bartimus 8y agoSection 3.2 'Advancing fingerprinting' shows some more ways you can find particularities which will be hard to hide.
- mobjack 8y agoUser agents are not that great of tracking. If you use a common device and browser kept up to date to the latest versions, then you are not going to be unique. Using Safari on an iPhone will make you similar to 30% of web traffic. Browsers also update all the time changing the user agent so it isn't that reliable tracking over extended periods of time. The am I unique websites seem to compare your user agent to a database with outdated browser versions from the past data, making your score look much scarier than it really is. If you keep things up to date, chances are that you are not that unique.
- Jonnax 8y agoBrowser plugins really need to go away. If it's not implementable normally then it shouldn't be on the web. In my opinion at least. GPU models also should not be given, browsers need to abstract features and performance into something else. Like if I'm writing a WebGL app, I should just be able to test a few baselines configs. User agent is a tricky one, Chrome on Android gives too much info because it's built by an advertising company.
- modzu 8y agothats like saying programs should go away if its not implementable by the OS. its just a different layer. browser plugins are tremendously useful edit: also your comment seems to imply that plugins are used for websites trying to do something the browser doesnt support (ex flash) -- while this is sometimes done, most plugins add additional functionality for the user, ex adblockers, usability improvements, etc
- kalleboo 8y agoPlugins and extensions are different things. The `navigator.plugins` used for fingerprinting is just for NPAPI/PPAPI stuff like Flash, Java, Silverlight. Just about all browsers are also in the process of deprecating support for them. (it can also be possible to fingerprint browser extensions, but that is a bit trickier as it's not served up directly by the browser as a handy array)
- modzu 8y agooh yes my bad, thanks. i was thinking extensions (maybe thanks to all the ff news!). wrt fingerpritning plugins, it seems to be the least of the issues and hopefully not an issue for long :)
- ekianjo 8y ago> Browser plugins really need to go away. If it's not implementable normally then it shouldn't be on the web. In my opinion at least. So no more ad blockers?
- everdrive 8y agoI'm a bit old school when it comes to browser tracking, and as such I'm not as familiar with Canvas. What exactly is Canvas? What information is provided which can be tracked? Are there ways to disable Canvas without installing browser extensions?
- kalleboo 8y agoThe Wikipedia page has a pretty good summary https://en.wikipedia.org/wiki/Canvas_fingerprinting https://en.wikipedia.org/wiki/Canvas_fingerprinting Basically Canvas is a JavaScript API for programmatically drawing graphics and text. Subtle differences in color, font rendering, antialiasing etc will produce different rendering on different hardware depending on OS, browser, GPU, drivers, etc. This lets a site running JavaScript to generate a hash unique to everyone with your specific combination of software and hardware and uniquely identify you without cookies.
- matthewaveryusa 8y agoBasically different devices and browsers render high-level graphical objects, such as fonts, differently. When you visit a site that does canvas tracking, a small javascript snippet will ask your browser to render a few graphical things on an html5 canvas and export that canvas to a png. The hash of that png is a good fingerprint of your hardware, browser and rendering software.
- rubidium 8y agoJust to be clear, the only reason to do this is fingerprinting, correct?
- dillondoyle 8y agowhich has legitimate use cases in fraud detection and login security (eg recaptcha)
- mindslight 8y agoIt's a bit of a stretch to cast those as "legitimate use". A security vulnerability is a security vulnerability, regardless of who exploits it.
- 3xblah 8y agoThe first "attribute" is simply an HTTP header. As such it can be selected and changed by the user. The user may choose not to send a User-Agent header at all. IME, few sites actually require a User-Agent header in order to retrieve a page. Developers sometimes try to vary page content based on this header. For example, send a certain string containing the name of a "bot" and you might get nothing. The detection occurs before any content is returned. The rest of these "attributes" are not HTTP headers, and occurs after the resource is fetched. We do not need to give away this information in order to retrieve the resource. The fingerprinting problem arises because the software we use to do the retrieval does far more than retrieve web pages. These other attributes cannot be detected unless the software used to retrieve the web page also includes other features that process what is retrieved, including a Javascript engine that runs code straight from the internet ("browser"). Looking to the authors of a popular browser to solve the problem they themselves have created. Is it rational to expect that this is where the solution will come from? If one is willing to make some "useability tradeoffs" then one might use a simple http client to retrieve web pages instead of a popular browser. After the pages are retrieved, then one can use a popular browser to view them if desired; the browser need not have access to the internet. This is what I do. Not to avoid "fingerprinting" but just because it is faster and more robust. With the help of a trivial program that transforms urls into http (I wrote one), one can retrieve the text/html of web pages, without requesting all the third party advertising cruft, with any tcp client such as netcat. HTTP pipelining becomes easy, making consumption of large quantities of information more efficient -- many pages, one connection. The two programs together form an "http client" with, relative to a popular browser, or even a program like curl, very low code complexity. Whenever I see the "fingerprinting" debate come up, I always go through the same thought experiment: For situations where "fingerprinting" is a problem, web users all use the same simple http client. All send the same minimal headers. The web must accomodate users not the other way around.
- gruez 8y ago>The first "attribute" is simply an HTTP header. As such it can be selected and changed by the user. Maybe if you have script disabled, but if you have javascript it's trivial to detect which browser you're on based on javascript implementation quirks alone. >We do not need to give away this information in order to retrieve the resource. You clearly haven't seen mandatory javascript sites.
- username223 8y ago> - User agent This could be fixed with a bit of courage. Firefox could use "Firefox", Safari "Safari," etc. UA sniffing and UA strings are completely absurd at this point, and need to go away. > - List of Plugins JavaScript should not see this, especially not their versions. The last three are harder to avoid for "responsive" web design. One attribute you didn't mention was the font list. There is no good reason for JavaScript to be able to see this. The model should be that the page requests a font, and the browser uses either that or its best try at a substitute.
- ken 8y agoIt's a nice idea, but major sites still do user agent sniffing. Try setting your UA to one of those strings and visiting google.com -- the SERP looks like it came from 2009. If Firefox tried that, it would instantly become that weird browser that makes Google look bad. The internet would be flooded with tips on how to set a custom UA that made it pretty again.
- username223 8y ago> Try setting your UA to one of those strings and visiting google.com -- the SERP looks like it came from 2009. I just tried, and it's great! I had forgotten that search could be so snappy and simple. The more likely outcome, unfortunately, is that Google would adjust its UA-sniffing to serve the same 2019 bloat to "Firefox."
- alkonaut 8y agoWhat plug-ins I have shouldn’t concern the server on the other end. Why does is it transferred? Canvases should never be readable by the other end without explicit permission. Basically transmitting anything rendered to a canvas should be equivalent to using my web camera from an integrity standpoint. Time zone, operating system (from a short list) and language is fine, because it’s not a lot of entropy and my ip is known anyway unless on a vpn. Gl renderer/graphics card, desktop resolution - nah. The viewport dimension is all that should be known. Basically the browser should by default have an entropy budget for my entire fingerprint that ensures I’m not personally identifiable.
- 9HZZRfNlpR 8y agoHow can you not transfer the info about plugins? You test them the in front, can he done in million ways with JavaScript and send it to a server of your choice.