From owner-freebsd-isp Mon Jul 3 17:23:28 2000 Delivered-To: freebsd-isp@freebsd.org Received: from metva.com.au (metva.com.au [202.0.82.1]) by hub.freebsd.org (Postfix) with ESMTP id BD5F137BCC5 for ; Mon, 3 Jul 2000 17:23:22 -0700 (PDT) (envelope-from enno.davids@metva.metva.com.au) Received: (from daemon@localhost) by metva.com.au id KAA11100; Tue, 4 Jul 2000 10:20:29 +1000 (EST) Message-Id: <200007040020.KAA11100@metva.com.au> Received: from localhost(127.0.0.1), claiming to be "metva.metva.com.au" via SMTP by metva.com.au, id smtpdAAAa11089; Tue Jul 4 10:20:02 2000 X-Mailer: exmh version 2.1.1 10/15/1999 To: "Max Clark" Cc: freebsd-isp@FreeBSD.ORG Subject: Re: SSL Web Servers In-Reply-To: Your message of "Mon, 03 Jul 2000 15:50:20 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jul 2000 10:20:00 +1000 From: Enno Davids Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org |"Max Clark" wrote: | Apache + OpenSSL | Apache + RavenSSL (http://www.covalent.net/raven/ssl/) | Stronghold (www.c2net.com) | | Does anyone have experience with any of these products? Has anyone | implemented one and then switched to another? We've been running Apache/mod_ssl/open_ssl for close to 18 months now. THe only caveat was that Verisign didn't know how to get us an SGC certificate (the old start at 40 bits and step up to 128 bits tech) but we found that they would do one for Stronghold, the commercial Apache port, and that was compatible. Enno. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message