From: Johannes B. <Joh...@hr...> - 2013-08-06 09:53:10
|
Am Dienstag 06 August 2013 schrieb Viktor Tarasov: > Strange. I don't sufficiently know this card. > Have no this kind of problems with the one that I have -- also CardOS 4.3b. > > Does it formatted with OpenSC? No, it's formatted by cryptovision. I have a log of cryptovision's scManger replacing the certificate: http://www.uni-giessen.de/~g013/opensc/scMan-Import-Cert.txt There you have the line 00000050 APDU: 00 E4 00 00 02 43 02 which - I presume - deletes the file 4302. If I try to send this apdu with opensc-explorer, I again get the INS-error: $ opensc-explorer OpenSC Explorer version 0.13.0 Using reader with a card: Dell Dell Smart Card Reader Keyboard 00 00 OpenSC [3F00]> cd 5015 OpenSC [3F00/5015]> cd 4304 OpenSC [3F00/5015/4304]> apdu 00 20 00 81 0A 32 33 34 35 36 37 FF FF FF FF Sending: 00 20 00 81 0A 32 33 34 35 36 37 FF FF FF FF Received (SW1=0x90, SW2=0x00) Success! OpenSC [3F00/5015/4304]> apdu 00 E4 00 00 02 43 02 Sending: 00 E4 00 00 02 43 02 Received (SW1=0x6D, SW2=0x00) Failure: Unsupported INS byte in APDU > Question aside, > why do you manually erase the certificate file? After that you will need, > also manually, update the PKCS#15 CDF data? > Would it be better for you to use the pkcs15-init tool? It knows what to do > with these data. > There the PIN is not accepted: $ pkcs15-init --pin 234567 --id 46 --update-certificate Testperson1117-46.pem Using reader with a card: Dell Dell Smart Card Reader Keyboard 00 00 Failed to store data object: PIN code or key incorrect I suppose this is because the maximal PIN length is 10. Kind regards Johannes |