1. Topic:
A bugfix release of Secure Web Server 3.2 (U.S.) is now available.
2. Problem description:
Secure Web Server 3.2 did not start properly when multiple SSL-enabled
virtual hosts were configured.
3. Bug IDs fixed (see bugzilla for more information):
11162 - Startup error with multiple SSL certificates
4. Relevant releases/architectures:
Red Hat Secure Web Server 3.2 - i386
5. Obsoleted by:
N/A
6. Conflicts with:
N/A
7. RPMs required:
Intel:
ftp://ftp.redhat.com/secureweb/3.2/i386/secureweb-3.2.1-1.i386.rpm.rhmask
ftp://ftp.redhat.com/secureweb/3.2/i386/secureweb-devel-3.2.1-1.i386.rpm
ftp://ftp.redhat.com/secureweb/3.2/i386/secureweb-manual-3.2.1-1.i386.rpm
Source:
ftp://ftp.redhat.com/secureweb/3.2/SRPMS/secureweb-3.2.1-1.nosrc.rpm
8. Solution:
Some of these files are distributed in rhmask format, and may
only be used by individuals who have purchased Red Hat Linux 6.2
Professional.
To produce installable RPM files from the rhmask files, retrieve
the rhmask files via ftp and type the following:
rhmask secureweb-3.2-12.i386.rpm secureweb-3.2.1-1.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).
For each RPM for your particular architecture, run:
rpm -Fvh [filename]
where filename is the name of the RPM.
To restart your Secure Web Server, type the following:
/etc/rc.d/init.d/httpsd restart
9. Verification:
MD5 sum Package Name
-------------------------------------------------------------------------
d6f89b66263e11dd26878b7cd0054885 3.2/SRPMS/secureweb-3.2.1-1.nosrc.rpm
30c5979fe1f1bad0170e5d08ca209e11 3.2/i386/secureweb-3.2.1-1.i386.rpm.rhmask
3e8ce8ab3ff0a4883a5be349d1423b83 3.2/i386/secureweb-devel-3.2.1-1.i386.rpm
08680702b667820bbba91ce912889979 3.2/i386/secureweb-manual-3.2.1-1.i386.rpm
These packages are GPG signed by Red Hat, Inc. for security. Our key
is available at:
http://www.redhat.com/about/contact.html
You can verify each package with the following command:
rpm --checksig filename
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 filename
Note that you need RPM >= 3.0 to check GnuPG keys.
10. References:
N/A