[Privoxy-users] Privoxy-users Digest, Vol 17, Issue 3

Lee ler762 at gmail.com
Mon Nov 6 19:49:54 UTC 2017

On 11/6/17, Robert Klemme <rklemme at klemmeconsulting.com> wrote:
> Thanks Lee for the excellent explanation.
> I have created block lists in this manner before and they work great.
> I was trying to come up with a way to use a wildcard or some regex solution
> to block anything "tile" related.  It seems like either "tile" or "
> tile-x.com" is usually involved.

.tile.  (leading and trailing period) will block anything with .tile.
in the name; problem is that also blocks things like

> I won't be able to catch them all and I cannot find a list of all of these
> hosts.  I know they only downside to this is there might be false positives
> but I am willing to give it a shot.

Something else to consider would be running your own DNS recursive
resolver & blocking things there.

Short story is that I wanted DNSSEC & my isp doesn't do that.  So I
intalled bind as a recursive resolver on my PC and a nice side effect
is that DNS lookups are logged and it's real easy to block things - eg
this bit in named.conf
  zone "telemetry.microsoft.com" { type master; notify no; file
"ZONES/null.zone"; };
blocks everything in the telemetry.microsoft.com zone

> Then I can search the log files for blocks related to this and we can
> create the first ever "Live Tile" blocklist and share it on Git.  I would
> love that!
> Also, I didn't have to set my Windows 10 PC to use the proxy the way you
> mentioned. I have Privoxy setup in all of the browsers and somehow the OS
> is pulling it from there. Seems to be working?!

Good to know.  I wasn't sure if setting the proxy in ms edge would
tell the system to proxy everything or just edge traffic.


More information about the Privoxy-users mailing list