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

[Feature request] Make connection approvals/refusals more granular #463

Open
SonephetR2 opened this issue Jul 26, 2021 · 2 comments
Open

Comments

@SonephetR2
Copy link

I'd love to see another option (or more!) somewhere between greenlighting a connection "Until next reboot" and "Forever". How about approving/refusing a connection for a week, a month, a year… This creates quite a lot of friction with legitimate programs that include updaters. I don't particularly want these programs to switch off the updater forever, so I'm stuck with denying the connection day after day. Thanks :)

@gustavo-iniguez-goya
Copy link
Collaborator

hi @SonephetR2 ,

Yes, I think that we can add more options, even time ranges, which I think would be more useful for the use case you described.

So, what options would be nice to have?

  • Options between 1h and "until restart": 12h, 1 day, 1 week, ... ?
  • Time ranges/: every day from 20:00pm to 20:30pm, every monday/month, etc..

Please, comment below if this is interesting/wanted, or vote 👍 👎 , in order to have an idea.

@SonephetR2
Copy link
Author

Hi @gustavo-iniguez-goya and thanks a lot for taking this into account!

I would prefer options personally, and way longer than 1 week. How often would I want Opensnitch to let me review whether I'll finally let my PDF viewer ping back "home"? ... Once every 3 or 6 months perhaps?

To be honest, as a mere individual user, I actually cannot really think up any useful situation where I'd need a time range rather than an option.

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

2 participants