From owner-freebsd-isp  Wed Dec 17 13:56:36 1997
Return-Path: <owner-freebsd-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA17628
          for isp-outgoing; Wed, 17 Dec 1997 13:56:36 -0800 (PST)
          (envelope-from owner-freebsd-isp)
Received: from host.berk.com (berk.com [207.16.104.250])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA17622
          for <isp@FreeBSD.ORG>; Wed, 17 Dec 1997 13:56:34 -0800 (PST)
          (envelope-from rip@berk.com)
Received: from [207.16.107.34] by host.berk.com; (5.65v3.0/1.1.8.2/16Aug95-0520PM)
	id AA03705; Wed, 17 Dec 1997 16:55:03 -0500
Date: Wed, 17 Dec 1997 16:55:03 -0500
Message-Id: <9712172155.AA03705@host.berk.com>
X-Sender: ber00021@berk.com
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Archie Cobbs <archie@whistle.com>
From: Jim <rip@berk.com>
Subject: Re: Support for secure http protocols
Cc: isp@FreeBSD.ORG
Sender: owner-freebsd-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Yeah, Stronghold is a modified version of Apache1.2.4
It costs a pretty penny for commercial use.
edu is free... I think they have a 30day evaluation.
It takes alot of the frills out of Apache as well as providing SSL support.

        -Jim Palmer

At 11:07 AM 12/17/97 -0800, you wrote:
>Wes Peters writes:
>> So, my question is: if I have the capability (time, interest, etc) to 
>> implement only ONE secure http transport, which one should it be?  There
>> is a draft ieft standard for S-HTTP, but Netscape et al HTTP-SSL seems to
>> have garnered more support in the real world.
>
>I think SSL is more prevalent than SHTTP. Also, there already exists
>a version of Apache (called Stronghold I think) that includes SSL.
>
>-Archie
>
>___________________________________________________________________________
>Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com