“Hardware problem” with OpenPGP smart card

[Nicolas Boullis]

Hi,

On Sun, Dec 06, 2020 at 12:37:19PM +0100, Werner Koch wrote:
> 
> To make sure that this is really the card (or reader), I'd like to ask
> you to put
> 
> --8<---------------cut here---------------start------------->8---
> log-file /some/path/scd.log
> verbose
> debug cardio
> --8<---------------cut here---------------end--------------->8---
> 
> into scdaemon.conf.  Kill scdaemon.conf and retry. You should see a line
> with status code 0x6581 (EEPROM FAILURE) in response to a VERIFY (00 20
> ... PIN) APDU or a PSO (00 2A ....) APDU.  If that is the case you are
> probably out of luck.  It is a rare thing; iirc, I recall one other
> report about a hardware failure.

Thanks for your suggestion.
I just tried it, and found, in the scd.log file:

2020-12-06 16:26:24 scdaemon[4732] DBG: send apdu: c=00 i=20 p1=00 p2=82 lc=8 le=-1 em=0
2020-12-06 16:26:24 scdaemon[4732] DBG:  raw apdu: 00 20 00 82 08 ***PIN***
2020-12-06 16:26:24 scdaemon[4732] DBG:  response: sw=6581  datalen=0
2020-12-06 16:26:24 scdaemon[4732] verify CHV2 failed: Hardware problem
2020-12-06 16:26:24 scdaemon[4732] operation decipher result: Hardware problem
2020-12-06 16:26:24 scdaemon[4732] app_decipher failed: Hardware problem

Do you think there is still a chance that the reader is at fault rather 
than the smartcard?
Any hope besides replacing the smartcard *and the subkeys*?


Thanks for your help,

-- 
Nicolas