Red Hat 3.2 RHSA-2001:164-08 Moderate: Directory Listing Threat

The main secureweb package is provided as an rhmask file. In order to generate the actual secureweb RPM package, you will need the secureweb-3.2-12 package file from the Secure Web Server CD. Then, using the rhmask command, generate the secureweb RPM package:

rhmask secureweb-3.2-12.i386.rpm secureweb-3.2.4-1.i386.rpm.rhmask

Before applying this update, make sure you have applied all previously released errata relevant to your system.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs.

5. Bug IDs fixed ( for more info):

6. RPMs required:

Red Hat Secure Web Server 3.2:

i386:

7. Verification:

MD5 sum Package Name 3097ba872708a54b64354a54a3e38771 3.2/en/secureweb/i386/secureweb-3.2.4-1.i386.rpm.rhmask 93f2a1bbe394454bf35c665b5ceebddf 3.2/en/secureweb/i386/secureweb-devel-3.2.4-1.i386.rpm f819ce00eea66d0524cba6f92c7a661e 3.2/en/secureweb/i386/secureweb-manual-3.2.4-1.i386.rpm

These packages are GPG signed by Red Hat, Inc. for security. Our key is available at: About

You can verify each package with the following command: rpm --checksig

If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg