search

Yubico / yubikey-personalization

YubiKey Personalization cross-platform library and tool
https://developers.yubico.com/yubikey-personalization/
BSD 2-Clause "Simplified" License
297 stars 83 forks source link

After I upgraded to version 1.19.3-2 I can't read my Yubikeys.It shows is "Unknow error occured #143

Closed madgitvisitor closed 5 years ago

madgitvisitor commented 5 years ago

Package: yubikey-personalization Version: 1.19.3-2 Severity: important

Dear Maintainer,

Reporter, please consider answering these questions, where appropriate 

 * What led up to the situation?
 upgraded to version 1.19.3-2
 * Explain the issue.
 I can't read my Yubikeys.The only message it shows is "Unknow error occured" Keepass2/Keepassxc also can't read the Keys. 
 But other programs like yubikey-luks or pam can read the keys in challenge-response.
 * What exactly did you do (or not do) that was effective (or
    ineffective)?
 I reconfigure the package.
 * What was the outcome of this action?
 Nothing, the issue stil belive.
 * What outcome did you expect instead?
 Fix the issue.

End of the template - remove these template lines

-- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled

Versions of packages yubikey-personalization depends on: ii libc6 2.28-8 ii libjson-c3 0.12.1+ds-2 ii libusb-1.0-0 2:1.0.22-2 ii libykpers-1-1 1.19.3-2 ii libyubikey0 1.13-4

yubikey-personalization recommends no packages.

yubikey-personalization suggests no packages.

klali commented 5 years ago

As I understand this some software works, some doesn't, correct?

What software works? What doesn't?

Does the ykinfo tool that comes with yubikey-personalization work? What about ykchalresp?

madgitvisitor commented 5 years ago

Ok it's a Debian Buster specific problem in the udev rules - in 1.19.3-2, the package switched from providing udev rules to using the rules in libu2f-udev (source package libu2f-host).

Addthe new udev rule for the yubikey solve the issue:

bash

add yubikey rule nano /etc/udev/rules.d/71-yubikey.rules paste SUBSYSTEMS=="usb", ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120|0200|0402|0403|0406|0407|0410", TAG+="uaccess", GROUP="plugdev", MODE="0660"

End bash

Bug listed on debian buster package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924787

The issue can be mark as solved.

Thanks