-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PV USB #531
Comments
Modified by marmarek on 17 Apr 2012 12:59 UTC |
Comment by marmarek on 3 Oct 2012 23:25 UTC |
Modified by joanna on 8 Oct 2012 09:31 UTC |
Comment by marmarek on 8 Nov 2012 03:00 UTC |
Comment by joanna on 8 Feb 2013 12:53 UTC |
Modified by joanna on 8 Feb 2013 13:03 UTC |
Modified by joanna on 1 Aug 2013 11:56 UTC |
Modified by joanna on 20 Apr 2014 17:07 UTC |
Modified by marmarek on 20 Apr 2014 17:25 UTC |
Generally there are multiple implementations possible here:
USBIP seems to be the easiest and the most mature implementation, available in mainline Linux. I have some work in progress scripts for setting it up ("the backend part"). Will push it somehow this week. Probably needs help on frontend part (updating cc @caschulz88 |
Hey, thanks for posting the possible implementation options here. For me also USBIP sounds the best way to go for an implementation. I'm looking forward to grab your code and work with it. Of course I'm also willing to support you and help on working on the backend and frontend part. Please let me know as soon as it's online somewhere. |
Here: https://github.com/QubesOS/qubes-app-linux-usb-proxy |
Mostly useful for tests in practice. QubesOS/qubes-issues#531
While having dom0 package anyway, it doesn't cost much. QubesOS/qubes-issues#531
1. wait=False isn't supportet together with localcmd (explicit, or implicit via 'input') - qrexec-client refuses such combination 2. When using localcmd, qrexec-client exists as soon as the local command terminates, not necessary remote. This may not be desired effect when used with wait=True (the default), so do not use localcmd in such a case Found while debugging tests for qubes.USBAttach/qubes.USBDetach - with wait=True broken, there were a lot of race conditions. Related to QubesOS/qubes-issues#531
Even if particular PV USB implementation doesn't support it, still have it included in QubesDB. It should be up to attaching code to decide. Also, don't fail if xen-usbback module doesn't exist. This isn't the only option (the other one is usbip over qrexec). QubesOS/qubes-issues#531
Those devices are most likely attached using "PV USB" from another domain, so it doesn't make sense to list them as available for further passthrough. QubesOS/qubes-issues#531
Make the API consistent. QubesOS/qubes-issues#531
Make sure that even compromised frontend will be cut of (possibly sensitive - like a webcam) device. On the other hand, if backend domain is already compromised, it may already compromise frontend domain too, so none of them would be better to call detach to. QubesOS/qubes-issues#531
1. wait=False isn't supportet together with localcmd (explicit, or implicit via 'input') - qrexec-client refuses such combination 2. When using localcmd, qrexec-client exists as soon as the local command terminates, not necessary remote. This may not be desired effect when used with wait=True (the default), so do not use localcmd in such a case Found while debugging tests for qubes.USBAttach/qubes.USBDetach - with wait=True broken, there were a lot of race conditions. Related to QubesOS/qubes-issues#531 (cherry picked from commit 046149e)
Reported by marmarek on 17 Apr 2012 12:59 UTC
PV USB with Linux 3.x works fine, but needs some work to integrate with Qubes:
2a. This includes some script in backend VM (in some/most cases not dom0) that bind USB device to usbback driver - /usr/lib/qubes/unbind_pci_device.sh equivalent.
Migrated-From: https://wiki.qubes-os.org/ticket/531
The text was updated successfully, but these errors were encountered: