I have a plugin extension which is also a PKCS#11 module and while it's "easy" to install the plugin via the install.rdf system I can't figure out a way to register it as a PKCS#11 module.
pkcs11.addmodule() would work but how can I get the path to the library which is going to be in the current user's profile/extensions area? I imagine I might be able to figure this out in an install.js type XPI since you can get paths to things but is it possible with the newer extensions mechanism using install.rdf? Is there a way to put a script in the install that will run when the extension/plugin is installed or some way to register a PKCS11 module? I thought maybe I could use the multiple item packaging of XPI's and have one XPI for my RDF extension install then have another XPI with the old install.js style install. This doesn't work though, it gives some cryptic error about a package not providing "install- <randomstring>.rdf" (where <randomstring> is just that, some random string). The XPI's work fine on their own, just not bundled together. It acts like all the XPI's have to be install.rdf type installers (which may be true but the documentation says any type will work). Altogether this is highly confusing and frustrating because of all the misinformation out there. So far I haven't been able to find much of any information on this. Documentation is either extremely out of date or nonexistent. Especially anything regarding PKCS#11 modules. I hope this is a good/correct group to post this question in, half the dev groups appear practically dead (eg. the plugin group). Thanks for any help. CR _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
