Redhat secure server - Dec 1998 - Red Hat Secure Server updates

-----BEGIN PGP SIGNED MESSAGE-----

This is a general errata update for Secure Web Server 2.0.  The server
is now based on Apache 1.3.3 instead of Apache 1.3.1.  PHP(2) and PHP3
have been updated, as well as mod_perl.  Several severe bugs in the
secureweb-devel package which made building third party Dynamic Shared
Object modules difficult have been fixed.

The secureweb packages are distributed as a rhmask file to comply with
our patent licensing agreements with RSA Data Security, Inc. for their
encryption technology. To use them, you need to use the
''rhmask''
utility which is distributed as a part of Red Hat Linux.  If you do
not already have it installed, please install it from your Red Hat
Linux CD or ftp site before proceeding.  The other packages are normal RPMs.

The new packages can be found on ftp.redhat.com in the directory
/pub/redhat/updates/secureweb/2.0/i386.

To produce installable RPM files from the rhmask files, retrieve the
rhmask files via ftp and do the following, depending on which version
of Red Hat Linux you are using:

Red Hat 5.x:
- ------------
rhmask secureweb-2.0-1libc6.i386.rpm \
	secureweb-2.0-2libc6.i386.rpm.rhmask

The original RPM is located only on your Secure Web Server CD, and
cannot be obtained via the Internet. Note: if you do not have the original
RPM located in the same directory as the rhmask file, you will need to
prefix the name of the RPM with the full path name to its location
(i.e. on your installation CD).

Once the new package has been created, you can upgrade with:

rpm -Uvh secureweb-2.0-2libc6.i386.rpm

If you wish to upgrade any of the Secure Web Server development
packages, you can do so as follows:

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/secureweb-devel-2.0-2libc6.i386.rpm

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/secureweb-source-2.0-2libc6.i386.rpm

If you are using PHP(2), PHP3, or mod_perl, upgrade them as follows:

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/mod_perl-1.16-1libc6.i386.rpm

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/mod_php-2.0.1-6libc6.i386.rpm

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/mod_php3-3.0.5-3libc6.i386.rpm


Red Hat 4.2:
- ------------
rhmask secureweb-2.0-1libc5.i386.rpm \
       secureweb-2.0-2libc5.i386.rpm.rhmask

The original RPM is located only on your Secure Web Server CD, and
cannot be obtained via the Internet. Note: if you do not have the original
RPM located in the same directory as the rhmask file, you will need to
prefix the name of the RPM with the full path name to its location
(i.e. on your installation CD).

Once the new package has been created, you can upgrade with:

rpm -Uvh secureweb-2.0-2libc5.i386.rpm

If you wish to upgrade any of the Secure Web Server development
packages, you can do so as follows:

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/secureweb-devel-2.0-2libc5.i386.rpm

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/secureweb-source-2.0-2libc5.i386.rpm

If you are using PHP(2), PHP3, or mod_perl, upgrade them as follows:

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/mod_perl-1.16-1libc5.i386.rpm

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/mod_php-2.0.1-4libc5.i386.rpm

rpm -Uvh
ftp://updates.redhat.com/secureweb/2.0/i386/mod_php3-3.0.5-2libc5.i386.rpm


-
-------------------------------------------------------------------------------

Note: two Apache modules which were previously compiled as Shared
Objects (.so files) have now been directly included into the apache
binary, as is the default for apache 1.3.3.  They are mod_log_config
and mod_proxy.  If you have LoadModule directives for these two
modules in your /etc/httpd/conf/httpd.conf file, Secure Web Server
will give errors at startup time and refuse to run until the offending
lines are commented out or removed.  The standard httpd.conf file that
is shipped in the new packages does not have these lines, but if you
are keeping your own configuration file, you will have to make this
change manually.

To restart your Secure Web Server, do the following:

/etc/rc.d/init.d/httpsd restart

These packages have been PGP signed by Red Hat for security.

