Mats Andersson wrote:
The pinReference seems to be 0x06, padChar is 0xff. (EF(AODF) is
wrong/incomplete). I found this while sniffing this card. OpenSC
doens't like that card for two other reasons as well. First it has
it's own DF for pkcs15 (found in EF(DIR), add this to apps[] in dir.c:
{ (const u8 *) "\xE8\x28\xBD\x08\x0F\x00\xA0\x00\x00\x02\x24", 11,
"Vasco P15" }
Secondly the EF(TokenInfo) just contains zeros (making
sc_pkcs15_parse_tokeninfo() angry).
Cheers,
/Mats
Is it possible to buy somewhere 2-3 cards CardOS, that will be accepted
by OpenSC (formatted, initialized, ...)?
Viktor.
On 11/16/09 3:00 PM, "JP Szikora" <jean-pierre.szik...@uclouvain.be>
wrote:
Viktor TARASOV a écrit :
> JP Szikora wrote:
>> Viktor TARASOV a écrit :
>>>
>>> I would try to prepare patch, but actually I have no CardOS card
>>> recognized by OpenSC .
>>> The card CardOS that I have is:
>>> 3b:fb:18:00:02:c1:0a:31:fe:58:56:44:53:43:34:c8:08:00:00:00:01:4a
>>> Info : CardOS V4.3B (C) Siemens AG 1994-2004
>>> Chip type: 124
>>>
>>> Any help would be greatly appreciated.
>>>
>> Hi Viktor,
>>
>> You have a strange CardOS card ;-) The ATR is not the usual CardOS
>> 4.3B (but that can be changed) and the chip type is usually 123. Can
>> you send a complete output of the cardos-info command?
> Hi Jean-Pierre,
>
> here it is:
>
> 3b:fb:18:00:02:c1:0a:31:fe:58:56:44:53:43:34:c8:08:00:00:00:01:4a
> Info : CardOS V4.3B (C) Siemens AG 1994-2004
> Chip type: 124
> Serial number: 27 20 ab 15 2a 12
> Full prom dump:
> 33 66 00 1B 5B 5B 5B 5B 7C FF 27 20 AB 15 2A 12 3f..[[[[|.' ..*.
> 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: 16 (operational)
> Security Status of current DF:
> Free memory : 818
> ATR Status: 0x128 unknown
> Packages installed:
> E1 09 01 04 13 02 C8 08 8F 01 01 ...........
> Ram size: 4, Eeprom size: 64, cpu type: 66, chip config: 63
> Free eeprom memory: 41116
> System keys: PackageLoadKey (version 0x00, retries 10)
> System keys: StartKey (version 0xff, retries 10)
> Path to current DF:
>
>
> This card has been formated with Vasco tools, it contains some
PKCS#15
> system.
> I know the values of PIN, SOPIN(PUK ?) but I could not verify any of
> the PINs referenced in it's EF.AOD .
Hi Viktor,
You have a 64k Cardos 4.3B card. The StartKey is still the default one
(0xFF), but probably the erase command is protected or blocked at the
ACL level. Need a deeper analysis. I'm not sure you can do too
much with
OpenSC and this externally formatted card. With opensc-explorer,
you can
always try to look and to understand the structure of your card.
Maybe the best is to find an clean CardOS 4.3B to play with it.
Cheers,
Jean-Pierre
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
Scanned by Check Point Total Security Gateway.
--
Viktor Tarasov <viktor.tara...@opentrust.com>
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
