Hi I am successfully using newpki 2.0-beta4 as a PKI. Thank you Frederic:-)
I have come across an interesting problem when I began using a SSL Server certificate which I created using newpki then installed on apache 2.0.53. The SSL server cert is signed by an intermediate CA which is in turn signed by the Root CA. I am using the SSL Server extensions template provided in newpki. When I access the web site using Internet Explorer 6 I am informed the cert is OK but is not signed by an authority I trust. This is to be expected and is OK. However, when I access the web site using Firefox 1.0 or Mozilla, I get an alert error in the browser "Could not establish an encrypted connection because certificate presented by ... is invalid or corrupted. Error code: -8102". I cannot go any further after this. I never get to view the cert or accept it. Any ideas what is causing this? The key length is 1024 bits using a sha1rsa signature algorithm, Basic Constraints CA:False. I notice the cert does not contain DirName or serial values under the X509v3 Authority Key Identifier section. The keyid value is present. Could this cause the problem? I have verified the cert using the openssl verify tool. All is OK. If I create a self-signed cert using the makefile.crt tool of apache (basic constraint CA:true) then both mozilla/FIrefox and Internet Explorer work as expected. I look forward to your comments. Regards Paul +++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++ EML Consulting Services Pty Ltd Telephone: +61 3 9836 1999 417-431 Canterbury Road Facsimile: +61 3 9836 0517 SURREY HILLS, VICTORIA 3127 Email: [EMAIL PROTECTED] +++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++ _____________________________________________________________________ NewPKI http://www.newpki.org User Support Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
