Le 30/05/2011 10:20, HOURY William a écrit :
> Hi Viktor,
>
> It's not working either...
>
> I put the cardmod logs attached. It's very small ...


Have you possibility to test the same scenario with the minidriver of another 
producer ?


> Thanks
> Will

Kind regards,
Viktor.


> -----Message d'origine-----
> De : Viktor Tarasov [mailto:viktor.tara...@gmail.com]
> Envoyé : dimanche 29 mai 2011 17:50
> À : Viktor TARASOV
> Cc : opensc-devel@lists.opensc-project.org; HOURY William
> Objet : Re: [opensc-devel] First Smartcard logon issue on XP SP3 with OpenSC 
> 12.1
>
> Hello William,
>
> Le 26/05/2011 20:38, Viktor TARASOV a écrit :
>> I'm also actually looking into this logs and it seems strange the after 
>> releasing of context it starts to read the cardcf .
>> In any case the 'zero' cardcf can be disturbing for baseCSP.
> Another 'feature' is when the 'HANDLES CHANGED' event happens, the 
> disassociate/associate card procedures pair called,
> and 'cardcf' content is cleaned but not re-initialized. That's where from 
> there is 'zero' content.
>
> Could you please try the following test patch .
> With this patch the cardcf content is deduced from the 'last_update' 
> attribute of the token info data,
> and not from the minidriver internal data. So that we'll avoid a 'zero' 
> content of cardcf.
>
> Also the initialization of  'cardcf' content is moved from 
> CardAcquireContext() to the associate_card() procedure .
>
> Kind regards,
> Viktor.
>
> ________________________________
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
> exclusif de ses destinataires. Il peut également être protégé par le secret 
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne 
> pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne 
> pourra être recherchée quant au contenu de ce message. Bien que les meilleurs 
> efforts soient faits pour maintenir cette transmission exempte de tout virus, 
> l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
> saurait être recherchée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended solely 
> for the addressee; it may also be privileged. If you receive this e-mail in 
> error, please notify the sender immediately and destroy it. As its integrity 
> cannot be secured on the Internet, the Atos Origin group liability cannot be 
> triggered for the message content. Although the sender endeavours to maintain 
> a computer virus-free network, the sender does not warrant that this 
> transmission is virus-free and will not be liable for any damages resulting 
> from any virus transmitted.

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to