/qubes-issues

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

Can't attach Yubikey 4 or webcam to any qube after QSB#38 updates #3612

Open
n1m1 opened this Issue Feb 20, 2018 · 44 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 4.0 updates
7 participants
@n1m1 @andrewdavidwong @na-- @rustybird @marmarek @ThierryIT @protoEvangelion
@n1m1

n1m1 commented Feb 20, 2018 •
edited
Edited 3 times
  • @n1m1 n1m1 edited Feb 20, 2018 (most recent)
  • @n1m1 n1m1 edited Feb 20, 2018
  • @n1m1 n1m1 edited Feb 20, 2018

Qubes OS version:

4.0 rc4

Affected TemplateVMs:

dom0
debian-9 (work-gpg and voip VMs)
fedor-26-minimal (sys-usb)

Steps to reproduce the behavior:

  1. I plug in a Yubikey 4 in sys-usb.
  2. I try to attach it to work-gpg. In dom0 I type

qvm-usb attach work-gpg sys-usb:2-1

Or

  1. I try to attach the webcam to a VM

qvm-usb attach voip sys-usb:2-8

Expected behavior:

Yubikey is attached to work-gpg and can be used in order to decrypt emails.

Webcam is attached to the voip vm and can be regularly used.

Actual behavior:

Can't attach Yubikey to work-gpg

In dom0 I get this output:

"Device attach failed: No device info received, connection failed, check backend side for details"

In work-gpg I get this output

Feb 20 15:13:42 localhost qrexec-agent[444]: executed root:QUBESRPC qubes.USBAttach dom0 pid 986
Feb 20 15:13:42 localhost systemd[1]: Created slice User Slice of root.
Feb 20 15:13:42 localhost systemd[1]: Starting User Manager for UID 0...
Feb 20 15:13:42 localhost systemd[1]: Started Session c9 of user root.
Feb 20 15:13:42 localhost systemd[987]: Starting D-Bus User Message Bus Socket.
Feb 20 15:13:42 localhost systemd[987]: Listening on GnuPG network certificate management daemon.
Feb 20 15:13:42 localhost systemd[987]: Reached target Timers.
Feb 20 15:13:42 localhost systemd[987]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 20 15:13:42 localhost systemd[987]: Reached target Paths.
Feb 20 15:13:42 localhost systemd[987]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 20 15:13:42 localhost systemd[987]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 20 15:13:42 localhost systemd[987]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 20 15:13:42 localhost systemd[987]: Listening on D-Bus User Message Bus Socket.
Feb 20 15:13:42 localhost systemd[987]: Reached target Sockets.
Feb 20 15:13:42 localhost systemd[987]: Reached target Basic System.
Feb 20 15:13:42 localhost systemd[987]: Reached target Default.
Feb 20 15:13:42 localhost systemd[987]: Startup finished in 16ms.
Feb 20 15:13:42 localhost systemd[1]: Started User Manager for UID 0.
Feb 20 15:13:42 localhost qubes.USBAttach-dom0: No device info received, connection failed, check backend side for details
Feb 20 15:13:42 localhost qrexec-agent[444]: send exit code 1
Feb 20 15:13:42 localhost qrexec-agent[444]: pid 986 exited with 1
Feb 20 15:13:42 localhost qrexec-agent[444]: eintr
Feb 20 15:13:42 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 20 15:13:42 localhost systemd[987]: Stopped target Default.
Feb 20 15:13:42 localhost systemd[987]: Stopped target Basic System.
Feb 20 15:13:42 localhost systemd[987]: Stopped target Timers.
Feb 20 15:13:42 localhost systemd[987]: Stopped target Paths.
Feb 20 15:13:42 localhost systemd[987]: Stopped target Sockets.
Feb 20 15:13:42 localhost systemd[987]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Feb 20 15:13:42 localhost systemd[987]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 20 15:13:42 localhost systemd[987]: Closed GnuPG network certificate management daemon.
Feb 20 15:13:42 localhost systemd[987]: Closed D-Bus User Message Bus Socket.
Feb 20 15:13:42 localhost systemd[987]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 20 15:13:42 localhost systemd[987]: Closed GnuPG cryptographic agent (access for web browsers).
Feb 20 15:13:42 localhost systemd[987]: Reached target Shutdown.
Feb 20 15:13:42 localhost systemd[987]: Starting Exit the Session...
Feb 20 15:13:42 localhost systemd[987]: Received SIGRTMIN+24 from PID 1004 (kill).
Feb 20 15:13:42 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 20 15:13:42 localhost systemd[1]: Removed slice User Slice of root.

Can't attach the webcam to a VM

In dom0 I get this error:

"Device attach failed: No device info received, connection failed, check backend side for details"

And in the voip VM I get this error:

Feb 20 19:40:49 localhost qrexec-agent[505]: executed root:QUBESRPC qubes.USBAttach dom0 pid 1890
Feb 20 19:40:49 localhost systemd[1]: Created slice User Slice of root.
Feb 20 19:40:49 localhost systemd[1]: Starting User Manager for UID 0...
Feb 20 19:40:49 localhost systemd[1]: Started Session c9 of user root.
Feb 20 19:40:49 localhost systemd[1891]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 20 19:40:49 localhost systemd[1891]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 20 19:40:49 localhost systemd[1891]: Listening on GnuPG network certificate management daemon.
Feb 20 19:40:49 localhost systemd[1891]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 20 19:40:49 localhost systemd[1891]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 20 19:40:49 localhost systemd[1891]: Starting D-Bus User Message Bus Socket.
Feb 20 19:40:49 localhost systemd[1891]: Reached target Paths.
Feb 20 19:40:49 localhost systemd[1891]: Reached target Timers.
Feb 20 19:40:49 localhost systemd[1891]: Listening on D-Bus User Message Bus Socket.
Feb 20 19:40:49 localhost systemd[1891]: Reached target Sockets.
Feb 20 19:40:49 localhost systemd[1891]: Reached target Basic System.
Feb 20 19:40:49 localhost systemd[1891]: Reached target Default.
Feb 20 19:40:49 localhost systemd[1]: Started User Manager for UID 0.
Feb 20 19:40:49 localhost systemd[1891]: Startup finished in 19ms.
Feb 20 19:40:49 localhost qubes.USBAttach-dom0: No device info received, connection failed, check backend side for details
Feb 20 19:40:49 localhost qrexec-agent[505]: send exit code 1
Feb 20 19:40:49 localhost qrexec-agent[505]: pid 1890 exited with 1
Feb 20 19:40:49 localhost qrexec-agent[505]: eintr
Feb 20 19:40:49 localhost systemd[1891]: Stopped target Default.
Feb 20 19:40:49 localhost systemd[1891]: Stopped target Basic System.
Feb 20 19:40:49 localhost systemd[1891]: Stopped target Timers.
Feb 20 19:40:49 localhost systemd[1891]: Stopped target Sockets.
Feb 20 19:40:49 localhost systemd[1891]: Closed D-Bus User Message Bus Socket.
Feb 20 19:40:49 localhost systemd[1891]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 20 19:40:49 localhost systemd[1891]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Feb 20 19:40:49 localhost systemd[1891]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 20 19:40:49 localhost systemd[1891]: Stopped target Paths.
Feb 20 19:40:49 localhost systemd[1891]: Closed GnuPG cryptographic agent (access for web browsers).
Feb 20 19:40:49 localhost systemd[1891]: Closed GnuPG network certificate management daemon.
Feb 20 19:40:49 localhost systemd[1891]: Reached target Shutdown.
Feb 20 19:40:49 localhost systemd[1891]: Starting Exit the Session...
Feb 20 19:40:49 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 20 19:40:49 localhost systemd[1891]: Received SIGRTMIN+24 from PID 1908 (kill).
Feb 20 19:40:49 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 20 19:40:49 localhost systemd[1]: Removed slice User Slice of root.

General notes:

  • It has been possible to passthrough Yubikey to work-gpg, or use the webcam, untill the QSB#38 updates.

  • It is still possible to attach USB mass storage devices to work-gpg and other qubes.

  • Testing and security-testing repositories are enabled.

Related issues:

@n1m1 n1m1 changed the title from Can't attach Yubikey 4 to work-gpg to Can't attach Yubikey 4 or webcam to any qube Feb 20, 2018

@n1m1 n1m1 changed the title from Can't attach Yubikey 4 or webcam to any qube to Can't attach Yubikey 4 or webcam to any qube after QSB#38 updates Feb 20, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 21, 2018

Member

Duplicate of #3524
Member

andrewdavidwong commented Feb 21, 2018

Duplicate of #3524

@andrewdavidwong andrewdavidwong marked this as a duplicate of #3524 Feb 21, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 21, 2018

Member

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.
Member

andrewdavidwong commented Feb 21, 2018

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

@andrewdavidwong andrewdavidwong closed this Feb 21, 2018

@andrewdavidwong andrewdavidwong added the duplicate label Feb 21, 2018

@n1m1

This comment has been minimized.

Show comment
Hide comment
@n1m1

n1m1 Feb 21, 2018

Thanks for your answer and for taking care of this. Just one note: I might be wrong, but I am not sure that this issue is a duplicate of #3524 (even though it might be related). In my case, the problem turned up only after QSB 38 updates: before, either the webcam and my Yubikey were perfectly working and it was possible to attach them to VMs. Thanks.

n1m1 commented Feb 21, 2018

Thanks for your answer and for taking care of this. Just one note: I might be wrong, but I am not sure that this issue is a duplicate of #3524 (even though it might be related). In my case, the problem turned up only after QSB 38 updates: before, either the webcam and my Yubikey were perfectly working and it was possible to attach them to VMs. Thanks.
@na--

This comment has been minimized.

Show comment
Hide comment
@na--

na-- Feb 21, 2018

I'm not sure that this is a duplicate as well. Yesterday evening I could attach a USB device to a VM without problems, this morning I updated dom0 and the templates with security-testing enabled to mitigate QSB 38 and right now I can't attach that same USB device that worked yesterday. I think that nothing else has been installed or changed in the configuration.

My error is a bit different though, qvm-device usb a vm-name sys-usb:<device> produces only Device attach failed:. That's it, no error message after. journalctl output in dom0 contains only qubes.USB+1-3: vm-name -> sys-usb: allowed to sys-usb.

Edit: journalctl in sys-usb has the error /usr/lib/qubes/usb-export: line 82: modprobe: command not found, so that seems promising. I'll investigate later and post if I can fix it.

na-- commented Feb 21, 2018 •
edited
Edited 2 times
  • @na-- na-- edited Feb 21, 2018 (most recent)
  • @na-- na-- edited Feb 21, 2018

I'm not sure that this is a duplicate as well. Yesterday evening I could attach a USB device to a VM without problems, this morning I updated dom0 and the templates with security-testing enabled to mitigate QSB 38 and right now I can't attach that same USB device that worked yesterday. I think that nothing else has been installed or changed in the configuration.

