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
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://open
Martin Paljak wrote:
> > - Needs a consensus on variable list,names and so
>
> 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 standard
Hello,
On Apr 19, 2011, at 18:08 , Juan Antonio Martinez wrote:
> Studing eidenv code and how I did it in opendnie, I suggest a change to
> make eidenv.c card independent, and rely in each card driver the work of
> get (when available) proper results:
>
> 1- Create a new generic cardctl call SC_CA
Hi all:
In our development on OpenDNIe[1] We've writen a "dnie-tool" to get
extra, non pkcs15 related card info.
Martin proposed me to use eidenv tool as common tool to display these
extra data, and if requested setup environment for calling an external
application.
Studing eidenv code and how I
