-
-
Notifications
You must be signed in to change notification settings - Fork 558
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
thread 'thread_write_report' panic when run not as root. additionally, it'd be nice to save report file in a fixed location independently from running directory. #51
Comments
If you previously run as root and then you try to run as normal user, it will panic because it tries to overwrite the previously generated report without success: in fact the previously generated report has admin privileges and cannot be overwritten by a normal user. Delete the report file previously generated and you should be fine. Let me know if it helps. |
Oh, makes sense. That's why it suddenly started working after changing current directory in the terminal. Maybe |
Has it something to do with admin privileges? What benefit would this change introduce? Or, are you just asserting that it's not a good standard to generate the report in the current directory? |
At least the subject of this issue will become irrelevant. The current behaviour is surprising (not in a good way). Even if I always run
I certainly think that. Traditional place for things like that is |
Thanks for pointing out, I will implement this change in the next release! |
Textual report is now saved in a fixed directory, instead of using the directory where the execution was started. The output is now saved in the same folder containing configuration files storing Sniffnet settings. |
Describe the bug
When run not as root, sniffnet panics even with the capabilities set:
Runs just fine under
kdesu
.To Reproduce
Desktop:
Manjaro Linux 22.0.0
The text was updated successfully, but these errors were encountered: