On 14/02/07, Justin Karneges <[EMAIL PROTECTED]> wrote:
Hi folks,
Hello,
It seems that there are 4 communication areas: 1) I/O to the smart card 2) I/O to the reader 3) filesystem layout/control for reading 4) filesystem layout/control for all else There would appear to be a standard for #1. I don't remember what it is called, but it involves the ATR and then T=0 or 1 and friends.
I think you are talking about ISO 7816-3 "Identification cards -- Integrated circuit cards -- Part 3: Cards with contacts -- Electrical interface and transmission protocols"
However, my experience with hacking on the Eutron driver showed that that either there are still vendor-specific issues (bugs? workarounds?) to iron out, or OpenCT is simply incomplete.
You should describe your problem.
For #2 we have CCID. This seems to be about the only thing we can count on to work. Can anyone correct me?
It depends on what you call "the only thing we can count on to work" I agree that CCID simplify the use of smart card readers since the same driver can be used by many readers.
For #3 we have PKCS#15. Why this only applies to reading, I don't know, but 99% of smart card applications are read-only so this is still a very worthy standard, if it works as advertised that is. Are there any known cases where PKCS#15 software has been incompatible for read access?
Be more specific in your question.
And then there's ICCD. I briefly looked at the usb.org PDF file, and indeed it does look like a standard for integrated USB crypto tokens. It is dated April 2005. Does anyone know what is going on with this specification, or if any devices are in development for it?
Some devices using ICCD are already available. Axalto has an ICCD e-gate for example. I don't know the exact commercial name.
Correct me if I'm wrong, but would ICCD count as a standard for both #1 and #2?
I think you are right.
I'm confused about this, because if we already have a standard for #1 (ATR, T=0, whatever), then it doesn't seem like we need the ICCD spec at all. CCID would be enough.
An ICCD device is _one_ chip being the reader _and_ the smart card. You don't have to define a protocol between the reader and the card since both are in the same chip. All you need is an access to the "reader". Bye, -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
