>we could define some new structure with reader parameters to be passed
>as third argument and store the values there. still a hack, but I wonder
>if that would be cleaner than using the config file code as transport.
>
>not sure, what does everyone else think?
Ok, I see now what you mean.
>I saw this
>+ BYTE modulus[1024/8];
>and thought it would limit the code to 1024 byte keys maybe?
Yes it is why I replace PUBKEYSTRUCT with PUBKEYSTRUCT_BASE
and dynamically allocate memory for the key.. I need to remove PUBKEYSTRUCT.
>> I've in mind to generate this file like it done with opensc-install.bat. I
>> think it will be necessary if we want to manage all opensc card since you
>> have to provide this for each atr card.
>
>ah. can you document in README maybe what registry keys are necessary?
>or maybe better a wiki page about the new baseCSP mini driver,
>so we have all the information in that central place.
>
>I guess people will want to customize / configure this, or for debugging
>will need to check if some other driver claimed some atr opensc wants to
>claim too.
>
Yes it will be necessary for a clean release.
François.
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
