El jue, 21-04-2011 a las 22:42 +0200, Frank Morgner escribió: > Hi! > > > > I guess there's some kind of (international/EU) standard for travel > > > documents (ICAO MRTD?) that define names for common fields of such > > > documents. That could be used as a reference, probably there's even > > > a standardized translation available somewhere under *.eu > > http://openmrtd.org/projects/libmrtd/ > Did you implement basic access control (BAC) for an MRTD via MRZ, Juan? > If yes, the protocol should be the same for all cards. So something > driver/card specific should not be needed, but a program implementing > BAC with OpenSC is nice.
At all: My proposal (and Martin's) is just to extend eidenv functionality to convert it in a general card independent tool to extract non-pkcs15 related data from any card that supports them. Which data is available is card-dependent, and has no relation with mrtd. In OpenDNIe I've written a "dnie-tool" that does allmost the same that eidenv does, and Martin suggested me to patch eidenv to make it card independent and unify every xxx-tool that only handle non-pkcs15 related data Martin's proposal on ICAO MRTD was just for use an standard for required fields and nameing convention, not to implement BAC on OpenSC. Juan Antonio _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
