Debian Bug report logs - #852702
[gnupg2] gpg: OpenPGP card not available: No such device after upgrade to 2.1.18-3

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Shin Ice <shin.ice@shinice.net>

To: submit@bugs.debian.org

Subject: [gnupg2] gpg: OpenPGP card not available: No such device after upgrade to 2.1.18-3

Date: Thu, 26 Jan 2017 15:46:04 +0100

Package: gnupg2
Version: 2.1.18-3
Severity: important

--- Please enter the report below this line. ---

Hi,

after upgrading gnupg2 (and related) to version 2.1.18-3 the yubikey 4
can't be used. On a different system (still sid) with version 2.1.16-3
all works as desired and designed.

$ gpg2 --card-status
gpg: selecting openpgp failed: No such device
gpg: OpenPGP card not available: No such device

$ pcsc_scan
PC/SC device scanner
V 1.4.27 (c) 2001-2011, Ludovic Rousseau <ludovic.rousseau@free.fr>
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

Thu Jan 26 14:50:02 2017
Reader 0: Yubico Yubikey 4 CCID 00 00
  Card state: Card inserted,
  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

output from /var/log/messages
Jan 26 14:44:15 akira kernel: [ 1065.486401] perf: interrupt took too
long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Jan 26 14:48:08 akira kernel: [ 1298.188119] usb 2-1.2: USB disconnect,
device number 13
Jan 26 14:49:58 akira kernel: [ 1408.239508] usb 2-1.2: new full-speed
USB device number 14 using ehci-pci
Jan 26 14:49:58 akira kernel: [ 1408.355525] usb 2-1.2: New USB device
found, idVendor=1050, idProduct=0404
Jan 26 14:49:58 akira kernel: [ 1408.355529] usb 2-1.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Jan 26 14:49:58 akira kernel: [ 1408.355533] usb 2-1.2: Product: Yubikey
4 CCID
Jan 26 14:49:58 akira kernel: [ 1408.355536] usb 2-1.2: Manufacturer:
Yubico

Same output from the system with 2.1.16-3 running:
$ pcsc_scan 
PC/SC device scanner
V 1.4.27 (c) 2001-2011, Ludovic Rousseau <ludovic.rousseau@free.fr>
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

Thu Jan 26 14:48:57 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

$ gpg2 --card-status

Reader ...........: Yubico Yubikey 4 CCID 00 00

output from /var/log/messages
Jan 26 14:40:22 motoko kernel: [1824155.938692] usb 4-2: USB disconnect,
device number 8
Jan 26 14:48:11 motoko kernel: [1824624.984164] usb 4-2: new full-speed
USB device number 9 using ohci-pci
Jan 26 14:48:11 motoko kernel: [1824625.177260] usb 4-2: New USB device
found, idVendor=1050, idProduct=0404
Jan 26 14:48:11 motoko kernel: [1824625.177267] usb 4-2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Jan 26 14:48:11 motoko kernel: [1824625.177272] usb 4-2: Product:
Yubikey 4 CCID
Jan 26 14:48:11 motoko kernel: [1824625.177275] usb 4-2: Manufacturer:
Yubico

If you need more infos/tests, feel free to let me know =)

c'ya
Shin



--- System information. ---
Architecture: 
Kernel:       Linux 4.9.0-1-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       (>= 2.1.18-3) | 2.1.18-3


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*

Message #10 received at 852702@bugs.debian.org (full text, mbox, reply):

From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

To: Shin Ice <shin.ice@shinice.net>, 852702@bugs.debian.org, NIIBE Yutaka <gniibe@fsij.org>

Subject: Re: [pkg-gnupg-maint] Bug#852702: [gnupg2] gpg: OpenPGP card not available: No such device after upgrade to 2.1.18-3

Date: Thu, 26 Jan 2017 19:00:14 -0500

Control: reassign 852702 scdaemon

Hi Shin Ice--

