-
Notifications
You must be signed in to change notification settings - Fork 140
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
Usbguard applet #334
Comments
FTR: There is https://github.com/6E006B/usbguard-gnome And GNOME will most likely have a built-in frontend in the next release (3.36). |
Thanks muelli, I'm aware of that applet, but unfortunately I'm not using GNOME as my WM:( |
You don't have to in order to use https://github.com/6E006B/usbguard-gnome |
Hi guys, check this out! https://github.com/Cropi/usbguard-notifier |
The Qt applet will be maintained in a separate repository (again).
As @dkopecek mentioned in his commit, it should be in a separate repo. Maybe he can give us some information? |
It would have been much better to leave the Qt applet as is, until other solutions are available in all distributions. Right now and for it's probable main purpose (desktop systems), usbguard seems pretty limited by this. |
Indeed -- Daniel, can you please upload the repository with the Qt applet? In case it is needed, I can help to create it from the usbguard.git repository. |
My quick and dirty script as an easy to use "gui" https://gist.github.com/kisst/3932f2cc30281915f8ec5be7deed98b3 |
Anything new on this? |
Based on the work of @pinotree (https://github.com/pinotree/usbguard-applet-qt - thanks!) and my own changes, I have created packages for openSUSE Tumbleweed (https://build.opensuse.org/package/show/home:munix9/usbguard-applet-qt). |
I actually meant to mention my repo, just that I forgot to do that.
I need to write a proper README for it... |
Thanks for your initiative. I believe we are close to 1.0.0 release and stable API. |
Oh, and of course it is fine for me if you want to take the applet back within the usbguard project. However, judging from the past happenings, I'd think that this is not wanted. To be clear, I have no problem either way. |
Thanks for your initiative! @munix9 wrote
I wouldn't do that as it provides no additional security. If your GUI application can access the DBus service, so can any other application written to use DBus. Everyone who can run processes with your permission can do that. |
I just tried the CLI and it doesn't work:
I just dont want to waste time with this. It's a shame the applet has been removed. So I'm uninstalling usbguard. |
okay. There are a few alternatives that you might consider exploring, e.g. usbauth. For the future, I'd be helpful to stick on-topic and avoid inflammatory language to keep everybody focussed on the issue at hand. Thanks. |
The applet is now in different location: https://github.com/pinotree/usbguard-applet-qt it is not part of the usbguard anymore... When you want to allow a device you need an id. You can get it by listing devices.
|
@muelli don't give up, you still have easy options like #334 (comment) or the external qt libs. |
Arh. Sorry about the ID. It wasn't very clear in the documentation. |
Hi guys, anything new on this? I am using command line commands, this is not a problem for me. But for many users it is. And i believe those users also need protection and security, i. e. this application is intended to them. It would be great if there was some good GUI for them. |
Please bring back the Qt applet - it was much easier and more user-friendly to quickly allow/block the device than using the CLI.
Or at least make it a separate project that can be used as a GUI for usbguard.
Thanks in advance!
The text was updated successfully, but these errors were encountered: