Re: Modify transparent mode
Redback <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Message-ID | <[email protected]> |
On 4/2/19 12:34 am, Lee wrote: > On 2/3/19, Redback <[email protected]> wrote: >> Is there a way to modify transparent mode so as to also block tracker >> /ad domains from SSL request, privoxy is running on a DD-WRT router >> (ex-netgear router). > > Privoxy can't block things like > /(.*/)?js/hitbox > on SSL requests, but it can block hostname patterns like > .*tracking. > .*ad. > > And it's pretty easy to turn an ad blocker hostfile into a privoxy > action file - eg > curl https://raw.githubusercontent.com/lightswitch05/hosts/master/ads-and-tracking-extended.txt >> lightswitch-hosts.txt > to get the file and > sed -e "s/0\.0\.0\.0 //" -e "s/^ *//" -e "s/ *$//" -e "/^$/d" > lightswitch-hosts.txt > to remove the leading "0.0.0.0 " on the lines > > Regards, > Lee > G'day Lee Thank you for the feed back, I am aware the program has it short coming with regards to SSL issue, it just the hostname/domains that I wish to block, however, saying this, the privoxy program is running on the router only , not on any other device's or computers. Since TV's and etc now go through this proxy to protect my privacy since TV's are a very chatty device. I see in the logs, the request for non SSL hostname are blocked from time to time, and it seem to be a mix bag for SSL request as most time there is no SSL request in the logs, could this last part be related to having no setting in the network / proxies property box on any devices or computers themselves! All device get their IP by the router DHCP only. P.S Privoxy and DHCP run on the same router, the curl section worked the lather part is a no go. confdir /jffs/etc/privoxy templdir /jffs/etc/privoxy/templates logdir /jffs/var/log/privoxy actionsfile /jffs/etc/privoxy/match-all.action actionsfile /jffs/etc/privoxy/default.action actionsfile /jffs/etc/privoxy/PrimerRules.action actionsfile /jffs/etc/privoxy/RefusedPath.action actionsfile /jffs/etc/privoxy/block.action actionsfile /jffs/etc/privoxy/yoyo.action actionsfile /jffs/etc/privoxy/Genric.action actionsfile /jffs/etc/privoxy/adblock.action actionsfile /jffs/etc/privoxy/TightAccess.action actionsfile /jffs/etc/privoxy/rpft.action actionsfile /jffs/etc/privoxy/Cookies.action actionsfile /jffs/etc/privoxy/Mail.action actionsfile /jffs/etc/privoxy/Media.action actionsfile /jffs/etc/privoxy/Mobile.action actionsfile /jffs/etc/privoxy/News.action actionsfile /jffs/etc/privoxy/Sharefiles.action actionsfile /jffs/etc/privoxy/Technews.action actionsfile /jffs/etc/privoxy/Websites.action actionsfile /jffs/etc/privoxy/Unblock-Torrents.action actionsfile /jffs/etc/privoxy/user.action actionsfile /jffs/etc/privoxy/PathExcepts.action filterfile /jffs/etc/privoxy/default.filter filterfile /jffs/etc/privoxy/rpft.filter filterfile /jffs/etc/privoxy/Cookies.filter filterfile /jffs/etc/privoxy/Mail.filter filterfile /jffs/etc/privoxy/Media.filter filterfile /jffs/etc/privoxy/News.filter filterfile /jffs/etc/privoxy/Sharefiles.filter filterfile /jffs/etc/privoxy/Technews.filter filterfile /jffs/etc/privoxy/Websites.filter filterfile /jffs/etc/privoxy/user.filter logfile logfile ############################################################# ############################################################# debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. # debug 2 # show each connection status # debug 4 # show I/O status # debug 8 # show header parsing # debug 16 # log all data written to the network # debug 32 # debug force feature # debug 64 # debug regular expression filters # debug 128 # debug redirects # debug 256 # debug GIF de-animation # debug 512 # Common Log Format debug 1024 # Log the destination for requests Privoxy didn\t let through, and the reason why. # debug 2048 # CGI user interface debug 4096 # Startup banner and warnings. debug 8192 # Non-fatal errors # debug 32768 # log all data read from the network # debug 65536 # Log the applying actions ############################################################# listen-address :8118 toggle 1 enable-remote-toggle 1 enable-remote-http-toggle 0 enable-edit-actions 1 buffer-limit 16384 keep-alive-timeout 600 default-server-timeout 60 socket-timeout 25 handle-as-empty-doc-returns-ok 1 accept-intercepted-requests 1