Thanks for the report!  I'm afraid i don't understand what's going on
here (and i don't have a yubikey 4 to test with, but maybe gniibe
(cc'ed) can shed some light on it.

Regards,

        --dkg

On Thu 2017-01-26 09:46:04 -0500, Shin Ice wrote:
> Package: gnupg2
> Version: 2.1.18-3
> Severity: important
>
> --- Please enter the report below this line. ---
>
> Hi,
>
> after upgrading gnupg2 (and related) to version 2.1.18-3 the yubikey 4
> can't be used. On a different system (still sid) with version 2.1.16-3
> all works as desired and designed.
>
> $ gpg2 --card-status
> gpg: selecting openpgp failed: No such device
> gpg: OpenPGP card not available: No such device
>
> $ pcsc_scan
> PC/SC device scanner
> V 1.4.27 (c) 2001-2011, Ludovic Rousseau <ludovic.rousseau@free.fr>
> 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
>
> Thu Jan 26 14:50:02 2017
> Reader 0: Yubico Yubikey 4 CCID 00 00
>   Card state: Card inserted,
>   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
>
> output from /var/log/messages
> Jan 26 14:44:15 akira kernel: [ 1065.486401] perf: interrupt took too
> long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
> Jan 26 14:48:08 akira kernel: [ 1298.188119] usb 2-1.2: USB disconnect,
> device number 13
> Jan 26 14:49:58 akira kernel: [ 1408.239508] usb 2-1.2: new full-speed
> USB device number 14 using ehci-pci
> Jan 26 14:49:58 akira kernel: [ 1408.355525] usb 2-1.2: New USB device
> found, idVendor=1050, idProduct=0404
> Jan 26 14:49:58 akira kernel: [ 1408.355529] usb 2-1.2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=0
> Jan 26 14:49:58 akira kernel: [ 1408.355533] usb 2-1.2: Product: Yubikey
> 4 CCID
> Jan 26 14:49:58 akira kernel: [ 1408.355536] usb 2-1.2: Manufacturer:
> Yubico
>
> Same output from the system with 2.1.16-3 running:
> $ pcsc_scan 
> PC/SC device scanner
> V 1.4.27 (c) 2001-2011, Ludovic Rousseau <ludovic.rousseau@free.fr>
> 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
>
> Thu Jan 26 14:48:57 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
>
> $ gpg2 --card-status
>
> Reader ...........: Yubico Yubikey 4 CCID 00 00
>
> output from /var/log/messages
> Jan 26 14:40:22 motoko kernel: [1824155.938692] usb 4-2: USB disconnect,
> device number 8
> Jan 26 14:48:11 motoko kernel: [1824624.984164] usb 4-2: new full-speed
> USB device number 9 using ohci-pci
> Jan 26 14:48:11 motoko kernel: [1824625.177260] usb 4-2: New USB device
> found, idVendor=1050, idProduct=0404
> Jan 26 14:48:11 motoko kernel: [1824625.177267] usb 4-2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=0
> Jan 26 14:48:11 motoko kernel: [1824625.177272] usb 4-2: Product:
> Yubikey 4 CCID
> Jan 26 14:48:11 motoko kernel: [1824625.177275] usb 4-2: Manufacturer:
> Yubico
>
> If you need more infos/tests, feel free to let me know =)
>
> c'ya
> Shin
>
>
>
> --- System information. ---
> Architecture: 
> Kernel:       Linux 4.9.0-1-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       (>= 2.1.18-3) | 2.1.18-3
>
>
> 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*
>
> _______________________________________________
> pkg-gnupg-maint mailing list
> pkg-gnupg-maint@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gnupg-maint

Message #19 received at 852702@bugs.debian.org (full text, mbox, reply):

From: Michael Berg <michael.berg@misumasu.com>

To: 852702@bugs.debian.org

Subject: Partial fix

Date: Mon, 30 Jan 2017 18:43:54 -0700

A friend and I both encountered this problem with our Yubikey 4 devices
after upgrading to gnupg and scdaemon 2.1.18-3.
Here is what I found, along with a partial solution.

The new scdaemon does NOT get along with pcscd anymore.
There is a race condition for which one opens the Yubikey device first.
Normally pcscd opens the device first, after which scdaemon refuses to
use the device. Occasionally, scdaemon would open the device first and
things would work as expected.

A work around for many people is to remove the pcscd package from
your system. If you don't require the PIV-card features of the Yubikey
(you are just using the PGP-card, U2F, and OTP features), then removing
pcscd will allow scdaemon to reliably get ownership of the device.

Also ensure is that the libykpers-1-1 package is installed. You can
install libykpers-1-1 directly, or install yubikey-personalization-gui
(which depends on it).

The libykpers-1-1 package contains /lib/udev/rules.d/69-yubikey.rules,
which is required to set various properties on the Yubikey device so
that scdaemon can access it as your unprivileged user.
Without this package installed, `gpg --card-status` would return
expected results when run as root, but would produce the
"No such device" error messages in the original bug report when run as
an unprivileged user.

After removing the pcscd package and ensuring that the libykpers-1-1
package was installed, my Yubikey is working on my Debian systems again.

Message #24 received at 852702@bugs.debian.org (full text, mbox, reply):

From: NIIBE Yutaka <gniibe@fsij.org>

To: Shin Ice <shin.ice@shinice.net>, 852702@bugs.debian.org

Subject: Re: [pkg-gnupg-maint] Bug#852702: [gnupg2] gpg: OpenPGP card not available: No such device after upgrade to 2.1.18-3

Date: Sat, 04 Feb 2017 01:59:58 +0900

Shin Ice <shin.ice@shinice.net> writes:
> Package: gnupg2
> Version: 2.1.18-3
> Severity: important
>
> --- Please enter the report below this line. ---
>
> Hi,
>
> after upgrading gnupg2 (and related) to version 2.1.18-3 the yubikey 4
> can't be used. On a different system (still sid) with version 2.1.16-3
> all works as desired and designed.
>
> $ gpg2 --card-status
> gpg: selecting openpgp failed: No such device
> gpg: OpenPGP card not available: No such device

I think that I enbugged scdaemon.  Could you please try to put
a line in your .gnupg/scdaemon.conf?

------------------- .gnupg/scdaemon.conf
disable-ccid
-------------------

-- 

Message #33 received at 852702@bugs.debian.org (full text, mbox, reply):

From: Shin Ice <shin.ice@shinice.net>

To: NIIBE Yutaka <gniibe@fsij.org>

Cc: 852702@bugs.debian.org

Subject: Re: [pkg-gnupg-maint] Bug#852702: [gnupg2] gpg: OpenPGP card not available: No such device after upgrade to 2.1.18-3

Date: Wed, 8 Feb 2017 00:25:16 +0100

[Message part 1 (text/plain, inline)]

Hi,

sorry for the delay.

On Sat, Feb 04, 2017 at 01:59:58AM +0900, NIIBE Yutaka wrote:
> 
> I think that I enbugged scdaemon.  Could you please try to put
> a line in your .gnupg/scdaemon.conf?
> 
> ------------------- .gnupg/scdaemon.conf
> disable-ccid
> -------------------
> 

Yes, it works.

Updated to the last version 2.1.18-4, created the scdaemon.conf and
added the line.

shin@akira:~$ gpg2 --card-status

Reader ...........: Yubico Yubikey 4 CCID 00 00

Thank you for the bug fix =)

