On 2009-09-04 08:36 PDT, Klaus Heinrich Kiwi wrote: > I did a quick look around the testcases and bltest code. I was hoping to > find someplace where the testcases would set-up NSS to use the internal > PKCS#11 module, then I'd replace that for my own module. > > Or even somewhere where I could specify my PKCS#11 module as the default > module to use by every NSS app (including testcases) > > I'll admit I haven't got far, being someone just recently presented to NSS.
I think you should plan to crawl before you walk, and plan to walk before you run, and plan to run before you space-walk. But you're trying to figure out how to space-walk as the first milestone, I think. For various reasons that are advanced topics, I think trying to completely obviate NSS's own software module is not a target for which you should be aiming now. You should set your sights a little lower, to (say) do the steps needed for SSL first. I'd suggest you try to a) get your module to load b) get RSA public and private key ops to work with your module, and only then c) try to get your module to do all the other operations for SSL. > Right now I'd just like to debug simple things like loading the module, > logging in, generate some keys, doing some encryption. Maybe I should > use certutil to do some tests? (not sure if certutil has options to use > my defined PKCS#11 module instead of the default one). After that, I > don't know what to use in order to test other functions/ciphers. NSS has a variety of test tools to facilitate testing with PKCS#11 modules. I suggest you start with modutil and pk11util. -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
