Oh! I forgot to mention the point of this 9.5 hour debugging session! The device never gets the startup message from the client. This implies:

Qubes 4.2 filters writes to rawhid devices

Qubes 4.1 and earlier did not do this

I have more research to do in order to track down exactly how Qubes is accomplishing this. It doesn't look like it is usbguard (which seems to be running in dom0).

I don't see anything in the release notes about this.

https://www.qubes-os.org/doc/releases/4.2/release-notes/

Next stop: how does qubes accomplish making devices available from one qube to another? 🚂

nostr:nevent1qqst7gq0hzydw5sufr54q3qqykkhw68gez382kg3w6gskcexq5jky5spz9mhxue69uhkummnw3e82efwvdhk6q3q6v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gsxpqqqqqqzneeprl

Reply to this note

Please Login to reply.

Discussion

No replies yet.