Your message dated Mon, 08 May 2017 16:25:51 +0200 with message-id <[email protected]> and subject line Re: Bug#862032: [scdaemon] yubikey 4 stops working after upgrade from 2.1.18-6 has caused the Debian Bug report #862032, regarding [scdaemon] yubikey 4 stops working after upgrade from 2.1.18-6 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 862032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862032 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: scdaemon Version: 2.1.18-7 Severity: important --- Please enter the report below this line. --- Hi there, after upgrading to 2.1.18-7 my yubikey stops working again. In difference to #852702 I can't get serious output to append to the bug report since an "gpg --card-status" dont' get me any update. shin 7947 0.0 0.1 33504 3880 pts/1 SL+ 17:11 0:00 \_ gpg --card-status akira[/home/shin/working_gpg]0> strace -p 7947 strace: Process 7947 attached read(3, 0x5645c2ab7d90, 1002) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} --- munmap(0x7fca6ad96000, 65536) = 0 write(2, "\n", 1) = 1 write(2, "gpg", 3) = 3 write(2, ": signal ", 9) = 9 write(2, "Interrupt", 9) = 9 write(2, " caught ... exiting\n", 20) = 20 rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fca69766030}, NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [INT], 8) = 0 getpid() = 7947 gettid() = 7947 tgkill(7947, 7947, SIGINT) = 0 rt_sigprocmask(SIG_SETMASK, [INT], NULL, 8) = 0 rt_sigreturn({mask=[]}) = -1 EINTR (Interrupted system call) --- SIGINT {si_signo=SIGINT, si_code=SI_TKILL, si_pid=7947, si_uid=1000} --- +++ killed by SIGINT +++ akira[/home/shin/working_gpg]0> pcsc_scan can still access the yubikey akira[/home/shin/working_gpg]0> pcsc_scan PC/SC device scanner V 1.4.27 (c) 2001-2011, Ludovic Rousseau <[email protected]> Compiled with PC/SC lite version: 1.8.17 Using reader plug'n play mechanism Scanning present readers... 0: Yubico Yubikey 4 CCID 00 00 Sun May 7 17:21:46 2017 Reader 0: Yubico Yubikey 4 CCID 00 00 Card state: Card inserted, Exclusive Mode, ATR: 3B F8 13 00 00 81 31 FE 15 59 75 62 69 6B 65 79 34 D4 ATR: 3B F8 13 00 00 81 31 FE 15 59 75 62 69 6B 65 79 34 D4 + TS = 3B --> Direct Convention + T0 = F8, Y(1): 1111, K: 8 (historical bytes) TA(1) = 13 --> Fi=372, Di=4, 93 cycles/ETU 43010 bits/s at 4 MHz, fMax for Fi = 5 MHz => 53763 bits/s TB(1) = 00 --> VPP is not electrically connected TC(1) = 00 --> Extra guard time: 0 TD(1) = 81 --> Y(i+1) = 1000, Protocol T = 1 ----- TD(2) = 31 --> Y(i+1) = 0011, Protocol T = 1 ----- TA(3) = FE --> IFSC: 254 TB(3) = 15 --> Block Waiting Integer: 1 - Character Waiting Integer: 5 + Historical bytes: 59 75 62 69 6B 65 79 34 Category indicator byte: 59 (proprietary format) + TCK = D4 (correct checksum) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F8 13 00 00 81 31 FE 15 59 75 62 69 6B 65 79 34 D4 Yubico Yubikey 4 OTP+CCID ^C akira[/home/shin/working_gpg]130> After a downgrade to 2.1.18-6 all works again like a charm. Related packages are: dirmngr, gnupg, gnupg2, gnupg-agent, gnupg-l10n, gpgv, scdaemon If you need additional information or anything that I can troubleshoot, tell it :) Greetings Shin --- System information. --- Architecture: Kernel: Linux 4.9.0-3-amd64 Debian Release: 9.0 500 unstable ftp.de.debian.org 500 stable repo.vivaldi.com 500 stable repo.sinew.in --- Package information. --- Depends (Version) | Installed ==============================-+-============= gnupg-agent (= 2.1.18-7) | 2.1.18-7 libassuan0 (>= 2.2.0) | 2.4.3-2 libc6 (>= 2.15) | 2.24-10 libgcrypt20 (>= 1.7.0) | 1.7.6-1 libgpg-error0 (>= 1.14) | 1.26-2 libksba8 (>= 1.3.4) | 1.3.5-2 libnpth0 (>= 0.90) | 1.3-1 libusb-1.0-0 (>= 2:1.0.9) | 2:1.0.21-1 Package's Recommends field is empty. Package's Suggests field is empty. -- I'm just a placeholder for a really awesome signature... ...that is still missing *sob*
--- End Message ---
--- Begin Message ---Version: 2.1.20-3 Control: severity -1 serious Control: tags -1 +confirmed Le dimanche, 7 mai 2017, 17.27:45 h CEST Shin Ice a écrit : > after upgrading to 2.1.18-7 my yubikey stops working again. > In difference to #852702 I can't get serious output to append to the bug > report since an "gpg --card-status" dont' get me any update. > (…) > After a downgrade to 2.1.18-6 all works again like a charm. I confirm this behaviour. This looks like a serious regression from 2.1.18-6 to me, but I tried 2.1.20-3 from experimental, and it just works. Using scdeamon (and all the suite) in 2.1.18-7 version, actually, I can get _one_ signature (or SSH authentication) through. Then the only way I found to get another one is to kill scdaemon and retry. Staying at your disposal for any debugging! Cheers, OdyX
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
