search

USBGuard / usbguard

USBGuard is a software framework for implementing USB device authorization policies (what kind of USB devices are authorized) as well as method of use policies (how a USB device may interact with the system)
https://usbguard.github.io/
GNU General Public License v2.0
1.1k stars 133 forks source link

usb-c passthrough USB-HUB are 'forgotten' #617

Open commandline-be opened 2 months ago

commandline-be commented 2 months ago

Though use of 'gsettings set org.gnome.desktop.privacy usb-protection false' has some effect there is no permanent fix.

Set-up is a Monitor with USB-C and USB-A ports, there is a USB-A (3.1) hub connected to the monitor USB-A port, the usb-c port is connected to the computer. The monitor steering happens over USB-C, the USB-HUB(s) in the monitor are found on the computer.

Whenever the computer reboots are resumes from suspend or hibernate the USB HUBs must be permitted again, the connect-type is reported as 'unknown'

There is one allow-action required for the via-port (N-N.N) and one for the child via-port (N-N.N.n) There is no difference on the with-interface mentioned for these ports. So, though there's some variance in the hashes this setup seems mostly if not entirely stable.

In other words, it seems the connection are forgotten while they're now repeatedly found in the rules.conf file

Is this a known issue ?

edit: looking a bit deeper into this it seems a hub connected to a hub is prone to cause such issues and these seem reproducible. Connecting a hub to a hub happens with devices offering pass through, monitor, docking, keyboard with a pass-through etc.

bwildenhain commented 2 months ago

I can confirm forgotten devices connected via a USB-C screen (Dell P3223DE) (USB 3.2 internal Ethernet adapter and USB 2.1 Logitech C930e webcam), while other devices on the same screen work (no additional hub involved).