OpenPGP card bricked

[Peter Lebbing]

On 13/03/18 15:34, Matthias Apitz wrote:
> Is there some config missing so that scdaemon opens directly the reader?
> What does 'pcsc_establish_context failed' mean?

A notable difference between the built-in CCID driver and pcscd is probably the
user credentials that open the USB device. Make sure you have write access to
the character device in /dev/bus/usb that corresponds to your smartcard:

$ lsusb
[...]
Bus 001 Device 006: ID 04e6:e003 SCM Microsystems, Inc. SPR532 PinPad SmartCard
Reader
[...]
$ ll /dev/bus/usb/001/006
crw-rw-r--+ 1 root root 189, 5 Mar 13 15:55 /dev/bus/usb/001/006
$ getfacl /dev/bus/usb/001/006
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/001/006
# owner: root
# group: root
user::rw-
user:peter:rw-
group::rw-
mask::rw-
other::r--

Also, if I were you, I'd clean the smartcard contacts with isopropyl alcohol.
I'm not sure what other cleaning agents would work well, I just use that one.

It could be that your card has just died. Smartcards are not the most robust
devices, and they are subjected to stress usually.

HTH,

Peter.

PS: I'm not 100% sure that libusb opens that particular character device... I
believe it's the correct one, but wouldn't swear on it.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180313/b9d736ef/attachment.sig>