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

[NIIBE Yutaka]

On 06/12/2016 04:51 AM, Petter Reinholdtsen wrote:
> Hi, and sorry it took so long before I had time to revisit this issue.

No problem.

>> (4) To debug scdaemon, please have the following configuration file.
>>     Note that it may log your PIN information, so, don't send the log
>>     when you do authenticate the card (or change your PIN before your
>>     experiment and debug).
> 
> I did this, and got this content in /run/user/1000/scd.log when I ran
> 'gpg2 --card-status':
> 
> 2016-06-11 21:46:26 scdaemon[16023] listening on socket `/tmp/gpg-x5maJc/S.scdaemon'
> 2016-06-11 21:46:26 scdaemon[16023] handler for fd -1 started
[...]
> 2016-06-11 21:46:26 scdaemon[16023] DBG: ccid-driver: usb_claim_interface failed: -1
> 2016-06-11 21:46:26 scdaemon[16023] PC/SC OPEN failed: no service (0x8010001d)

It successfully got the information of the USB device.  But, if fails
at usb_claim_interface.  After that, it tries to use PC/SC, and fails too
(because there is no PC/SC service on your host).

Most common cause of failures at usb_claim_interface is permission
problem.  Do you have a permission to access the USB device?

In my case (Debian experimental), now, I have UDEV rules.

    /lib/udev/rules.d/60-scdaemon.rules

For my token, I wrote this page:

    http://www.fsij.org/doc-gnuk/udev-rules.html#udev-rules-for-gnuk-token

You can prepare a file, say, /etc/udev/rules.d/60-scdaemon.rules, with
following content:

    SUBSYSTEMS=="usb", ATTRS{idVendor}=="08E6",
ATTRS{idProduct}=="3438",   \
    ENV{ID_SMARTCARD_READER}="1", ENV{ID_SMARTCARD_READER_DRIVER}="gnupg"

If you are using udev.
-- 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20160615/7413f9a6/attachment.sig>