[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Browser Fingerprinting
- From: Boruch Baum <boruch_baum@xxxxxxx>
- Date: Fri, 17 Apr 2020 01:35:53 -0400
- X-ml-name: emacs-w3m
- X-mail-count: 13610
- References: <87lfmx8frv.fsf@ebih.ebihd> <873694mu9f.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> <20200417025514.5gotmp6vlvg3v25x@E15-2016.optimum.net> <87r1wmyef5.fsf@ebih.ebihd>
On 2020-04-17 05:33, Emanuel Berg wrote:
> Boruch Baum wrote:
>
> > fingerprinting can only happen when the client either
> > voluntarily puts fingerprinting data in HTTP GET/POST
> > requests [...] AFAICT, neither emacs-w3m nor w3m
> > do either.
>
> C-h v w3m-add-user-agent RET
>
> w3m-add-user-agent is a variable defined in ‘w3m.el’.
> Its value is nil
> Original value was t
>
> Documentation:
> Non-nil means add the User-Agent field to the request header.
> The value of ‘w3m-user-agent’ is used for the field body.
And thus? Oh, maybe you're confusing user-agent strings with
fingerprinting? They're very different concepts. I gave several
examples of fingerprinting data elements in my original e-mail.
Otherwise, I don't understand what point you're trying to make.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0