Re: [opensc-devel] pkcs15-rtecp.c question
Hello Viktor, Viktor TARASOV wrote: > rv = sc_change_reference_data(card, pin_info->type, pin_info->reference, ... > > My humble question is: does there any mis-usage of the 'type' member of > the 'pin_info' data? > > Afaik, > 'type' in 'sc_pkcs15_pin_info' structure holds the PKCS#15 > PinAttributes.pinType -- PIN encoding style; > the 'sc_change_reference_data()' expects as a second argument the > 'authentication method' like SC_AC_CHV. It's a bug. Thanks! Committed at revision 4037. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] pkcs15-rtecp.c question
Hello Aleksey, in http://www.opensc-project.org/opensc/browser/trunk/src/pkcs15init/pkcs15-rtecp.c#L216 there is a call rv = sc_change_reference_data(card, pin_info->type, pin_info->reference, ... My humble question is: does there any mis-usage of the 'type' member of the 'pin_info' data? Afaik, 'type' in 'sc_pkcs15_pin_info' structure holds the PKCS#15 PinAttributes.pinType -- PIN encoding style; the 'sc_change_reference_data()' expects as a second argument the 'authentication method' like SC_AC_CHV. Kind wishes, Viktor. Viktor Tarasov ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] remove cardmod pcsc driver from internal.
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
Re: [opensc-devel] remove cardmod pcsc driver from internal.
Am Mittwoch 17 Februar 2010 08:58:49 schrieb François Leblanc: > Hello, > > In file src/libopensc/ctx.c: > > since 'cardmod' driver is a subset of pcsc drivers it should not be use > with pcsc driver, if we use the internal keyword (by default) cardmod is > loaded too and may conflict with pcsc reader. > > 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. how does this "internal keyword" work? Regards, Andreas ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
