2011/1/27 Aventra :
> Hi,
>
> Thanks for the tips for building the correct package.
> I managed to build it with the timeout fix, but it does not seem to help.
> Attached is the new log.
Still the same problem :-(
According to your new log file the problem does not occur with the
APDU "00 B0 00 F
uuta 2011 12:52
> To: Aventra
> Cc: OpenSC Development
> Subject: Re: [opensc-devel] Misleading information about capabilities of
> readers
>
> 2011/1/21 Aventra :
> > Hello Ludovic,
> >
> > Well I have been looking into this and have some issues with compiling
t
2011/1/21 Aventra :
> Hello Ludovic,
>
> Well I have been looking into this and have some issues with compiling the
> code.
> The CCID driver version from trunk requires pcsc-lite version 1.6.5, which I
> don't have, so I need to compile that too.
>
> We usually use only the versions that are distr
2011/1/21 Aventra :
> Hello Ludovic,
>
> Well I have been looking into this and have some issues with compiling the
> code.
> The CCID driver version from trunk requires pcsc-lite version 1.6.5, which I
> don't have, so I need to compile that too.
Why don't you patch the version of the driver you
to:ludovic.rouss...@gmail.com]
> Sent: 20. tammikuuta 2011 21:56
> To: Aventra
> Cc: opensc-devel
> Subject: Re: [opensc-devel] Misleading information about capabilities of
> readers
>
> Hello "Aventra",
>
> I did not get any reply to my mail.
> Does the patch wo
Hello "Aventra",
I did not get any reply to my mail.
Does the patch works for you?
Thanks
2011/1/13 Ludovic Rousseau :
> 2011/1/13 Aventra :
>> Hi,
>>
>> Sorry, a typo when doing logging...
>> Attached is a new log.
>
> Found the bug (I think).
>
> The CCID driver calculate a timeout accordings
Le jeudi 13 janvier 2011 à 18:52 +0100, Andre Zepezauer a écrit :
> It would be easier to call it 'certified'. And of cause, certification
> may be a service that is not for free.
I second that. Certification is loud and clear.
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
Le jeudi 13 janvier 2011 à 18:47 +0100, Ludovic Rousseau a écrit :
> But I can't support a reader I do not have. So they are listed (by
> default) in the "Should work but untested by me" list.
You have the R-301 v2. I shipped it to you and I have an email telling
us that you received it. It is li
On Thu, 2011-01-13 at 18:39 +0100, Jean-Michel Pouré - GOOZE wrote:
> Le jeudi 13 janvier 2011 à 18:08 +0100, Peter Stuge a écrit :
> > > * Unsupported.
> > > * Supported (and not should work).
> > > * Supported and reviewed (and not Supported).
> >
> > The good names depend on what "support" mean
Le 13 janvier 2011 18:39, Jean-Michel Pouré - GOOZE a écrit :
> Le jeudi 13 janvier 2011 à 18:08 +0100, Peter Stuge a écrit :
>> > * Unsupported.
>> > * Supported (and not should work).
>> > * Supported and reviewed (and not Supported).
>>
>> The good names depend on what "support" means in this c
Le jeudi 13 janvier 2011 à 18:08 +0100, Peter Stuge a écrit :
> > * Unsupported.
> > * Supported (and not should work).
> > * Supported and reviewed (and not Supported).
>
> The good names depend on what "support" means in this context. I
> don't know that. Do you? Maybe Ludovic can help clarify?
On Jan 13, 2011, at 7:08 PM, Peter Stuge wrote:
> Jean-Michel Pouré - GOOZE wrote:
>>> I've been under the impression (based on the header in "should work"
>>> list [1]) that it contains readers which work as expected and which
>>> Ludovic has.
>>
>> The names should be then:
>> * Unsupported.
>
Hello,
On Jan 13, 2011, at 7:08 PM, Peter Stuge wrote:
> Jean-Michel Pouré - GOOZE wrote:
>>> I've been under the impression (based on the header in "should work"
>>> list [1]) that it contains readers which work as expected and which
>>> Ludovic has.
>>
>> The names should be then:
>> * Unsuppor
Jean-Michel Pouré - GOOZE wrote:
> > I've been under the impression (based on the header in "should work"
> > list [1]) that it contains readers which work as expected and which
> > Ludovic has.
>
> The names should be then:
> * Unsupported.
> * Supported (and not should work).
> * Supported and r
Hello,
On Thu, 2011-01-13 at 11:37 +0100, Ludovic Rousseau wrote:
> Found the bug (I think).
>
> The CCID driver calculate a timeout accordings to the card ATR. In
> your case the timeout is 1428 ms rounded to 2 seconds.
> Log says:
> 0007 ifdhandler.c:791:IFDHSetProtocolParameters() Timeout:
Dear all,
> I've been under the impression (based on the header in "should work"
> list [1]) that it contains readers which work as expected and which
> Ludovic has.
The names should be then:
* Unsupported.
* Supported (and not should work).
* Supported and reviewed (and not Supported).
> So ple
Hello,
On Jan 12, 2011, at 2:04 PM, Jean-Michel Pouré - GOOZE wrote:
> Le mercredi 12 janvier 2011 à 13:26 +0200, Martin Paljak a écrit :
>>
>>> Per discussion, we have to pay to get the reader out of the
>> unsupported
>>> list, and this is quite a large sum of money.
>> Pay whom? How much?
P
Le jeudi 13 janvier 2011 à 11:37 +0100, Ludovic Rousseau a écrit :
> The CCID driver calculate a timeout accordings to the card ATR. In
> your case the timeout is 1428 ms rounded to 2 seconds.
Are all CCID readers impacted?
Kind regards,
--
Jean-Michel Pouré - Gooze - http://w
2011/1/13 Aventra :
> Hi,
>
> Sorry, a typo when doing logging...
> Attached is a new log.
Found the bug (I think).
The CCID driver calculate a timeout accordings to the card ATR. In
your case the timeout is 1428 ms rounded to 2 seconds.
Log says:
0007 ifdhandler.c:791:IFDHSetProtocolParamete
Hi,
Sorry, a typo when doing logging...
Attached is a new log.
Kind regards,
Toni
> -Original Message-
> From: Ludovic Rousseau [mailto:ludovic.rouss...@gmail.com]
> Sent: 12. tammikuuta 2011 19:29
> To: Aventra
> Cc: opensc-devel
> Subject: Re: [opensc-devel] Misl
Hello,
> -Original Message-
>
> On 12.01.2011 18:41, Aventra wrote:
> > My questions are:
> > - have other OpenSC users tried cards that use T=1 protocol?
> > - have somebody managed to use MyEID cards without adjusting the
> > configuration?
>
> In OpenSC-trunk r5087 MyEID card is n
Le mercredi 12 janvier 2011 à 23:41 +0100, Peter Stuge a écrit :
> What do you mean by this? It sounds really obnoxious, but I think
> there is a language barrier here and I do not want to jump to
> conclusions.
Sure, French is my mother tongue, not English. I am a nice guy, always
pleasant with
Jean-Michel Pouré - GOOZE wrote:
> The libccid supported list is for companies which pay technical review.
> When companies do not pay, readers are listed in "Should be supported".
What do you mean by this? It sounds really obnoxious, but I think
there is a language barrier here and I do not want
On 12.01.2011 18:41, Aventra wrote:
> My questions are:
> - have other OpenSC users tried cards that use T=1 protocol?
> - have somebody managed to use MyEID cards without adjusting the
> configuration?
In OpenSC-trunk r5087 MyEID card is normally working (erase,init,import
PKCS#12) without c
On Wed, 2011-01-12 at 19:41 +0200, Aventra wrote:
> Hi,
>
> > -Original Message-
> > > > -Original Message-
> > > > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de]
> > > > Sent: 12. tammikuuta 2011 12:46
> > > > >
> > > > > There is nothing special about MyEID t
Hi,
> -Original Message-
> > > -Original Message-
> > > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de]
> > > Sent: 12. tammikuuta 2011 12:46
> > > >
> > > > There is nothing special about MyEID that would cause the issue. In
> > windows
> > > > everything works
2011/1/12 Aventra :
> Hi,
>
> I have attached the requested logs.
Try again with _exactly_ what is documented on the web page:
LIBCCID_ifdLogLevel=0x000F
export LIBCCID_ifdLogLevel
pcscd --foreground --debug --apdu
Thanks
--
Dr. Ludovic Rousseau
___
On Wed, 2011-01-12 at 17:22 +0200, Aventra development wrote:
> Hi,
>
> > -Original Message-
> > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de]
> > Sent: 12. tammikuuta 2011 12:46
> > >
> > > There is nothing special about MyEID that would cause the issue. In
> windows
Hi,
> -Original Message-
> From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de]
> Sent: 12. tammikuuta 2011 12:46
> >
> > There is nothing special about MyEID that would cause the issue. In
windows
> > everything works just fine if we follow the readers maxIFSD value.
> > On
Le mercredi 12 janvier 2011 à 13:26 +0200, Martin Paljak a écrit :
>
> > Per discussion, we have to pay to get the reader out of the
> unsupported
> > list, and this is quite a large sum of money.
> Pay whom? How much?
I would say 'technical review', nothing special. Reviewing a smartcard
reade
On Jan 12, 2011, at 1:22 PM, Jean-Michel Pouré - GOOZE wrote:
> Le mercredi 12 janvier 2011 à 12:07 +0200, Martin Paljak a écrit :
>> Jean-Michel, what were the symptoms of the bug?
>
> As for R-301-v1, it used to have an unsupported message, but it proved
> to be an OpenCT incompatibility. So e
Le mercredi 12 janvier 2011 à 12:07 +0200, Martin Paljak a écrit :
> Jean-Michel, what were the symptoms of the bug?
Feitian R-301 was updated recently with a new CCID firmware,
which works fine:
http://www.gooze.eu/feitian-r-301-v2
In the CCID database, it is listed as the Feitian SCR310:
http:
2011/1/12 Andre Zepezauer :
> On Wed, 2011-01-12 at 12:26 +0200, Aventra development wrote:
>> There is nothing special about MyEID that would cause the issue. In windows
>> everything works just fine if we follow the readers maxIFSD value.
>> One difference with many other cards supported by OpenS
uuta 2011 11:22
> > To: opensc-devel
> > Subject: Re: [opensc-devel] Misleading information about capabilities of
> > readers
> >
> > 2011/1/11 Andre Zepezauer :
> > > Hello,
> > >
> > > the wiki page of MyEID [1] contains the following parag
Hi,
> -Original Message-
> From: opensc-devel-boun...@lists.opensc-project.org [mailto:opensc-devel-
> boun...@lists.opensc-project.org] On Behalf Of Ludovic Rousseau
> Sent: 12. tammikuuta 2011 11:22
> To: opensc-devel
> Subject: Re: [opensc-devel] Misleading
Hello,
On Jan 12, 2011, at 11:22 AM, Ludovic Rousseau wrote:
> Every _non-bogus_ reader.
> For example the Feitian SCR301 [2] is bogus and can't support CASE 2
> APDU with Le=0 (256 bytes). That is why this reader is listed in the
> "unsupported" list of my CCID driver.
Interesting. Too bad the o
Hello,
On Jan 12, 2011, at 11:34 AM, Aventra development wrote:
> Readers we have tested are:
> - ACS ACR38 CCID
This is a very broad range, ACS re-uses the chip in different incarnations in
several products that are marketed under different names and I would not bet on
it being 100% the same chi
Hi,
Well this is just something we (and our customers) have encountered with the
readers that we have tested.
I don't know what causes the limitation (probably not the reader itself,
because they work in windows just fine).
So it might be in pcsc-lite, the ccid driver or something to do with usb
2011/1/11 Andre Zepezauer :
> Hello,
>
> the wiki page of MyEID [1] contains the following paragraph:
>
> "Many readers don't support receiving the default amount of data (254).
> Problems will only appear when reading larger files from the card (e.g.
> certificates). So if you have problems with r
Hello,
the wiki page of MyEID [1] contains the following paragraph:
"Many readers don't support receiving the default amount of data (254).
Problems will only appear when reading larger files from the card (e.g.
certificates). So if you have problems with reading the card with no
apparent reason,
40 matches
Mail list logo