Cristian
- --
- ----------------------------------------------------------------------
Cristian Gafton   --   gafton@redhat.com   --   Red Hat Software, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 UNIX is user friendly. It''s just selective about who its friends are.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNn/yjPGvxKXU9NkBAQE6mgP+PvqBzEij8Y2c49aQSHDeW9o+q0FzBQsd
qBusKi061BB7yMT1l7ynqrpby9rFJQV63PJT2H8UB42nmruQBtJe0wrW0kX56+oA
RAhXa+i5hbFy6qR/gg+ISiahIYiUamFQzKobN3rDPlj4+U1HWIgymFTMMRmicBNm
zkQoDVnhiiU=Jlva
-----END PGP SIGNATURE-----

Does the errata update include SUEXEC support? We really need the
support on our secure server.

Thanks.
> 
> This is a general errata update for Secure Web Server 2.0.  The server
> is now based on Apache 1.3.3 instead of Apache 1.3.1.  PHP(2) and PHP3

-- 
========================================================================Clinton
Work                                     workc@cadvision.com
Calgary, Alberta

> Does the errata update include SUEXEC support? We really need the
> support on our secure server.

I second that motion.

-- Andy
_________________________

Andrew R. Beebe
Maine Web Design
RR 2 Box 363 A
Bridgton, ME 04009
(207) 647-8411
http://www.datamaine.com
_________________________

On Wed, 23 Dec 1998, Clinton Work wrote:
> 
> Does the errata update include SUEXEC support? We really need the
> support on our secure server.
The errata update includes SUEXEC.  HOWEVER, it is not enabled by default,
because we don''t want to ship a program with possible security
concerns,
even though it has been thoroughly reviewed and tested.

You will have to enabled the SUID ownership of /usr/sbin/suexec for
yourself; we shipped with normal permissions.

---
  Preston Brown          
  Red Hat Software, Inc. 
  pbrown@redhat.com

> You will have to enabled the SUID ownership of /usr/sbin/suexec for
> yourself; we shipped with normal permissions.
Is that all we "should" have to do? I did a chmod 4711
/usr/sbin/suexec
as per the suexec instructions but when I stopped and started httpsd, it
still didn''t start with suexec enabled. Is there anything else we need
to do?

-- Andy
_________________________

Andrew R. Beebe
Maine Web Design
RR 2 Box 363 A
Bridgton, ME 04009
(207) 647-8411
http://www.datamaine.com
_________________________

> You will have to enabled the SUID ownership of /usr/sbin/suexec for
> yourself; we shipped with normal permissions.
I found out what the problem was. The secure server didn''t say it was
starting with suexec like the old Apache used to, it was in the log
files.

I also noticed that suexec was set to a document root of
/home/httpd/htdocs, instead of what secure server defaults to as
/home/httpd/html.

-- Andy
_________________________

Andrew R. Beebe
Maine Web Design
RR 2 Box 363 A
Bridgton, ME 04009
(207) 647-8411
http://www.datamaine.com
_________________________

Hi There,

The manual does a nice job covering requesting a new certificate.
How about moving one?  Specificlly moving a certiciate from one server to
another.  

If I understand it correctly there should be some type of import 
facilty.  Likewise on our existing server there should be
some type of export facility.

To be specific we are moving from a stronghold server to a Red Hat Secure
Server.  This seems like it should not be too difficult since both are
based on ssleay. 

Any help would be greatly appreciated

Thanks
Brad

On Sun, 27 Dec 1998, Andrew Beebe wrote:
> I also noticed that suexec was set to a document root of
> /home/httpd/htdocs, instead of what secure server defaults to as
> /home/httpd/html.
I apologize about this, if we have an errata release in the future, this
will be corrected.  However, because suexec isn''t supported by us, I
can''t
issue a new errata release to only correct this flaw.

Thank you for reporting it however.

---
 -Preston Brown
  Red Hat Software, Inc.
  pbrown@redhat.com

> > To be specific we are moving from a stronghold server to a Red Hat
Secure
> > Server.  This seems like it should not be too difficult since both are
> > based on ssleay.
>
> You should be able to use your certificate from Stronghold with Secure
> Server without any modifications.  Simply rename your key(s) and
> certificate(s) to the names specified in the manual, fire up the server,
> and you should be all set.

