Message-ID: <200311240846.hAO8kqm24498@lacrosse.corp.redhat.com>
From: bugzilla at redhat.com (bugzilla@...hat.com)
Subject: [RHSA-2003:296-01] Updated stunnel packages available

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

- ---------------------------------------------------------------------
                   Red Hat Security Advisory

Synopsis:          Updated stunnel packages available
Advisory ID:       RHSA-2003:296-01
Issue date:        2003-11-24
Updated on:        2003-11-24
Product:           Red Hat Linux
Keywords:          stunnel signal
Cross references:  RHSA-2003:297
Obsoletes:         RHSA-2003:221
CVE Names:         CAN-2002-1563 CAN-2003-0740
- ---------------------------------------------------------------------

1. Topic:

Updated stunnel packages are now available for Red Hat Linux 7.1, 7.2, 7.3,
and 8.0 systems.  These updates address problems stemming from improper use
of non-reentrant functions in signal handlers.

2. Relevant releases/architectures:

Red Hat Linux 7.1 - i386
Red Hat Linux 7.2 - i386, ia64
Red Hat Linux 7.3 - i386
Red Hat Linux 8.0 - i386

3. Problem description:

Stunnel is a wrapper for network connections. It can be used to tunnel an
unencrypted network connection over an encrypted connection (encrypted
using SSL or TLS) or to provide an encrypted means of connecting to
services that do not natively support encryption.

A previous advisory provided updated packages to address re-entrancy
problems in stunnel's signal-handling routines.  These updates did not
address other bugs that were found by Steve Grubb, and introduced an
additional bug, which was fixed in stunnel 3.26.

All users should upgrade to these errata packages, which address these
issues by updating stunnel to version 3.26.

NOTE: After upgrading, any instances of stunnel configured to run in daemon
mode should be restarted, and any active network connections that are
currently being serviced by stunnel should be terminated and reestablished.

4. Solution:

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

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.

Please note that this update is also available via Red Hat Network.  Many
people find this an easier way to apply updates.  To use Red Hat Network,
launch the Red Hat Update Agent with the following command:

up2date

This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.

If up2date fails to connect to Red Hat Network due to SSL Certificate 
Errors, you need to install a version of the up2date client with an updated 
certificate.  The latest version of up2date is available from the Red Hat 
FTP site and may also be downloaded directly from the RHN website:

https://rhn.redhat.com/help/latest-up2date.pxt

5. RPMs required:

Red Hat Linux 7.1:

SRPMS:
ftp://updates.redhat.com/7.1/en/os/SRPMS/stunnel-3.26-1.7.1.src.rpm

i386:
ftp://updates.redhat.com/7.1/en/os/i386/stunnel-3.26-1.7.1.i386.rpm

Red Hat Linux 7.2:

SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/stunnel-3.26-1.7.3.src.rpm

i386:
ftp://updates.redhat.com/7.2/en/os/i386/stunnel-3.26-1.7.3.i386.rpm

ia64:
ftp://updates.redhat.com/7.2/en/os/ia64/stunnel-3.26-1.7.3.ia64.rpm

Red Hat Linux 7.3:

SRPMS:
ftp://updates.redhat.com/7.3/en/os/SRPMS/stunnel-3.26-1.7.3.src.rpm

i386:
ftp://updates.redhat.com/7.3/en/os/i386/stunnel-3.26-1.7.3.i386.rpm

Red Hat Linux 8.0:

SRPMS:
ftp://updates.redhat.com/8.0/en/os/SRPMS/stunnel-3.26-1.8.0.src.rpm

i386:
ftp://updates.redhat.com/8.0/en/os/i386/stunnel-3.26-1.8.0.i386.rpm



6. Verification:

MD5 sum                          Package Name
- --------------------------------------------------------------------------
cfd2b7c9519812d58a945d4b5e189fdd 7.1/en/os/SRPMS/stunnel-3.26-1.7.1.src.rpm
f05723a19a2990ce17ded0ce817890b5 7.1/en/os/i386/stunnel-3.26-1.7.1.i386.rpm
f1c75122248f440e96adff582de64520 7.2/en/os/SRPMS/stunnel-3.26-1.7.3.src.rpm
e307840b930fc50e4bb2b61a0578af5a 7.2/en/os/i386/stunnel-3.26-1.7.3.i386.rpm
cd223922c7a690d7dfcfdd2e49c49e24 7.2/en/os/ia64/stunnel-3.26-1.7.3.ia64.rpm
f1c75122248f440e96adff582de64520 7.3/en/os/SRPMS/stunnel-3.26-1.7.3.src.rpm
e307840b930fc50e4bb2b61a0578af5a 7.3/en/os/i386/stunnel-3.26-1.7.3.i386.rpm
071ab6a4091737a4292e631bd7490975 8.0/en/os/SRPMS/stunnel-3.26-1.8.0.src.rpm
d3718eebbd8b921de713c4914da22dec 8.0/en/os/i386/stunnel-3.26-1.8.0.i386.rpm


These packages are GPG signed by Red Hat for security.  Our key is
available from https://www.redhat.com/security/keys.html

You can verify each package with the following command:
    
    rpm --checksig -v <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:
    
    md5sum <filename>


7. References:

http://marc.theaimsgroup.com/?l=stunnel-users&m=105980139926784
http://marc.theaimsgroup.com/?l=stunnel-users&m=106221975232250
http://marc.theaimsgroup.com/?l=bugtraq&m=106260760211958
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-1563
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0740

8. Contact:

The Red Hat security contact is <secalert@...hat.com>.  More contact
details at https://www.redhat.com/solutions/security/news/contact.html

Copyright 2003 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/wcV5XlSAg2UNWIIRAnw4AJ9u7klajUMumofqL1o9vU6/uhjTGACeIRIC
ehS8TWOZF6fd+owIpBhNSwE=
=69GI
-----END PGP SIGNATURE-----

Powered by blists - more mailing lists