Re: [opensc-devel] eidenv: a proposal

2011-04-21 Thread Juan Antonio Martinez
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

Re: [opensc-devel] eidenv: a proposal

2011-04-21 Thread Frank Morgner
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

Re: [opensc-devel] eidenv: a proposal

2011-04-21 Thread Peter Stuge
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

[opensc-devel] [PATCH ] Re: eidenv: a proposal

2011-04-21 Thread Juan Antonio Martinez
El mar, 19-04-2011 a las 18:26 +0300, Martin Paljak escribió: > 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 av

Re: [opensc-devel] IASECC problem with Oberthur compliant card

2011-04-21 Thread Viktor TARASOV
Hello, Le 21/04/2011 14:51, BLANC Gilles a écrit : > Hi, > > this is my first message, so first and foremost I want to tell you that I am > very pleased to develop in OpenSC. welcome to club. > I am currently working on the Oberthur's Cosmo One card (V7.0.1-n) support, > for an important p

[opensc-devel] IASECC problem with Oberthur compliant card

2011-04-21 Thread BLANC Gilles
Hi, this is my first message, so first and foremost I want to tell you that I am very pleased to develop in OpenSC. I am currently working on the Oberthur's Cosmo One card (V7.0.1-n) support, for an important project. I have access to Oberthur ressources, and they are ready to help. Basic

Re: [opensc-devel] Automatic read binary in iso driver

2011-04-21 Thread Juan Antonio Martinez
El jue, 21-04-2011 a las 10:03 +0200, NdK escribió: > > The problem I have is to read a file with an unknown length. > How is that possible? Aren't file sizes fixed at file creation time? > Have I missed something? > IIUC, when you issue a SELECT_FILE, you can see its size, too. I'm confused. Sure

Re: [opensc-devel] Automatic read binary in iso driver

2011-04-21 Thread Viktor TARASOV
Le 21/04/2011 10:55, Frank Morgner a écrit : > Hi! > > I think that a flag could be invented for switching between these > two modes of operation (the otherwise unused "flags" parameter to > sc_read_binary). The default could be the mode that honors passed > in parameters. Act

Re: [opensc-devel] Automatic read binary in iso driver

2011-04-21 Thread Frank Morgner
Hi! I think that a flag could be invented for switching between these two modes of operation (the otherwise unused "flags" parameter to sc_read_binary). The default could be the mode that honors passed in parameters. >>> Actually the 0x6282 is mapped to the general SC_ERROR_CA

Re: [opensc-devel] Automatic read binary in iso driver

2011-04-21 Thread Frank Morgner
Hi! > > But all other functions of libopensc require the caller to allocate > > enough space. > Vital for maintainable software: who needs memory, allocates (*and > frees*) it. As a sage said a long time ago: "or you rewrite your project > this way, or your project will rewrite you" :) As long as

Re: [opensc-devel] Automatic read binary in iso driver

2011-04-21 Thread NdK
Il 20/04/2011 22:24, Frank Morgner ha scritto: > But all other functions of libopensc require the caller to allocate > enough space. Vital for maintainable software: who needs memory, allocates (*and frees*) it. As a sage said a long time ago: "or you rewrite your project this way, or your project

Re: [opensc-devel] Automatic read binary in iso driver

2011-04-21 Thread Viktor TARASOV
Hi! In the svn tree there is a change that breaks my code: The ISO driver automatically sends read binary APDUs until the number of requested bytes is reached (iso7816.c:136). You mean r5237 [1] ? Yes! Previously only one APDU was sent. The change surely intendeds to read as much as possible