From: Tomas Nordin <tomasn@posteo.net>
To: Boruch Baum <boruch_baum@gmx.com>, emacs-w3m@namazu.org
Cc: help-gnu-emacs@gnu.org, Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: [emacs-w3m:13607] Re: Browser Fingerprinting
Date: Fri, 17 Apr 2020 10:15:23 +0200 [thread overview]
Message-ID: <87h7xio7dw.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20200417025514.5gotmp6vlvg3v25x@E15-2016.optimum.net>
Boruch Baum <boruch_baum@gmx.com> 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,
> or when the client has a javascript API that can be queried to reveal
> 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
User Agent
HTTP_ACCEPT Headers
Browser Plugin Details
Time Zone Offset
Time Zone
Screen Size and Color Depth
System Fonts
Are Cookies Enabled?
Limited supercookie test
Hash of canvas fingerprint
Hash of WebGL fingerprint
WebGL Vendor & Renderer
DNT Header Enabled?
Language
Platform
Touch Support
Ad Blocker Used
AudioContext fingerprint
CPU Class
Hardware Concurrency
Device Memory (GB)
And most of the values are "no javascript" when testing with w3m,
otherwise yes/no or true/false. The "no javascript" gives a
fingerprinting value as well (bits of identifying information).
The most identifying characteristics is User Agent followed by
HTTP_ACCEPT Headers.
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.
Best regards
--
Tomas
next prev parent reply other threads:[~2020-04-17 8:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 5:44 Browser Fingerprinting Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-15 19:19 ` Tomas Nordin
2020-04-17 1:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-17 7:46 ` Tomas Nordin
2020-04-17 2:55 ` [emacs-w3m:13608] " Boruch Baum
2020-04-17 3:33 ` [emacs-w3m:13609] " Emanuel Berg
2020-04-17 8:15 ` Tomas Nordin [this message]
2020-04-17 8:57 ` [emacs-w3m:13611] " Boruch Baum
2020-04-17 9:35 ` [emacs-w3m:13607] " tomas
2020-04-17 19:17 ` Vladimir Sedach
2020-04-17 21:08 ` Vladimir Sedach
2020-04-18 1:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-17 21:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-18 6:56 ` tomas
2020-04-18 10:12 ` Tomas Nordin
2020-04-19 1:26 ` Boruch Baum
2020-04-19 3:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-17 8:17 ` tomas
2020-04-17 19:31 ` Vladimir Sedach
2020-04-19 1:21 ` Boruch Baum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7xio7dw.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=tomasn@posteo.net \
--cc=boruch_baum@gmx.com \
--cc=emacs-w3m@namazu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.