From owner-freebsd-hackers Wed Dec 10 20:40:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA00944 for hackers-outgoing; Wed, 10 Dec 1997 20:40:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA00935 for ; Wed, 10 Dec 1997 20:40:29 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xg0Ga-0002sj-00; Wed, 10 Dec 1997 20:30:28 -0800 Date: Wed, 10 Dec 1997 20:30:23 -0800 (PST) From: Tom To: Charles Mott cc: hackers Subject: Re: FW: Why so many steps to build new kernel? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Dec 1997, Charles Mott wrote: > My understanding is that only commercial web servers support SSL, which I > am guessing is the name for standard secure link used by MSIE and > Netscape. Is it possible that Apache supports SSL?? > Netscape and Microsoft take over the market and set standards. It may be > impossible to ever go back. No, ssl is an open standard. There is an freely available ssl library (ssleay?). You can get Apache-SSL, which is just Apache plus the ssl library. ssl uses RSA encryption which is protected by a US patent. This makes it illegal to use the ssl lib in the US. You can get stronghold, which is Apache plus a properly licensed ssl library for use in the US. Tom