On Wed, 2011-01-12 at 12:26 +0200, Aventra development wrote: > 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 information about capabilities of > > readers > > > > 2011/1/11 Andre Zepezauer <andre.zepeza...@student.uni-halle.de>: > > > 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, try to set this to e.g. 192, to be on the safe side. > > > You can then try to iterate to find the maximum for your card reader." > > > > > > That statement is simply wrong, because every USB reader can handle > > > Short-APDUs of every size. For that reason no other card has similar > > > problems. > > > > 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. > > > > > If there are readers that don't work properly with MyEID, then list them > > > explicitly by name. That would definitely of more help to users then > > > such a vague statement like "Many readers don't support [...]". > > > > The reader above has a problem with Le=256. Le=254 should work and the > > reader should not have a problem with MyEID. > > > > I don't know which readers have problem with MyEID. An explicit list > > of bogus readers would be great so that users can avoid buying such > > readers. > > > 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 OpenSC that they use T=0 > protocol (MyEID use T=1).
I have a guess about the source of trouble: MyEID cards do not support T1-Block-Chaining. @Ludovic: What's your opinion? _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
