On 07/18/2010 07:09 AM, Anders Rundgren wrote: > On 2010-07-18 15:46, Stef Walter wrote: > > >> I'm thinking of using PAM for ideas. If you're familiar with PAM the >> following will make sense: >> >> * Directory of configuration files one per application. >> * Each file specifies modules to load. >> * Default configuration file when an application doesn't have its own. >> * Optional string to pass in as C_Initialize's pReserved so we >> can modules like NSS. >> >> I will ask around elsewhere besides OpenSC though. It's hard to believe >> I'm the first one who has run into this need. >> > I'm not familiar with PAM but with other applications using > PKCS #11 like browsers, e-mail and CAs. > > I think it would be a major achievement makimg PKCS #11 > providers discoverable. As it is now each application > must either be manually configured or the provider installation > is mucking around in the applications' config files. >
There was an attempt to define this. Early PKCS #11 working groups came up with some unofficial guidelines. The current NSS system (where they are stored in pkcs11.txt) was an attempt to implement that unofficial guideline. I wrote up the design a couple of times an kind of pushed it up for comment in the cryptoki mailing list, but have not really gotten much traction (partitially because I haven't had time to really push it). bob > anders > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel >
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
