[EMAIL PROTECTED] wrote: > When I go into into my profile directory, I am able to view it > using signtool. It gives the following output : > > Object signing certificates > --------------------------------------- > Common Name - Organization > Issued by: Common Name - Organization (Common Name) > Expires: Fri Sep 14, 2007 > ---------------------------------------
Is that really the verbatim output of signtool -l? Does your self-signed cert have "Common Name - Organization" as its name? > However, when I try to sign a directory. I get this > following error : > > Generating test/META-INF/manifest.mf file.. > Generating zigbert.sf file.. > signtool: the cert "testcert" does not exist in the database: security > library: bad database. "security library: bad database" is a somewhat generic error you'll encounter when signtool fails to find a cert for signing. The first part of the error message actually indicates what the problem is: apparently you used "-k testcert" to specify the name of the cert, but there is no cert with this nickname in your cert database (if the output above is really what signtool -l shows, then you'd have to use -k "Common Name - Organization"). > So does anyone know why the NSS/Mozilla dbs are, I guess, > incompatible? It seems very strange that I am able to list the > certificates, but get a "bad database" error when I try to use it. The "Mozilla dbs" *are* NSS DBs, there's no difference between them. However, when using the NSS command-line tools it's always a good idea to specify the cert db directory explicitly (using the "-d" switch), otherwise they pick the DB from the default location (~/.netscape), which is usually not what you want. Kaspar _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
