On 26 August 2011 08:24, Ludovic Rousseau <[email protected]> wrote:
> raw apdu: 00 20 00 83 08 31 32 33 34 35 36 37 38
> response: sw=6985
>
> Your APDU looks correct with pin code 12345678
> card answer is 6985: "Conditions of use not satisfied."
> Do you have the same error with a different PIN?

Yes, for both user PIN and admin PIN a wrong PIN gives the same error
and the retry counter does not go down.

> Have you locked your card?

Not that I know of. It is fresh out of the envelope, with a piece of
paper just telling me the default PINs and advising that a blocked PIN
can be reset with admin PIN etc. I have tried the reset file...

On 26 August 2011 08:25, Martin Paljak <[email protected]> wrote:
> Don't know for sure, maybe --card-status shows something? Maybe the
> card is in deactivated state and you need to run the last apdu from
> the "erase" sequence (activate file iirc)?

Here is --card-status:

Application ID ...: (I'll leave this out)
Version ..........: 2.0
Manufacturer .....: ZeitControl
Serial number ....: (I'll leave this out)
Name of cardholder: [not set]
Language prefs ...: de
Sex ..............: unspecified
URL of public key : [not set]
Login data .......: [not set]
Signature PIN ....: forced
Key attributes ...: 2048R 2048R 2048R
Max. PIN lengths .: 32 32 32
PIN retry counter : 3 0 3
Signature counter : 0
Signature key ....: [none]
Encryption key....: [none]
Authentication key: [none]
General key info..: [none]

Having read in the spec about life cycle status, I see my log includes:

2011-08-26 09:36:28 scdaemon[11914] Historical Bytes: 00 31 C5 73 C0
01 40 05 90 00

of which I believe 05 is the life cycle status and means operational.

The reset file I'm using is this:

/hex
scd serialno
scd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40
scd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40
scd apdu 00 e6 00 00
scd apdu 00 44 00 00
/echo card has been reset to factory defaults

This seemed strange from reading the spec: ending with Activate File
(E6) and then Terminate DF (44)? I have tried duplicating the E6 line
onto the end of the file, but it did not help. In all reset attempts,
all of these commands had responses 6985 except Terminate DF (44),
which had 9000 (ok). None of these attempts changed the --card-status
output or the Historical bytes.

-- 
Chris Boyle
http://chris.boyle.name/
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to