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
Lines started with # are ignored. Write comments always on a new line, not after a domain.
This is good for compatibility, but cumbersome in practice:
All domains must be prefixed by 0.0.0.0. That results in a lot of noise in the file.
Comments can only be added on a standalone line. This makes sorting the file risky, because comments will be separated from their domains, unless you build a custom sort tool aware of this limitation.
Proposal
Allow end-of-line comments. # is not a valid domain character, so anything following \s*# can be safely ignored. This will keep comments attached to their domains:
d1fc6k0zwgx3pa.cloudfront.net # Instacart CDN
Make the 0.0.0.0 IP part optional. In other words, if a string is standalone on the line, accept it as a domain, up to \s*(#.*)?$
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
Uh oh!
There was an error while loading. Please reload this page.
https://github.com/evilsocket/opensnitch/wiki/block-lists states the allow/block lists must be in hosts format, and:
This is good for compatibility, but cumbersome in practice:
0.0.0.0. That results in a lot of noise in the file.Proposal
Allow end-of-line comments.
#is not a valid domain character, so anything following\s*#can be safely ignored. This will keep comments attached to their domains:Make the
0.0.0.0IP part optional. In other words, if a string is standalone on the line, accept it as a domain, up to\s*(#.*)?$All reactions