OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: [Muscle] 2nd: Differences in ScardDisconnect betweenSCARD_LEAVE_CARD and SCARD_RESET_CARD

From: Ludovic Rousseau (ludovic.rousseaugmail.com)
Date: Wed Mar 29 2006 - 03:30:45 CST


On 29/03/06, Merlet Fabien <fabien.merletnagra.com> wrote:
> Hi Ludovic,
> Thanks for your comments.
> I've installed pcsc-lite 1.3.0 and started the test again.
> I obtained exactly the same result.
>
> Here is an extract of the server logs during the tests if it may help:
>
> ---
> pcscdaemon.c:259:main() pcscd set to foreground with debug send to
> stderr
> pcscdaemon.c:464:main() pcsc-lite 1.3.0 daemon ready.
> ... # ?
> readerfactory.c:812:RFLoadReader() Warning library pointer not NULL

Do you have two SCM readers connected?

> ... # next lines observed hundred times
> winscard_msg_srv.c:243:SHMProcessEventsContext() select returns with
> failure: Bad file descriptor

Very strange.
After that I guess anything is possible.

Can you do (or a equivalent if you do not have the pidof(8) command)
$ sudo ls -l /proc/`pidof pcscd`/fd
before and after the errors to see how the file handles evolve?

> - As I stated in my last mail, I don't think this is linked to the SCM
> driver we use, because problem is at the end in the server,
> ("Exclusive reader" which can't be cleaned except if I kill the pcscd
> daemon) and changing parameters in SCardDisconnect calls has an effect,
> so IMHO this is somewhere in the PCSC layer... (but I may be wrong of
> course). On rare occasions, I also observed pcscd daemon crashes...

Maybe the SCM driver corrupts the memory on pcscd side in some cases.
Can you try with another driver?

Bye,

--
  Dr. Ludovic Rousseau

_______________________________________________
Muscle mailing list
Musclelists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle