mirror of
https://github.com/evilsocket/opensnitch.git
synced 2025-03-04 08:34:40 +01:00
Update README.md
This commit is contained in:
parent
41a320efac
commit
721e356ad6
1 changed files with 6 additions and 0 deletions
|
@ -30,3 +30,9 @@ I tried, but for very fast updates it failed bad on my configuration (failed bad
|
||||||
The UI service is able to use a TCP listener instead of a UNIX socket, that means the UI service itself can be executed on any
|
The UI service is able to use a TCP listener instead of a UNIX socket, that means the UI service itself can be executed on any
|
||||||
operating system, while receiving messages from a single local daemon instance or multiple instances from remote computers in the network,
|
operating system, while receiving messages from a single local daemon instance or multiple instances from remote computers in the network,
|
||||||
therefore DBUS would have made the protocol and logic uselessly GNU/Linux specific.
|
therefore DBUS would have made the protocol and logic uselessly GNU/Linux specific.
|
||||||
|
|
||||||
|
##### OpenSnitch displays too many dialogs to allow/deny connections
|
||||||
|
|
||||||
|
Yes, it does. But only the first time it's been used. Once you configure which processes/connections you want to allow/deny, you won't notice that it's running.
|
||||||
|
|
||||||
|
In the future, maybe we add an option to queue the events, and from the GUI allow/deny them.
|
||||||
|
|
Loading…
Add table
Reference in a new issue