-
-
Notifications
You must be signed in to change notification settings - Fork 492
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] UI improvements #1073
Comments
Up until now, the GUI was refreshed if: - it was not minimized or hidden. - if there were new events (even if we received events from the daemon, they were filtered out if they were duplicated). But still, there were scenarios where refreshing the views every second (more or less) was too much, like when monitoring multiple machines. Now it's possible to configure the views' refresh interval, regardless of what the daemon sends. Asked here: #1073
Up until now, the GUI was refreshed if: - it was not minimized or hidden. - if there were new events (even if we received events from the daemon, they were filtered out if they were duplicated). But still, there were scenarios where refreshing the views every second (more or less) was too much, like when monitoring multiple machines. Now it's possible to configure the views' refresh interval, regardless of what the daemon sends. Asked here: #1073 (cherry picked from commit 6006717)
if devs want a separate issue opened for this, let me know rules tab: for the rules tab, the order by alpha can be a bit of a hassle - imagine several rules, starting with [000], then you want add another in 1st place, so you have to rename all the existing rules what i think would be better is a drag 'n drop list, or buttons to move the selected rule(s) up/down maybe this could also alleviate the need for the "priority rule" setting which i think might create some confusion? i'm also wondering if it's necessary to be able to sort the rules by the column headers - i suppose it depends on how many rules one has, but my thinking here is that the order in which they're processed could be misunderstood if they happen to not be sorted by priority/name rule creation: also i'd personally like to see some/all rule criteria stored when a new rule is created (exe, command and network info primarily) - this would make it a lot easier/quicker to switch or add criteria for a rule, such as creating a rule based on the exe, then later adding the command to it, or IP, etc. |
Hello, I've just tested on a fresh Ubuntu 22.04 installation. I won't comment on the installation hurdles (manual deb installation, gui not working at first - found the fix on github issues), but on this enhancement list I would like to add one important thing I would consider :
When going in "monitor" mode, after rules piled up, having to recreate them one by one to make permanent can be a hassle, also export them to reimport afterwards in config is not ideal, when it could be streamlined with very few mouse clicks :) |
hi @seboss666 , what version are you using? if you right click on a rule(s), you can change many options of the rules, like making it permanent: |
Hello, I've tested the 1.6.5. I cannot check the virtual machine I tested the software on (holidays FTW), if it was there it was not obvious, so i'm glad if we technically can do that (I was seeking a "make it permanent" instead of "Duration: always"). |
Hello. very useful program I use every day
If you have time I made a list of UI improvements I would like to see added
General:
Option to Update the UI every * seconds (sometimes it is slow to update)
Change Timezone/format
Log all Events to file + log events on system start and when UI is not running
Events tab:
Origin IP/Network/host
Network interface
Allowed/blocked hits
Hosts tab:
How many hits allowed/rejected
Time of last hit
Addresses tab:
How many hits allowed/rejected
Time of last hit
Resolve IP to DNS hostname (button)
Rules tab:
Short rule name (allow-15m-simple-)
Group by rejected, allow
Hide rules or better layout when there are LOTS of rules (too much scrolling)
Time rule was last used
The text was updated successfully, but these errors were encountered: