You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So hosts format lists based blocking works without any problem. However, no one clever uses hosts format lists anymore as this format is rather stupid & very outdated, 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 has >10MB and it works super-fast without any problem at all. I can shut down for example 50% of Microsoft tracking 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 OpenSnitch works great (but it is stupid you can not move / rearrange columns in views and also 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.)
So regexps logic processing works in general as it works properly in [Rule>Network>To_this_host] (using full regexps notation) and also for - regexps in general, not for domains processing - [Rule>Network>Protocol] and [Rule>Network>To_this_port].
But it does not work when list is used as in [...>To_this_list_of_domains_(regular_expressions)]. All is ok with folder and file.txt. I saw in logs that OpenSnitch reports changes in the file - how many new regexps 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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, thank you (all) for your (their) great work.
Hi, thank you for your great work.
So hosts format lists based blocking works without any problem. However, no one clever uses hosts format lists anymore as this format is rather stupid & very outdated, 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 has >10MB and it works super-fast without any problem at all. I can shut down for example 50% of Microsoft tracking 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 OpenSnitch works great (but it is stupid you can not move / rearrange columns in views and also 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.)
So regexps logic processing works in general as it works properly in [Rule>Network>To_this_host] (using full regexps notation) and also for - regexps in general, not for domains processing - [Rule>Network>Protocol] and [Rule>Network>To_this_port].
But it does not work when list is used as in [...>To_this_list_of_domains_(regular_expressions)]. All is ok with folder and file.txt. I saw in logs that OpenSnitch reports changes in the file - how many new regexps 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).Beta Was this translation helpful? Give feedback.
All reactions