How to get Ledger Nano S connected to VM

[li...@tutanota.com]

Qubes 4.0 default installation with USB keyboard and USB mouse
The device-manager-icon works with normal flash drives perfectly
___

Tried to follow
https://www.whonix.org/wiki/Ledger_Hardware_Wallet#Qubes_R4 <https://www.whonix.org/wiki/Ledger_Hardware_Wallet#Qubes_R4>
https://www.qubes-os.org/doc/usb-devices/ <https://www.qubes-os.org/doc/usb-devices/>

Ledger Nano S connected and unlocked
directly connected (without hub); tested on all USB ports)

Generated a new VM:
VM 'ledger-nano-s'
type: Standalone qube based on a template
based on Debian 9
___

# checking VM 'ledger-nano-s'

$ sudo apt-get install qubes-usb-proxy
Reading package lists... Done
Building dependency tree      
Reading state information... Done
qubes-usb-proxy is already the newest version (1.0.21+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# checking dom0:

$ qvm-usb
BACKEND: DVID DESCRIPTION    USED BY

# So, I do not see any USB; more precisely missing the line# sys-usb:2-1.4  Ledger_Nano_S_0001

$ lsusb

# show several connected USB devices like my keyboard, mouse and USB hub etc. but no Nano.

___

How do I uncover the Nano S in Qubes?

[pr...@tuta.io]

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA512

> How do I uncover the Nano S in Qubes?

Hi,

after unlocking the ledger it shows up in qvm-usb for me.

I think this may be something to do with the way you have

the USBs configured, so it's not specifically a ledger

problem.

-----BEGIN PGP SIGNATURE-----

iIgEARMKADAWIQRFNnsoPo7HH0XEMXc88cBGMbAIWAUCXSPV0RIccHJhZ29AdHV0

YW5vdGEuZGUACgkQPPHARjGwCFgTlAEA+fn1CsG5GDEl18QwEEU1FbJT5Mxzhb85

q1CU2zKQmYwA/3pMkr70piOWOlxRH5OzxGppVgy5Cir9pCYeY8cwjI/s

=VxgA

-----END PGP SIGNATURE-----

[Dave C]

I find that with Fedora 30, it is necessary to add the following to /rw/config/rc.local (and then restart VM):

# http://support.ledgerwallet.com/knowledge_base/topics/ledger-wallet-is-not-recognized-on-linux
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2581\", ATTRS{idProduct}==\"1b7c\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2581\", ATTRS{idProduct}==\"2b7c\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2581\", ATTRS{idProduct}==\"3b7c\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2581\", ATTRS{idProduct}==\"4b7c\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2581\", ATTRS{idProduct}==\"1807\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2581\", ATTRS{idProduct}==\"1808\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2c97\", ATTRS{idProduct}==\"0000\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
echo "SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"2c97\", ATTRS{idProduct}==\"0001\", MODE=\"0660\", OWNER=\"user\", GROUP=\"plugdev\"" >>/etc/udev/rules.d/20-hw1.rules
udevadm trigger
udevadm control --reload-rules

[Rafael Reis]

You probably did an installation without sys-usb. The installer defaults to not create sys-usb if during installation you have a USB keyboard attached. If that is the case, I find that following https://www.qubes-os.org/doc/usb-qubes/ and Auto Enabling Keyboard and Mouse input is a good solution. I ran into the exact same situation, and did that myself a couple of days ago.

After this change, all your USB devices will show at the Qubes Devices applet the same way block devices does, and you'll be able to pass them through to any vm.

Rafael