Eric Norman wrote: ... >>> # cardos-info >>> Info : CardOS V4.3B (C) Siemens AG 1994-2004 >>> Chip type: 123 >>> Serial number: 56 71 90 17 32 11 >>> Full prom dump: >>> 33 66 00 40 EB EB EB EB 7B FF 56 71 90 17 32 11 [EMAIL PROTECTED] >>> 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................ >>> OS Version: 200.8 (that's CardOS M4.3b) >>> Current life cycle: 52 (manufacturing) >> that is the problem. If a cardos card is the state "manufacturing" >> you need proprietary (=> we cannot include them in opensc) scripts >> to "open" the card etc. (in the "manufacturing" state most normal >> card operations aren't available). > > That's curious. A few years ago, I was able to put a messed up > eToken back in the "manufacturing" state (as told by cardos-info) > using an APDU that someone sent to the list (it might have been > Nils). After that, I was able to re-initialize the eToken using > pkcs15-init --create-pkcs15 ... > > I repeat; this was a few years ago and with a different CardOS > version. So I don't know if this is helpful or not.
unless you know what you do this can be dangerous (for the card). In this case one needs at least to scripts: one to set the "startkey" to 0xff,0xff,... and another to open the card (plus optional scripts to load service packs and some additional modules). Unfortunately these scripts are afaik not public ... Nils _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