My error is a bit different though, qvm-device usb a vm-name sys-usb:<device> produces only Device attach failed:. That's it, no error message after. journalctl output in dom0 contains only qubes.USB+1-3: vm-name -> sys-usb: allowed to sys-usb.

Edit: journalctl in sys-usb has the error /usr/lib/qubes/usb-export: line 82: modprobe: command not found, so that seems promising. I'll investigate later and post if I can fix it.
@rustybird

This comment has been minimized.

Show comment
Hide comment
@rustybird

rustybird Feb 21, 2018

Edit: journalctl in sys-usb has the error /usr/lib/qubes/usb-export: line 82: modprobe: command not found, so that seems promising.

Sounds like a duplicate of a different issue: #3615 (comment)

rustybird commented Feb 21, 2018

Edit: journalctl in sys-usb has the error /usr/lib/qubes/usb-export: line 82: modprobe: command not found, so that seems promising.

Sounds like a duplicate of a different issue: #3615 (comment)
@na--

This comment has been minimized.

Show comment
Hide comment
@na--

na-- Feb 21, 2018

Yeah, seems like it could be. Anyway, I edited /usr/lib/qubes/usb-export manually to use the full path of modprobe and the qvm-device usb a vm-name sys-usb:<device> issue didn't change. I don't have time to properly debug right now, will try later today.

na-- commented Feb 21, 2018 •
edited
Edited 1 time
  • @na-- na-- edited Feb 21, 2018 (most recent)

Yeah, seems like it could be. Anyway, I edited /usr/lib/qubes/usb-export manually to use the full path of modprobe and the qvm-device usb a vm-name sys-usb:<device> issue didn't change. I don't have time to properly debug right now, will try later today.
@na--

This comment has been minimized.

Show comment
Hide comment
@na--

na-- Feb 21, 2018

I think this whole issue is caused by the root cause of #3615 ... I added export PATH="/sbin:/usr/sbin:/usr/local/sbin:${PATH:-/bin:/usr/bin:/usr/local/bin}" in the beginning of /usr/lib/qubes/usb-export in sys-usb (copied from @rustybird's temporary fixes of split-dm-crypt) and that solved the issue, USB devices can now be attached without problems.

I assume that some of the commits from here or here are responsible, maybe this.

na-- commented Feb 21, 2018 •
edited
Edited 2 times
  • @na-- na-- edited Feb 21, 2018 (most recent)
  • @na-- na-- edited Feb 21, 2018

I think this whole issue is caused by the root cause of #3615 ... I added export PATH="/sbin:/usr/sbin:/usr/local/sbin:${PATH:-/bin:/usr/bin:/usr/local/bin}" in the beginning of /usr/lib/qubes/usb-export in sys-usb (copied from @rustybird's temporary fixes of split-dm-crypt) and that solved the issue, USB devices can now be attached without problems.

I assume that some of the commits from here or here are responsible, maybe this.
@na--

This comment has been minimized.

Show comment
Hide comment
@na--

na-- Feb 21, 2018

Actually, when I tried to attach a USB device to a fedora-26 AppVM, it was also necessary to add export PATH="/sbin:/usr/sbin:/usr/local/sbin:${PATH:-/bin:/usr/bin:/usr/local/bin}" in the beginning of /usr/lib/qubes/usb-import in the AppVM as well as the change in sys-usb. The strange thing is that wasn't necessary for attaching USB devices to an Archlinux AppVM, possibly because of the somewhat different filesystem hierarchy in Arch.

na-- commented Feb 21, 2018

Actually, when I tried to attach a USB device to a fedora-26 AppVM, it was also necessary to add export PATH="/sbin:/usr/sbin:/usr/local/sbin:${PATH:-/bin:/usr/bin:/usr/local/bin}" in the beginning of /usr/lib/qubes/usb-import in the AppVM as well as the change in sys-usb. The strange thing is that wasn't necessary for attaching USB devices to an Archlinux AppVM, possibly because of the somewhat different filesystem hierarchy in Arch.
@n1m1

This comment has been minimized.

Show comment
Hide comment
@n1m1

n1m1 Feb 21, 2018

Thanks. On my laptop the solution proposed by @na-- and based on @rustybird 's code seems to solve the problem for the Yubikey (in my case, it has been enough to modify/usr/lib/qubes/usb-export in sys-usb) but not for the webcam.

Indeed, if I try to attach the webcam to the voip VM,

  1. I get this output in/var/log/syslog:
Feb 21 22:32:01 localhost qrexec-agent[509]: executed root:QUBESRPC qubes.USBAttach dom0 pid 1606
Feb 21 22:32:01 localhost systemd[1]: Created slice User Slice of root.
Feb 21 22:32:01 localhost systemd[1]: Starting User Manager for UID 0...
Feb 21 22:32:01 localhost systemd[1]: Started Session c6 of user root.
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG network certificate management daemon.
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 21 22:32:01 localhost systemd[1607]: Starting D-Bus User Message Bus Socket.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Timers.
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 21 22:32:01 localhost systemd[1607]: Reached target Paths.
Feb 21 22:32:01 localhost systemd[1607]: Listening on D-Bus User Message Bus Socket.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Sockets.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Basic System.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Default.
Feb 21 22:32:01 localhost systemd[1607]: Startup finished in 18ms.
Feb 21 22:32:01 localhost systemd[1]: Started User Manager for UID 0.
Feb 21 22:32:01 localhost kernel: [  517.462098] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0)
Feb 21 22:32:01 localhost kernel: [  517.462115] vhci_hcd vhci_hcd.0: devid(65539) speed(3) speed_str(high-speed)
Feb 21 22:32:01 localhost kernel: [  517.681355] usb 1-1: new high-speed USB device number 3 using vhci_hcd
Feb 21 22:32:02 localhost kernel: [  517.796386] usb 1-1: SetAddress Request (3) to port 0
Feb 21 22:32:02 localhost kernel: [  517.857612] usb 1-1: New USB device found, idVendor=13d3, idProduct=5248
Feb 21 22:32:02 localhost kernel: [  517.857694] usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Feb 21 22:32:02 localhost kernel: [  517.857774] usb 1-1: Product: Integrated Camera
Feb 21 22:32:02 localhost kernel: [  517.857834] usb 1-1: Manufacturer: Azurewave
Feb 21 22:32:02 localhost kernel: [  517.857884] usb 1-1: SerialNumber: NULL
Feb 21 22:32:02 localhost kernel: [  517.875492] uvcvideo: Found UVC 1.00 device Integrated Camera (13d3:5248)
Feb 21 22:32:02 localhost kernel: [  517.879009] uvcvideo: Failed to initialize entity for entity 6
Feb 21 22:32:02 localhost kernel: [  517.879031] uvcvideo: Failed to register entites (-22).
Feb 21 22:32:02 localhost kernel: [  517.879202] input: Integrated Camera: Integrated C as /devices/platform/vhci_hcd.0/usb1/1-1/1-1:1.0/input/input2
Feb 21 22:32:02 localhost mtp-probe: checking bus 1, device 3: "/sys/devices/platform/vhci_hcd.0/usb1/1-1"
Feb 21 22:32:02 localhost mtp-probe: bus: 1, device: 3 was not an MTP device
  1. The applet freezes. In order to unblock it I have to type in dom0

qvm-usb -d voip sys-usb:1-8

n1m1 commented Feb 21, 2018 •
edited
Edited 1 time
  • @n1m1 n1m1 edited Feb 21, 2018 (most recent)

Thanks. On my laptop the solution proposed by @na-- and based on @rustybird 's code seems to solve the problem for the Yubikey (in my case, it has been enough to modify/usr/lib/qubes/usb-export in sys-usb) but not for the webcam.

Indeed, if I try to attach the webcam to the voip VM,

  1. I get this output in/var/log/syslog:
Feb 21 22:32:01 localhost qrexec-agent[509]: executed root:QUBESRPC qubes.USBAttach dom0 pid 1606
Feb 21 22:32:01 localhost systemd[1]: Created slice User Slice of root.
Feb 21 22:32:01 localhost systemd[1]: Starting User Manager for UID 0...
Feb 21 22:32:01 localhost systemd[1]: Started Session c6 of user root.
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG network certificate management daemon.
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 21 22:32:01 localhost systemd[1607]: Starting D-Bus User Message Bus Socket.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Timers.
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 21 22:32:01 localhost systemd[1607]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 21 22:32:01 localhost systemd[1607]: Reached target Paths.
Feb 21 22:32:01 localhost systemd[1607]: Listening on D-Bus User Message Bus Socket.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Sockets.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Basic System.
Feb 21 22:32:01 localhost systemd[1607]: Reached target Default.
Feb 21 22:32:01 localhost systemd[1607]: Startup finished in 18ms.
Feb 21 22:32:01 localhost systemd[1]: Started User Manager for UID 0.
Feb 21 22:32:01 localhost kernel: [  517.462098] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0)
Feb 21 22:32:01 localhost kernel: [  517.462115] vhci_hcd vhci_hcd.0: devid(65539) speed(3) speed_str(high-speed)
Feb 21 22:32:01 localhost kernel: [  517.681355] usb 1-1: new high-speed USB device number 3 using vhci_hcd
Feb 21 22:32:02 localhost kernel: [  517.796386] usb 1-1: SetAddress Request (3) to port 0
Feb 21 22:32:02 localhost kernel: [  517.857612] usb 1-1: New USB device found, idVendor=13d3, idProduct=5248
Feb 21 22:32:02 localhost kernel: [  517.857694] usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Feb 21 22:32:02 localhost kernel: [  517.857774] usb 1-1: Product: Integrated Camera
Feb 21 22:32:02 localhost kernel: [  517.857834] usb 1-1: Manufacturer: Azurewave
Feb 21 22:32:02 localhost kernel: [  517.857884] usb 1-1: SerialNumber: NULL
Feb 21 22:32:02 localhost kernel: [  517.875492] uvcvideo: Found UVC 1.00 device Integrated Camera (13d3:5248)
Feb 21 22:32:02 localhost kernel: [  517.879009] uvcvideo: Failed to initialize entity for entity 6
Feb 21 22:32:02 localhost kernel: [  517.879031] uvcvideo: Failed to register entites (-22).
Feb 21 22:32:02 localhost kernel: [  517.879202] input: Integrated Camera: Integrated C as /devices/platform/vhci_hcd.0/usb1/1-1/1-1:1.0/input/input2
Feb 21 22:32:02 localhost mtp-probe: checking bus 1, device 3: "/sys/devices/platform/vhci_hcd.0/usb1/1-1"
Feb 21 22:32:02 localhost mtp-probe: bus: 1, device: 3 was not an MTP device
  1. The applet freezes. In order to unblock it I have to type in dom0

