openSUSE Security July 2002

security@lists.opensuse.org

193 participants
223 discussions

RE: [suse-security] IPsec (FreeS/WAN) and SuSEfirewall2
by Andreas Marbet 03 Jul '02

03 Jul '02

> From: Stefan Nilsen [mailto:stefan.nilsen@millnet.se] > Sent: Wednesday, July 03, 2002 7:17 PM > > > > ---------------- > > > conn xpfwlsn-xpfwnsn > > > left=193.193.193.200 > > > leftsubnet=192.168.1.0/24 > > > leftnexthop=193.193.193.193 > > > right=194.194.194.200 > > > rightsubnet=192.168.3.0/24 > > > rightnexthop=194.194.194.194 > > > auto=start Perhaps its not a good idea to set auto=start on both gw. One should have 'start', the other one 'add'. > > Maybe you could post your ipsec.conf and settings in > SuSEfirewall2? Please... ok here they are: my settings in SuSEfirewall2 are the same as you are using. And its correct not to use '$FW_DEV_EXT' in FW_MASQ_DEV but only your external interface. Otherwise all traffic on ipsec will get masqueraded before it arrives at FreeS/WAN and that doesn't work. ipsec.conf right (static IP): config setup interfaces=%defaultroute plutoload=%search plutostart=%search uniqueids=yes conn %default keyingtries=0 right=ext_IP_of_Right rightid=ext_IP_of_Right rightsubnet=192.168.100.0/24 rightnexthop=def_gw_of_right # connection for Andreas Marbet home conn amahome auto=add authby=rsasig rightrsasigkey=0sAQN.... compress=no left=0.0.0.0 leftsubnet=192.168.1.0/24 leftid=(a)vpnama.home leftrsasigkey=0sAQOQ.... # NO leftnexthop here in my case ipsec.conf left (in my case =roadwarrior): config setup interfaces=%defaultroute plutoload=amahome plutostart=amahome uniqueids=yes conn %default keyingtries=0 authby=rsasig compress=no right=ext_IP_of_Right rightid=ext_IP_of_Right rightsubnet=192.168.100.0/24 rightnexthop=192.168.100.91 #=internal IP of right conn amahome auto=start authby=rsasig rightrsasigkey=0sAQN... left=%defaultroute leftsubnet=192.168.1.0/24 leftid=(a)vpnama.home leftrsasigkey=0sAQOQ... is it a bit more clear? > Jul 3 18:57:30 xpfwl ipsec__plutorun: 112 "xpfwlsn-xpfwnsn" #2: > STATE_QUICK_I1: initiate > Jul 3 18:57:30 xpfwl ipsec__plutorun: 004 "xpfwlsn-xpfwnsn" #2: > STATE_QUICK_I2: sent QI2, IPsec SA established > Jul 3 18:57:30 xpfwl Pluto[2310]: "xpfwl-xpfwnsn" #3: > initiating Quick Mode > PSK+ENCRYPT+TUNNEL+PFS > Jul 3 18:57:30 xpfwl Pluto[2310]: "xpfwl-xpfwnsn" #3: sent > QI2, IPsec SA > established > Jul 3 18:57:30 xpfwl ipsec__plutorun: 112 "xpfwl-xpfwnsn" > #3: STATE_QUICK_I1: > initiate > Jul 3 18:57:30 xpfwl ipsec__plutorun: 004 "xpfwl-xpfwnsn" > #3: STATE_QUICK_I2: > sent QI2, IPsec SA established > Jul 3 18:57:30 xpfwl Pluto[2310]: "xpfwlsn-xpfwn" #4: > initiating Quick Mode > PSK+ENCRYPT+TUNNEL+PFS > Jul 3 18:57:30 xpfwl Pluto[2310]: "xpfwlsn-xpfwn" #4: sent > QI2, IPsec SA > established > Jul 3 18:57:30 xpfwl ipsec__plutorun: 112 "xpfwlsn-xpfwn" > #4: STATE_QUICK_I1: > initiate > Jul 3 18:57:30 xpfwl ipsec__plutorun: 004 "xpfwlsn-xpfwn" > #4: STATE_QUICK_I2: > sent QI2, IPsec SA established I assume this is going on and on and on.. but it looks good, you're very close. > > Don't know if IP-Protocol 51 is needed as well? > > Here it says that 51 is only needed if I use packet level > authentication. > Typical case is to use 50. I added it anyway, but it did not make any > difference. you are right, I just tried it myself > > Jul 3 14:31:42 xpfwl kernel: SuSE-FW-DROP-DEFAULT IN=ipsec0 > > OUT=eth1 SRC=194.194.194.200 DST=192.168.1.10 LEN=84 TOS=0x00 > > Why does it arrive on ipsec0, should be eth0. Taking the wrong tunnel? > I think it is correct for it arrive on ipsec0 (in the tunnel), and later > delivered to the machine on the subnet using eth1. But for some reason > SuSEfirewall2 does not want to deliver. an official IP shouldn't arrive on ipsec, it arrives on ethx even if it carries encrypted data which is then passed over to ipsec > Maybe there is a simple addition I can make to enable the route after the > SuSEfirewall2 is loaded? what does 'ipsec eroute' or 'route' tell you after starting ipsec on both ends? skol and good night, Andreas

1 0

ipchains - paketfilter
by Oliver Block 03 Jul '02

03 Jul '02

Hi, I want to setup a paket-filter on a computer which is running a squid-cache an rinetd-proxy for the local network. Is it correct, that squid and rinetd are using the input and output chains and not the forward chain. And does it make sense in your opinion to define new chains for that? tia Oliver __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Yahoo! präsentiert als offizieller Sponsor das Fußball-Highlight des Jahres: - http://www.FIFAworldcup.com

1 0

Re: [suse-security] SuSE-SA:2002:024
by Alexander Schiftner 03 Jul '02

03 Jul '02

Dear Günther, I understood that these special installation instructions ("--force --nodeps" or the "--oldpackage) where mentioned because of a version downgrade of openssh. As far as I know SuSE provided newer openssh packages but then decided to patch the old ones. That's why I think that I do not need these instructions. If I would use them they would maybe suppress the error message, nevertheless it is the best for me to update glibc to 2.2.4 too, as this was also a security update that I missed. best regards, Alex Schiftner At 14:04 03.07.2002 +0200, you wrote: >Dear Alexander, > >Am 03.07.2002 12:09:02, schrieb Alexander Schiftner ><alexander.schiftner(a)austrosoft.at>: > > >[...] > >server:~/rpm # rpm -Fhv openssh-2.9.9p2-102.i386.rpm > >in the special installation instructions wihtin the >announcement the use of the " "--force --nodeps" or the "-- >oldpackage" commandline option in addition to the "-Fhv" >option" is mentioned. I don't know if this will help, I just >saw that there was something missing in the commandline option. >Just in case I've appended the special installation >instructions. > >Kind Regards, >Günther Diederich > > SPECIAL INSTALLATION INSTRUCTIONS: > =================================== > * For SuSE Linux 6.4 through 7.3, the now offered packages >are a version > downgrade. The rpm command refuses to install the package >unless you > either use the "--force --nodeps" or the "--oldpackage" >commandline > option in addition to the "-Fhv" option. > * For the update package to become effective, you have to >restart the > running parent ssh daemon with the following command: > rcsshd stop ; rcsshd start > If you perform the update and the daemon restart via a >remote secure > shell connection, you might want to play safe by running >the command > echo "rcsshd stop; rcsshd start"|at now + 3 minutes > from a root shell. If your running instance of sshd gets >killed for > some reason, then your sshd will start again after three >minutes. > Afterwards, make sure that remote login to your host is >possible. > > > > -------- Alexander Schiftner Support Austrosoft Weiss Datenverarbeitung GmbH Hietzinger Hauptstrasse 33 1130 Wien / Austria Phone: +43 - 1 - 8776205 - 17 Fax: +43 - 1 - 8776205 - 21 mailto:alexander.schiftner@austrosoft.at http://www.austrosoft.at

2 1

RE: [suse-security] Gobbles Apache Exploit
by Alan Rouse 03 Jul '02

03 Jul '02

There seems to be a presumption that we are safe until proven otherwise, despite indications to the contrary. That worries me. In case you missed it, you should read this: http://online.securityfocus.com/archive/1/278446/2002-06-23/2002-06-29/0 (Possibly exploited on linux / intel in April). Keep in mind also that gobbles claims to have exploited linux. -----Original Message----- From: Roman Dorr [mailto:rdo@tro.net] Sent: Wednesday, July 03, 2002 4:20 AM To: suse-security(a)suse.com Subject: RE: [suse-security] Gobbles Apache Exploit Hi, afaik the exploit is targeted vs. *BSD Systems. Running it against our Apache's "only" resulted in higher load and error logs filling up. This potential DoS was still possible even with the latest Apache version though, so I wouldn't expect any update helping here. with kind regards, Roman Doerr > -----Original Message----- > From: Patrik Breitenmoser [mailto:pbreitenmoser@festland.ch] > Sent: Wednesday, July 03, 2002 10:03 AM > To: suse-security(a)suse.com > Subject: [suse-security] Gobbles Apache Exploit > > > > Hi, > > I was just wondering if my patched apache on suse 7.3 is save against that > exploit. > > regards > Patrik > > > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

2 1

root cannot delete file, thanx
by rutger 03 Jul '02

03 Jul '02

hello all, thanx for helping. the rootkit changed the attribute to i on the file. therefore even root couldnt delete it. after chattr -i on the file i could delete it. special thanx to r.drahtmueller greetings, r.frechen

1 0

What's the length of ssh keys?
by Praise 03 Jul '02

03 Jul '02

A friend of mine told me that 1024bit keys were broken, and he advised me to use 4096bit keys... I think he is confusing ssl with ssh. Do you have similar information on this? Praise

9 9

SuSE-SA:2002:024
by Alexander Schiftner 03 Jul '02

03 Jul '02

Dear all, I got a problem installing the patched openssh version on SuSE 7.3 . When I issue the rpm-command for installing I get the following error message: server:~/rpm # rpm -Fhv openssh-2.9.9p2-102.i386.rpm error: failed dependencies: libc.so.6(GLIBC_2.2.4) is needed by openssh-2.9.9p2-102 server:~/rpm # I am a little bit confused about that, because asking the rpm - database tells me that I have got glibc-2.2.2 . server:~/rpm # rpm -q glibc glibc-2.2.2-38 server:~/rpm # Anyone who knows about that problem ? regards, Alex -------- Alexander Schiftner Support Austrosoft Weiss Datenverarbeitung GmbH Hietzinger Hauptstrasse 33 1130 Wien / Austria Phone: +43 - 1 - 8776205 - 17 Fax: +43 - 1 - 8776205 - 21 mailto:alexander.schiftner@austrosoft.at http://www.austrosoft.at

2 1

RE: [suse-security] SuSE-SA:2002:023
by Mario Neubert 03 Jul '02

03 Jul '02

Hello List, i have installed OpenSSH 3.3p1 on Suse 7.3. After the hint to modify /etc/init.d/sshd and adding export LD_PRELOAD=/usr/lib/libcrypt.so, sshd works fine and seems to be stable. Should i downgrade to openssh-2.9.9? Thanks, Mario

3 2

httpd/mod_php/fileupload & segmentation faults
by Bastian Schmick 03 Jul '02

03 Jul '02

(I am reposting this because of a wrong In-Reply-To address in the original post - sorry for the inconvenience!) Hi, I am new to this list and I have a question concerning possible attacks on a webserver I am maintaining at my university. Regular checks of our logfiles turned up some strange requests coming from various IP addresses over the last week. They usually lasted for half an hour leaving the following entries in our logfiles: in /var/log/access_log: xxx.xxx.xxx.xxx - - [01/Jul/2002:19:24:51 +0200] "POST /index.php HTTP/1.1" 200 12781 ... (every 5 secs.) in /var/log/error_log: [Mon Jul 1 19:24:48 2002] [notice] child pid 877 exit signal Segmentation fault (11) ... (roughly 4000 segfaults altogether) The machine is running SuSE 7.3 with the following packages that may be related to these events: nue007:~ # rpm -q --all | grep "apache\|php" apache-devel-1.3.20-66 mod_php4-core-4.0.6-160 mod_php4-4.0.6-160 phpMyAdmin-2.2.0-21 apache-doc-1.3.20-66 apache-1.3.20-66 Perhaps this is nothing to worry about, but I was not sure and had a look on the internet. I assumed a connection with the PHP file upload vulnerabilities and exploits as discussed in <http://www.cert.org/advisories/CA-2002-05.html>, and <http://lists.insecure.org/vuln-dev/2002/Mar/0025.html> but thought that these were already patched using the above packages as described in <http://www.suse.de/de/support/security/2002_007_mod_php4_txt.html>. Does anybody know if there are other explanations for these segfaults? Am I still vulnerable even after doing regular security updates of all packages? How can I find out if my machine has been hacked? Perhaps this information is available somewhere on the Internet, but I didn´t find anything and am hoping that someone on this list can give me a hint. Thanks in advance, Bastian

2 4

SuSE Security Announcement: openssh (SuSE-SA:2002:024)
by Roman Drahtmueller 03 Jul '02

03 Jul '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: openssh Announcement-ID: SuSE-SA:2002:024 Date: Tuesday, Jul 2nd 2002 22:00 MEST Affected products: 6.4, 7.0, 7.1, 7.2, 7.3, 8.0 SuSE Linux Database Server, SuSE eMail Server III, SuSE Linux Enterprise Server, SuSE Linux Firewall on CD Vulnerability Type: possible remote access Severity (1-10): 3 SuSE default package: yes Content of this advisory: 1) security vulnerability resolved: openssh problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information SuSE Security has issued two warnings and one SuSE Security Announcement on 25th and 26th of June concerning the vulnerabilities found in the openssh package that is contained and installed by default on most SuSE products. For a few days, the nature of the errors were unknown to the public, making it difficult for distributors to provide proper solutions against the problem. Now that details of the errors have been disclosed, we hereby re-release SuSE Security Announcement SuSE-SA:2002:023 (openssh) under a new announcement ID with links to a set of update packages that represent SuSE's permanent fix for the problems found. After closer investigation it turned out that the packages in SuSE products were not vulnerable to the problems if the admin did not change the configuration file of the secure shell daemon (/etc/ssh/sshd_config). In particular, the administrator must actively have set the sshd_config option PAMAuthenticationViaKbdInt to "yes" for the installation to become vulnerable. Since the SuSE openssh packages are compiled without S/KEY support, they are not vulnerable to the second bug that is triggered by the option ChallengeResponseAuthentication if it is set to "yes" (default). The two configuration options correspond to the two security problems found in openssh. Our SuSE Linux distributions have seen a version upgrade from version 2.9.9p2 to 3.3p1 on Tuesday last week. In order to provide properly functioning packages for our products, we have decided to return to the commonly known stable version 2.9.9p2 with the necessary patch to fix the vulnerability for the SuSE Linux distributions 6.4 up to 7.3 and for our server products. SuSE Linux 8.0 came with the newer version 3.0.2p1 and will therefore be upgraded to openssh-3.4p1. We think that adding the patches to the existing versions without a version upgrade is best-service for our customers because we can provide a solution that we know not to break anything else. For more information about the bugs in openssh please visit the openssh project homepage at http://www.openssh.org/ and read the SuSE Security Announcements at http://www.suse.de/security/. 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. SPECIAL INSTALLATION INSTRUCTIONS: =================================== * For SuSE Linux 6.4 through 7.3, the now offered packages are a version downgrade. The rpm command refuses to install the package unless you either use the "--force --nodeps" or the "--oldpackage" commandline option in addition to the "-Fhv" option. * For the update package to become effective, you have to restart the running parent ssh daemon with the following command: rcsshd stop ; rcsshd start If you perform the update and the daemon restart via a remote secure shell connection, you might want to play safe by running the command echo "rcsshd stop; rcsshd start"|at now + 3 minutes from a root shell. If your running instance of sshd gets killed for some reason, then your sshd will start again after three minutes. Afterwards, make sure that remote login to your host is possible. Note: ====== In addition to the usual update packages, we have started providing "patch" packages a few days ago. The patch-rpm is an addition to the standard rpm package that consists of the binary changes to the package only. As such, these patch-rpm packages consume considerably less space to save resources during download and storage. We will officially announce the availability of this new packaging technique at SuSE shortly. i386 Intel Platform: SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssh-3.4p1-4.i386.patch… 94c4a554b59902816347a090cd0f6868 SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssh-3.4p1-4.i386.rpm e935b74725f6c5b336a56c6a2be47d9b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssh-3.4p1-4.src.rpm 4ea70c5f1e15343b984c5bbc1891cbbb SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssh-2.9.9p2-102.i386.r… d00552391dd7c7b1bafbb6199002741b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssh-2.9.9p2-102.src.rpm 84a7ce0f267a94bf2accf6b6fd668bb8 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssh-2.9.9p2-103.i386.r… 3d2afbcf5c2b2d85f4d3209e773d4877 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssh-2.9.9p2-103.src.rpm 49bab0993be8dd2742b4eac849b818a6 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/openssh-2.9.9p2-102.i386.r… 38f3dc8257b5bc20b7853b3537ce8cbb source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/openssh-2.9.9p2-102.src.rpm 689ab0e50631d88c207c68be86fcde3b SuSE-7.0 ftp://ftp.suse.de/pub/suse/i386/update/7.0/sec1/openssh-2.9.9p2-101.i386.rpm 0e280e54f4b8f40869ba30a6445cefe7 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/7.0/zq1/openssh-2.9.9p2-101.src.rpm 5f9cc1e1b595a5e96ca1c5197a2ce708 SuSE-6.4 ftp://ftp.suse.de/pub/suse/i386/update/6.4/sec1/openssh-2.9.9p2-100.i386.rpm 5dceb6fedf88887bb2fcfe585307f2ed source rpm: ftp://ftp.suse.de/pub/suse/i386/update/6.4/zq1/openssh-2.9.9p2-100.src.rpm 4f0fb935353b25560e155a8e0853b728 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/openssh-2.9.9p2-39.sparc.… 804425b14c394ed1a645602257a0f412 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssh-2.9.9p2-39.src.rpm 6eea48b1f6aef53a755938bcd7306378 SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/sec1/openssh-2.9.9p2-38.sparc.… 25979bd61822c84c4c3275cc99b5e386 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/openssh-2.9.9p2-38.src.rpm d1228bb5e26d69eedbf061646a67271c SuSE-7.0 ftp://ftp.suse.de/pub/suse/sparc/update/7.0/sec1/openssh-2.9.9p2-37.sparc.rpm 3d3a4e3cf0bd0768fa00460f52ed8d89 source rpm: ftp://ftp.suse.de/pub/suse/sparc/update/7.0/zq1/openssh-2.9.9p2-37.src.rpm c2b869d59828ea318323bea708b87975 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec1/openssh-2.9.9p2-42.alpha.rpm 92447fd373aab8e8c0265f5b17202ebd source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/openssh-2.9.9p2-42.src.rpm 755bb8485731155878efb56b621f9b1d SuSE-7.0 ftp://ftp.suse.de/pub/suse/axp/update/7.0/sec1/openssh-2.9.9p2-41.alpha.rpm ecbd5a39d693263985a3714c726beb90 source rpm: ftp://ftp.suse.de/pub/suse/axp/update/7.0/zq1/openssh-2.9.9p2-41.src.rpm 67f9fcbe7ae123d9ba91a652f17a6d4d SuSE-6.4 ftp://ftp.suse.de/pub/suse/axp/update/6.4/sec1/openssh-2.9.9p2-41.alpha.rpm 6b2336c4e0f0f41b1e853d1c99e99b51 source rpm: ftp://ftp.suse.de/pub/suse/axp/update/6.4/zq1/openssh-2.9.9p2-41.src.rpm 78f6cd253479161a582e1edbb490059e PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssh-2.9.9p2-72.ppc.rpm e13ed7cfe9fea868560435c34cba3b56 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssh-2.9.9p2-72.src.rpm fd9f91dda0207c62173a71f40bcf4228 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/openssh-2.9.9p2-72.ppc.rpm 354f6776649dc90ab4c58370f036fa3e source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/openssh-2.9.9p2-72.src.rpm 2e43d0ad97204214d85f500f445af7f5 SuSE-7.0 ftp://ftp.suse.de/pub/suse/ppc/update/7.0/sec1/openssh-2.9.9p2-71.ppc.rpm 7f0020f1443292d6f74740e7c306e50f source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/7.0/zq1/openssh-2.9.9p2-71.src.rpm adc52fb1be19f8d7f87ac2c1bf425b60 SuSE-6.4 ftp://ftp.suse.de/pub/suse/ppc/update/6.4/sec1/openssh-2.9.9p2-71.ppc.rpm d3e150e0f3bdd04a6ab8b9c47d43f005 source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/6.4/zq1/openssh-2.9.9p2-71.src.rpm d4fc34b96fb2b19929834260d43efef5 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - We are investigating if recently found weaknesses in resolver libraries on BSD systems affect the SuSE Linux glibc as well. - crontab/cron Paul Starzetz found a small bug in crontab that allows a local user to read the contents of the (read-protected) file /var/spool/cron/deny due to an inherited file descriptor from the crontab command that runs the editor to change the user's crontab. We will fix this problem in future releases, but due to the minor severity of the bug we don't provide update packages. - mozilla Cross-dependencies between mozilla and other packages in SuSE Linux products keep us from providing version upgrades for the mozilla packages. Fixing security bugs in our packages is usually done by adding the necessary patches to the existing version to ensure the compatibility and consistency that is expected from our products. In some cases (as with the mozilla package) the complexity of the issue does not allow to add patches any more. By consequence, security related issues in mozilla cannot be addressed. As a service to our user community, we provide packages of newer mozilla versions at ftp://ftp.suse.com/pub/projects/mozilla/. These packages have been verified to run fine; they are not located in the update directory of the distribution in question because we cannot make any claims about the compatibility with the other packages in the product. Security-aware users are encouraged to install the packages from the projects/ directory. - ghostscript RedHat released a security announcement concerning a problem in ghostscript, which could be exploited to gain privilege of the print server user. We are investigating whether SuSE Linux is affected. - fetchmail we are in the process of releasing a security update for fetchmail that corrects a vulnerability that could be exploited by hostile mail servers. ______________________________________________________________________________ 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(a)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 uninstalled 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(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel 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(a)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(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SuSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)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 cleartext signature shows proof of the authenticity of the text. SuSE GmbH 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(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- Roman Drahtmüller, SuSE Security. - -- - - | Roman Drahtmüller <draht(a)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 | - - -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPSIGGney5gA9JdPZAQHl+gf7BM1PWXqoxm0B+sghyQu835KburpV2U5Y B8kicZhzsq7V8oRiD7VNcGi/zJknL7kXik6Pv0M0/uvTr26FRQBHYjdrWhua92NH LzaS8DomoCWyOAvQvTvnSmmxp4Mr5sbfUbPAhU1dCbBUQA7glLLOZkcv6hULqgay v/hFjDatmZVDdnrxZsopliwmEGoehFO/CQCLhA6wqlBpdyrylMrWHQsH4ycnPkX+ BFiH7M78vTUNCGUL15FyX3y517T8uBR7TH4QlvQ2HtMkBYFYDxonBtu7f+Ef5H0L B6lLwGDh9G/jX8Xe1JofKpC2wEu57DbXb3VXfd6OTucW+qeW/UXEMw== =CdGW -----END PGP SIGNATURE-----

2 1

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

openSUSE Security July 2002