Nelson B. Bolyard wrote:
.p12 files contain the nickname for the certs. When mozilla imports a
cert from a .p12 file, it uses the nickname found in the .p12 file.
If I'm not mistaken, iPlanet web server requires that the server's cert
have a particular nickname. It's possible that this was a
liug wrote:
Nelson B. Bolyard [EMAIL PROTECTED] wrote:
liug wrote:
How can I use the NSS tools to convert a openssl generated
key pem file to netscape key3.db ?
I believe there is some OpenSSL program that will create a .p12 file
(a.k.a PFX file) from your key/cert. Mozilla can import
liug wrote:
How can I use the NSS tools to convert a openssl generated
key pem file to netscape key3.db ?
Thanks!
Frank
You probably can't convert it, because a pem file is a simple collection
of certs, but a key3.db is a complex database.
You might want to create a database and use
liug wrote:
4) now try to import it (I already have key3.db and cert7.db created).
pk12util -i test2.p12 -d .
it gives:
pk12util: PKCS12 decode validate bags failed: The user pressed cancel.
any ideas?
thanks!
frank
Did you specify a password on your p12 file when you created it ?
Julien Pierre [EMAIL PROTECTED] wrote:
liug wrote:
4) now try to import it (I already have key3.db and cert7.db created).
pk12util -i test2.p12 -d .
it gives:
pk12util: PKCS12 decode validate bags failed: The user pressed cancel.
any ideas?
thanks!
frank
Did you specify
