More clarity needed for allow/deny once/all #5
Comments
|
yeah i need to implement a better rule handling/policy |
Merged
gustavo-iniguez-goya
added a commit
that referenced
this issue
Dec 9, 2020
We parse .desktop files to get the icon of a program, but sometimes we can't parse the Name translation due to unicode encoding problems. Besides, on some distributions there're .desktop files without Exec= line, so we also crash. With this workaround we miss (mainly) the icon of a program, but at least we won't crash. It should help with #5.
gustavo-iniguez-goya
added a commit
that referenced
this issue
Dec 9, 2020
When a new connection is about to be established and the system performs a dns resolution, we displayed it like this: 9.9.9.9 (www.opensnitch.io) It added visibility of what was going on, but if you created a rule to filter by destination host, you were prompted twice to allow firstly the DNS query, and secondly the TCP connection, which was a bit annoying. Some users (#5) also asked to display just the domain, so now we only display the domain name.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Experimentally it seems to mean "$ACTION just this connection" or "... every connection" from this process. There could be some middle ground, eg. always allowing port 53 to my expected DNS resolvers while still requiring intervention for other connections.
The text was updated successfully, but these errors were encountered: