With our Java apps, however, I'm having less luck. I'm creating a JSSSocketFactory (to pass in to the LDAPConnection object) and passing it the same directory of the certificate DBs as I am in our C++ apps, but I keep getting some general error saying unable init security subsystem (it's just a Java Exception, not even one of the four exceptions that CryptoManager.initialize() declares it can throw). Just reading through documentation I have a couple of questions...
1) I'm assuming that since both the C and Java APIs are from Mozilla, both should support the cert7.db , key3.db, and secmod.db databases, right? Is the C side using NSS for all its security handling when I establish an SSL connection?
2) I downloaded JSS 3.4 with NSS 3.7.3 and NSPR 4.2.2. I have the binaries for NSS and NSPR, but I'm compiling jss.jar myself. I read somewhere that when you get this jar from Mozilla, it's signed, and if you plan on building it yourself, you should also sign the jar. Could the fact that my own jar isn't signed be causing problems? Also, the name of the jar shouldn't matter ( i.e. jss.jar vs. jss34.jar) right? Seems like a stretch but at this point I'm running out of ideas.
3) Does JSS need any env variables or system properties set at runtime?
Thanks for any help.
Mike
_______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
