On 03/30/2017 07:01 AM, daltong defourne wrote:
Hello!
I have been using a debian-based USB-VM qube for quite some time (have
to use debian, but TBH fedora is not much better), and am getting large
amount of annoying "USB device stuck/fails to detach/etc etc" problems.
The issue is well-known (I've submitted a lot of logs to the relevant
issue on github) but, well, I need to do something to improve my
experience asap as I am likely to have a lot of USB flashdrives in my
workflow pretty soon. Like, tens of attach/detach per day.
Is there enough difference between
qvm-block -a <recepient vm> <USB-VM>:sd(x)
and
qvm-usb -a <recepient vm> <USB-VM>:x-y
to bother with trying to use the latter instead of the former ?
Are there any additional security implications of qvm-usb that would not
be present with qvm-block?
qvm-block is a fully supported feature of Qubes, and its a more secure
way to use a block device. qvm-usb can expose your VMs to (more types
of) attacks by malicious devices---its risky.
OTOH, if the USB drives contain secure encrypted disk images (like .img
files using LUKS) then attaching the image files via qvm-block -A is
pretty safe.
--
Chris Laprise, [email protected]
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/73b60db8-32a4-ab44-91d8-b6d459eacdb5%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.
