UnlockMe App for Linux Lite

[ralphy]

[member=6811]Oobuntus[/member] interesting recommendation. Indeed! I was in fact working directly on a hosts file substitution with this based on the fact that TLDs do matter for dnsmasq (DNS) - while the hosts file doesn't care for TLDs at all - and I never thought even once about implementing additional checks for cases as the one you have just described. Kudos to you!

But yeah, to also address part of your initial comment... the difference between the hosts file approach and dnsmasq is that we are dealing with TLDs in dnsmasq, which is more effective for blocking in my opinion. For example, you could tell the hosts file to block domain.tld and it will not care about any other subdomain - *.domain.tld would still be accessible... while with dnsmasq blocking domain.tld effectively blocks all *.domain.tld  subdomains.

Also, just so you know, I was trying to "hit two birds in one shot" with the Blacklist Generator... The generated list can be used on security appliances such as pfsense; which offers dnsmasq and unbound DNS Server services. Blacklist Generator can actually generate lists for either service for later use on pfsense appliances - unbound list cleanup needs more work but I'll get to that at some point, besides I'm getting off-topic there.

Back to your suggestion... perhaps hint users with hosts files with more than 100 lines? Would that be a reasonable threshold? That's assuming users blocking via hosts file blacklists will easily exceed the 100 lines threshold.