Rich Wareham
Fri, 29 Jun 2001 06:07:10 -0700
The MFC docs claim it to be ISO 7816 compliant. Is there anyone who has has success reading IBM MFC cards with a GemPlus reader? Rich On Fri, 29 Jun 2001, Peter Tomlinson wrote: > >From ISO 7816-3:1997, ATR looks like: > > 3B Direct data convention > EF TB1, TC1, TD1 present, 15 historical bytes > 00 TB1 Vpp not used > FF TC1 Min delay between character transmissions is default value (11 etu > for T=1) > 81 TD1 T=1 protocol only, TD2 is present > 31 TD2 TB3 and TC3 present > FF TB3 BWI for T=1 not as per ISO (value F is 'reserved'), CWI for T=1 = 15 > 65 TC3 Bit 0 says LRC used in T=1, other bits should be all be set to zero > for ISO 7816 > Historical bytes say: IBM MFC92292890, where the first byte (49) both says > that the hist bytes are not coded as per 7816-4 and also is the character > 'I' as the start of 'IBM' > > I seem to remember that the IBM MFC card is an ETSI TE9 / CEN EN726 > (telecoms standard) card, and not an ISO 7816 card... > > Peter T > Bristol UK > > ----- Original Message ----- > From: "Rich Wareham" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, June 29, 2001 9:49 AM > Subject: MUSCLE Error using an IBM MFC in GemPlus readers. > > > > > > Hello, > > > > I am currently porting some Windows software for the management of > > smartcards over to Linux, the cards in question are IBM MFC 4.22 smart > > cards. I get the same error on card power up from both the GemPlus 410 > > serial and GemPlus 430 USB card reader when using the PCSClite drivers. In > > both cases the drivers send the following OROS command: > > > > 12 > > > > which attempts to power up the card and return the ATR, the response is > > > > A0 3B EF 00 FF 81 31 FF 65 49 42 4D 20 4D 46 43 39 32 32 39 32 38 39 30 17 > > > > The first byte is an error code which is, according to the GemPlus docs, > > "Error in the card reset response, such as unknown exchange protocol, or > > byte TA1 not recognized [sic]. The card is not supported by OROS. The card > > reset response is nevertheless returned." > > > > Since I'm rather new to smart-card programming, could someone tell me what > > this means and who is at fault. > > > > BTW, the same readers and cards work fine with PC/SC under Windows. > > > > Rich > > > > -- > > rich > > > > The box says 'Requires Win95 or better' so it /must/ run under Linux > > > > *************************************************************** > > Linux Smart Card Developers - M.U.S.C.L.E. > > (Movement for the Use of Smart Cards in a Linux Environment) > > http://www.linuxnet.com/smartcard/index.html > > *************************************************************** > > > > *************************************************************** > Linux Smart Card Developers - M.U.S.C.L.E. > (Movement for the Use of Smart Cards in a Linux Environment) > http://www.linuxnet.com/smartcard/index.html > *************************************************************** > -- rich The box says 'Requires Win95 or better' so it /must/ run under Linux *************************************************************** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***************************************************************