From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Tomas Nordin Newsgroups: gmane.emacs.help,gmane.emacs.w3m Subject: Re: [emacs-w3m:13607] Re: Browser Fingerprinting Date: Fri, 17 Apr 2020 10:15:23 +0200 Message-ID: <87h7xio7dw.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> References: <87lfmx8frv.fsf@ebih.ebihd> <873694mu9f.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> <20200417025514.5gotmp6vlvg3v25x@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="69424"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org, Emanuel Berg To: Boruch Baum , emacs-w3m@namazu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Apr 17 10:15:52 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jPMAB-000Hx6-Dr for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 17 Apr 2020 10:15:51 +0200 Original-Received: from localhost ([::1]:43666 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jPMAA-00037d-Cs for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 17 Apr 2020 04:15:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43983) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jPM9p-00037X-9w for help-gnu-emacs@gnu.org; Fri, 17 Apr 2020 04:15:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jPM9n-0003KW-PG for help-gnu-emacs@gnu.org; Fri, 17 Apr 2020 04:15:28 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:59179) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jPM9n-0003JJ-7f for help-gnu-emacs@gnu.org; Fri, 17 Apr 2020 04:15:27 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 7C8612400FE for ; Fri, 17 Apr 2020 10:15:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1587111325; bh=Wm8e5L7asmrlBO/HldxfcK2bg9K9qKfV4LRuzCxNDwE=; h=From:To:Cc:Subject:Date:From; b=i634U8kldxiIR8o1yPBfQebBZTL/I4xxCB5kV50lDyzU4foel+vQ49EWca9Kikvgy VCGIQ+Lyo3MKGQPede/khnjZStuPQ76S420ROfUqiYY7LLcvbwFaAHeT4qhhEM7nFN t9MIgcsxLqv/A584wl9lM6RkQWQBPfj/6On4SMaJpZ0QPH5FA3E84wy1sTugwqKGW9 hwsCrhUFUT5u+8FRtIlYH+KMLQ9hRJQ3YLFUiQeQ9RDaCkDRte3yBOIFWVKyqa/m/f v3qnXQlH6x5kEW7/Pu09wzPwWdN2XgjiUkM8N8OkKbvanha9IJDfudw4FkW6wwVs+9 JitmY9qipCZ5g== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 493TRc13Zqz9rxD; Fri, 17 Apr 2020 10:15:24 +0200 (CEST) In-Reply-To: <20200417025514.5gotmp6vlvg3v25x@E15-2016.optimum.net> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 185.67.36.66 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:122857 gmane.emacs.w3m:10490 Archived-At: Boruch Baum writes: >> Does your browser protect from fingerprinting? =E2=9C=97 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