On Thursday, July 10, 2014 4:28:30 AM UTC-4, ramahmoo wrote: > > platform fashion. Using Firefox only is not a problem. Can i extend the > > existing internal softtoken implementation to achieve the above? If yes > > which methods has to be overriden. If no, from where should i start? What > > about pin management in this case?I am newbie to PKCS#11 :) Thanks for your >
I'm relatively new with PKCS#11 as well. From my perspective, I'd recommend starting with SoftHSM instead of NSS. http://www.opendnssec.org/softhsm/ In all honesty, the code in both NSS and SoftHSM seem very similar in structure - the major difference being that NSS is more full featured in that it not only provides a PKCS#11 interface for other applications to use, it can also be configured to use one or more PKCS#11 interfaces from other providers. As I am working on something similar myself, I find it easier to modify SoftHSM since it's code doesn't include a large amount of extra functionality that is not of interest to me. -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
