Le 05/04/2011 20:58, Frank Morgner a écrit : > My previous remarks in this mail apply to the inner structure of the SM > module. I consider your layout as the most promising. (Maybe because I > implemented something similar ;-) ) Beyond that what I have already said > about where to trigger SM, I have some other questions: > > You speak of the SM module like a separate library. What can be said > against putting everything into libopensc?
No, this library could be linked into libopensc and SM context could be populated with its callbacks. What I'm looking for is the *possibility* to load dynamically the SM module. > The ACL mode sounds like it could be superseded by the APDU mode. If > ACLs request SM, you could set the correct parameters for APDU mode. Is > there a more complex operation needed which justifies the ACL mode? ACL mode is more appropriate when working with the 'distant' SM module, when the keysets and credentials (keys to import, admin PINs, ...) are not present locally but on the distant entity . Also in this mode it's easier to regroup multiple APDUs, APDU answers and to limit the transactions with SM module . > Cheers, Frank. Kind wishes, Viktor. -- Viktor Tarasov <viktor.tara...@opentrust.com> _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
