How the USB proxy works in Qubes https://github.com/QubesOS/qubes-app-linux-usb-proxy
I also found that while the docs point me to /etc/qubes-rpc/policy, the configs have moved to /etc/qubes/policy.d, which was incredibly confusing because there ARE still config files in the documented location. It's just that the main stash moved and it's pulling in the configs from the documented (deprecated) location.
I have not yet found anything that looks like it would be filtering specific traffic to the device, so I'm not sure where the issue lies with not being able to communicate with my hidraw device
Looks like it could be something the kernel is doing, either in sys-usb, or the qube that the device is being attached to.
I saw issue 3628 that was kernel bugs/incompatibilities related to USBIP.
That issue isn't what I'm facing, but I am seeing some weird stuff in the syslogs...
dmesg in qube show: unlink->seqnum and urb->status -104
In journalctl in sys-usb: unlinked by a call to usb_unlink_urb()
I see selinux is enabled in sys-usb, which adds another possible layer that might be messing around with things...
