Sorry I certainly bad explain what I mean, I will try to be more clear:
>> So I propose to change this with joined patch if someone get better idea
>> I can have a look.
>
>how does it exactly work? it is fine for me to "hide" the cardmod driver
>under normal operations. and people should be able to switch from normal
>things (e.g.initializing a card, using firefox with opensc-pkcs11.so)
>to cardmod without config file or registry changes, if that is possible.
It's is the goal, nothing to do. For cardmod I use app cardmod configuration in
opensc.conf with reader_drivers = cardmod -> so get only cardmod driver.
For other the use of app defaut with reader_drivers not set load all available
drivers
Present in list (see ctx.c internal_reader_drivers) but cardmod should not be
avalaible
this way.
>how does this "internal keyword" work?
I talk about "internal" defined in opensc.conf :
# A special value of 'internal' will load all
# statically linked drivers. If an unknown (ie. not
# internal) driver is supplied, a separate configuration
# configuration block has to be written for the driver.
# Default: internal
# NOTE: if "internal" keyword is used, must be the
# last entry in reader_drivers list
#
# reader_drivers = openct, pcsc, ctapi;
I don't define a new keyword...
>Regards, Andreas
Hope I've been more clear, sorry if it's difficult to see what I mean.
Regards,
François.
smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
