Well, I am look at passing the handles in the ctx params,
and that part appears to work, but there is an issue with
refreshing the attributes. The reader name point is bad.



On 1/18/2011 2:55 AM, Martin Paljak wrote:
> Hello Douglas,
>
> On Jan 18, 2011, at 12:09 AM, Douglas E. Engert wrote:
>> Using the registry for this does not look correct for a
>> number of reasons:
>>
>> (1) there maybe multiple mini-drivers being run at the same
>>      time.
>> (2) The location in the registry can only be written be the system,
>>      yet the min-driver may be called as a user.
>> (3) The DLLMain routine attempts to see if the key is readable
>>      but is called before the CardAcquireContext can create
>>      the key.
>> (4) I don't see how the pcsc_ctx or pcscd_card can ever be changed.
>>
>> I have not done much with mini-drivers, but have made changes to a
>> number of CSPs and using the registry looks wrong.
> I have to agree. This has been discussed several times before [1], but it did 
> not create any sensible result,  none of the comments resulted in action.
>
>> I would suggest that some other way to store this data is needed,
>> by the cardmod_detect_readers in reader-pcsc.c
>
> Of course. The correct way is to extend the context creation parameters and 
> proper modifications to the PC/SC driver (instead of code copying in 
> reader-pcsc.c to create a copy-driver)
>
> [1] 
> http://www.opensc-project.org/pipermail/opensc-devel/2010-September/015010.html

-- 

  Douglas E. Engert  <deeng...@anl.gov>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to