Incidentally this ATR matches a Vasco CertiID initialized CardOS4.3b card, could that be what you have? I've investigated (sniffed) a card like this and found 3 anomalies (from a pkcs15-perspective): Empty/zero-filled EF(TokenInfo), wrong padChar in EF(AODF) pin object, missing pinReference in EF(AODF) (sniffed value used in VERIFY is 0x06).
Cheers, /Mats On 11/16/09 9:15 AM, "JP Szikora" <jean-pierre.szik...@uclouvain.be> 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? 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.
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
