Date: Fri, 06 Jun 1997 14:57:59 -0400 From: Chris Shenton <cshenton@it.hq.nasa.gov> To: Nadav Eiron <nadav@barcode.co.il> Cc: questions@freebsd.org Subject: Re: Apache with SSL or shttp Message-ID: <199706061858.OAA11368@gratia.it.hq.nasa.gov>
next in thread | raw e-mail | index | archive | help
From: Nadav Eiron <nadav@barcode.co.il> Well, I'm using Apache-SSL (ver. 1.1.1 of Apache and 0.6.4 of SSLeay BTW). It's not trivial to set up. It comes as a set of patches to the Apache source, but it works just fine (at least for me). It carries a BSD-style license, so you can pretty much do whatever you want with it (assuming you have no legal problems using SSLeay, I think you might in the U.S.). How did you deal with the Certification issue so that clients trust your server? That is, where did you get the certificate for the server, or do clients just get the banner "Hey, I don't know the CA who signed this server -- are you sure you want to trust it?" The other option is a commercial product called Stronghold that is based on Apache. For details see: http://www.c2.net/ I set this one up here (on Slowaris)-: because Verisign refuses to sell certificates for non-commercial servers. I haven't yet gotten client certificate based authentication working though ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706061858.OAA11368>