Answers to Common QuestionsChapter 13 Netscape Signing Tool 111Answers to Common QuestionsThis section answers the most common technical questions regarding NetscapeSigning Tool.Netscape Signing Tool, or Communicator, fails to report the presence of aparticular certificate in the database, even though that certificate should bethere.Netscape Signing Tool 1.x and Communicator 4.x are designed to read only thecert7.db files used by Communicator 4.x. If it happens that a certificate getsdownloaded with Navigator 3.x after Communicator 4.x was installed and run,that certificate is recorded in a database of the older (3.x) format. WhileCommunicator does automatically convert Navigator’s cert5.db and key.dbdatabases to the cert7.db and key3.db formats the first time it runs, it doesnot do so again.To get a certificate into the new database from an old one requires forcingCommunicator to reinitialize its cert7.db file as it does at first run-time. Thisrequires that the certificates in the current cert7.db file be exported for laterre-importing.a. Click the Security Info button on the Communicator toolbar.b. Click Yours under Certificates in the left panel, and select a certificate toexport.c. Click Export and save a PKCS #12 copy of the certificate to a safe location(if no copy already exists).d. Repeat steps 2 and 3 for each certificate present.e. Exit Communicator completely.f. Move the cert7.db and key3.db files from your user profile directory to abackup directory. This is a safety measure: these files shouldn’t be neededagain. Once the following steps are successfully completed, and you haveused signtool -l to verify that the upgraded cert7.db file has the rightcertificates, you can discard these backup copies.g. Copy Navigator’s cert5.db and key.db files to your Communicatoruser-profile directory.h. Restart Communicator. It automatically upgrades the older database files,including their contents.i. Click the Security Info button on the Communicator toolbar, then clickYours under Certificates in the left panel.