From 4e52673b7dd5bb198ac02128c8c4447d9c036f61 Mon Sep 17 00:00:00 2001 From: Mikaela Suomalainen Date: Mon, 8 Oct 2018 20:27:17 +0300 Subject: [PATCH] etc: rm -r polipo/ Polipo is no longer maintained and it seems that I am doing the same thing with Privoxy except censoring accept-language which I need to investigate. I think Privoxy warned about changing headers possibly making ones fingerprint more unique and thus trackable? But aren't those also going inside https so maybe there is no point? --- etc/polipo/config | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 etc/polipo/config diff --git a/etc/polipo/config b/etc/polipo/config deleted file mode 100644 index e2b5b4a5..00000000 --- a/etc/polipo/config +++ /dev/null @@ -1,21 +0,0 @@ -# This file only needs to list configuration variables that deviate -# from the default values. See /usr/share/doc/polipo/examples/config.sample -# and "polipo -v" for variables you can tweak and further information. - -# Defaults -logSyslog = true -logFile = /var/log/polipo/polipo.log - -# Address to listen, allowed clients & port -#proxyAddress = ::0 -#allowedClients = 172.16.0.0/16, fd6a:d4e8:95e6::/64 -#proxyPort = 8123 -proxyPort = 8080 - -# Tor -socksParentProxy = localhost:9050 -diskCacheRoot="" -disableLocalInterface=true -censoredHeaders = from, accept-language -censorReferer = maybe -