Indeed this true.  Thanks for the help

--
Brad

On Mon, 28 Dec 1998, Bradley Glonka wrote:
> To be specific we are moving from a stronghold server to a Red Hat Secure
> Server.  This seems like it should not be too difficult since both are
> based on ssleay. 
You should be able to use your certificate from Stronghold with Secure
Server without any modifications.  Simply rename your key(s) and
certificate(s) to the names specified in the manual, fire up the server,
and you should be all set.

---
 -Preston Brown
  Red Hat Software, Inc.
  pbrown@redhat.com


From mail@mail.redhat.com Sun Jan 3 19:48:07 1999
Received: (qmail 17474 invoked from network); 4 Jan 1999 01:06:03 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 4 Jan 1999 01:06:03 -0000
Received: from linuxcentral.com (linuxcentral.com [208.196.180.202])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id TAA22368
	for <redhat-secure-server@redhat.com>; Sun, 3 Jan 1999 19:48:07 -0500
Received: from localhost (bradley@localhost)
	by linuxcentral.com (8.8.7/8.8.7) with SMTP id SAA28163
	for <redhat-secure-server@redhat.com>; Sun, 3 Jan 1999 18:52:25 -0500
Date: Sun, 3 Jan 1999 18:52:24 -0500 (EST)
From: Bradley Glonka <bradley@linuxcentral.com>
To: redhat-secure-server@redhat.com
Subject: Re: Moving a Certificate
In-Reply-To: <Pine.LNX.4.05.9901031935450.9958-100000@xanadu.redhat.com>
Message-ID: <Pine.LNX.3.96.990103185201.26915C-100000@linuxcentral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
> > To be specific we are moving from a stronghold server to a Red Hat
Secure
> > Server.  This seems like it should not be too difficult since both are
> > based on ssleay. 
> 
> You should be able to use your certificate from Stronghold with Secure
> Server without any modifications.  Simply rename your key(s) and
> certificate(s) to the names specified in the manual, fire up the server,
> and you should be all set.

Indeed this true.  Thanks for the help

--
Brad


From mail@mail.redhat.com Jan 04:48:03 1999  -0500
Received: (qmail 197 invoked from network); 4 Jan 1999 10:06:09 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 4 Jan 1999 10:06:09 -0000
Received: from iserv.ttns.net (root@iserv.ttns.net [207.215.76.2])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id EAA03340;
	Mon, 4 Jan 1999 04:48:03 -0500
Received: from bowale (tina.ttns.net [207.215.76.8])
	by iserv.ttns.net (8.8.7/8.8.7) with SMTP id BAA00891;
	Mon, 4 Jan 1999 01:49:44 -0800
Message-ID: <003901be37c7$85dbb2a0$084cd7cf@ttns.net>
Reply-To: "Timothy Ayodele" <toa@ttns.net>
From: "Timothy Ayodele" <toa@ttns.net>
To: <redhat-list@redhat.com>
Cc: <linux-admin@vger.rutgers.edu>, <linux-net@vger.rutgers.edu>,
        <redhat-secure-server@redhat.com>
Subject: Help!: http not responding .... 
Date: Mon, 4 Jan 1999 01:49:28 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800

I just installed RH5.2 with the kernel updates 2.0.36-3 on my system. I used
my RH4.2 named tables for the RH5.2.

I keep getting the following errors from httpd for all my domain listed...

Jan  3 06:01:30 iserv named[395]: ns_forw: query(wcmonline.org) contains our
address (ISERV.TTNS.NET:207.215.76.2)
Jan  3 06:01:30 iserv named[395]: Lame server on
''wcmonline.org'' (in
''WCMONLINE.org''?): [207.215.76.3].53
''NTSERV.TTNS.NET''
Jan  3 06:01:30 iserv named[395]: Lame server on
''wcmonline.org'' (in
''WCMONLINE.org''?): [206.13.31.12].53
''NS2.SCRM01.PBI.NET''
and more .....

Can any one tell me if there is any known issue with DNS on RH5.2 or does it
have a different table structure from RH 4.2? Please any advice will
help.....

