Hi,
Of course you can (or should, actually) do that. I wast just talking about the
pre-defined list of CAs that the browser trust. Sorry if I wasn't clear. English is
not my native language.
Best regards,
Sebastian
Michael Sierchio (9/16/2001 6:48 PM):
Sebastian Paul Avarvarei wrote:
No
Averroes (9/17/2001 7:25 PM):
What I want to say: after importing my user's cert in pkcs12 format
in my Netscape Comm browser, I got an user cert plus server cert,
moreover with the same name!!
As Dr. S N Henson very well pointed out, don't use the same field details (especially
not the
Hi Steve,
Here is a pkcs12 fomat file in attached document.
I reproduced all steps below with at the beginning, a serial number 00
in serial file.
Password of the pckcs12 file: steve
User Key and Req:
openssl req -newkey rsa:1024 -keyout \
./member/averroesKey.pem -out ./member/averroesReq.pem
Hi,
Sebastian Paul Avarvarei wrote:
That's why you see the same name: Netscape checks what CA has signed the client
certificate you import. If the CA name is not on the list of signers it knows, it
will add it there. Because you (probably) use the same commonName for the CA and the
client
Averroes wrote:
This time, I managed to import the Certificate since I got
the successful message, but nothing appeared in my browser.
No user Cert and No Root-CA Certificate.
Unbelievable !!!
One other thing. Netscape can exhibit bizarre behaviour if its
key/certificate database is
