rzdrav@pcnet.co.nz wrote:
>
> At 07:26 PM 7/2/98 +0930, you wrote:
> >At 07:03 2/07/98 , you wrote:
> >>Holger Reif wrote:
> >>> The SSLCA* bug has hopefully been fixed in 1.18, else just point
> >>> SSLCACertificateFile demoCA/newcert.pem
> >>
> >Hi
> >Yup the server starts now, but Netscape returns an invalid signature error
> >- I believe someone else was having the same problem.
> >I'm using Communicator 4.05
>
> I have the same problem. I use Comunicator 4 and server version Apache 1.2.6
> Ben-SSL/1.13 CNC. Everything goes well, even Explorer 4 accepts the
> sertificate, but Comunicator keeps refusing with "...invalid signiture..."
>
> WE ARE IN DEEP TROUBLE !!!
>
> Only kidding :-)Must be some solution. Previously, I have tried 'Using
> SSLeay and Apache SSL'. It is a little bit diferent approach, but the
> trouble is, they never explained how to configure your apache 'httpd.conf'
> with the files you get. For this approach, Holger Reif described in details
> this aspect, but for some of us, does not work only for Netscape.
>
> If you find the solution for that Netscape error, please drop me a line.
> I've been trying many variations, but no luck for Netscape.
I do all my testing with Netscape, so I'm somewhat surprised.
Cheers,
Ben.
--
Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member
Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org/
and Technical Director|Email: ben@algroup.co.uk |
A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/
London, England. |"Apache: TDG" http://www.ora.com/catalog/apache/
WE'RE RECRUITING! http://www.aldigital.co.uk/recruit/