3 ms·
In the case where I have to use popualr browsers, I use local DNS and a forward proxy to do what this extension does, i.e., replace URLs. Google/Mozilla/Apple/
by 1vuio0pswjnm7 5y ago
In the case where I have to use popualr browsers, I use local DNS and a forward proxy to do what this extension does, i.e., replace URLs. Google/Mozilla/Apple/Microsoft/Opera have control over extensions to their browsers, but they have less/no control over a proxy server written by someone else.
- ghjklpoiuy 5y agoLink please to your setup
- grapescheesee 5y agoBump to this as well
- anshulag 5y agoI'm also curious about your setup.
- 1vuio0pswjnm7 5y agoSimplified setup, many variations possible DNS: nsd or tinydns listens on 127.8.8.1 query example.com @127.8.8.1 custom root.zone with wildcards answer example.com IN A 127.8.8.2 Proxy: haproxy listens on 127.8.8.2, returns user-provided certificate replaces URLs, etc. forwards to 93.184.216.34, verifies server certificate To generate certificates, I wrote a "mkcert" script years before the one written in Go that is now being promoted by someone working for Google. That company's web browser has the majority share of users. Alas, that browser is unreasonably hostile to user-provided certificates for local addresses.1 Hence this is probably not a setup that is appropriate for everyone or every situation. For recreational web use, I like to manipulate and inspect traffic, this is more lightweight than popular alternatives (mitmproxy, etc.), so it works for me. 1. https://stackoverflow.com/questions/7580508/getting-chrome-to-accept-self-signed-localhost-certificate https://stackoverflow.com/questions/7580508/getting-chrome-t...
- pretext 5y agoI wonder how to implement this with pi-hole.
- 1vuio0pswjnm7 5y agoPi-Hole used dnsmasq and modified it. Pi-Hole encourages users to forward DNS queries to (so-called "upstream") third party DNS providers; I think it comes with presets for GoogleDNS and others. I try to avoid dnsmasq (it is often used by default on OpenWRT) as well as third party DNS. I love the idea behind Pi-Hole but I cannot get excited about the implementation. If I were to make a "Pi-Hole", I would use nsd, tinydns and haproxy. There would be no need for third party DNS. For anyone that wanted to use third party DNS, optionally I would provide dnscache. It's easy to take public DNS blocklists and "import"^1 them into dnscache. There are lots of other interesting "alternative Pi-Hole" ideas yet to be tried. 1. dnscache uses the filesystem for nameserver manipulation instead of lists. Each domain is a file in the root/servers folder. Each file contains the address of a (blackhole) nameserver.