-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[slackware-security]  new mod_ssl packages (SSA:2004-207-02)

New mod_ssl packages are available for Slackware 8.1, 9.0, 9.1, 10.0
and -current to fix a security issue.  A format string vulnerability in
mod_proxy hook functions could allow an attacker to run code as the mod_ssl
user.  Sites using mod_ssl should upgrade (be sure to back up your existing
key files first).

Here are the details from the Slackware 10.0 ChangeLog:
+--------------------------+
Sun Jul 25 14:17:29 PDT 2004
patches/packages/mod_ssl-2.8.19_1.3.31-i486-1.tgz:
  Upgraded to mod_ssl-2.8.19-1.3.31.
  This fixes a security hole (ssl_log() related format string
  vulnerability in mod_proxy hook functions), so sites using mod_ssl
  should upgrade to the new version.  Be sure to back up your existing
  key files first.
  (* Security fix *)
+--------------------------+


Where to find the new packages:
+-----------------------------+

Updated package for Slackware 8.1:

Updated package for Slackware 9.0:

Updated package for Slackware 9.1:

Updated package for Slackware 10.0:

Updated package for Slackware -current:


MD5 signatures:
+-------------+

Slackware 8.1 package:
363f86afca6946e4840d7e2ed5efcc96  mod_ssl-2.8.19_1.3.31-i386-1.tgz

Slackware 9.0 package:
d213da77d2f8822206b76cf9c6c81067  mod_ssl-2.8.19_1.3.31-i386-1.tgz

Slackware 9.1 package:
d304dc1cf684e60c3611c998ac055986  mod_ssl-2.8.19_1.3.31-i486-1.tgz

Slackware 10.0 package:
efb6b8193b4c6189c9ae5fe2035526da  mod_ssl-2.8.19_1.3.31-i486-1.tgz

Slackware -current package:
efb6b8193b4c6189c9ae5fe2035526da  mod_ssl-2.8.19_1.3.31-i486-1.tgz


Installation instructions:
+------------------------+

First, stop apache:

# apachectl stop

IMPORTANT:  Backup any keys/certificates you wish to save for
mod_ssl (in /etc/apache/ssl.*)

Next, upgrade these packages as root:

# upgradepkg mod_ssl-2.8.19_1.3.31-i486-1.tgz

If necessary, restore any mod_ssl config files.

Finally, restart apache:

# apachectl startssl


+-----+

Slackware: 2004-207-02: new mod_ssl packages Security Update

July 26, 2004
New mod_ssl packages are available for Slackware 8.1, 9.0, 9.1, 10.0 and -current to fix a security issue

Summary

Here are the details from the Slackware 10.0 ChangeLog: Sun Jul 25 14:17:29 PDT 2004 patches/packages/mod_ssl-2.8.19_1.3.31-i486-1.tgz: Upgraded to mod_ssl-2.8.19-1.3.31. This fixes a security hole (ssl_log() related format string vulnerability in mod_proxy hook functions), so sites using mod_ssl should upgrade to the new version. Be sure to back up your existing key files first. (* Security fix *)

Where Find New Packages

Updated package for Slackware 8.1:
Updated package for Slackware 9.0:
Updated package for Slackware 9.1:
Updated package for Slackware 10.0:
Updated package for Slackware -current:

MD5 Signatures

Slackware 8.1 package: 363f86afca6946e4840d7e2ed5efcc96 mod_ssl-2.8.19_1.3.31-i386-1.tgz
Slackware 9.0 package: d213da77d2f8822206b76cf9c6c81067 mod_ssl-2.8.19_1.3.31-i386-1.tgz
Slackware 9.1 package: d304dc1cf684e60c3611c998ac055986 mod_ssl-2.8.19_1.3.31-i486-1.tgz
Slackware 10.0 package: efb6b8193b4c6189c9ae5fe2035526da mod_ssl-2.8.19_1.3.31-i486-1.tgz
Slackware -current package: efb6b8193b4c6189c9ae5fe2035526da mod_ssl-2.8.19_1.3.31-i486-1.tgz

Severity
[slackware-security] new mod_ssl packages (SSA:2004-207-02)
New mod_ssl packages are available for Slackware 8.1, 9.0, 9.1, 10.0 and -current to fix a security issue. A format string vulnerability in mod_proxy hook functions could allow an attacker to run code as the mod_ssl user. Sites using mod_ssl should upgrade (be sure to back up your existing key files first).

Installation Instructions

Installation instructions: First, stop apache: # apachectl stop IMPORTANT: Backup any keys/certificates you wish to save for mod_ssl (in /etc/apache/ssl.*) Next, upgrade these packages as root: # upgradepkg mod_ssl-2.8.19_1.3.31-i486-1.tgz If necessary, restore any mod_ssl config files. Finally, restart apache: # apachectl startssl

Related News