____________________________________________________________________________
SuSE Security Announcement
Package: libmcrypt
Announcement-ID: SuSE-SA:2003:0010
Date: Wednesday, Feb. 26th 2003 11:20 MET
Affected products: 7.1, 7.2, 7.3, 8.0, 8.1
SuSE eMail Server 3.1
SuSE eMail Server III
SuSE Linux Connectivity Server
SuSE Linux Enterprise Server 7
SuSE Linux Enterprise Server 8
SuSE Linux Office Server
Vulnerability Type: local privilege escalation
remote denial-of-service
Severity (1-10): 3
SuSE default package: no
Cross References: CAN-2003-0031
CAN-2003-0032
Content of this advisory:
1) security vulnerability resolved: buffer overflow
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds:
- openssl
- vnc
- w3m
3) standard appendix (further information)
____________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
Libmcrypt is a data encryption library that is able to load crypto-
modules at run-time by using libltdl.
Versions of libmcrypt prior to 2.5.5 include several buffer overflows
that can be triggered by passing very long input to the mcrypt_*
functions.
The way libmcrypt handles dynamic crypto-modules via libltdl leads
to memory-leaks that can cause a Denial-of-Service condition. This
Problem can just be solved by linking modules static. This security
update does not solve the memory-leak problem to avoid compatibility
problems. Future releases of libmcrypt will be linked statically.
To add the new library to the shared library cache you have to run
ldconfig(8) as root. Additionally every program that is linked with
libmcrypt needs to be restarted. ldd(1) can be used to find out which
libraries are used by a program.
Another way to determine which process uses a shared library that
had been deleted is:
lsof -n 2>/dev/null | grep RPMDELETE | cut -d " " -f 1 | sort | uniq
There is no temporary fix known. Please install the new packages from
our FTP servers.
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
Intel i386 Platform:
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-2.5.2-48.i586.rpm
6dc3127a069545b9cb00cafd9897021f
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-2.5.2-48.i586.patch.rpm
3b88d2a7f1bf409ec6cdee4702c8dc40
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/libmcrypt-2.5.2-48.src.rpm
8feed7301cb26aaa27084baea4a1677e
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-devel-2.5.2-48.i586.rpm
52bdf4a54df9fc698971fc1223b73d3d
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-devel-2.5.2-48.i586.patch.rpm
5ecc44d5b4d6f35a4f57db1d7092575e
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/libmcrypt-2.5.2-48.src.rpm
8feed7301cb26aaa27084baea4a1677e
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec2/libmcrypt-2.4.20-114.i386.rpm
45997d80e97ce180a14b692b1f63b34b
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec2/libmcrypt-2.4.20-114.i386.patch.rpm
5ee228e095fbb3f53027a8a902978975
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/libmcrypt-2.4.20-114.src.rpm
6c189dcf7bcbffa7f271cdeb9065e212
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/d4/libmcrypt-devel-2.4.20-114.i386.rpm
36b45ac7281a3dd2ba94794e26012180
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/d4/libmcrypt-devel-2.4.20-114.i386.patch.rpm
21ad28cb8dad5e418f0185b53470502c
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/libmcrypt-2.4.20-114.src.rpm
6c189dcf7bcbffa7f271cdeb9065e212
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/libmcrypt-2.4.15-98.i386.rpm
f38972e593b79b8e22d5db86d9f75083
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/libmcrypt-2.4.15-98.src.rpm
8390dbcef0b58b3cca5141254f3af8ea
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/libmcrypt-devel-2.4.15-98.i386.rpm
6c5df7c177d88509aa10868142262868
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/libmcrypt-2.4.15-98.src.rpm
8390dbcef0b58b3cca5141254f3af8ea
SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/libmcrypt-2.4.10-59.i386.rpm
5ff561010a642a26f92b1a491df6317c
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/libmcrypt-2.4.10-59.src.rpm
5430bf5ca7f79c16248024cbd6eb735a
SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/libmcrypt-devel-2.4.10-59.i386.rpm
7afa785605e65106a3a250bd166ca2ef
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/libmcrypt-2.4.10-59.src.rpm
5430bf5ca7f79c16248024cbd6eb735a
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec2/libmcrypt-2.4.7-19.i386.rpm
4208d6905aa7c7dd13de30aa945f1693
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/libmcrypt-2.4.7-19.src.rpm
d6c0a61d874869ee3927af3b58335ff4
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec2/libmcrypt-devel-2.4.7-19.i386.rpm
03028dbcf99e6fe167a30cd9b2e6da0f
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/libmcrypt-2.4.7-19.src.rpm
d6c0a61d874869ee3927af3b58335ff4
Sparc Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/libmcrypt-2.4.15-53.sparc.rpm
ae638ffb875f53df64325e8e0a148807
source rpm(s):
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/libmcrypt-2.4.15-53.src.rpm
c6bdd14b370e0ca912e8ca7615580df0
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/libmcrypt-devel-2.4.15-53.sparc.rpm
846455cc24b212f7b7287332cababc06
source rpm(s):
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/libmcrypt-2.4.15-53.src.rpm
c6bdd14b370e0ca912e8ca7615580df0
AXP Alpha Platform:
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec2/libmcrypt-2.4.7-26.alpha.rpm
3789bb0a9411d85ec4514490f342a70f
source rpm(s):
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/libmcrypt-2.4.7-26.src.rpm
c8dd2a18ccb249ed384df14359ba094e
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec2/libmcrypt-devel-2.4.7-26.alpha.rpm
fa61fea31359365d07ccf45a56b1ca80
source rpm(s):
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/libmcrypt-2.4.7-26.src.rpm
c8dd2a18ccb249ed384df14359ba094e
PPC Power PC Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/libmcrypt-2.4.15-89.ppc.rpm
f75b386d8894c98fd0fa534d3560abbe
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/libmcrypt-2.4.15-89.src.rpm
5a3b3ce95652b81efb738b59aec1a7e4
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/libmcrypt-devel-2.4.15-89.ppc.rpm
6d3cea579e658b66ea62c97d4c58ce17
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/libmcrypt-2.4.15-89.src.rpm
5a3b3ce95652b81efb738b59aec1a7e4
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec2/libmcrypt-2.4.7-23.ppc.rpm
f097c1a2ce67b85cffb8f0076a6c09c3
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/libmcrypt-2.4.7-23.src.rpm
9df0c47eb030905edeed919750aec9df
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec2/libmcrypt-devel-2.4.7-23.ppc.rpm
dc79a537365aae51c27d60dabb2615bf
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/libmcrypt-2.4.7-23.src.rpm
9df0c47eb030905edeed919750aec9df
____________________________________________________________________________
2) Pending vulnerabilities in SuSE Distributions and Workarounds:
- OpenSSL
Update packages for the recently found weakness in the openssl package
are available on our ftp servers. An announcement concerning this issue
follows this announcement.
- VNC
VNC (Virtual Network Computing) uses a weak cookie generation process
which can be exploited by an attacker to bypass authentication.
New packages are currently being tested and will be available on our
FTP servers soon.
- w3m
The textbased web-browser w3m does not properly escape HTML tags.
A malicious HTML page or img alt attribute may lead to information
leakage. New packages will be available soon.
____________________________________________________________________________
3) standard appendix: authenticity verification, additional information
- Package authenticity verification:
SuSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) execute the command
md5sum <name-of-the-file.rpm>
after you downloaded the file from a SuSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SuSE in rpm packages for SuSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SuSE Linux distributions version 7.1 and thereafter install the
key "build@suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SuSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- general/linux/SuSE security discussion.
All SuSE security announcements are sent to this list.
To subscribe, send an email to
<suse-security-subscribe@suse.com>.
suse-security-announce@suse.com
- SuSE's announce-only mailing list.
Only SuSE's security announcements are sent to this list.
To subscribe, send an email to
<suse-security-announce-subscribe@suse.com>.
For general information or the frequently asked questions (faq)
send mail to:
<suse-security-info@suse.com> or
<suse-security-faq@suse.com> respectively.
=====================================================================
SuSE's security contact is <security@suse.com> or <security@suse.de>.
The <security@suse.de> public key is listed below.
=====================================================================
____________________________________________________________________________
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SuSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>
Bye,
Thomas
--
Thomas Biege <thomas@suse.de>
SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg
Function: Security Support & Auditing
"lynx -source http://www.suse.de/~thomas/contact/thomas.asc | gpg --import"
Key fingerprint = 7254 B15D B3C4 943F 485E 0BBD 8ECC D7CB C200 A213
--
Swimming through the Void
We hear the Words
We lose Ourselves
But we find it All
-- Serj Tankian (Arials Lyrics)
____________________________________________________________________________
SuSE Security Announcement
Package: openssl
Announcement-ID: SuSE-SA:2003:011
Date: Wednesday, Feb. 26th 2003 15:20 MET
Affected products: 7.1, 7.2, 7.3, 8.0, 8.1
SuSE Linux Database Server,
SuSE eMail Server III, 3.1
SuSE Linux Enterprise Server 7
SuSE Linux Enterprise Server 8
SuSE Linux Firewall on CD/Admin host
SuSE Linux Connectivity Server
SuSE Linux Office Server
Vulnerability Type: remote attack on encryption
Severity (1-10): 5
SuSE default package: yes
Cross References: CAN-2003-0078
Content of this advisory:
1) security vulnerability resolved: openssl
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds:
- vnc
- w3m
3) standard appendix (further information)
____________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
OpenSSL is an implementation of the Secure Sockets Layer and Transport
Layer Security protocols and provides strong cryptography for many
applications in a Linux system. It is a default package in all SuSE
products.
A security weakness has been found, known as "Vaudenay timing attack
on CBC", named after one of the discoverers (Brice Canvel (EPFL), Alain
Hiltgen (UBS), Serge Vaudenay (EPFL), and Martin Vuagnoux (EPFL, Ilion)).
The weakness may allow an attacker to obtain a plaintext data block by
observing timing differences in response to two different error cases
(cipher padding errors vs. MAC verification errors).
In order to exploit this vulnerability, the attacker has to meet certain
requirements: The network connection between client and server must be
of high quality to be able to observe timing differences, the attacker
must be able to perform a man-in-the-middle attack, the transactions
must repeatedly contain the same (encrypted) plain text block (such as
a pop password or alike), and decoding failures in the SSL layer must
not be propagated to the application that is using the SSL connection.
These exploitation conditions considerably reduce the security risk
imposed by the vulnerability. However, we recommend to completely
remedy this weakness by installing the update packages for your system
according to the following guidelines. There does not exist any temporary
workaround for this problem other than applying the update packages.
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
SPECIAL INSTALLATION INSTRUCTIONS:
====================================
Please update your openssl package using the command
rpm -Fhv <package.rpm>
The operation of this command must not be interrupted! An interrupted
update of the openssl package may cause large protions of your system to
fail.
After performing the update, it is adviseable to run the command
"ldconfig" to update the shared library loading cache.
After the update, running processes in your system will continue to
use the shared libraries from the old package before the update.
Generally, it is necessary to restart all of these processes to
completely fix the vulnerability in your system. The command
lsof -n 2>/dev/null | grep RPMDELETE
can be used to find the binaries and processes that still use the old
shared libraries. In all cases, the next reboot of the system will cause
the old shared libraries to be completely removed from the system.
Alternatively, a transition to runlevel 1 (single user mode) and back
to the default runlevel will have the same effect.
Intel i386 Platform:
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-55.i586.rpm
7fbf4d975180a20ff8dedc8adbdecc59
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-55.i586.patch.rpm
6ed4321ec536aa718189702470c33091
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-55.src.rpm
90fc753346dd2aff00eee4c530cea84a
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-83.i386.rpm
d6246b820780993cc0e2b48597743a8f
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-83.i386.patch.rpm
2d933e913a9062de6a1fa35de969d211
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-83.src.rpm
b4b887a7311e9734a14d11e1a380f76e
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssl-0.9.6b-154.i386.rpm
d3c0f892441c09c8c5a689e2af04ba55
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-154.src.rpm
31ec962fe3549a713b9e6937190a88fb
SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssl-0.9.6a-78.i386.rpm
d14f67c34c589f168b750b18c9162508
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-78.src.rpm
2ba5a416d6ca3cb75c9aabb5a25bb532
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/openssl-0.9.6a-78.i386.rpm
c6b711573555982fadd31cfa179dd9dc
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/openssl-0.9.6a-78.src.rpm
d00df30aa6ec6a3872c58da709181879
Sparc Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/openssl-0.9.6b-87.sparc.rpm
6a8f19a49a698b93e740121321f59e5d
source rpm(s):
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-87.src.rpm
50712c3fd35042278063622ad5cc77c7
AXP Alpha Platform:
The packages for the 7.1-axp distribution will be published soon.
PPC Power PC Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssl-0.9.6b-147.ppc.rpm
051ef85d8e711819b2de38f55dc0023a
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-147.src.rpm
58631776b8fa88932eb57069a7f2878e
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/openssl-0.9.6a-28.ppc.rpm
da5e7caa177316f3016dd98497e580de
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/openssl-0.9.6a-28.src.rpm
b317144556c8f1890d15f304d95c5764
____________________________________________________________________________
2) Pending vulnerabilities in SuSE Distributions and Workarounds:
- vnc
VNC (Virtual Network Computing) uses a weak cookie generation process
which can be exploited by an attacker to bypass authentication.
New packages are currently being tested and will be available on our
FTP servers soon.
- w3m
The textbased web-browser w3m does not properly escape HTML tags.
A malicious HTML page or img alt attribute may lead to information
leakage. New packages will be available soon.
____________________________________________________________________________
3) standard appendix: authenticity verification, additional information
- Package authenticity verification:
SuSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) execute the command
md5sum <name-of-the-file.rpm>
after you downloaded the file from a SuSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SuSE in rpm packages for SuSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SuSE Linux distributions version 7.1 and thereafter install the
key "build@suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SuSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- general/linux/SuSE security discussion.
All SuSE security announcements are sent to this list.
To subscribe, send an email to
<suse-security-subscribe@suse.com>.
suse-security-announce@suse.com
- SuSE's announce-only mailing list.
Only SuSE's security announcements are sent to this list.
To subscribe, send an email to
<suse-security-announce-subscribe@suse.com>.
For general information or the frequently asked questions (faq)
send mail to:
<suse-security-info@suse.com> or
<suse-security-faq@suse.com> respectively.
=====================================================================
SuSE's security contact is <security@suse.com> or <security@suse.de>.
The <security@suse.de> public key is listed below.
=====================================================================
____________________________________________________________________________
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SuSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>
- -
| Roman Drahtmüller <draht@suse.de> // "You don't need eyes to see, |
SuSE Linux AG - Security Phone: // you need vision!"
| Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless |
- -
SuSE Linux Advisories: libmcrypt, openssl
By
Get the Free Newsletter!
Subscribe to Developer Insider for top news, trends, & analysis