Netscape MANAGEMENT SYSTEM 6.0 - COMMAND-LINE Manual page 112

Command-line tools guide
Table of Contents

Advertisement

Answers to Common Questions
j.
k.
l.
The certificate needed to sign an object is in the certificate database, but
Netscape Signing Tool's
certificate" or "Unknown user" errors.
Netscape Signing Tool 1.x reads the
Normally,
information using the PKCS #7 cryptographic message-syntax standard.
However, Navigator 3.x wasn't designed to properly use this standard (it
wasn't in wide use yet). Therefore, certificates used by Communicator 4.x that
were originally imported with Navigator 3.x may not have all the certificate
chain information required for object signing.
In the case of VeriSign Class 2 or Class 3 certificates, the missing portion of the
chain is the intermediate node, since the root is provided with Communicator
by default and the leaf is included in the existing certificate information. To get
the intermediate portion, use Communicator 4.x and click these links for
VeriSign Class 2 or VeriSign Class 3 certificate authority updates.
When trying to read a JAR file into Communicator 4.05 the error message
"Inconsistent files in manifest" appears in the Java console.
Communicator 4.05 (and only that version) has a bug that makes it sensitive to
the case of the JAR manifest's filename as stored in the META-INF directory.
Version 4.05 requires the filename to be all lowercase. Although the JAR
specification calls for case insensitivity and Netscape Signing Tool does
generate a lowercase filename, an uppercase filename can appear if another
tool is used to create the JAR, or case translation occurs on the Windows
platform.
This problem can be repaired by re-signing the JAR with Netscape Signing
Tool, or by unzipping the file and changing
How can users change the nicknames of their own certificates?
For convenience, users may want to shorten the nicknames of some of the
certificates they use. While certificates cannot be renamed directly, it may be
possible to replace them and give the replacement a new name.
Note that this process can present a risk because it requires the user to delete a
certificate before replacing it, and if the replacement fails and there is no
backup certificate, the certificate is lost.
112
Netscape Certificate Management System Command-Line Tools Guide • March 2002
Click Import a Certificate and give the database password.
Select a certificate file to open and give the certificate's password.
Repeat steps 9 and 10 for each certificate to be re-imported.
and
-l
files record a certificate's complete certificate chain
cert7.db
options report "Unable to find issuer
-k
files used by Communicator 4.x.
cert7.db
MANIFEST.MF
to
.
manifest.mf

Advertisement

Table of Contents
loading

This manual is also suitable for:

Certificate management system 6.0

Table of Contents