On 07/10/2014 01:53 PM, ramahmoo wrote:
It's probably not a good idea to try to create your own softokn3.dll to replace the mozilla one, you will be forever chacing the upstream version (Any new ciphers supported in firefox will wind up in softoken3.dll).Thanks,i would ready the documentation.Can i extend/modify the NSS internal pkcs#11 source (softokn3.dll source) to achieve my requirement?
You could use the softoken source to build our own PKCS #11 module, though I would recommend using ckfw instead.
There are tools to help install your own PKCS #11 modules, and you don't have to update them everytime NSS updates.
look at: In NSS itself, there's modutil: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_modutil https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Reference/NSS_tools_:_modutil http://lxr.mozilla.org/nss/source/cmd/modutil/ From the coolkey project, there's pk11install: http://svn.fedorahosted.org/svn/coolkey/trunk/src/install/This tools has code that searches for all your mozilla profiles and installs your module in them. Once installed, new version of Firefox will automatically inherit your PKCS #11 module.
I'd suggest starting with capi or builtins as a better example of what you need to build a pkcs #11 module.Or it is meant only internal usage. If it can be used as starting point then which methods should i override?
bob
-- View this message in context: http://mozilla.6506.n7.nabble.com/NSS-Custom-Crypto-Module-tp319226p319284.html Sent from the Mozilla - Cryptography mailing list archive at Nabble.com.
smime.p7s
Description: S/MIME Cryptographic Signature
-- dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
