Hi, thank you for your great work. I was shadow banned for a time due to my totally incognito set up account so I am bumping my issue.
So hosts format lists based blocking works without any problem (whether system-wide DNS query-based blocks or for individual apps).
However, no one clever uses hosts format lists anymore as this format is very outdated, circa 2005 poor amateur internet cowboy, while you need to specify all sub-domains instead of using just *.domain.com / domain.com like in dnscrypt-proxy [it assumes ^(.*\.)?domain\.com$ automatically]. You can also use just *telemetry* (it is .*telemetry.*) or pixel* in dnscrypt-proxy. It is almost all anybody needs.
Regular expressions are of course more powerful but my blocking list for dnscrypt-proxy in Windows has >10MB and it works super fast without any problem at all. I can shut down for example 50% of Microsoft tracking, even without firewall, with just *microsoft*, *office*, *bing* and *azure* - and I have many methods if I really want to check something at microsoft.com in browsers.
So you just choose modern "wildcard domains" format per for example superb github.com/hagezi/dns-blocklists?tab=readme-ov-file#pro and that's all.
So OpenSnitch is working great (but you can not rearrange columns in tabs and automatically adjust / readjust columns widths. Check NetLimiter for Windows - it's very well done there. Also please add a few words to Preferences>Database options as I really did tried to understand but really don't know what some of these options do.)
RegExps logic processing works generally here as it works properly in [Rule>Network>To_this_host] (using full regexps notation) and also for regexps for example in [Rule>Network>Protocol] and [Rule>Network>To_this_port].
But they do not work when list is used as in [...>To_this_list_ofdomains(regular_expressions)]. All is ok with folder and . I saw in logs that OpenSnitch reports changes done in the file - how many new regexps were found. However, It does not use those regexps, neither full regexps (^(.*\.)?example\.com$) nor plain domains (example.com).
???
Fedora Gnome newest (40, but also 39), kernel newest (was 6.8.7-300.fc40.x86_64 - even newer now).
OpenSnitch most new rpms.
opensnitchd -check-requirements OK (for 39 but I think for my fresh 40 should be too).
Nothing interesting in 'debug' type log I think, though please write what to look for. It confirms for example that there are 5 regexps entered in the file but does not process them at all.
Hi, thank you for your great work. I was shadow banned for a time due to my totally incognito set up account so I am bumping my issue.
So hosts format lists based blocking works without any problem (whether system-wide DNS query-based blocks or for individual apps). However, no one clever uses hosts format lists anymore as this format is very outdated, circa 2005 poor amateur internet cowboy, while you need to specify all sub-domains instead of using just
*
.domain.com / domain.com like in dnscrypt-proxy [it assumes ^(.*\
.)?
domain\
.com$ automatically]. You can also use just*
telemetry*
(it is .*
telemetry.*
) or pixel*
in dnscrypt-proxy. It is almost all anybody needs. Regular expressions are of course more powerful but my blocking list for dnscrypt-proxy in Windows has >10MB and it works super fast without any problem at all. I can shut down for example 50% of Microsoft tracking, even without firewall, with just*
microsoft*
,*
office*
,*
bing*
and*
azure*
- and I have many methods if I really want to check something at microsoft.com in browsers. So you just choose modern "wildcard domains" format per for example superb github.com/hagezi/dns-blocklists?tab=readme-ov-file#pro and that's all.So OpenSnitch is working great (but you can not rearrange columns in tabs and automatically adjust / readjust columns widths. Check NetLimiter for Windows - it's very well done there. Also please add a few words to Preferences>Database options as I really did tried to understand but really don't know what some of these options do.)
RegExps logic processing works generally here as it works properly in [Rule>Network>To_this_host] (using full regexps notation) and also for regexps for example in [Rule>Network>Protocol] and [Rule>Network>To_this_port]. But they do not work when list is used as in [...>To_this_list_ofdomains(regular_expressions)]. All is ok with folder and. I saw in logs that OpenSnitch reports changes done in the file - how many new regexps were found. However, It does not use those regexps, neither full regexps (^(.
*\
.)?
example\
.com$) nor plain domains (example.com).???
opensnitchd -check-requirements
OK (for 39 but I think for my fresh 40 should be too).