> Hello, > > The conversion from NSS3.1 to NSS3.2 is painful. I was using a lot of CERT_ > and SEC_ that are not accessible anymore. How solid is NSS3.2? Is it being > used successfully internally? I also noticed that the security DBs (key3.db, > cert7.db and secmodule.db) created with NSS3.2 or JSS3.0 cannot be read by > my NSS3.1. Why not? Any NSS functions not listed in nss/nss.def are not public functions; applications should not be calling them. NSS 3.2 has been around since March 2. It has been QAd and is pretty solid. The databases should be compatible between NSS 3.2 and NSS 3.1. What problems are you seeing? > Also on the Mozilla Web site, it says: "NSS 3.2.1 is binary compatible with > NSS 3.2. The source is backward compatible with NSS 3.1.1, NSS 3.1, and NSS > 3.0.x." > I 'm not sure I understand "source is backward compatible"? This means code written for NSS 3.1 should still work with NSS 3.2.1--assuming it only called public functions.
