MESSAGE
DATE | 2016-06-17 |
FROM | Rick Moen
|
SUBJECT | Re: [Hangout-NYLXS] Qualys Cloud Web Application Scanner bug: | |
|
Quoting Ruben Safir (mrbrklyn-at-panix.com):
> On 06/17/2016 03:50 AM, Rick Moen wrote: > > ou asked what a Web site is doing. I asked what you found out when you > > investigated, starting in the obvious first place to look. > > yes, but I miss understood what you meant. However, I don't think they > need hooks in html or otherwise to track me. They can simply match my > browser fingerprint to searches.
Indeed, that seems safest to assume that any Web site _can_ do, and it's well worth considering whether its business model gives it an incentive to do so.
EFF's Panopticlick is a https://panopticlick.eff.org/ , is a good starting point in seeing how one's browser footprint comes across.
I've often thought it might be useful to deploy a privacy proxy that rewrites outgoing HTML headers to randomise the footprint in various ways.
Of course, users tend to get lured into errors that greatly reduce their privacy such as _logging in_ to sites related to the search engines (e.g., the way GMail / Google Accounts is related ot Google Search) and letting those sites set persistent browser state that then registers at the search engine.
One argument for 'any search engine except for Google Search' is to spread around your Web footprint and not permit any one entity to accumulate much data or benefit much from tracking across multiple sites.
I personally take measures to frequently clear out browser-side state data and to limit its scope (e.g., Adblock Plus and NoScript), plus as I identify abusive tracking domains that I wish to banish completely, I add them to the growing list of those resolved to localhost by my authoritative nameserver. (See: http://linuxmafia.com/pub/linux/network/bind9-examples-linuxmafia.tar.gz)
That is also one of several reasons to run one's own nameservers.
_______________________________________________ hangout mailing list hangout-at-nylxs.com http://www.nylxs.com/
|
|