Perhaps anyone can help me:
Now that my DNIe has died [1] I'm trying to get dni code to be aware of this
situation.
¿What's the standard way to tell libopensc that a card has been invalidated?,
that is: the card is recognized,
but cannot operate with it because manipulation detected, too many
[...]
Not sure on other cards, but DNIe mark this situation by mean of
change on ATR status code from 03 90 00 to
0F 65 81 (Memory error). Not sure what to do if detected this
situation:
1. When data structures of your card are still readable, then match on
both ATRs. And fail
On 9/14/2010 8:27 AM, Andre Zepezauer wrote:
On Tue, 2010-09-14 at 14:38 +0200, jons...@terra.es wrote:
[...]
Not sure on other cards, but DNIe mark this situation by mean of
change on ATR status code from 03 90 00 to
0F 65 81 (Memory error). Not sure what to do if detected this
On Sep 14, 2010, at 4:43 PM, Douglas E. Engert wrote:
In older versions of many of the tools, like pkcs15-tool, the
opensc.conf debug level is reset to the verbose:
pkcs15-tool.c: Verbose operation. Use several times to enable debug
output.,
pkcs15-tool.c: ctx-debug =
On 9/14/2010 8:58 AM, Martin Paljak wrote:
On Sep 14, 2010, at 4:43 PM, Douglas E. Engert wrote:
In older versions of many of the tools, like pkcs15-tool, the
opensc.conf debug level is reset to the verbose:
pkcs15-tool.c: Verbose operation. Use several times to enable debug
output.,
On Tue, 2010-09-14 at 16:04 +0200, jons...@terra.es wrote:
[...].
Supposed that the attached log file is complete, then the card fails
on
receiving the first APDU. In this case the card provides only it's
ATR
and nothing more. This makes it less useful and thus I would prefer
to
