Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 21366 invoked by uid 500); 3 Jan 2003 05:09:03 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 21355 invoked from network); 3 Jan 2003 05:09:03 -0000 Received: from sabre.velocet.net (216.138.209.205) by daedalus.apache.org with SMTP; 3 Jan 2003 05:09:03 -0000 Received: from gej-it.com (H213.C220.tor.velocet.net [216.138.220.213]) by sabre.velocet.net (Postfix) with ESMTP id F19F4138039 for ; Fri, 3 Jan 2003 00:09:12 -0500 (EST) Received: from jeff ([192.168.0.101]) by gej-it.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.5.1.R) for ; Fri, 03 Jan 2003 00:07:02 -0500 From: "Jeff Cohen" To: Date: Fri, 3 Jan 2003 00:07:20 -0500 Message-ID: <000901c2b2e5$fede1f60$6500a8c0@jeff> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <4.3.2.7.0.20030102204940.00b711c0@mail.netnevada.net> X-MDRemoteIP: 192.168.0.101 X-Return-Path: apache@gej-it.com X-MDaemon-Deliver-To: users@httpd.apache.org X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: RE: [users@httpd] Apache HTTPS You can either, create a VirtualHost or add the line: Listen 443 To your conf file, or add the following line: Include /etc/httpd/ssl.conf and in that ssl.conf file add any configuration for the SSL, such as Listen , , AuthType and etc. All the best, Jeff Cohen > -----Original Message----- > From: Bill Parker [mailto:dogbert@netnevada.net] > Sent: Thursday, January 02, 2003 11:59 PM > To: suse-linux-e@suse.com > Cc: users@httpd.apache.org > Subject: [users@httpd] Apache HTTPS > > Hi All, > > I need to know how to get apache 1.3.23 working so it can service > HTTPS > requests properly. I have a Caldera OpenLinux 3.1.1 box which works fine > with > https:// so I know it should NOT be that hard on SuSE 8.0 > > Here is what I have installed: > > billp@nermal:~> rpm -q apache > apache-1.3.23-142 > > billp@nermal:~> rpm -q openssl > openssl-0.9.6c-80 > > billp@nermal:~> rpm -q mod_ssl > mod_ssl-2.8.7-110 > > Now I have added the the following lines to /etc/httpd/httpd.conf: > > after line 316 I inserted: > > AddModule mod_ssl.c > > This is the section which contains all the AddModule directives > > after line 267 I inserted: > > LoadModule ssl_module /usr/lib/apache/libssl.so > > Now in starting up apache with /etc/init.d/apache start, I see no LISTEN > requests > on port 443 (https/TCP), but in the /var/log/httpd/ssl_engine_log I get > the > info > listed below: > > [02/Jan/2003 14:49:36 18296] [info] Server: Apache/1.3.23, Interface: > mod_ssl/2.8.7, Library: OpenSSL/0.9.6c > [02/Jan/2003 14:49:36 18296] [info] Init: 1st startup round (still not > detached) > [02/Jan/2003 14:49:36 18296] [info] Init: Initializing OpenSSL library > [02/Jan/2003 14:49:36 18296] [info] Init: Seeding PRNG with 136 bytes of > entropy > [02/Jan/2003 14:49:36 18296] [info] Init: Generating temporary RSA > private > keys (512/1024 bits) > [02/Jan/2003 14:49:37 18296] [info] Init: Configuring temporary DH > parameters (512/1024 bits) > [02/Jan/2003 14:49:38 18297] [info] Init: 2nd startup round (already > detached) > [02/Jan/2003 14:49:38 18297] [info] Init: Reinitializing OpenSSL library > [02/Jan/2003 14:49:38 18297] [info] Init: Seeding PRNG with 136 bytes of > entropy > [02/Jan/2003 14:49:38 18297] [info] Init: Configuring temporary RSA > private keys (512/1024 bits) > [02/Jan/2003 14:49:38 18297] [info] Init: Configuring temporary DH > parameters (512/1024 bits) > [02/Jan/2003 14:49:38 18297] [info] Init: Initializing (virtual) servers > for SSL > > Can someone tell me what I am doing wrong, it shouldn't be so hard to get > apache > under SuSE 8.0 to process https:// > > Also, will SuSE be upgrading Apache to 1.3.27, since apache.org states > that > this > should be done to close all security issues? Or does keeping everything > patched > via Online Update in 'Yast2' cover apache 1.3.23 effectively? > > -Bill > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org