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
Justin Karneges wrote:
Hi folks,
I'm just trying to wrap my head around all of the various protocols involved
in smart card use, and today I was reading the OpenSC website and it got my
mind going again. I'm glad that the website finally discusses these
important details.
Now, PKCS#11,
Justin Karneges wrote:
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. However, my
experience with hacking on the Eutron driver showed that that either there
are still vendor-specific issues (bugs?
On Thursday 15 February 2007 12:02 am, Ludovic Rousseau wrote:
On 14/02/07, Justin Karneges [EMAIL PROTECTED] wrote:
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
On Thursday 15 February 2007 7:14 am, Douglas E. Engert wrote:
Yes propriety vendor solutions are a major problem. Have a look at the
PIV card comments at:
http://www.opensc-project.org/opensc/wiki/UnitedStatesPIV
The intent is to standardize on multiple vendors for cards,
multiple
Justin Karneges wrote:
On Thursday 15 February 2007 7:14 am, Douglas E. Engert wrote:
Yes propriety vendor solutions are a major problem. Have a look at the
PIV card comments at:
http://www.opensc-project.org/opensc/wiki/UnitedStatesPIV
The intent is to standardize on multiple vendors for
