USBGuard enhancement and bugfix update:
sudo dnf upgrade --refresh --advisory=FEDORA-2019-d4c4bf697a
Please login to add feedback.
0 | 2 | Test Case usbguard CLI devices |
0 | 2 | Test Case usbguard CLI rules |
-1 | 2 | Test Case usbguard GUI |
0 | 2 | Test Case usbguard setup |
This update has been submitted for testing by rsroka.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
rsroka edited this update.
rsroka edited this update.
rsroka edited this update.
rsroka edited this update.
rsroka edited this update.
This update has been pushed to testing.
The update is not installable:
You should add
Obsoletes: usbguard-applet-qt < 0.7.6-4
to the spec file.Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
rsroka edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by rsroka.
I have provided a new build. The update should work.
This update has been pushed to testing.
selinux prevents this package from running: SELinux is preventing (d-daemon) from mounton access on the directory /run/systemd/unit-root/etc/usbguard
This update can be pushed to stable now if the maintainer wishes
rsroka edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by rsroka.
SELinux issues appear to be resolved.
This update has been pushed to testing.
Causes usbguard to fail to detect any usb path on 2 of my computers. If I use(d) a USB mouse and keyboard, this update completely locks me out of my computer forever (external changes from another linux system required).
GUI is missing, so "Test Case usbguard GUI" cannot work.
For my previous comment, see https://github.com/USBGuard/usbguard/issues/279.
This update's test gating status has been changed to 'greenwave_failed'.
This update's test gating status has been changed to 'ignored'.
This update can be pushed to stable now if the maintainer wishes
GUI is obsolete, I should remove it from the test cases.
Is your problem caused really because of unresolved realpath for /sys ? Does regen of your rules.conf help? There are a few new attributes in rules language and that can affect how the computed hash looks like. If you are not using any hash or parent hash in your rules.conf you should be safe but you should try to regen your rules anyway.
The basic features s.a. allowing devices, blocking devices and listing devices work for me.
This update's test gating status has been changed to 'greenwave_failed'.
This update's test gating status has been changed to 'ignored'.
Features like list-devices,reject devices work great and also allowing and blocking devices work well.
This update has been submitted for stable by rsroka.
This update has been pushed to stable.