Pierre wrote: > When using CryptoManager.JAR_JSS_VERSION and > CryptoManager.JAR_NSS_VERSION to get JSS and NSS version from JSS I > get this: > > JSS_VERSION = JSS_3_0 > NSS_VERSION = NSS_3_2_RTM > > That's wrong because I'm using JSS version 3.1 and NSS version 3.3 > > What's wrong ? Did I miss something ?
You didn't miss anything. That is a bug. In http://lxr.mozilla.org/mozilla/source/security/jss/org/mozilla/jss/manage/CryptoManager.c#70, you can see that these version numbers are hardcoded. They need to be updated whenever we upgrade to a new version of NSPR, NSS, or DBM, but we didn't update these version numbers in JSS 3.1. So JSS 3.1 still returns the version numbers of JSS 3.0. Those hardcoded values should be replaced by the macros PR_VERSION and NSS_VERSION defined in "prinit.h" and "nss.h". DBM_VERSION isn't really necessary now that it is contained in the nss3 shared library. Does JDK define a macro that expands to the JDK version? Jamie, could you file a bug report? Wan-Teh
