Re: Suppressing/modifying some browser fingerprints (ie. Am I Unique?)
"U.Mutlu" <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Organization | mutluit.com |
| Message-ID | <[email protected]> |
Ian Silvester wrote on 07/15/2020 03:02 PM: > Some additional thoughts: > > For what it's worth, Privoxy can use the user-agent string to uniquely > identify given clients within your LAN and apply unique filtering based on > it (I mention this based on your previous enquiry). That sounds indeed good. Can this already be done in the config files? If you have one or a few examples handy, would appreciate if you could post it, thx. > Thinking further about Javascript, perhaps one could create a custom rule > to block whichever Javascript functions are leveraged to sniff the more > unique elements that comprise the fingerprint; if you do take on this and > perform the research into the appropriate strings to look for please do > report back to this list. Thanks, yes, I'm interessted in finding a solution especially for the Javascript functions. Best would be to have the choice to allow/deny each single of these JS queries, optionally building own strings to send back. I must admit I'm new to internals of privoxy, but I can say I'm highly motivated, if necessary even ready to do do some C coding in the sources. Unfortunately I'm not an expert in HTML nor in Javascript nor JS DOM nor privoxy nor privacy etc., but I'm confident I can master them :-) When I saw all the tracking/spying and of course also the nasty ads, I realized that I need to find a generic solution for this problem. My current solution is IMO not that bad: in firewall blocking everything by default for both inbound _and_ outbound, and only on demand allowing the minimum required URLs (ie. their address parts) necessary for a site to function. By this method all external trackers of that site get automatically blocked. Of course it requires some work and experimenting for finding out the right addresses (from those inside the HTML) and putting them into the firewall and trying & retrying... This works well I can say, IMO better (more restrictive) than say the DNS-based concept of Pi-hole, but this alone is of course not enough, one _also needs_ privoxy to modify the HTML data. I'm glad to have found the privoxy project. Many thanks to the authors.