[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Browser Fingerprinting
- From: Tomas Nordin <tomasn@xxxxxxxxxx>
- Date: Fri, 17 Apr 2020 10:15:23 +0200
- X-ml-name: emacs-w3m
- X-mail-count: 13614
- References: <firstname.lastname@example.org> <email@example.com> <20200417025514.5gotmp6vlvg3v25x@E15-2016.optimum.net>
Boruch Baum <boruch_baum@xxxxxxx> writes:
>> Does your browser protect from fingerprinting? ✗ no
> This has me puzzled. How did the website reach this answer? My memory of
> this subject is that fingerprinting can only happen when the client
> either voluntarily puts fingerprinting data in HTTP GET/POST requests,
> fingerprinting data. AFAICT, neither emacs-w3m nor w3m do either. Off
> the top of my head, some examples of fingerprint data that I remember
> being common are: available fonts, display geometry and properties,
> geo-location, data from device sensors (eg. temperature, accelerometer)
> , hardware specifications, software environment, and device specific
> stuff like UUID numbers.
The fields tested as browser characteristics were
Browser Plugin Details
Time Zone Offset
Screen Size and Color Depth
Are Cookies Enabled?
Limited supercookie test
Hash of canvas fingerprint
Hash of WebGL fingerprint
WebGL Vendor & Renderer
DNT Header Enabled?
Ad Blocker Used
Device Memory (GB)
fingerprinting value as well (bits of identifying information).
The most identifying characteristics is User Agent followed by
Browsing the web with a text based browser is not a common thing to do,
so from a browser fingerprinting point of view I guess the uniqeness is
to be expected.