|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
[Muscle] CCID pinpad, TeleTrust Class 2
From: Martin Paljak (martin.paljak
gmail.com)
Date: Thu Mar 03 2005 - 18:50:48 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello all,
Here are patches against latest pcsc-lite and ccid libraries, that:
(again, all are incompatible ;)
* Introduce pin modification capability to ccid readers (tested with
SPR 532, fw 5.05)
* Change the implementation to rflect TeleTrust understanding of thing
(in theory this should be a step towards multiplatform pinpad support
via ccid)
* introduce a few constants and lifts code around as it is needed for
the implementation. (Windows has SCARD_CTL_CODE,
http://doc.ddart.net/msdn/header/include/winsmcrd.h.html)
* make the pinpad functions return sensible CTBCS defined values to
application when user cancels pin operations or they time out
* Some other stuff i don't care or can't remember 02.39 am ....
To quote Torsten Maykranz from SCM:
I'm convinced, that this will be THE standard for PIN handling under PC/SC:
V1.14 was defined by 3 manufacturers: Omnikey, Kobil and SCM Cherry
and Reiner will follow this way Gemplus was very active in the
discussion in the PC/SC workgroup, therefore I assume, they will use
this spec for their new readers too -> the biggest market players will
follow this standard,
....
the actual schedule of the PC/SC workgroup is to publish a release
version of this document in April 2005
So get the related docs from here:
http://martin.paljak.pri.ee/download/esteid/ccid/docs/
patch for ccid from here:
http://martin.paljak.pri.ee/download/esteid/patches/ccid-teletrust.diff
patch for pcsc from here:
http://martin.paljak.pri.ee/download/esteid/patches/pcsc-teletrust.diff
It is most probly a bit hairy, but at least a move in some direction.
There are currently some inconsistencies in ccid spec (no way to know
when pin1 and pin2 don't match when chaning a pin) and teletrust spec
(CCID structures differ in minor ways from the structures defined in
CCID spec)
Those who read both lists - please excuse for spamming.
Feedback welcome. 'Example application' will be available in nearest
days (Pin modification for OpenSC)
--
Martin Paljak - consultant
martin.paljak
gmail.com - Gmail
http://martin.paljak.pri.ee/ - web
+372.5156495 - phone
_______________________________________________
Muscle mailing list
Muscle
lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]