evilsocket / evilsocket/opensnitch
[Feature Request] Debug existing rules
- Dominant language
- Python
- Stars
- 14.1k
- Forks
- 665
- PR merge metrics
- No merged PRs in 30d
Description
### Summary:
When prompted about a new connection it'd be nice to be able to understand why a certain rule didn't apply to the connection.
### Use case
- I start a new application and shortly add a new rule for it.
- Later, I get a new prompt for a new connection from the same App
- However, I think that it should be captured by the existing rule.
#### Today
- I just write a new rule, and then try to do a side-by-side diff to understand how my first rule missed this case, and then fix the first and only rule.
#### With debugging UI
- I select which rule should've covered this case.
- The UI shows my what rule matchers passed and which ones failed so I can better understand why the rule didn't work.
- I notice an error and fix the existing rule by relaxing constraints around all the missed rule matchers.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.