Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

default_action": "deny" doesn't apply #14

Closed
emrekanca opened this issue Apr 19, 2020 · 3 comments
Closed

default_action": "deny" doesn't apply #14

emrekanca opened this issue Apr 19, 2020 · 3 comments

Comments

@emrekanca
Copy link

Hi,

I change this file as below "/etc/opensnitchd/default-config.json"

{
"default_action": "deny",
"default_duration": "once",
"intercept_unknown": true
}

default_action deny doesn't apply.
When a new app connection is claimed it still shows allow connect option as default
https://i.paste.pics/ca4a268f618da59728dfe3cffe9f927f.png

Ubuntu 20.04
opensnitch v1.0.0rc7

How can I get default option as deny.

@Ph0rk0z
Copy link

Ph0rk0z commented Apr 19, 2020

There is .config/opensnitch in your home folder. This is for the daemon.

@gustavo-iniguez-goya
Copy link
Owner

Yes, @Ph0rk0z is right. There're 2 configuration files (in v1.0.0rc7):

  • daemon: /etc/opensnitchd/default-config.json
  • UI: ~/.config/opensnitch/settings.conf

The daemon configuration applies for example when the UI is not running, or in case of communication failure with the UI.

The UI configuration applies only to the options displayed in the UI. You can change this configuration and set it to the default options you desire.

I'm finishing the option to handle both configurations from the UI, including remote daemos and the local daemon. Hopefully it'll help to ease configuring both cases.

@emrekanca
Copy link
Author

It helped, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants