June 2006 - openSUSE Security - openSUSE Mailing Lists

Statefull packet inspection in SuSEfirewall2
by pronco＠conae.gov.ar 25 Jul '06

25 Jul '06

Hi, Is it there any way to configure stateful packet inspection rules in SuSEfirewall2 for masquerade networks? When I configure a rule in FW_MASQ_NETS in order to allow traffic from the outside to the DMZ, I also have to configure a rule for responses. Example: Incoming traffic to my web server in a DMZ with private addresses FW_FORWARD_MASQ="0/0,192.168.1.5,tcp,80 I also need to set up the following rules in order to let responses out FW_MASQ_NETS="192.168.1.5/32,0/0,tcp,1024:65535" This rule permits not only established sessions, but additionally it allows my web server to establish connections to the outside world. Dont know why the FW_FORWARD rules are stateful as I want, but FW_MASQ_NETS ones dont. Any suggestion? Is it possible to math the SYN, ACK and FIN TCP bits with SuSEfirewall2? Thanks in advance. Pablo Ronco

4 5

Re: [suse-security-announce] SUSE Security Announcement: freetype2 (SUSE-SA:2006:037)
by Mathias Homann 29 Jun '06

29 Jun '06

Am Dienstag, 27. Juni 2006 14:24 schrieb Thomas Biege: > SUSE Security Announcement > > Package: freetype2, freetype2-devel > SUSE LINUX 9.2 as soon as i recompile the source rpm for suse 9.2 with the ft-smooth-cvs patch from this site: http://www.cs.mcgill.ca/~dchest/xfthack/ freetype just stops working, truetype fonts just aren't displayed anymore... with the source rpm from the DVD it worked fine. that patch gives me much better font display quality than "regular" freetype2, even better than ClearType on windows XP, especially on TFT screens... Any ideas? bye, MH

1 1

Re: [suse-security-announce] SUSE Security Announcement: freetype2 (SUSE-SA:2006:037)
by Carlos E. R. 28 Jun '06

28 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-06-27 at 14:24 +0200, Thomas Biege wrote: ... > 3) Special Instructions and Notes > > Please log out from your window-manager session and log in again > to let all applications restart and load the new code. If you are using 'wdm' instead of the typical kdm, you need to switch to runlevel 3 and then back to 5, because wdm doesn't fully restart even after "ctrl-alt-backspace". Perhaps "rcxdm restart" would work as well. I noticed that using the method posted here by "Bob Vickers" last Jan 10 (# Subject: Re: [suse-security] Patch Noifications). - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEopQ7tTMYHG2NR9URAl9YAJ48Rti1CUF0tlXbcj7xuGljEkmFEQCeNbNW sNYNj4dVBAX73vlLx+5BT2Y= =9wqn -----END PGP SIGNATURE-----

1 0

Asterisk update?
by Hubertus A. Haniel 28 Jun '06

28 Jun '06

Hi, Is there a reason that there is a new asterisk rpm in the SuSE 9.2 update tree that has been build on the 26th of June with the same version of the rpm build on the 26th of April? On update tree: Name : asterisk Relocations: (not relocatable) Version : 1.0.0.20040814 Vendor: SUSE LINUX AG, Nuernberg, Germany Release : 0.1 Build Date: Mon 26 Jun 2006 19:06:41 BST Install date: (not installed) Build Host: ensslin.suse.de Group : Productivity/Telephony/Servers Source RPM: asterisk-1.0.0.20040814-0.1.src.rpm Size : 11838743 License: GPL, BSD Signature : DSA/SHA1, Mon 26 Jun 2006 19:09:20 BST, Key ID a84edae89c800aca Packager : http://www.suse.de/feedback URL : http://www.asterisk.org Summary : The Asterisk Open Source PBX Description : Asterisk is a complete PBX in software. It provides all of the features you would expect from a PBX and more. Asterisk does voice over IP in three protocols, and can interoperate with almost all standards-based telephony equipment using relatively inexpensive hardware. Asterisk provides Voicemail services with Directory, Call Conferencing, Interactive Voice Response, and Call Queuing. It has support for three-way calling, caller ID services, ADSI, SIP and H.323 (as both client and gateway). Documentation is available on the Asterisk homepage (http://www.asterisk.org) and on the Asterisk wiki (http://www.voip-info.org/wiki-Asterisk) Currently installed on my system: Name : asterisk Relocations: (not relocatable) Version : 1.0.0.20040814 Vendor: SUSE LINUX AG, Nuernberg, Germany Release : 0.1 Build Date: Wed 26 Apr 2006 11:05:28 BST Install date: Sun 07 May 2006 11:03:38 BST Build Host: couperin.suse.de Group : Productivity/Telephony/Servers Source RPM: asterisk-1.0.0.20040814-0.1.src.rpm Size : 11838743 License: GPL, BSD Signature : DSA/SHA1, Thu 27 Apr 2006 00:31:03 BST, Key ID a84edae89c800aca Packager : http://www.suse.de/feedback URL : http://www.asterisk.org Summary : The Asterisk Open Source PBX Description : Asterisk is a complete PBX in software. It provides all of the features you would expect from a PBX and more. Asterisk does voice over IP in three protocols, and can interoperate with almost all standards-based telephony equipment using relatively inexpensive hardware. Asterisk provides Voicemail services with Directory, Call Conferencing, Interactive Voice Response, and Call Queuing. It has support for three-way calling, caller ID services, ADSI, SIP and H.323 (as both client and gateway). Documentation is available on the Asterisk homepage (http://www.asterisk.org) and on the Asterisk wiki (http://www.voip-info.org/wiki-Asterisk) Regards Hubba

2 2

Puzzled with gawk
by Pablo 28 Jun '06

28 Jun '06

Hello there, I've just found a rather weird problem on my opensuse10.1 box. I've produced a simple awk script and a sample input file which makes gawk crash on my 10.1, while it works as expected on my gentoo. I got also what I would expect on non-gnu awk running under Mac OS X. I would really appreciate if someone ran my script under 10.1 and tried to reproduce the error. It's a one minute task: I've arranged everything below so you can run it on your ~/tmp with a single copy/paste, if you feel like giving it a try. Maybe I'm not seeing the obvious, I would expect a broken awk build to cause lots of trouble on my system, but this sample script is quite tricky. So I would appreciate if someone confirms the odd behaviour or has any clue before I go on with further testing. $ uname -a Linux 2.6.16.13-4-smp #1 SMP Wed May 3 04:53:23 UTC 2006 i686 i686 i386 GNU/Linux $ rpm -qa | grep awk gawk-3.1.5-18 $ gawk --version | head -n 1 GNU Awk 3.1.5 Thank you for getting so far, and thank you very much if you choose to go on ;) Kind regards. Pablo -8<-------------cut here--------------------- #skip this if your CWD is a better place for two temp files ;) cd ~/tmp # the script; PLEASE take care if you copy on your own file # to remove the BACKSLASH just before the DOLLAR; It's # there to prevent the shell from evaluating $i when copy/pasting. cat > problem.awk <<-EOF { print "RECORD " NR; for ( i = 0; length( \$i ) > 0; i++ ) print " FIELD " i " of " NF; } EOF # It doesn't seem to really matter what kind of input you # give to the script. Also it doesn't matter if it's given # on a file via gawk command line invocation or if it's fed # via stdin through a pipe. cat > awk_example <<EOF drwxr-xr-x 2 pablo users 112 2006-06-20 19:29 . drwxr-xr-x 3 pablo users 248 2006-06-20 19:26 .. -rw-r--r-- 1 pablo users 0 2006-06-20 19:43 awk_example -rw-r--r-- 1 pablo users 91 2006-06-20 19:37 problem.awk drwxr-xr-x 2 pablo users 112 2006-06-20 19:29 . drwxr-xr-x 3 pablo users 248 2006-06-20 19:26 .. -rw-r--r-- 1 pablo users 0 2006-06-20 19:43 awk_example -rw-r--r-- 1 pablo users 91 2006-06-20 19:37 problem.awk EOF # Unleash hell! gawk -f problem.awk awk_example -8<-------------cut here--------------------- This is the expected output (what I get on my Gentoo's gawk and on my Mac OS X's awk): $ gawk -f problem.awk awk_example RECORD 1 FIELD 0 of 8 FIELD 1 of 8 FIELD 2 of 8 FIELD 3 of 8 FIELD 4 of 8 FIELD 5 of 8 FIELD 6 of 8 FIELD 7 of 8 FIELD 8 of 8 [... records 2 to 7 ...] RECORD 8 FIELD 0 of 8 FIELD 1 of 8 FIELD 2 of 8 FIELD 3 of 8 FIELD 4 of 8 FIELD 5 of 8 FIELD 6 of 8 FIELD 7 of 8 FIELD 8 of 8 This is what I get on my opensuse10.1: $ gawk -f problem.awk awk_example RECORD 1 FIELD 0 of 8 FIELD 1 of 8 FIELD 2 of 8 FIELD 3 of 8 FIELD 4 of 8 FIELD 5 of 8 FIELD 6 of 8 FIELD 7 of 8 FIELD 8 of 8 RECORD 2 FIELD 0 of 8 FIELD 1 of 8 FIELD 2 of 8 *** glibc detected *** gawk: double free or corruption (fasttop): 0x08089be0 *** ======= Backtrace: ========= /lib/libc.so.6[0xb7e80911] /lib/libc.so.6(__libc_free+0x84)[0xb7e81f84] gawk(str2wstr+0x37)[0x806f2dd] gawk(do_length+0x1f3)[0x8056c73] gawk(r_tree_eval+0x3a2)[0x80742f2] gawk(r_tree_eval+0x75)[0x8073fc5] gawk[0x8075d12] gawk(interpret+0x2c6)[0x80727e6] gawk(interpret+0x221)[0x8072741] gawk(interpret+0x1b1)[0x80726d1] gawk(do_input+0x33)[0x806a743] gawk(main+0x79b)[0x806e33b] /lib/libc.so.6(__libc_start_main+0xdc)[0xb7e3287c] gawk[0x804c9b1] ======= Memory map: ======== 08048000-08082000 r-xp 00000000 03:01 431340 /bin/gawk 08082000-08083000 rw-p 0003a000 03:01 431340 /bin/gawk 08083000-080a9000 rw-p 08083000 00:00 0 [heap] b7b00000-b7b21000 rw-p b7b00000 00:00 0 b7b21000-b7c00000 ---p b7b21000 00:00 0 b7d12000-b7de9000 r--p 00000000 03:01 441088 /usr/lib/locale/ en_US.utf8/LC_COLLATE b7de9000-b7e1c000 r--p 00000000 03:01 441087 /usr/lib/locale/ en_US.utf8/LC_CTYPE b7e1c000-b7e1d000 rw-p b7e1c000 00:00 0 b7e1d000-b7f36000 r-xp 00000000 03:01 473445 /lib/libc-2.4.so b7f36000-b7f38000 r--p 00118000 03:01 473445 /lib/libc-2.4.so b7f38000-b7f3a000 rw-p 0011a000 03:01 473445 /lib/libc-2.4.so b7f3a000-b7f3d000 rw-p b7f3a000 00:00 0 b7f3d000-b7f60000 r-xp 00000000 03:01 473453 /lib/libm-2.4.so b7f60000-b7f62000 rw-p 00022000 03:01 473453 /lib/libm-2.4.so b7f62000-b7f64000 r-xp 00000000 03:01 473451 /lib/libdl-2.4.so b7f64000-b7f66000 rw-p 00001000 03:01 473451 /lib/libdl-2.4.so b7f6b000-b7f75000 r-xp 00000000 03:01 473492 /lib/libgcc_s.so.1 b7f75000-b7f76000 rw-p 00009000 03:01 473492 /lib/libgcc_s.so.1 b7f76000-b7f77000 rw-p b7f76000 00:00 0 b7f77000-b7f78000 r--p 00000000 03:01 441084 /usr/lib/locale/ en_US.utf8/LC_NUMERIC b7f78000-b7f79000 r--p 00000000 03:01 429431 /usr/lib/locale/ en_US.utf8/LC_TIME b7f79000-b7f7a000 r--p 00000000 03:01 431263 /usr/lib/locale/ en_US.utf8/LC_MESSAGES/SYS_LC_MESSAGES b7f7a000-b7f81000 r--s 00000000 03:01 428430 /usr/lib/gconv/ gconv-modules.cache b7f81000-b7f82000 rw-p b7f81000 00:00 0 b7f82000-b7f9c000 r-xp 00000000 03:01 479433 /lib/ld-2.4.so b7f9c000-b7f9e000 rw-p 00019000 03:01 479433 /lib/ld-2.4.so bf868000-bf87d000 rw-p bf868000 00:00 0 [stack] ffffe000-fffff000 ---p 00000000 00:00 0 [vdso] Aborted

2 1

trusted crontab
by discip＠pjm.com 23 Jun '06

23 Jun '06

Does anyone know what the preferred way is to eliminate the restriction that crontab only be available to users in the trusted group? I would like all local users to be able to use cron. I changed the ownership of the crontab command from root:trusted to root:users, but it appears there must be something else I should change because certain command complain (the rpmbuild command even reset the permissions back to root:trusted). Any help would be greatly appreciated. This is SLES 9 SP3 Thanks, Paul

3 2

nntp and irc
by wpc 22 Jun '06

22 Jun '06

on my linux server i can use irc and nntp but on my workstations i can't. have opened ports for nntp and irc on internal and external. what could be wrong ? "Who the heck is General Failure, and why is he reading my harddisk?" __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

traceroute to SuSEfirewall
by Frank Stuehmer 20 Jun '06

20 Jun '06

Hi, in earlier versions of SuSEfirewall there was a parameter FW_ALLOW_FW_TRACEROUTE. In version 3.3 isn't. I could use FW_ALLOW_INCOMING_HIGHPORTS_UDP but it's deprecated. How may I allow to traceroute the firewall? Frank

2 1

Open Source call graph paper announcement
by Sebastian Krahmer 19 Jun '06

19 Jun '06

Hi, For those who are interested in: http://www.suse.de/~krahmer/instrumental/instrumental.pdf and http://www.suse.de/~krahmer/bbpaint/bbpaint.pdf The first one describes how to use certain GCC features to generate call graphs from a running program. The second one describes how ptrace() might be used to build a Control Flow Integrity system. Code for playing is included for both, but for the later its not yet uploaded (mainly because the Branch Trapping has just been implemented). l8er, Sebastian -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0

Re: [suse-security] userdd userdel very slow/delayed..???
by Andy 16 Jun '06

16 Jun '06

Hm... you're right. What does that do exactly and how do I disable it? ----- Original Message ----- From: "Richard Ems" <Richard.Ems(a)mtg-marinetechnik.de> To: "Andy" <frum(a)ar-sd.net> Cc: <suse-security(a)suse.com> Sent: Friday, June 16, 2006 1:24 PM Subject: Re: [suse-security] userdd userdel very slow/delayed..??? > Did you tried "rcnscd stop" ? > > Richard > > -- > Richard Ems > Tel: +49 40 65803 312 > Fax: +49 40 65803 392 > Richard.Ems(a)mtg-marinetechnik.de > > MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg > > GF Dipl.-Ing. Ullrich Keil > Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 > USt.-IdNr.: DE 1186 70571 > > >

2 1

userdd userdel very slow/delayed..???
by Andy 16 Jun '06

16 Jun '06

Hi, I am running a Suse 9.1 server, and I needed the --stdin option for the passwd command, to create the users from some scripts. So I installed the pwdutils3.0 form http://www.suse.com/~kukuk/pam/pwdutils/ and I have the problem that: - after I add a used or delete the user the user is not deleted imediately although the bash command is finished. So it takes a few seconds(about 10 - 20 secs) for the user to be added or deleted I am having the problem that: I add the user and then I run the passwd command which returnes that the user does not exist. After a few repetitions the user is finaly created and I can change the password. I find very odd this behavior, and I don't know which is the solution. I really need to run the passwd command after useradd, but it always returns user unknown. If I run it after 20 seconds it runs well. Thankx, Andy.

1 0

SUSE Security Announcement: sendmail remote denial of service attack (SUSE-SA:2006:032)
by Marcus Meissner 14 Jun '06

14 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: sendmail Announcement ID: SUSE-SA:2006:032 Date: Wed, 14 Jun 2006 19:00:00 +0000 Affected Products: SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SuSE Linux Enterprise Server 8 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: remote denial of service Severity (1-10): 5 SUSE Default Package: no Cross-References: CVE-2006-1173, VU#146718 Content of This Advisory: 1) Security Vulnerability Resolved: sendmail remote denial of service attack Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion The Mail Transfer Agent sendmail has a remote exploitable problem, where a specially crafted MIME messages can crash sendmail and block queue processing. This issue is tracked by the Mitre CVE ID CVE-2006-1173 and CERT VU#146718. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart all running instances of sendmail after the update. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv <file.rpm> to apply the update, replacing <file.rpm> with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/sendmail-8.13.6-9.3.i586.r… 1e3fa1b7a729d2b260a4da6d9ff962f4 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/sendmail-8.13.4-8.6.i… 70a41db80164fb7d50e823774566ea9e SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/sendmail-8.13.3-5.6.i5… 94679162ea3b479f20362f0d01ea4d72 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/sendmail-8.13.1-5.6.i5… 10e79f3a40ec0c25911cf2549009d609 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/sendmail-8.12.11-2.7.i… adc59ac9fa4ba76743bd073e0334b9d9 Power PC Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/sendmail-8.13.6-9.3.ppc.rpm 81580c25511daa9862a1dd8f5ca7d48b SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/sendmail-8.13.4-8.6.pp… ff81143d1dee29c58aea6038a952c903 x86-64 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/sendmail-8.13.6-9.3.x86_… 8f724bcf3c0aaac8923241c9f3288c40 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/sendmail-8.13.4-8.6… 40fc8a5f7ad12159528b8cc1d4c2173f SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/sendmail-8.13.3-5.6.… d8b8ba804ac1a04b22d673c52d654f69 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/sendmail-8.13.1-5.6.… 6dcf297dbbcfb5d2b7d0a55efb9c3099 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/sendmail-8.12.11-2… dd3ed5bd5318928a9bfe4320eed67027 Sources: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/sendmail-8.13.6-9.3.src.rpm 7ed5b46eb2ed2a18becadf43b8cba7b1 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/sendmail-8.13.4-8.6.sr… 0f93d3d608305d44667ec1b35a76e626 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/sendmail-8.13.3-5.6.src… c9ac83c770a63f94fe18a156898ffe70 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/sendmail-8.13.1-5.6.src… 6dd980cf9e4ee2d14d9ec1e8f7c804f5 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/sendmail-8.12.11-2.7.sr… d312bd0544a7e3b7456abfb79a296383 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/sendmail-8.12.11-2.7.… c1bfd5c0dbd95faee42ae0a2694147bf Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: UnitedLinux 1.0 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/e92dc8b293ef625… SUSE SLES 9 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/e92dc8b293ef625… SuSE Linux Enterprise Server 8 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/e92dc8b293ef625… ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify <file> replacing <file> with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made <DATE> using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team <security(a)suse.de>" where <DATE> is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. 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) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal 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, replacing <file.rpm> with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from build(a)suse.de with the key ID 9C800ACA. This key is automatically imported into the RPM database (on RPMv4-based distributions) and the gpg key ring of 'root' during installation. You can also find it on the first installation CD and at the end of this announcement. 2) If you need an alternative means of verification, use the md5sum command to verify the authenticity of the packages. Execute the command md5sum <filename.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 SUSE security announcement. Because the announcement containing the checksums is cryptographically signed (by security(a)suse.de) the checksums show proof of the authenticity of the package if the signature of the announcement is valid. Note that the md5 sums published in the SUSE Security Announcements are valid for the respective packages only. Newer versions of these packages cannot be verified. - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - General Linux and SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an e-mail to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an e-mail 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>. ===================================================================== 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, the clear text signature should show proof of the authenticity of the text. SUSE Linux Products GmbH provides 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.4.2 (GNU/Linux) mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBmQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCk YS3yEKeueNWc+z/0Kvff4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP +Y0PFPboMvKx0FXl/A0dM+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR 8xocQSVCFxcwvwCglVcOQliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U 8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0S cZqITuZC4CWxJa9GynBED3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEh ELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtB UVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOo AqajLfvkURHAeSsxXIoEmyW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1n KFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohi BBMRAgAiBQJA2AY+AhsDBQkObd+9BAsHAwIDFQIDAxYCAQIeAQIXgAAKCRCoTtro nIAKypCfAJ9RuZ6ZSV7QW4pTgTIxQ+ABPp0sIwCffG9bCNnrETPlgOn+dGEkAWeg KL+IRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lx yoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWn B/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDV wM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklLsnr35SJDZ6ram51/CWOnnaVh UzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF 5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3 D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGu zgpJt9IXSzyohEJB6XG5+D0BuQINBDnu9JIQCACEkdBN6Mxf5WvqDWkcMRy6wnrd 9DYJ8UUTmIT2iQf07tRUKJJ9v0JXfx2Z4d08IQSMNRaq4VgSe+PdYgIy0fbj23Vi a5/gO7fJEpD2hd2f+pMnOWvH2rOOIbeYfuhzAc6BQjAKtmgR0ERUTafTM9Wb6F13 CNZZNZfDqnFDP6L12w3z3F7FFXkz07Rs3AIto1ZfYZd4sCSpMr/0S5nLrHbIvGLp 271hhQBeRmmoGEKO2JRelGgUJ2CUzOdtwDIKT0LbCpvaP8PVnYF5IFoYJIWRHqlE t5ucTXstZy7vYjL6vTP4l5xs+LIOkNmPhqmfsgLzVo0UaLt80hOwc4NvDCOLAAMG B/9g+9V3ORzw4LvO1pwRYJqfDKUq/EJ0rNMMD4N8RLpZRhKHKJUm9nNHLbksnlZw rbSTM5LpC/U6sheLP+l0bLVoq0lmsCcUSyh+mY6PxWirLIWCn/IAZAGnXb6Zd6Tt IJlGG6pqUN8QxGJYQnonl0uTJKHJENbI9sWHQdcTtBMc34gorHFCo1Bcvpnc1LFL rWn7mfoGx6INQjf3HGQpMXAWuSBQhzkazY6vaWFpa8bBJ+gKbBuySWzNm3rFtT5H RKMWpO+M9bHp4d+puY0L1YwN1OMatcMMpcWnZpiWiR83oi32+xtWUY2U7Ae38mMa g8zFbpeqPQUsDv9V7CAJ1dbriEwEGBECAAwFAkDYBnoFCQ5t3+gACgkQqE7a6JyA CspnpgCfRbYwxT3iq+9l/PgNTUNTZOlof2oAn25y0eGi0371jap9kOV6uq71sUuO =ypVs - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBRJBeM3ey5gA9JdPZAQJVQgf/bwNm+ZLLDbUIBT4xj6/vbjoyuYScRHwV CIbU73rHkHJSNCjjTjXOeU5inNu/YYkNs1T7DLkFQFiYxy9V2p6voHiZhcjwGOZg VxmUyo707ybQJayvzLTq2U0y+PWHYQ0/CdRD6jZTFJ7etOiQCcqAGXTCuMvuK1Bl 4CfpQj80tMwNzcrldzAsD1UTBZ05DXLVgUO2hNzx0BOydvM6pHXco4Ow5am4mbFW LMTP+LkmKIgqkhMk+WInxvVglVEyrbFszcv0D2tGC9M8wMlUPYulbhVRBJboc/do xQBHa0MhQ9BuxmfdvqLudrwIHmBb8Cy9uqKO/dGG+RP97DhiH6UhYw== =0D4O -----END PGP SIGNATURE-----

1 0

Re: [suse-security] Problem with Postfix and Amavis on SuSE 10.1
by Dragan Andric 13 Jun '06

13 Jun '06

-----Original Message----- From: Guido Tschakert [mailto:guido.tschakert@src-gmbh.de] Sent: Thursday, June 08, 2006 10:58 AM To: suse-security(a)suse.com Subject: [suse-security] Problem with Postfix and Amavis on SuSE 10.1 >I reactivated the following line in /etc/postfix/master.cf >and restartet postfix: >localhost:10025 inet n - n - - smtpd -o >content_filter= Guido, Have the same problem. Resolved it replacing localhost with 127.0.0.1. Somehow the resolution of localhost does not work. Dragan Andric

4 3

Update for SUSE Linux 10.1 Package Management
by Marcus Meissner 10 Jun '06

10 Jun '06

Hi, If you are a user of SUSE Linux 10.1 you will have likely noticed that the Package Update System is not up to the quality you were accustomed to in previous SUSE Linux versions. The reason for this is that SUSE Linux 10.1 got a completely rewritten package handling, which offers a multitude of new features necessary in todays world of dozens external package repositories, Add-On products, multiple update sources, remote management and cryptographic repository integrity assurance. This incurred not just a new lowlevel packagement (called ZYPP) but also inclusion of the Novell product Zenworks in the form of the ZMD daemon, the commandline tool "rug", and the graphical "zen-updater", "zen-installer" and "zen-remover" frontends. As we shipped SUSE Linux 10.1 we were aware of these quality issues and had already planned to release a online update. At that time we were confident that it would be possible to use all updater frontends to install this update. Unfortunately this was not the case so some special procedure is required once to install this update: - Start the YaST Online Update (as root user). If you are not familar with YaST this can for instance be done: - via The KDE or GNOME menu link to the YaST control center -> System -> YaST (Control Center) -> Online Update - by starting: KDE: kdesu yast2 online_update GNOME: gnomesu yast2 online_update - By opening an shell window (xterm, konsole, or similar) and doing: $ su Password: <enter rootpassword here> # you ... follow the graphical interface ... - In the patch overview only the "libzypp update" patch will be selected. Just press "Accept" to install it. This will install the update and should not result in errors. - Afterwards you will need to restart "zen-updater" once on the desktop to be able to install the rest of the updates. If you install a new system now, you can avoid this by running the Online Update during installation (if network is available). This will also download the "libzypp patch". Also please note that not all of our mirrors have this update yet and might take some days to get it. The list of fixed bugs can be found below. Open issues: - Patch and Delta RPMs are not supported yet. The update will always download full RPMs. - Performance and memory usage is not optimal. Sincerely, Marcus Meissner * Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * restarting zmd if it is updated (#178218) * While updating ourself delay the call to ShutdownManager.allow() so the client polling the transaction can get the final status of the transaction before we restart (#179413)

