Radovan Sroka
Radovan Sroka
The behavior is expected. We will need to implement a new operator like "match-all" that will try to match each device interface against provided mask. ``` allow with-interface match-all {...
Hello, I think that your ruleset works as expected. Rule number 1 matched your first mass storage once and then you inserted the second mass storage, rule was evaluated as...
> I actually meant to mention my repo, just that I forgot to do that. > As @munix9 noticed, I created https://github.com/pinotree/usbguard-applet-qt, which provides the applet combining all the git...
> I just tried the CLI and it doesn't work: > > > usbguard allow-device 059f:1027 > > IPC ERROR: request id=1: Device lookup: device id: id doesn't exist >...
I can see a benefit of ```keep``` option in respecting device in ```blocked``` state. > This is the context around this question: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928032. > > Generally, to achieve this behaviour,...
Hello, I've no experience with writing, building or deploying of the USBGuard... I believe that it is possible.
Have you tried to use rule/policy without hashes?
Why do you need the dbus so bad? If you don't want polkit on your system you can just stay with usbguard CLI and IPC perms.
Yeah, PRs are welcomed :)
IIRC generate-policy -X does something like that. We need to introduce similar flags for the command or invent some filter mechanism without changing the default behavior.