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 > > > 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. > > MyEID supports this block chaining because it is based on standard NXP JCOP > smartcard chips. > However, block chaining is used only after the maximum packet size is > reached, i.e. above 256 bytes, > so it would not be used here anyway. > > From our point of view, this is handled totally transparently by the reader > and the smartcard chip.
Manually adjusting max_*_size to some magic value isn't transparent at all. So the question is, why MyEID needs such adjustment whereas other cards don't. You should definitely start investigating that issue. As a short term solution you could provide a list of readers known to work. That would be most valuable for your customers. Regards Andre _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