1 0

Problem with Postfix and Amavis on SuSE 10.1
by Guido Tschakert 08 Jun '06

08 Jun '06

Hello I'm trying to use postfix and amavis together on SuSE 10.1 and have a problem with postfix listening on port 10025 (this is not directly a security problem but as I need this socket to use amavis it is somewhat security related ;-) ) I reactivated the following line in /etc/postfix/master.cf and restartet postfix: localhost:10025 inet n - n - - smtpd -o content_filter= After that I run some commands #lsof -i -nP | grep master master 25767 root 11u IPv4 187669 TCP *:25 (LISTEN) master 25767 root 12u IPv6 187670 TCP *:25 (LISTEN) master 25767 root 72u IPv4 187753 TCP 127.0.0.1:10025 (LISTEN) master 25767 root 73u IPv6 187754 TCP [::1]:10025 (LISTEN) #telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail-gw.src-bonn.de ESMTP Postfix but #telnet localhost 10025 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. For me it seems that postfix does not listen correct on port 10025 since the message of postfix is missing. I tested it with SuSE 9.3 and everything is fine. Anybody have the same problem and maybe a solution? tia guido

1 0

RE: [suse-security] New Fou4s Release 0.14.1-2
by GarUlbricht7＠netscape.net 07 Jun '06

07 Jun '06

Markus Gaugusch <markus(a)gaugusch.at> wrote: >Dear Fou4s Users, > >More than a year has passed since the last version. > Really Shocking ;-) > >Since I hope to start on 10.1 support soon > (zen-updater is just soooo slow!), > I have released a new version with all fixes > that I have included ...(snip) > Hi Markus, I just did my second update to Fou4s Release 0.14.1-2 today. Glad to hear that you have found a little time to update fou4s which is my preferred method to see what security patches are available for my system. I have been holding off updating to SUSE-10.1 until the new fou4s is out - so hopefully you (and/or your Team) will be able to find the time to deal with the new SUSE rpm "tree". Thanks again. Best regards, Gar -- __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp

2 1

SuSEfirewall2 on sles9 SP3 blocking yahoo messenger
by wpc 05 Jun '06

05 Jun '06

My SuSE firewall on sles9 is blocking yahoo messenger. when i increase the logging level, it doesn't show any blocking of yahoo messenger traffic. how best can i debug this ? "Who the heck is General Failure, and why is he reading my harddisk?" __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 3

New Fou4s Release 0.14.1
by Markus Gaugusch 05 Jun '06

05 Jun '06

Dear Fou4s Users, More than a year has passed since the last version. Really Shocking ;-) Since I hope to start on 10.1 support soon (zen-updater is just soooo slow!), I have released a new version with all fixes that I have included during the last year. The version from yesterday (0.14.0) has a bug with kernel update reboot notifications only working at the first run. This is fixed now. Changelog: * Changed rsync to follow symlinks * Added support for CURL * Added support for https proxies and other https fixes (mostly for business products) * Warn if more than one kernel is installed, because reboot check won't work * Fixes for 0.13.1 + Use only files in SuSE "directory" files, not all that are found (--usedir) + Downloading of server list works again (--server -w) + Fix wrong cache invalidation on business products + Fix renaming of module directory for kernel backups + Fix kernel check to work every time, not only during the first run * New config file options: + UseCurl (default:off) + ProxyDigest (default:off) * New parameters + usecurl + proxydigest (digest authentication, only supported by curl!) regards, Markus Gaugusch -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(at)gaugusch.at X Against HTML Mail / \

1 0