qvm-usb -d voip sys-usb:1-8

@andrewdavidwong andrewdavidwong reopened this Feb 22, 2018

@andrewdavidwong andrewdavidwong added bug C: core C: templates and removed duplicate labels Feb 22, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Feb 22, 2018

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 22, 2018

Member

@n1m1 does it also apply to yubikey after modifying usb-export script?

BTW the modification is not needed anymore if you update to qubes-core-agent 4.0.23
Member

marmarek commented Feb 22, 2018

@n1m1 does it also apply to yubikey after modifying usb-export script?

BTW the modification is not needed anymore if you update to qubes-core-agent 4.0.23
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 22, 2018

Member

Oh, you've said that already.

Anyway, check with qubes-core-agent updated.
Member

marmarek commented Feb 22, 2018

Oh, you've said that already.

Anyway, check with qubes-core-agent updated.
@n1m1

This comment has been minimized.

Show comment
Hide comment
@n1m1

n1m1 Feb 24, 2018

Hello. I do apologize for the late answer but I've been very busy in the last two days.

qubes-core-agent 4.0.23 fixed the problem for Yubikey, but not for the webcam. I am experiencing the same behavior reported above. Actually, I noticed one more detail:

  1. When I try to attach the webcam to the voip VM using the USB applet it freezes.
  2. However, if I type qvm-usb in dom0 the webcam seems to be attached to the voip VM.
  3. In order to unblock the USB applet, I type qvm-usb d voip sys-usb:2-8
  4. The applet is now responsive again and, according to qvm-usb, the webcam is not attached anymore to voip VM.
  5. ... but, if now I plugin a USB device (i.e. a Yubikey or a USB stick), it is not detected by the USB applet (whereas I can see it in a dom0 terminal typing qvm-usb)

n1m1 commented Feb 24, 2018 •
edited
Edited 1 time
  • @n1m1 n1m1 edited Feb 24, 2018 (most recent)

Hello. I do apologize for the late answer but I've been very busy in the last two days.

qubes-core-agent 4.0.23 fixed the problem for Yubikey, but not for the webcam. I am experiencing the same behavior reported above. Actually, I noticed one more detail:

  1. When I try to attach the webcam to the voip VM using the USB applet it freezes.
  2. However, if I type qvm-usb in dom0 the webcam seems to be attached to the voip VM.
  3. In order to unblock the USB applet, I type qvm-usb d voip sys-usb:2-8
  4. The applet is now responsive again and, according to qvm-usb, the webcam is not attached anymore to voip VM.
  5. ... but, if now I plugin a USB device (i.e. a Yubikey or a USB stick), it is not detected by the USB applet (whereas I can see it in a dom0 terminal typing qvm-usb)
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 24, 2018

Member

Check ~/.xsession-errors in dom0 for any python stack trace (especially related to devices.py).
Member

marmarek commented Feb 24, 2018

Check ~/.xsession-errors in dom0 for any python stack trace (especially related to devices.py).
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 24, 2018

Member

You can also restart that widget and retry: look for process python3 -mqui.tray.devices, kill it and start again manually.
Member

marmarek commented Feb 24, 2018

You can also restart that widget and retry: look for process python3 -mqui.tray.devices, kill it and start again manually.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 24, 2018

Hi,
I do have exactly the same problem.
I am running Qubes 4 rc4.
When speaking about qubes-core-agent, you are speaking about "qubes-core-dom0 version 4.0.23 ?

ThierryIT commented Feb 24, 2018

Hi,
I do have exactly the same problem.
I am running Qubes 4 rc4.
When speaking about qubes-core-agent, you are speaking about "qubes-core-dom0 version 4.0.23 ?
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 24, 2018

Member

Nope, the qubes-core-agent* packages in VM - check in both sys-usb and the VM where you attach the device to.
Member

marmarek commented Feb 24, 2018

Nope, the qubes-core-agent* packages in VM - check in both sys-usb and the VM where you attach the device to.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 24, 2018

Heu ... the original problem is that I cannot attached it (device attached failed) :)
And even if I have done all the modifications from "na--" post, I do still have the same problem.
My sys-usb has been done with the fedora-26 template.

What I have done:

  1. clone fedora-26 template
  2. change the default template in Qubes settings to the fedora-26 clone template
  3. add all the modification to the clone template
  4. building the sys-usb

When checking in my sys-usb, I can see that all the modifications have been taken into account.

ThierryIT commented Feb 24, 2018 •
edited
Edited 3 times
  • @ThierryIT ThierryIT edited Feb 24, 2018 (most recent)
  • @ThierryIT ThierryIT edited Feb 24, 2018
  • @ThierryIT ThierryIT edited Feb 24, 2018

Heu ... the original problem is that I cannot attached it (device attached failed) :)
And even if I have done all the modifications from "na--" post, I do still have the same problem.
My sys-usb has been done with the fedora-26 template.

What I have done:

  1. clone fedora-26 template
  2. change the default template in Qubes settings to the fedora-26 clone template
  3. add all the modification to the clone template
  4. building the sys-usb

When checking in my sys-usb, I can see that all the modifications have been taken into account.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 24, 2018

