mirror of
https://github.com/evilsocket/opensnitch.git
synced 2025-03-04 16:44:46 +01:00
21c6a914d6
Prior to v1.4.x versions, when a pop-up asked the user to allow or deny
a connection, the rest of the network traffic was dropped until an
action was taken.
We fixed it, but when a pop-up was asking to allow or deny a new connection,
we let it passing by if the daemon's DefaultAction option was set to
allow, even if the user hadn't taken an action on it yet.
It also caused some confusion if the users had configured the pop-up's
DefaultAction to deny, they were expecting to not allow the connection
until they had decided what to do.
Now the previous behaviour has been restored, having these usage
scenarios:
- If the GUI is connected + daemon DefaultAction set to allow or deny.
Result:
1. Prompt the user to allow or deny the new connection.
2. Deny the new connection until the user takes an action on it.
3. Allow the rest of traffic, allowing known connections, and
denying new ones until the active pop-up is closed and we can
prompt the user again.
- GUI disconnected.
Result:
1. Apply daemon's DefaultAction from the configuration file
default-config.json.
closes: #392
|
||
|---|---|---|
| .. | ||
| conman | ||
| core | ||
| dns | ||
| firewall | ||
| log | ||
| netfilter | ||
| netlink | ||
| netstat | ||
| procmon | ||
| rule | ||
| statistics | ||
| ui | ||
| .gitignore | ||
| default-config.json | ||
| go.mod | ||
| Gopkg.toml | ||
| main.go | ||
| Makefile | ||
| opensnitch.spec | ||
| opensnitchd.service | ||
| system-fw.json | ||