- Issued:
- 2004-05-11
- Updated:
- 2004-05-11
RHBA-2004:214 - Bug Fix Advisory
Synopsis
Updated imap packages available
Type/Severity
Bug Fix Advisory
Topic
An updated imap-devel package which fixes a symbol conflict in the c-client library is now
available.
Description
The imap package provides server daemons for both the IMAP (Internet Message Access Protocol)
and POP (Post Office Protocol) mail access protocols. The POP protocol uses a "post office"
machine to collect mail for users and allows users to download mail to a local machine for
reading. The IMAP protocol allows users to read mail on a remote machine without downloading
it to a local machine.
The imap-devel package contains the header files and static libraries for developing programs
which will use the IMAP (Internet Message Access Protocol) library.
Both the c-client libary and the cyrus-sasl library contain routines to perform CRAM-MD5
authentication with associated utility routines. Both libraries named their routines with the same
global names but had different API's. When linking a program that use both cyrus-sasl and c-
client libraries, the linker could potentially select the wrong symbol, resulting in a run-time
error. It is not necessary for some of the symbols in c-client to be globally visible. By making the
CRAM-MD5 utility routines private to the CRAM-MD5 module, it elminates the potential for
incorrect symbol resoulution when linking with both c-client and cyrus-sasl.
This change effects only those programs or libraries that link against c-client. Because the c-
client library is part of the imap-devel subpackage, it is only provided as a static library. Progams
will have to be relinked or rebuilt for the change to be effective. The fact that the c-client library
is not a shared library means updating this package will not effect any existing programs already
installed on a system.
Users of Red Hat Enterprise Linux 3 should upgrade to these updated packages
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:
Affected Products
- Red Hat Enterprise Linux Server 3 x86_64
- Red Hat Enterprise Linux Server 3 ia64
- Red Hat Enterprise Linux Server 3 i386
- Red Hat Enterprise Linux Workstation 3 x86_64
- Red Hat Enterprise Linux Workstation 3 ia64
- Red Hat Enterprise Linux Workstation 3 i386
- Red Hat Enterprise Linux for IBM z Systems 3 s390x
- Red Hat Enterprise Linux for IBM z Systems 3 s390
- Red Hat Enterprise Linux for Power, big endian 3 ppc
Fixes
- BZ - 118137 - PHP imap_open crashes when remote servers used CRAM-MD5
CVEs
(none)
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.