from the VM I would like to attached my device to ...

Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG network certificate management daemon.
Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG cryptographic agent (access for web browsers).
Feb 24 18:01:03 localhost systemd[2408]: Reached target Shutdown.
Feb 24 18:01:03 localhost systemd[2408]: Starting Exit the Session...
Feb 24 18:01:03 localhost systemd[2408]: Stopped target Paths.
Feb 24 18:01:03 localhost systemd[2408]: Received SIGRTMIN+24 from PID 2427 (kill).
Feb 24 18:01:03 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 24 18:01:03 localhost systemd[1]: Removed slice User Slice of root.
Feb 24 18:01:52 localhost qrexec-agent[616]: executed root:QUBESRPC qubes.USBAttach dom0 pid 2437
Feb 24 18:01:52 localhost systemd[1]: Created slice User Slice of root.
Feb 24 18:01:52 localhost systemd[1]: Starting User Manager for UID 0...
Feb 24 18:01:52 localhost systemd[1]: Started Session c12 of user root.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Paths.
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG network certificate management daemon.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Timers.
Feb 24 18:01:52 localhost systemd[2438]: Starting D-Bus User Message Bus Socket.
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 24 18:01:52 localhost systemd[2438]: Listening on D-Bus User Message Bus Socket.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Sockets.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Basic System.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Default.
Feb 24 18:01:52 localhost systemd[2438]: Startup finished in 17ms.
Feb 24 18:01:52 localhost systemd[1]: Started User Manager for UID 0.
Feb 24 18:01:53 localhost qubes.USBAttach-dom0: No device info received, connection failed, check backend side for details
Feb 24 18:01:53 localhost qrexec-agent[616]: send exit code 1
Feb 24 18:01:53 localhost qrexec-agent[616]: pid 2437 exited with 1
Feb 24 18:01:53 localhost qrexec-agent[616]: eintr
Feb 24 18:01:53 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Default.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Basic System.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Timers.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Paths.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Sockets.
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent (access for web browsers).
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG network certificate management daemon.
Feb 24 18:01:53 localhost systemd[2438]: Closed D-Bus User Message Bus Socket.
Feb 24 18:01:53 localhost systemd[2438]: Reached target Shutdown.
Feb 24 18:01:53 localhost systemd[2438]: Starting Exit the Session...
Feb 24 18:01:53 localhost systemd[2438]: Received SIGRTMIN+24 from PID 2457 (kill).
Feb 24 18:01:53 localhost systemd[1]: Stopped User Manager for UID 0.

ThierryIT commented Feb 24, 2018 •
edited by andrewdavidwong
Edited 4 times
  • @andrewdavidwong andrewdavidwong edited Feb 25, 2018 (most recent)
  • @ThierryIT ThierryIT edited Feb 24, 2018
  • @ThierryIT ThierryIT edited Feb 24, 2018
  • @ThierryIT ThierryIT edited Feb 24, 2018

from the VM I would like to attached my device to ...

Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG network certificate management daemon.
Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 24 18:01:03 localhost systemd[2408]: Closed GnuPG cryptographic agent (access for web browsers).
Feb 24 18:01:03 localhost systemd[2408]: Reached target Shutdown.
Feb 24 18:01:03 localhost systemd[2408]: Starting Exit the Session...
Feb 24 18:01:03 localhost systemd[2408]: Stopped target Paths.
Feb 24 18:01:03 localhost systemd[2408]: Received SIGRTMIN+24 from PID 2427 (kill).
Feb 24 18:01:03 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 24 18:01:03 localhost systemd[1]: Removed slice User Slice of root.
Feb 24 18:01:52 localhost qrexec-agent[616]: executed root:QUBESRPC qubes.USBAttach dom0 pid 2437
Feb 24 18:01:52 localhost systemd[1]: Created slice User Slice of root.
Feb 24 18:01:52 localhost systemd[1]: Starting User Manager for UID 0...
Feb 24 18:01:52 localhost systemd[1]: Started Session c12 of user root.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Paths.
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG network certificate management daemon.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Timers.
Feb 24 18:01:52 localhost systemd[2438]: Starting D-Bus User Message Bus Socket.
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 24 18:01:52 localhost systemd[2438]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 24 18:01:52 localhost systemd[2438]: Listening on D-Bus User Message Bus Socket.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Sockets.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Basic System.
Feb 24 18:01:52 localhost systemd[2438]: Reached target Default.
Feb 24 18:01:52 localhost systemd[2438]: Startup finished in 17ms.
Feb 24 18:01:52 localhost systemd[1]: Started User Manager for UID 0.
Feb 24 18:01:53 localhost qubes.USBAttach-dom0: No device info received, connection failed, check backend side for details
Feb 24 18:01:53 localhost qrexec-agent[616]: send exit code 1
Feb 24 18:01:53 localhost qrexec-agent[616]: pid 2437 exited with 1
Feb 24 18:01:53 localhost qrexec-agent[616]: eintr
Feb 24 18:01:53 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Default.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Basic System.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Timers.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Paths.
Feb 24 18:01:53 localhost systemd[2438]: Stopped target Sockets.
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent (access for web browsers).
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 24 18:01:53 localhost systemd[2438]: Closed GnuPG network certificate management daemon.
Feb 24 18:01:53 localhost systemd[2438]: Closed D-Bus User Message Bus Socket.
Feb 24 18:01:53 localhost systemd[2438]: Reached target Shutdown.
Feb 24 18:01:53 localhost systemd[2438]: Starting Exit the Session...
Feb 24 18:01:53 localhost systemd[2438]: Received SIGRTMIN+24 from PID 2457 (kill).
Feb 24 18:01:53 localhost systemd[1]: Stopped User Manager for UID 0.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 26, 2018

Member

@ThierryIT do you get anything more useful from sys-usb at that time?
Member

marmarek commented Feb 26, 2018

@ThierryIT do you get anything more useful from sys-usb at that time?
@protoEvangelion

This comment has been minimized.

Show comment
Hide comment
@protoEvangelion

protoEvangelion Feb 26, 2018

@marmarek Do I have to be running Qubes 4.0 to benefit from the updates of qubes-core-agent 4.0.23? Currently I am running Qubes 3.2

I am getting the same error reported by @n1m1 at the beginning of this issue:

"Device attach failed: No device info received, connection failed, check backend side for details"

protoEvangelion commented Feb 26, 2018

@marmarek Do I have to be running Qubes 4.0 to benefit from the updates of qubes-core-agent 4.0.23? Currently I am running Qubes 3.2

I am getting the same error reported by @n1m1 at the beginning of this issue:

"Device attach failed: No device info received, connection failed, check backend side for details"
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 26, 2018

Member

Equivalent qubes-core-agent version for 3.2 is 3.2.25
Member

marmarek commented Feb 26, 2018

Equivalent qubes-core-agent version for 3.2 is 3.2.25
@protoEvangelion

This comment has been minimized.

Show comment
Hide comment
@protoEvangelion

protoEvangelion Feb 26, 2018

If I've updated my VMs through the Qubes VM Manager gui will that upgrade the core agent?

If not, are there docs on how to upgrade qubes-core-agent?

protoEvangelion commented Feb 26, 2018

If I've updated my VMs through the Qubes VM Manager gui will that upgrade the core agent?

If not, are there docs on how to upgrade qubes-core-agent?
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 26, 2018

Member

By default it include only stable updates, see here for info about testing: https://www.qubes-os.org/doc/software-update-vm/#testing-repositories
Member

marmarek commented Feb 26, 2018

By default it include only stable updates, see here for info about testing: https://www.qubes-os.org/doc/software-update-vm/#testing-repositories
@protoEvangelion

This comment has been minimized.

Show comment
Hide comment
@protoEvangelion

protoEvangelion Feb 26, 2018

@marmarek That fixed it for me thanks!

protoEvangelion commented Feb 26, 2018 •
edited
Edited 1 time
  • @protoEvangelion protoEvangelion edited Feb 26, 2018 (most recent)

@marmarek That fixed it for me thanks!
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 26, 2018

@marmarek : I am updating my system through this command: qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Concerning sys-usb, I will provide what you need, I have done a new reinstall from the fedora-26 template but still do have the same pb.
How to know the qubes-core-agent version my system is using ?
Thx for your support

ThierryIT commented Feb 26, 2018 •
edited
Edited 2 times
  • @ThierryIT ThierryIT edited Feb 26, 2018 (most recent)
  • @ThierryIT ThierryIT edited Feb 26, 2018

@marmarek : I am updating my system through this command: qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Concerning sys-usb, I will provide what you need, I have done a new reinstall from the fedora-26 template but still do have the same pb.
How to know the qubes-core-agent version my system is using ?
Thx for your support
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 26, 2018

Member

Checking package version:
Fedora: rpm -q qubes-core-agent
Debian: dpkg -l qubes-core-agent
Member

marmarek commented Feb 26, 2018

Checking package version:
Fedora: rpm -q qubes-core-agent
Debian: dpkg -l qubes-core-agent
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 26, 2018

Hi,
It is not installed.
When trying to install it in the template of my sys-usb, I do have:

  • sudo dnf install qubes-core-agent
    No match for argument
    Error: Unable to find a match
    Is there another way to install this packages ?

ThierryIT commented Feb 26, 2018

Hi,
It is not installed.
When trying to install it in the template of my sys-usb, I do have:

  • sudo dnf install qubes-core-agent
    No match for argument
    Error: Unable to find a match
    Is there another way to install this packages ?
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 26, 2018

Member

Are you sure if this is the template you've got with Qubes OS 4.0 installation? Isn't that a template restored from 3.2? On 3.2, the package was named qubes-core-vm.
Member

marmarek commented Feb 26, 2018

Are you sure if this is the template you've got with Qubes OS 4.0 installation? Isn't that a template restored from 3.2? On 3.2, the package was named qubes-core-vm.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 26, 2018

I don't remember it ... I am going to reinstall a new fedora-26 template.
I will let you know.

ThierryIT commented Feb 26, 2018

I don't remember it ... I am going to reinstall a new fedora-26 template.
I will let you know.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 27, 2018

Ok, upgrade to the right fedora 26 template has been done, I am now running qubes-core-agent 4.0.23.
But ....

qvm-block doesn't detect the Yubico

sudo qvm-usb usb a vm-comms sys-usb:3-2:

Device attached failed: /usr/lib/qubes/usb-import: 33: /usr/lib/qubes/usb-import: cannot open /sys/devices/platform/vhci_hcd Directory nonexistant ....

Same for line 51

usb-import doesn't exist

the logs of my targeting VM is strictely identical than what I have posted three days ago.

ThierryIT commented Feb 27, 2018 •
edited
Edited 3 times
  • @ThierryIT ThierryIT edited Feb 27, 2018 (most recent)
  • @ThierryIT ThierryIT edited Feb 27, 2018
  • @ThierryIT ThierryIT edited Feb 27, 2018

Ok, upgrade to the right fedora 26 template has been done, I am now running qubes-core-agent 4.0.23.
But ....

qvm-block doesn't detect the Yubico

sudo qvm-usb usb a vm-comms sys-usb:3-2:

Device attached failed: /usr/lib/qubes/usb-import: 33: /usr/lib/qubes/usb-import: cannot open /sys/devices/platform/vhci_hcd Directory nonexistant ....

Same for line 51

usb-import doesn't exist

the logs of my targeting VM is strictely identical than what I have posted three days ago.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 27, 2018

After the upgrade of my targeted VM alias "vm-comms" I am able to attach the Yubico ....
It seems that the packages "qubes-usb-proxy" has been updated too ....

How to mount it now ? xvdi doesn't exist

ThierryIT commented Feb 27, 2018

After the upgrade of my targeted VM alias "vm-comms" I am able to attach the Yubico ....
It seems that the packages "qubes-usb-proxy" has been updated too ....

How to mount it now ? xvdi doesn't exist
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 27, 2018

Member

Mount? Does Yubikey provide some storage? Mine doesn't, it's visible as HID device. You can try for example U2F on this site: https://demo.yubico.com/u2f
Member

marmarek commented Feb 27, 2018

Mount? Does Yubikey provide some storage? Mine doesn't, it's visible as HID device. You can try for example U2F on this site: https://demo.yubico.com/u2f
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 28, 2018

Yubico working with "Chromium" but not with "Firefox-esr" ... What browser are you using to make it working ?

ThierryIT commented Feb 28, 2018

Yubico working with "Chromium" but not with "Firefox-esr" ... What browser are you using to make it working ?
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2018

Member

Last time tried with Firefox 56 (with addon installed).
Member

marmarek commented Feb 28, 2018

Last time tried with Firefox 56 (with addon installed).
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 28, 2018

In firefox u2f is not activated by defaut, you have to "about:config" in the URL and switch "security.webauth.u2f to "True"

ThierryIT commented Feb 28, 2018

In firefox u2f is not activated by defaut, you have to "about:config" in the URL and switch "security.webauth.u2f to "True"
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2018

Member

Does it solve the problem?
Member

marmarek commented Feb 28, 2018

Does it solve the problem?
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 28, 2018

Under Windows .... Yes :)
Under Linux .... No, the device is not flashing if using firefox ...

ThierryIT commented Feb 28, 2018

Under Windows .... Yes :)
Under Linux .... No, the device is not flashing if using firefox ...
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2018

Member

Fedora? Do you have u2f-hidraw-policy package installed? Try install it (run sudo udevadm control -R afterwards).
Member

marmarek commented Feb 28, 2018

Fedora? Do you have u2f-hidraw-policy package installed? Try install it (run sudo udevadm control -R afterwards).
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 28, 2018

Are you talking about the VM where the device is attached ? If yes, I am running Debian on it ...

ThierryIT commented Feb 28, 2018

Are you talking about the VM where the device is attached ? If yes, I am running Debian on it ...
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2018

Member

I believe equivalent files on Debian are in libu2f-host0 package, see here: https://wiki.debian.org/Smartcards/YubiKey4#udev

Anyway, after plugging it in, check permissions on /dev/hidraw*, and adjust if necessary - you should have read and write access.
Member

marmarek commented Feb 28, 2018

I believe equivalent files on Debian are in libu2f-host0 package, see here: https://wiki.debian.org/Smartcards/YubiKey4#udev

Anyway, after plugging it in, check permissions on /dev/hidraw*, and adjust if necessary - you should have read and write access.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 28, 2018

Is it not better to have a look there instead :
https://www.yubico.com/support/knowledge-base/categories/articles/can-set-linux-system-use-u2f/

the device should be "hidraw" (Yubico link) not "usb" (debian link) no ?

Anf for the permission, I have to check the template that I have used to build my "sys-usb" ?

If yes, I do have for all my "hidraw*"

crw-------- root:root

ThierryIT commented Feb 28, 2018 •
edited
Edited 3 times
  • @ThierryIT ThierryIT edited Feb 28, 2018 (most recent)
  • @ThierryIT ThierryIT edited Feb 28, 2018
  • @ThierryIT ThierryIT edited Feb 28, 2018

Is it not better to have a look there instead :
https://www.yubico.com/support/knowledge-base/categories/articles/can-set-linux-system-use-u2f/

the device should be "hidraw" (Yubico link) not "usb" (debian link) no ?

Anf for the permission, I have to check the template that I have used to build my "sys-usb" ?

If yes, I do have for all my "hidraw*"

crw-------- root:root
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2018

Member

the device should be "hidraw" (Yubico link) not "usb" (debian link) no ?

Both should work.

If yes, I do have for all my "hidraw*"

crw-------- root:root

Try changing to 666 and try with firefox. If that helps, then it is permissions problem, if not - something else.
Member

marmarek commented Feb 28, 2018

the device should be "hidraw" (Yubico link) not "usb" (debian link) no ?

Both should work.

If yes, I do have for all my "hidraw*"

crw-------- root:root

Try changing to 666 and try with firefox. If that helps, then it is permissions problem, if not - something else.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Mar 1, 2018

There is no /dev/hidraw* in my template, so I have done the permissions change directly in my sys-usb but it doesn't work ...
I will have to stay with Chromium I suppose :(

ThierryIT commented Mar 1, 2018

There is no /dev/hidraw* in my template, so I have done the permissions change directly in my sys-usb but it doesn't work ...
I will have to stay with Chromium I suppose :(
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 1, 2018

Member

No, in the VM where you have firefox running, after attaching yubikey there.
Member

marmarek commented Mar 1, 2018

No, in the VM where you have firefox running, after attaching yubikey there.

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0, Release 4.0 updates Mar 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment