[pkg-gnupg-maint] Bug#814584: gnupg2: gpg2 --card-status fail on armel / Raspberry Pi - "Card error"

Petter Reinholdtsen pere at hungry.com
Wed Aug 3 12:03:52 UTC 2016

[NIIBE Yutaka]
> OK, I located the issue for ccid-driver.  It is fixed in our
> repository.
> master:
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=971064f8b7ad676326b2a468f688037a303717df
> 2.0.x:
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=c68d39f7114623075c0b407b05927b61b190a377
> I don't know if this is all for the problem, but it will improve the
> situation.

Thank you.  I just tested on a Raspberry Pi using the gnupg2/scdaemon
version 2.1.14-2 in Debian experimental, and this now segfaults when I
try 'gpg2 --card-status'.  But for some reason I can't get info from
valgrind, so here is the backtrace from gdb:

Program received signal SIGSEGV, Segmentation fault.
0xb6cbc020 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) bt
#0  0xb6cbc020 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x7f5b2174 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

But I do not quite understand why the old code should work on amd64 but
not on arm.

> Umm... IIUC, it is pcsc service which let "power on" the card.
> I don't know why it fails.
> Running pcscd foreground with debug option shows more information
> (I mean, pcscd --foreground --debug).
> Please see:
> http://ludovicrousseau.blogspot.jp/2011/07/pcscd-debug-output.html


Happy hacking
Petter Reinholdtsen

More information about the pkg-gnupg-maint mailing list