Greetings
Shin

-- 

I'm just a placeholder for a really awesome signature...
...that is still missing *sob*

[signature.asc (application/pgp-signature, inline)]

Message #38 received at 852702-submitter@bugs.debian.org (full text, mbox, reply):

From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

To: 852702-submitter@bugs.debian.org

Subject: Bug#852702 marked as pending

Date: Mon, 13 Feb 2017 15:01:00 +0000

tag 852702 pending
thanks

Hello,

Bug #852702 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

    http://git.debian.org/?p=pkg-gnupg/gnupg2.git;a=commitdiff;h=4c91bae

---
commit 4c91bae777022f7ffd2ac4fa69837d59653eeb8f
Author: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Date:   Mon Feb 13 09:41:56 2017 -0500

    prepare new debian release

diff --git a/debian/changelog b/debian/changelog
index edd953b..bca7302 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+gnupg2 (2.1.18-5) unstable; urgency=medium
+
+  [ Daniel Kahn Gillmor ]
+  * Xsession.d/90gpg-agent: use simpler and more direct gpgconf
+    invocations for socket names.
+
+  [ NIIBE Yutaka ]
+  * scdaemon.udev: Add Yubikey and Nitrokey (Closes: #648331, 734889).
+  * scdaemon fix for PC/SC (Closes: #852702, #854005, #854595, #854616).
+
+ -- Daniel Kahn Gillmor <dkg@fifthhorseman.net>  Mon, 13 Feb 2017 09:15:07 -0500
+
 gnupg2 (2.1.18-4) unstable; urgency=medium
 
   [ Daniel Kahn Gillmor ]

Message #43 received at 852702-close@bugs.debian.org (full text, mbox, reply):

From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

To: 852702-close@bugs.debian.org

Subject: Bug#852702: fixed in gnupg2 2.1.18-5

Date: Mon, 13 Feb 2017 15:18:52 +0000

Source: gnupg2
Source-Version: 2.1.18-5

We believe that the bug you reported is fixed in the latest version of
gnupg2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852702@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor <dkg@fifthhorseman.net> (supplier of updated gnupg2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 13 Feb 2017 09:15:07 -0500
Source: gnupg2
Binary: gnupg-agent scdaemon gpgsm gnupg gnupg2 gpgv gpgv2 dirmngr gpgv-udeb gpgv-static gpgv-win32 gnupg-l10n
Architecture: source
Version: 2.1.18-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers <pkg-gnupg-maint@lists.alioth.debian.org>
Changed-By: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Description:
 dirmngr    - GNU privacy guard - network certificate management service
 gnupg      - GNU privacy guard - a free PGP replacement
 gnupg-agent - GNU privacy guard - cryptographic agent
 gnupg-l10n - GNU privacy guard - localization files
 gnupg2     - GNU privacy guard - a free PGP replacement (dummy transitional pa
 gpgsm      - GNU privacy guard - S/MIME version
 gpgv       - GNU privacy guard - signature verification tool
 gpgv-static - minimal signature verification tool (static build)
 gpgv-udeb  - minimal signature verification tool (udeb)
 gpgv-win32 - GNU privacy guard - signature verification tool (win32 build)
 gpgv2      - GNU privacy guard - signature verification tool (dummy transition
 scdaemon   - GNU privacy guard - smart card support
Closes: 648331 734889 852702 854005 854595 854616
Changes:
 gnupg2 (2.1.18-5) unstable; urgency=medium
 .
   [ Daniel Kahn Gillmor ]
   * Xsession.d/90gpg-agent: use simpler and more direct gpgconf
     invocations for socket names.
 .
   [ NIIBE Yutaka ]
   * scdaemon.udev: Add Yubikey and Nitrokey (Closes: #648331, 734889).
   * scdaemon fix for PC/SC (Closes: #852702, #854005, #854595, #854616).
Checksums-Sha1:
 7107ae53a9a7b92c96abd2189b34a0d9cd1fba99 3148 gnupg2_2.1.18-5.dsc
 b31b7f97466e99c49c4eb9320b6df12d32d87e78 67321 gnupg2_2.1.18-5.debian.tar.bz2
 a1c521fc8bf43272c59490065eef86cecf06821d 9975 gnupg2_2.1.18-5_source.buildinfo
Checksums-Sha256:
 8eb4d1d8bb97ac770e8f50e558046981fd6f1fea169ae5e74ac959a6d033a35d 3148 gnupg2_2.1.18-5.dsc
 e6dbc03c9a163baff078a47b0f7c023d8b830f80bf6ae486e6a580fbdb71d9c2 67321 gnupg2_2.1.18-5.debian.tar.bz2
 e24155aeaccd93a834ace33df252d57538679afff471235bb770af4140365ec8 9975 gnupg2_2.1.18-5_source.buildinfo
Files:
 cffe62364ca47384f8347317a5d1a673 3148 utils optional gnupg2_2.1.18-5.dsc
 950b349fb8ed2ee14a00155da3ae2650 67321 utils optional gnupg2_2.1.18-5.debian.tar.bz2
 f39a698baf6d532deab22cb867f3a4b3 9975 utils optional gnupg2_2.1.18-5_source.buildinfo

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

iQJKBAEBCgA0FiEEOCdgUepHf6PklTkyFJitxsGSMjcFAlihyfYWHGRrZ0BmaWZ0
aGhvcnNlbWFuLm5ldAAKCRAUmK3GwZIyN9UvD/0aFI/Jphk4kTyJC/bx5G7vcgpu
pPCrtlb5/FDvko1XJUMohcS8dFuMf7PPHpQZH31kjqawbQMSzVYhXy9wZL6r+hrg
xz68kJ1CgCTFO/HB+h1dTLASt4OuVGfKGpkuueXenR3kCY7Ghx8H6YOlhYRMtVT6
yWhdpGKHIvR82sCLN61iqMut3NTh47MB1QUmWd1zQPNoGPWLBK2dt7hNvqQWvFZ4
XXsGkjk6LQrZegX4JIrAEjsqIjXQlKJhOWnCA4+86EIVbjnUaYjZKX7q2dHOG21Y
DxT6rn4qx9PCMTR5krJPht4R1hbc6C0aZT4y3I6Cp53FS3uZGD84YxGYND9v5WSb
auu5FGwE0xN+RAbHOVTxh0lIuySJJTkIdX78kqsnuaSaNkXCfgiNo3xacs9uY+9d
TYKg17ouRsbnETkVqpDngTaaaY9pK6ajk/u3uyA3znEWp870ww/7gvrMjCl1gkfP
hinmFseLTKOvHQFlDAZb6HTj/V7SXqSr25hMpSoWNXC8ylypfh90fnDD+YNpFXMm
VND3eZTNtW/EEQTxiWVbDrWXFoIrFTioRHLlbH4rC3dkJ0RjxeMiKcKPzrap/5ht
6vu/nqkBgltt/8UPIctb+6Qe5czMFDJj8T+B/m3+sarCzjd4njHcn0Og4H4flvqY
M07IRiEkzX00kH824A==
=fpGR
-----END PGP SIGNATURE-----

Message #48 received at 854005-close@bugs.debian.org (full text, mbox, reply):

From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

To: 854005-close@bugs.debian.org

Subject: Bug#854005: fixed in gnupg2 2.1.18-5

Date: Mon, 13 Feb 2017 15:18:52 +0000

Source: gnupg2
Source-Version: 2.1.18-5

We believe that the bug you reported is fixed in the latest version of
gnupg2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854005@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor <dkg@fifthhorseman.net> (supplier of updated gnupg2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 13 Feb 2017 09:15:07 -0500
Source: gnupg2
Binary: gnupg-agent scdaemon gpgsm gnupg gnupg2 gpgv gpgv2 dirmngr gpgv-udeb gpgv-static gpgv-win32 gnupg-l10n
Architecture: source
Version: 2.1.18-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers <pkg-gnupg-maint@lists.alioth.debian.org>
Changed-By: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Description:
 dirmngr    - GNU privacy guard - network certificate management service
 gnupg      - GNU privacy guard - a free PGP replacement
 gnupg-agent - GNU privacy guard - cryptographic agent
 gnupg-l10n - GNU privacy guard - localization files
 gnupg2     - GNU privacy guard - a free PGP replacement (dummy transitional pa
 gpgsm      - GNU privacy guard - S/MIME version
 gpgv       - GNU privacy guard - signature verification tool
 gpgv-static - minimal signature verification tool (static build)
 gpgv-udeb  - minimal signature verification tool (udeb)
 gpgv-win32 - GNU privacy guard - signature verification tool (win32 build)
 gpgv2      - GNU privacy guard - signature verification tool (dummy transition
 scdaemon   - GNU privacy guard - smart card support
Closes: 648331 734889 852702 854005 854595 854616
Changes:
 gnupg2 (2.1.18-5) unstable; urgency=medium
 .
   [ Daniel Kahn Gillmor ]
   * Xsession.d/90gpg-agent: use simpler and more direct gpgconf
     invocations for socket names.
 .
   [ NIIBE Yutaka ]
   * scdaemon.udev: Add Yubikey and Nitrokey (Closes: #648331, 734889).
   * scdaemon fix for PC/SC (Closes: #852702, #854005, #854595, #854616).
Checksums-Sha1:
 7107ae53a9a7b92c96abd2189b34a0d9cd1fba99 3148 gnupg2_2.1.18-5.dsc
 b31b7f97466e99c49c4eb9320b6df12d32d87e78 67321 gnupg2_2.1.18-5.debian.tar.bz2
 a1c521fc8bf43272c59490065eef86cecf06821d 9975 gnupg2_2.1.18-5_source.buildinfo
Checksums-Sha256:
 8eb4d1d8bb97ac770e8f50e558046981fd6f1fea169ae5e74ac959a6d033a35d 3148 gnupg2_2.1.18-5.dsc
 e6dbc03c9a163baff078a47b0f7c023d8b830f80bf6ae486e6a580fbdb71d9c2 67321 gnupg2_2.1.18-5.debian.tar.bz2
 e24155aeaccd93a834ace33df252d57538679afff471235bb770af4140365ec8 9975 gnupg2_2.1.18-5_source.buildinfo
Files:
 cffe62364ca47384f8347317a5d1a673 3148 utils optional gnupg2_2.1.18-5.dsc
 950b349fb8ed2ee14a00155da3ae2650 67321 utils optional gnupg2_2.1.18-5.debian.tar.bz2
 f39a698baf6d532deab22cb867f3a4b3 9975 utils optional gnupg2_2.1.18-5_source.buildinfo

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

iQJKBAEBCgA0FiEEOCdgUepHf6PklTkyFJitxsGSMjcFAlihyfYWHGRrZ0BmaWZ0
aGhvcnNlbWFuLm5ldAAKCRAUmK3GwZIyN9UvD/0aFI/Jphk4kTyJC/bx5G7vcgpu
pPCrtlb5/FDvko1XJUMohcS8dFuMf7PPHpQZH31kjqawbQMSzVYhXy9wZL6r+hrg
xz68kJ1CgCTFO/HB+h1dTLASt4OuVGfKGpkuueXenR3kCY7Ghx8H6YOlhYRMtVT6
yWhdpGKHIvR82sCLN61iqMut3NTh47MB1QUmWd1zQPNoGPWLBK2dt7hNvqQWvFZ4
XXsGkjk6LQrZegX4JIrAEjsqIjXQlKJhOWnCA4+86EIVbjnUaYjZKX7q2dHOG21Y
DxT6rn4qx9PCMTR5krJPht4R1hbc6C0aZT4y3I6Cp53FS3uZGD84YxGYND9v5WSb
auu5FGwE0xN+RAbHOVTxh0lIuySJJTkIdX78kqsnuaSaNkXCfgiNo3xacs9uY+9d
TYKg17ouRsbnETkVqpDngTaaaY9pK6ajk/u3uyA3znEWp870ww/7gvrMjCl1gkfP
hinmFseLTKOvHQFlDAZb6HTj/V7SXqSr25hMpSoWNXC8ylypfh90fnDD+YNpFXMm
VND3eZTNtW/EEQTxiWVbDrWXFoIrFTioRHLlbH4rC3dkJ0RjxeMiKcKPzrap/5ht
6vu/nqkBgltt/8UPIctb+6Qe5czMFDJj8T+B/m3+sarCzjd4njHcn0Og4H4flvqY
M07IRiEkzX00kH824A==
=fpGR
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.