Do you know if your cards comply with ISO 7816? Or perhaps they use one of
the other interface protocols not recognised by ISO (e.g. I2C). Or maybe its
the other way round: your cards are 7816 compliant but the reader is not.
Memory cards are an area where you have to be sure that the card and
Yes, Jim, I agree. But it should also tell the app in the terminal what it
has selected.
Peter Tomlinson
Bristol UK
- Original Message -
From: "Jim Rees" [EMAIL PROTECTED]
To: "Smart Muscleheads" [EMAIL PROTECTED]
Sent: Sunday, January 07, 2001 10:38 PM
Subject: Re:
T=14 is the indicator for proprietary protocols. Information about a
particular card's T=14 protocol can only come from the supplier.
EMV does indeed have a description of a protocol called T=1, but its a bit
different (in control parameter definitions and error recovery) from ISO -
but neither
, please
email me, including information about which country you are in, and we will
see what we can do to help you from the UK.
Regards,
Peter Tomlinson
Bristol UK
email [EMAIL PROTECTED] , web www.iosis.co.uk
- Original Message -
From: "ChongVa Cheong" [EMAIL PROTECTED]
To: [EMAIL
At risk of being declared off the topic, I add the following:
The situation can be even worse than Guido describes, because ISO allows a
card to refuse to accept (which means that it will give an error response)
standard ISO 7816-4 file handling commands unless a prior mutual
authentication
David,
Why reset the card twice? ISO doesn't say that the card must always give the
same ATR from a warm reset as from a cold reset, and EMV in particular take
advantage of this to insist that the card must send a 'basic ATR' (i.e. one
which says 'I will run with the startup parameters, but here
when trying to spec an
interoperable set of schemes.
Can anyone provide a dual interface ISO 7816 and 14443 card platform that
supports direct AID addressing for application selection?
Regards (or should it be commiserations?),
Peter Tomlinson
- Original Message -
From: "Friendly
that his cards take less power current than the maximum limit in the ISO
spec). However, be sure to test card and reader with the type of PC that you
are going to use, because different types of driver ICs in the PC have
different source impedances.
Regards,
Peter Tomlinson,
Bristol UK
Volts Vcc)
FI = 3 (means Fi = 744), Di = 2 also gives a bit rate of 9600 in our
example, but changes the wwt to 2 sec, and indicates (Table 7) a max clock
frequency of 8 MHz (e.g. for a Hitachi 3109 card as used by rollout spec
Mondex in a single application environment)
Regards,
Peter Tomlinson
34
On 7 June 2001 Carlos Prados wrote
Re: MUSCLE Work Waiting Time question
Hi,
It seems, therefore, that changing the value of Di
in the ATR does not
change the value of the wwt, but changing the value
of Fi does. Is this what
the writers of 7816-3:1997 meant? I don't think so,
Very interesting, but the text from Sun is not at all clear. If the smart
card really is connected [directly] to the I2C interface, this reader will
only accept I2C interface memory cards.
But because I2C is not 7816 compliant, one would expect that the reader
module has a 7816-compliant slot,
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
Purchase ISO 7816 parts 3 and 4 to understand the low level communication
between card and IFD (Terminal, card reader).
Peter T
Bristol UK
- Original Message -
From: Joe Phillips [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Wolf Geldmacher [EMAIL PROTECTED]
Sent: Thursday, August 02, 2001
The clean way to organise this is:
(a) An application in the terminal issues APDUs
(b) The software layer receiving the APDU knows whether the card is being
operated with T=0 or T=1, and sends information down to the card driver as
appropriate; if T=0 and a case 4 APDU, the APDU is split into a
CLA INS P1 P2 Lc data Le in 7816-4 speak (section 5.3.1 Fig 3)
Peter T
Bristol UK
- Original Message -
From: David Corcoran [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 31, 2001 9:26 PM
Subject: Re: MUSCLE Is 61xx handled in your driver?
I think you should handle the
15 matches
Mail list logo
