Hi, I hope this is the right group. I've done many searches, including this group for every message with pkcs in its title, and couldn't find answers which would satisfy me. I'd appreciate any pointer or help.
We're developing a PKCS#11 library (first implementation is for win32) for our hardware token. I'd like to use NSS for two cases: 1. Use a stand alone pkcs11 dll from NSS as a sort of reference for a working implementation. I'd like to use pre-compiled binaries from firefox/mozilla/etc (I'll gladly live with using a full installation of firefox/mozilla/etc for the sake of this test). The dll has to connect to a soft-token, i.e. zero crypto hardware needed but at least partial pkcs11 dll functionality working. It's ok if I have to use vendor specific initialization functions. 2. Use NSS pkcs11 test tools (preferably pre-compiled for win32) for testing compliancy of our implementation with Firefox. I know this isn't a formal compliancy test, but it would be a good start. I saw several threads on this subject, but thus far, none was explicit enough as for the procedures one should use to achieve that goal. also, in conjunction with my 1st question, can this compliancy test be used with the above mentioned soft-token+pkcs11 implementation? Any help on creating/configuring these cases would be greatly appreciated. Thanks in advance, avih _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