Also my httpd is giving me a write protection error..... Any advice ?

Thank in Advance...

========================TTNS Internet
P.O. Box 101
Elk Grove, CA  95759-0101
Tech: 1-916-799-9741
admin@ttns.net     http://www.ttns.net/


From mail@mail.redhat.com Mon Jan 4 22:05:21 1999
Received: (qmail 418 invoked from network); 5 Jan 1999 03:23:48 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 5 Jan 1999 03:23:48 -0000
Received: from xanadu.redhat.com (pbrown@xanadu.redhat.com [199.183.24.86])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id WAA08486
	for <redhat-secure-server@redhat.com>; Mon, 4 Jan 1999 22:05:21 -0500
Received: from localhost (pbrown@localhost)
	by xanadu.redhat.com (8.8.7/8.8.7) with ESMTP id WAA22508
	for <redhat-secure-server@redhat.com>; Mon, 4 Jan 1999 22:02:43 -0500
X-Authentication-Warning: xanadu.redhat.com: pbrown owned process doing -bs
Date: Mon, 4 Jan 1999 22:02:42 -0500 (EST)
From: Preston Brown <pbrown@redhat.com>
To: redhat-secure-server@redhat.com
Subject: RE: DSO woes (mod_perl & mod_php3) with Secure server 2.0
In-Reply-To:
<398CA5A5CAF0D1119BC00000F840E86D8290C3@uspto-is-105.uspto.gov>
Message-ID: <Pine.LNX.4.05.9901042202170.9958-100000@xanadu.redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 31 Dec 1998 Jon.Radel@USPTO.GOV wrote:
> And now to try figure out a new one:  why PHP3 appears to seg fault the
> httpsd child processes under certain circumstances.  Sigh.
Oh, that''s terrific. :(

Do you have it pinned down to anything in particular?  We''ve had no
other
reports of this that I have seen.

---
 -Preston Brown
  Red Hat Software, Inc.
  pbrown@redhat.com


From mail@mail.redhat.com Tue Jan 5 10:15:17 1999
Received: (qmail 13592 invoked from network); 5 Jan 1999 15:33:58 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 5 Jan 1999 15:33:58 -0000
Received: from mail2.uspto.gov (mail2.uspto.gov [151.200.97.39])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id KAA24485
	for <redhat-secure-server@redhat.com>; Tue, 5 Jan 1999 10:15:17 -0500
From: Jon.Radel@USPTO.GOV
Received: from uspto-mta-01.uspto.gov (exchange-gw-1.uspto.gov [151.207.9.29])
	by mail2.uspto.gov (8.8.8/8.8.8) with ESMTP id KAA28917
	for <redhat-secure-server@redhat.com>; Tue, 5 Jan 1999 10:14:10 -0500
(EST)
Received: by uspto-mta-01.uspto.gov with Internet Mail Service (5.5.2232.9)
	id <Z2ZLCC10>; Tue, 5 Jan 1999 10:15:07 -0500
Message-ID:
<398CA5A5CAF0D1119BC00000F840E86D8290C6@uspto-is-105.uspto.gov>
To: redhat-secure-server@redhat.com
Subject: RE: DSO woes (mod_perl & mod_php3) with Secure server 2.0
Date: Tue, 5 Jan 1999 10:15:02 -0500 
Return-Receipt-To: Jon.Radel@USPTO.GOV
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain

I''ve made the seg faults go away, without complete assurance that I
found
the root cause.  I strongly suspect it was my failure to turn magic quoting
on for PHP3 while using the phpMyAdmin package, which clearly states that it
requires magic quoting.  I''m quite willing to consider this a PHP/MySQL
problem, rather than a secure server problem.

I''m more worried about the inability to use the mod_perl package and
secure
server 2.0 update, both from updates.redhat.com, and continue to use CGI
scripts.  If I load the mod_perl module, CGI scripts all fail to run.
Nothing in the log files about the problem, but the client browser gets a
"premature end of headers" error document from apache.  If I comment
out the
2 lines for adding mod_perl, CGI scripts all start working the way they
should.  This is on a Pentium, RH 5.1, with all updates which apply loaded.
Since the updates to the secure server 2.0 were already out by the time I
got around to updating from secure server 1.0 to secure server 2.0, I never
tried the revision of secure server 2.0 shipped on the CD-ROM.

As I wrote earlier, I had exactly the same problem when, on a different RH
5.1 Pentium, I compiled apache 1.3.2 from the official distribution and
tried to build mod_perl 1.16 from the official distribution.  That was a few
months ago, so I no longer remember all the details, but I know I eventually
gave up and built an apache executable with mod_perl built in.  Obviously, I
can''t do that with the secure server.

I would be most curious to know if this is a problem that is reproducible
and/or appears to go away with RH5.2 (which I believe has a slightly newer
glibc).  If nothing else, it would be useful to know if taking the time to
go from RH 5.1 to RH 5.2 is worth the time.

Thanks.

--Jon Radel
> -----Original Message-----
> From:	pbrown@redhat.com [SMTP:pbrown@redhat.com]
> Sent:	Monday, January 04, 1999 10:03 PM
> To:	redhat-secure-server@redhat.com
> Subject:	RE: DSO woes (mod_perl & mod_php3) with Secure server 2.0
> 
> On Thu, 31 Dec 1998 Jon.Radel@USPTO.GOV wrote:
> 
> > And now to try figure out a new one:  why PHP3 appears to seg fault
the
> > httpsd child processes under certain circumstances.  Sigh.
> 
> Oh, that''s terrific. :(
> 
> Do you have it pinned down to anything in particular?  We''ve had
no other
> reports of this that I have seen.
> 

From mail@mail.redhat.com Tue Jan 5 14:14:39 1999
Received: (qmail 7755 invoked from network); 5 Jan 1999 19:33:23 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 5 Jan 1999 19:33:23 -0000
Received: from g-net.net (root@ultrasparc-3.g-net.net [12.13.147.5])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id OAA04624
	for <redhat-secure-server@redhat.com>; Tue, 5 Jan 1999 14:14:39 -0500
Received: from [12.13.147.111] (pmbr-as53001-9.g-net.net [12.13.147.111])
	by g-net.net (8.8.7/8.8.7) with ESMTP id PAA23308
	for <redhat-secure-server@redhat.com>; Tue, 5 Jan 1999 15:16:13 -0500
X-Sender: jscott@mail.g-net.net (Unverified)
Message-Id: <v04003a17b2b7fd1a83d2@[12.13.147.85]>
In-Reply-To: 
 <398CA5A5CAF0D1119BC00000F840E86D8290C6@uspto-is-105.uspto.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 5 Jan 1999 12:39:29 -0500
To: redhat-secure-server@redhat.com
From: Jack Scott <jscott@jacksworld.com>
Subject: RE: DSO woes (mod_perl & mod_php3) with Secure server 2.0

Jon.Radel@USPTO.GOV wrote:

[deleted]
>  If I load the mod_perl module, CGI scripts all fail to run.
>Nothing in the log files about the problem, but the client browser gets a
>"premature end of headers" error document from apache.  If I
comment out the
>2 lines for adding mod_perl, CGI scripts all start working the way they
>should.
I''m having the same problem, server machine has RedHat 5.2 running on
Pentium II and Secure Server 2.0 with all the latest updates applied.
Commenting out the mod-perl LoadModule and AddModule lines fixes the
problem.

Jack Scott


--
Jack Scott
jscott@jacksworld.com



From mail@mail.redhat.com Tue Jan 5 15:49:02 1999
Received: (qmail 21621 invoked from network); 5 Jan 1999 21:07:48 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 5 Jan 1999 21:07:48 -0000
Received: from pip.devel.redhat.com (pbrown@pip.devel.redhat.com
[207.175.42.15])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id PAA09599
	for <redhat-secure-server@redhat.com>; Tue, 5 Jan 1999 15:49:02 -0500
Received: from localhost (pbrown@localhost)
	by pip.devel.redhat.com (8.8.7/8.8.7) with ESMTP id PAA06498
	for <redhat-secure-server@redhat.com>; Tue, 5 Jan 1999 15:48:21 -0500
X-Authentication-Warning: pip.devel.redhat.com: pbrown owned process doing -bs
Date: Tue, 5 Jan 1999 15:48:21 -0500 (EST)
From: Preston Brown <pbrown@redhat.com>
X-Sender: pbrown@pip.devel.redhat.com
To: redhat-secure-server@redhat.com
Subject: RE: DSO woes (mod_perl & mod_php3) with Secure server 2.0
In-Reply-To: <v04003a17b2b7fd1a83d2@[12.13.147.85]>
Message-ID: <Pine.LNX.4.04.9901051547480.5114-100000@pip.devel.redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 5 Jan 1999, Jack Scott wrote:
> Jon.Radel@USPTO.GOV wrote:
> 
> [deleted]
> >  If I load the mod_perl module, CGI scripts all fail to run.
> >Nothing in the log files about the problem, but the client browser gets
a
> >"premature end of headers" error document from apache.  If I
comment out the
> >2 lines for adding mod_perl, CGI scripts all start working the way they
> >should.
> 
> I''m having the same problem, server machine has RedHat 5.2 running
on
> Pentium II and Secure Server 2.0 with all the latest updates applied.
> Commenting out the mod-perl LoadModule and AddModule lines fixes the
> problem.
I''ll look into the mod_perl problem with the new SWS update in the next
few days.  Thanks for letting me know that you people are having problems,
we''ll get this resolved.

---
  Preston Brown          
  Red Hat Software, Inc. 
  pbrown@redhat.com      


From mail@mail.redhat.com Wed Jan 6 15:37:19 1999
Received: (qmail 10737 invoked from network); 6 Jan 1999 20:56:33 -0000
Received: from mail.redhat.com (199.183.24.239)
  by lists.redhat.com with SMTP; 6 Jan 1999 20:56:33 -0000
Received: from pip.devel.redhat.com (pbrown@pip.devel.redhat.com
[207.175.42.15])
	by mail.redhat.com (8.8.7/8.8.7) with ESMTP id PAA00268
	for <redhat-secure-server@redhat.com>; Wed, 6 Jan 1999 15:37:19 -0500
Received: from localhost (pbrown@localhost)
	by pip.devel.redhat.com (8.8.7/8.8.7) with ESMTP id PAA07726
	for <redhat-secure-server@redhat.com>; Wed, 6 Jan 1999 15:36:37 -0500
X-Authentication-Warning: pip.devel.redhat.com: pbrown owned process doing -bs
Date: Wed, 6 Jan 1999 15:36:37 -0500 (EST)
From: Preston Brown <pbrown@redhat.com>
X-Sender: pbrown@pip.devel.redhat.com
To: redhat-secure-server@redhat.com
Subject: Attention all mod_perl users:
Message-ID: <Pine.LNX.4.04.9901061526340.7367-100000@pip.devel.redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

If you have applied the update to Secure Web Server 2.0 for mod_perl
(version 1.16), you have probably noticed it breaks your regular CGI
scripts.  I''ve done quite a bit of research and discovered this
isn''t a
problem isolated to Secure Web Server, it is a problem with mod_perl 1.16
as a Dynamic Shared Object in general.  My testing today leads me to
believe that mod_perl 1.17 does NOT have this problem.  I am putting a
src and glibc i386 binary for mod_perl 1.17 in my home ftp directory for
those who would like to test it...I would really like to get 1 or 2 "yes,
it works well for me" answers before we release it as official errata.

Get it from:  ftp://ftp.redhat.com/home/pbrown/, and please mail me
personally with any success/failure stories.  If all goes well, we''ll
have
an errata release this week.

Red Hat regrets any problems we may have caused by releasing the buggy
1.16 version of mod_perl.

The software may not become visible for an hour or so, as it has to be
mirrored over from the internal FTP site to the external one.  However,
you should be able to get it later this evening.

---
  Preston Brown          
  Red Hat Software, Inc. 
  pbrown@redhat.com