Account Links: Cart | Register | Log In

Skip to content

Red Hat Secure Web Server 2.0 Errata

(Updated: 03-Jan-1999)

Overview

The following are known problems with Red Hat Secure Web Server 2.0.

Detailed Errata

  • Package: Secure Web Server

    Updated: 07-Jun-1999

    Problem:

    • (07-Jun-1999):Notice
      This is a general errata release for Secure Web Server 2.0. It enables the server to properly display the RSA key password dialog at startup on Red Hat Linux 6.0 systems. However, Secure Web Server 2.0 still targets Red Hat Linux 5.2 and earlier as its primary platform; a new release tailored specially for Red Hat Linux 6.0 is forthcoming.

      If you are running Red Hat Linux 5.x, this errata is optional.

      Users of libc5-based Secure Web Server 2.0 (i.e. Red Hat Linux 4.2 systems) are not affected by this errata release, and should not attempt to upgrade..

      The secureweb packages are distributed as a rhmask file to comply with the single-CPU licensing agreement for the cryptographic portions of the server. 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 rhmask installed, please install it from your Red Hat Linux CD or a Red Hat Linux FTP site before proceeding.

    Solution:

    • Upgrade to:
      The new packages can be found at:

      ftp://updates.redhat.com/secureweb/2.0/i386

      Further Instructions To produce installable RPM files from the rhmask files, retrieve the rhmask files via ftp and do the following:

      rhmask secureweb-2.0-1libc6.i386.rpm secureweb-2.0-3libc6.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-3libc6.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-3libc6.i386.rpm

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

      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.

  • mod_perl

    Updated: 27-May-1999

    Problem:

    • (27-May-1999):Notice
      The mod_perl Apache module shipped with Red Hat Linux 5.2 and Secure Web Server 2.0 does not function properly with the latest errata release of perl available for that platform (perl-5.004m7-1). This is due to dependencies within mod_perl on perl itself.

      Users which rely on mod_perl functionality are encouraged to upgrade to a fixed version available at the following locations:

    Solution:

    • SSL Server

      Updated: 03-Jan-1999

      Problem:

      • (03-Jan-1999)Security Fix: A denial of service attack against the apache web server has been fixed.

      Solution:

      • These 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 new packages can be found on ftp.redhat.com in the secure web server errata directory.

        To produce installable RPM files from the rhmask files, do the following:

        Download the rhmasked RPM's
        Red Hat 4.2 (libc5) systems should download
        secureweb-2.0-2libc5.i386.rpm.rhmask
        secureweb-devel-2.0-2libc5.i386.rpm.rhmask
        secureweb-source-2.0-2libc5.i386.rpm.rhmask

        Red Hat 5.x (glibc2) systems should download
        secureweb-2.0-2libc6.i386.rpm.rhmask
        secureweb-devel-2.0-2libc6.i386.rpm.rhmask
        secureweb-source-2.0-2libc6.i386.rpm.rhmask

        Un-rhmask the RPM's

        Copy the rhmask rpms and the original rpms to /tmp and execute the following commands:

        For Red Hat 4.2 systems. 

        
rhmask secureweb-2.0-1libc5.i386.rpm secureweb-2.0-2libc5.i386.rpm.rhmask
rhmask secureweb-devel-2.0-1libc5.i386.rpm secureweb-devel-2.0-2libc5.i386.rpm.rhmask
rhmask secureweb-source-2.0-1libc5.i386.rpm secureweb-source-2.0-2libc5.i386.rpm.rhmask

        For Red Hat 5.x systems. 

        
rhmask secureweb-2.0-1libc6.i386.rpm secureweb-2.0-2libc6.i386.rpm.rhmask
rhmask secureweb-devel-2.0-1libc6.i386.rpm secureweb-devel-2.0-2libc6.i386.rpm.rhmask
rhmask secureweb-source-2.0-1libc6.i386.rpm secureweb-source-2.0-2libc6.i386.rpm.rhmask

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

        Once the new packages have been created, you can upgrade to them with:

        Red Hat 4.2:

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

        Red Hat 5.x:

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

        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.

    • mod_php

      Updated: 03-Jan-1999

      Problem:

      • (03-Jan-1999):Notice
        This update fixes some problems with the original package, plus works with the updated secureweb server.

      Solution:

    • mod_php3

      Updated: 03-Jan-1999

      Problem:

      • (03-Jan-1999):Notice
        This update fixes some problems with the original package, plus works with the updated secureweb server.

      Solution: