[pkg-gnupg-maint] Bug#889751: scdaemon: BAD PIN since 2.2.4-2 upgrade

[Yves-Alexis Perez]

On Tue, 2018-02-06 at 20:42 +0100, Yves-Alexis Perez wrote:
> Hi,
> 
> since the recent 2.2.4-2 upgrade, when trying to use my smartcard (auth
> key for SSH for example), I get:
> 
> févr. 06 20:37:35 scapa gpg-agent[1793]: scdaemon[26257]: verify CHV2 failed: Bad PIN
> févr. 06 20:37:35 scapa gpg-agent[1793]: scdaemon[26257]: app_auth failed: Bad PIN
> févr. 06 20:37:35 scapa gpg-agent[1793]: smartcard signing failed: Bad PIN
> 
> even though I'm sure it's the right PIN.
> 
> At that point I'm a little reluctant in doing another try because it's
> the last one before I need to get my admin PIN.
Downgrading scdaemon, gpg-agent and gpgconf to 2.2.4-1 fixes the problem. If
you need more information, please ask.

I've raised the severity to important, but actually I don't think scdaemon
should migrate to testing as-is, so I'd be inclined to raise again to RC
severity.

Regards,
-- 
Yves-Alexis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20180207/c1b4d251/attachment.sig>