On Wed, May 31, 2006 at 08:29:56AM +0200, Ludovic Rousseau wrote: > Hello, > > On 30/05/06, Henryk Plötz <[EMAIL PROTECTED]> wrote: > >I'm currently in the process of trying to write an ifd handler to be > >able to use librfid in openct (and therefore in opensc and pc/sc) to be > >run with the librfid that uses a patched openct ccid ifd handler that > >offers the ESCAPE protocol. (E.g. I'm talking about a cardman 5121 > >here.) > > [...] > > >The current way of having an openct ifd handler calling a library that > >calls another openct ifd handler seems to be ugly. For the future it > >would be nice to have the contact-less support in the same ifd as the > >contact-based part, e.g. as an additional slot (or even several slots, > >because I've been told that 4 cards should be possible). This would > >also nicely solve hotplug. Of course the most easy way would be to > >subclass the ccid handler, if there was something like subclassing in C. > > I don't have a Cardman 5121 so what I write may not apply to the Cardman 5121. > > The SCM Micro SCR 331-DI and the SCM Micro SDI 010 are contact + > contactless readers. They are seen a one reader with two slots under > pcsc-lite with my CCID driver [1]. The contactless slot uses normal > APDU and the reader firmware manages T=CL (or whatever it is) itself.
Yes, thats one (I think extremely limited) layer of abtstraction which is done in some readers. Basically you have readers where the 14443-1234 implementation resides completely in firmware (such as Integrated Engineering), readers where some bits are in firmware and others on the host (such as Philips Mifare Pegoda RD-700) and readers where the whole stack resides on the host (such as Omnikey cm5121). I personally preferr 'stupid' readers since it gives more flexibility to the driver. You can talk to i-code, mifare, 14443-4(T=CL), 15693, etc. - you can activate multiple cards, you can do whatever you want. Readers with firmware protocol implementations are all limited to some subset of the theoretical functionality that a contactless 13.56MHz reader offers. librfid IMHO has to stay independent of openct, exactly for this reason. OpenCT is nice for anything that resembles traditional smartcard operation (e.g. operating a single 14443-4 compliant card in one virtual slot). But for anything more RFID related (and less smartcard related), OpenCT is not a good choice. > The OmniKey CardMan 5125 is also a dual interface reader and is > reported as "should work" with my CCID driver. But I didn't tested it > myself and do not remember if the contactless interface is also > available from my CCID driver. the 'should work' refers to the contact based part of the reader. -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ ============================================================================ We all know Linux is great...it does infinite loops in 5 seconds. -- Linus
pgpgenlGptVdv.pgp
Description: PGP signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
