can someone explain me how to make the ifdhandler methods dynamically linkable, please? El 01/05/2012 22:13, "Francisco Rodríguez Algarra" <[email protected]> escribió:
> Ludovic, cards are fine. When I say that they block, I don't mean they > block ad infinitum. The only problem is that sometimes it takes too much > time to get their answer, but the response ends up arriving. It may be only > a little annoying issue, but I think (and my tutor does, too) that some > applications are too time-dependent to allow that to happen without being > able to control it. I suppose that IFDHPowerICC might be useful in that > case, as it would allow me to force a reset. But the problem is that the > IfdHandler Api from pcsc-lite is not dynamically linkable, at least with > the libpcsclite.so that it's built from the source files. So I thought that > those routines were meant to be used through libccid.so. Or maybe I'm doing > something wrong. In that case, some piece of help would be welcomed. > > Roger, I use the native Desfire Commands, and they work well. It's a > random problem that occurs very now and then > > 2012/5/1 Roger Brown <[email protected]> > >> Are you using native shortened DESfire APDU commands or ISO-7816 wrapped >> ones? >> >> You may need to use the later to be compatible with existing drivers. >> >> -----Original Message----- >> From: [email protected] [mailto: >> [email protected]] On Behalf Of Ludovic Rousseau >> Sent: Wednesday, 2 May 2012 2:08 a.m. >> To: MUSCLE >> Subject: Re: [Muscle] IfdHandler Lun parameter >> >> 2012/4/29 Francisco Rodríguez Algarra <[email protected]>: >> > Hi guys, >> >> Hello, >> >> > I am developing a Java library that allows communication with DESFire >> > cards through a Gemalto Prox-Du device, and it turns out that these >> > cards get blocked from time to time. Trying to minimize the problems >> > caused by this fact, I've been asked to include a timeout on each >> > command request that causes a reset if it expires. In order to do >> > this, I turned to the methods included in the ccid library, but due to >> > the absence of a previously created Java interface as is the case for >> > pcsc commands, I've been forced to try to implement it on my own. The >> > problem is that, despite my hard research, I'm not able to find a way >> > to determine the Logical Unit Number parameter that I need to send. >> > May someone give me a clue on how to find it or guide me to a >> workaround? >> >> If the card got blocked then the card is bogus. >> Maybe you do not wait enough? >> In all cases the reader should timeout and report an error if the card do >> not respond. The reader timeout maybe long (a few minutes). >> >> Using the CCID ifdhandler directly is not the best way to do what you >> want. You should keep using PC/SC instead. >> >> The IFD Handler API is documented at [1]. >> The Lun is selected by pcscd more or less at random. >> >> Bye >> >> [1] http://pcsclite.alioth.debian.org/api/group__IFDHandler.html >> >> -- >> Dr. Ludovic Rousseau >> >> _______________________________________________ >> Muscle mailing list >> [email protected] >> http://lists.drizzle.com/mailman/listinfo/muscle >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2411/4971 - Release Date: 05/01/12 >> >> _______________________________________________ >> Muscle mailing list >> [email protected] >> http://lists.drizzle.com/mailman/listinfo/muscle >> > >
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
