739630 – app-crypt/gnupg-2.2.22: Nitrokey is no longer used automatically after booting

Bug 739630 - app-crypt/gnupg-2.2.22: Nitrokey is no longer used automatically after booting

Summary: app-crypt/gnupg-2.2.22: Nitrokey is no longer used automatically after booting

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Kristian Fiskerstrand (RETIRED)

URL:
Whiteboard:
Keywords:	REGRESSION

Depends on:
Blocks:

Reported:	2020-08-30 14:34 UTC by Michał Górny
Modified:	2020-09-01 09:43 UTC (History)
CC List:	2 users (show)

See Also:	https://dev.gnupg.org/T5039
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michał Górny archtester

2020-08-30 14:34:43 UTC

gpg 2.2.21 automatically detected and used my Nitrokey after booting the system.  In other words, I did 'gpg -d foo.gpg', it asked for PIN and decrypted the file.

gpg 2.2.22 doesn't detect Nitrokey after boot:

$ gpg -d ~/cvc2.gpg 
gpg: encrypted with 4096-bit RSA key, ID 580C5E1242C5AD46, created 2013-02-20
      "Michał Górny (Gentoo) <mgorny@gentoo.org>"
gpg: public key decryption failed: End of file
gpg: decryption failed: No secret key


I need to manually issue 'gpg --card-status' to make it start working.

Comment 1 Mikle Kolyada (RETIRED) archtester

2020-09-01 09:43:58 UTC

patch backported.