February 2003 - openSUSE Security - openSUSE Mailing Lists

Spam/Bounce-Mail
by Joerg Frings-Fuerst 24 Feb '03

24 Feb '03

Hallo, first I say sorry for your trouble with my bounce-mails. This weekend I setup my new Mail-Backupserver. After this work I test a new version of my Spamcheck-script. In this script I call "rblcheck". My mistake was the test via list.dsbl.org. The big prob by my was that the powerline from my Primaryserver going offline. So the Backup-Server works with the bad script. Sorry Joerg -- Jörg Frings-Fürst 54526 Landscheid http://www.fixundfoxi.dyndns.info -- Registered Linux User # 280687 ICQ 170365098 GPG Key ID : 9E5F BE06 E208 BAA3

1 0

Re: [suse-security] OpenSesamMe
by GentooRulez 24 Feb '03

24 Feb '03

> Hi, > > To be honest, you'd be better off using PPTP if coming from Windoze or IPSEC > (FreeSWAN) if Linux. You can then firewall the resulting ppp* or ipsec* device > to control access. I wont a bidirectional communication to get the hole. My actual idea is to play with the source-ports and simulate a connection to the server on a often used destination port, e.g. tcp 80, dont care a httpd is runing there. This should look like "normal" traffic, not know where the advantage is, yet :O) > Your proposal begs the question "when do I close the hole?". We solved this by > establishing a connection that was open for the duration. It works as follows: When I logout myself via .bash_logout e.g. > Nominate a port. can be udp but tcp preferred. The port should be one that > should not attract much attention. > Client calls server > Server issues challenge > Client responds > Server opens firewall eg you drop into a jump to a pre-defined chain. > After a timeout (60s/5m/or what you want) Server issues a new challenge > Client responds. If no response, Server closes firewall > If tcp is used, you can also close firewall when connection drops. A time-out can be a good idea, e.g. my connection died before i closed the hole again. regards Michael

1 0

OpenSesamMe
by GentooRulez 24 Feb '03

24 Feb '03

OpenSesamMe is there a tool outthere that work as follows: 1. I'll send a sequence of small ip packets (udp|tcp) to certain ports in a certain order to a server destination. e.g. udp 213,tcp 112,udp 443,udp 4500,tcp 1200 2. The servers has got a daemon that sniffs all incoming packets, filtered too, on certain interface and waits for udp 213. If such a packet arrives, the daemon checks whether the other packets arrives in a certain time in that order or not. 3. If daemon check succeeded, a whole hole will be poked into the firewall for this incoming ip to allow access to e.g. ssh. or any other suggestions for that. And YES, somebody might name this security through obscurity. Thx in advance Michael

4 4

Re: [suse-security] OpenSesamMe
by John Trickey 22 Feb '03

22 Feb '03

Oops, forgot the reply behavior of this list! Michael, Don't reply to the direct mail as it will drop down a spam trap. John ----- Forwarded message from John Trickey <lists(a)g4rev.supanet.com> ----- Date: Sat, 22 Feb 2003 15:55:42 +0000 From: John Trickey <lists(a)g4rev.supanet.com> Reply-To: John Trickey <lists(a)g4rev.supanet.com> Subject: Re: [suse-security] OpenSesamMe To: GentooRulez <paranoiac_user(a)freenet.de> Quoting GentooRulez <paranoiac_user(a)freenet.de>: > OpenSesamMe > > is there a tool outthere that work as follows: > > ...etc... Hi, To be honest, you'd be better off using PPTP if coming from Windoze or IPSEC (FreeSWAN) if Linux. You can then firewall the resulting ppp* or ipsec* device to control access. I have implemented something similar but regretably the code is copyright a former employer :-( However in those days secure tunnels were not cheaply available. Your proposal begs the question "when do I close the hole?". We solved this by establishing a connection that was open for the duration. It works as follows: Nominate a port. can be udp but tcp preferred. The port should be one that should not attract much attention. Client calls server Server issues challenge Client responds Server opens firewall eg you drop into a jump to a pre-defined chain. After a timeout (60s/5m/or what you want) Server issues a new challenge Client responds. If no response, Server closes firewall If tcp is used, you can also close firewall when connection drops. Sorry, but I cannot release the port choice and challenge/response algorithm. HTH John ----- End forwarded message -----

1 0

openssl vulnerability
by Konstantin (Kastus) Shchuka 21 Feb '03

21 Feb '03

Are SuSE openssl packages vulnerable to this: http://www.openssl.org/news/secadv_20030219.txt If they are, when we might expect to see SuSE patches? Thanks, -Kastus

4 3

Fw: [SLE] Problem with SuSEfirewall2
by Derek Clifford 21 Feb '03

21 Feb '03

Cross-Posting to SuSE security - seems more appropriate Derek ----- Original Message ----- From: "Derek Clifford" <derek_clifford(a)fermi.demon.co.uk> To: <suse-linux-e(a)suse.com> Sent: 20 February 2003 16:22 Subject: Fw: [SLE] Problem with SuSEfirewall2 > > ----- Original Message ----- > From: "Derek Clifford" <derek_clifford(a)fermi.demon.co.uk> > To: "Jostein Berntsen" <jostein.berntsen(a)sensewave.com> > Sent: 20 February 2003 16:22 > Subject: Re: [SLE] Problem with SuSEfirewall2 > > > > Ok, thanks, I find that I don't have these files with SuSE 8.0, but here > are > > the SuSEfirewall2 files and the SuSEfirewall custom file. > > > > Regards, > > Derek > > > > ----- Original Message ----- > > From: "Jostein Berntsen" <jostein.berntsen(a)sensewave.com> > > To: <suse-linux-e(a)suse.com> > > Sent: 20 February 2003 11:45 > > Subject: Re: [SLE] Problem with SuSEfirewall2 > > > > > > > Hi, > > > > > > Check this: > > > > > > http://toganm.tripod.com/misc/unofficial.html#AEN1834 > > > > > > and send the output of the commands to the list. > > > > > > Jostein > > > > > > > I have a setup with a linux gateway connected to the internet serving > > > > two masqueraded networks, one my normal internal lan, the other a dmz > > > > running a web server. > > > > What I want to do is to use a machine on my normal lan to access the > > > > web server. > > > > Routing from the lan to the dmz using internal addresses works fine, > > > > but I want to be able to access the machine in the dmz via the > external > > > > interface, so that the machine addresses I use to test the setup are > > > > exactly the same as those used by someone connecting from outside. > > > > I have seen the suggestion to add in the custom setup file: > > > > iptables -A INPUT -i eth0 -s 192.168.xxx.0/24 -d xxx.xxx.xx.xxx -j > > > > ACCEPT Now this gets me as far as my gateway - if I put a web server > on > > > > the gateway I can access it with the external addresses from the > > > > internal LAN, but what I really want is to route this access to the > > > > server in the dmz. The routing works from outside my net, but I cannot > > > > simulate this from inside the net. Any suggestions? > > > > > > > > Regards, > > > > Derek > > > > > > > > > > > > -- > > > > Check the headers for your unsubscription address > > > > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > > > Also check the archives at http://lists.suse.com > > > > Please read the FAQs: suse-linux-e-faq(a)suse.com > > > > > > > > > > > > -- > > > Check the headers for your unsubscription address > > > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > > Also check the archives at http://lists.suse.com > > > Please read the FAQs: suse-linux-e-faq(a)suse.com > > > > > > > > > > ---------------------------------------------------------------------------- ---- > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com >

1 0

Re: [suse-security] Iptables bug?!
by Fabrizio Di Meo 20 Feb '03

20 Feb '03

Yep....it's my mistake....I'm sorry. Obviusly I removed EXACTLY the same rule....but I wrote wrong just using the cut and paste while writing my message. Thanks, Fab Timo Räty <timo.raty(a)allgon.fi> wrote: Hello, > I'm using suse 7.3 and iptables v1.2.2. > > Performing a prerouting operation like the folowing one: > > iptables -t nat -A PREROUTING -p tcp --dport 139 -i ppp0 -j DNAT --to > 192.168.1.5:139 > > I got an anomaly because even though it's really working fine it goes > on to forward the packets when removed by this: > > iptables -t nat -D PREROUTING -p tcp --dport 5900 -i ppp0 -j DNAT --to > 192.168.1.5:5900 > > I couldn't explain that such iptables' behaviour....is here anyone who > can? I'm not 100% sure but shouldn't you remove the EXACT rule? This would mean that the latter (-D, delete command) does not remove the former (-A, added rule). Check this with iptables -L /iptables -t nat -L to see what rules you really have there. I could be wrong too, regards, timo --------------------------------- Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino

1 0

Re: [suse-security] Iptables bug?!
by Fabrizio Di Meo 20 Feb '03

20 Feb '03

Yep....it's my mistake....I'm sorry. Obviusly I removed EXACTLY the same rule....but I wrote wrong just using the cut and paste while writing my message. Thanks, Fab Timo Räty <timo.raty(a)allgon.fi> wrote:Hello, > I'm using suse 7.3 and iptables v1.2.2. > > Performing a prerouting operation like the folowing one: > > iptables -t nat -A PREROUTING -p tcp --dport 139 -i ppp0 -j DNAT --to > 192.168.1.5:139 > > I got an anomaly because even though it's really working fine it goes > on to forward the packets when removed by this: > > iptables -t nat -D PREROUTING -p tcp --dport 5900 -i ppp0 -j DNAT --to > 192.168.1.5:5900 > > I couldn't explain that such iptables' behaviour....is here anyone who > can? I'm not 100% sure but shouldn't you remove the EXACT rule? This would mean that the latter (-D, delete command) does not remove the former (-A, added rule). Check this with iptables -L /iptables -t nat -L to see what rules you really have there. I could be wrong too, regards, timo --------------------------------- Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino

1 0

Antw: [suse-security] Iptables bug?!
by petry 20 Feb '03

20 Feb '03

Hi, taking only a very short look before going home I guess there is an error in the second line: do you want to delete ruleset for port 139 or port 5900? Nevertheless, I made the experience nat-rules are not deleteable correctly by *-D* (I used iptables with SuSE 7.2, don't know the iptables-version). So I agree with your opinion this is not really the way it should do. Olaf >>> Fabrizio Di Meo <fabriziodimeo(a)yahoo.it> 20.02.2003 20:06 >>> Hi, I'm using suse 7.3 and iptables v1.2.2. Performing a prerouting operation like the folowing one: iptables -t nat -A PREROUTING -p tcp --dport 139 -i ppp0 -j DNAT --to 192.168.1.5:139 I got an anomaly because even though it's really working fine it goes on to forward the packets when removed by this: iptables -t nat -D PREROUTING -p tcp --dport 5900 -i ppp0 -j DNAT --to 192.168.1.5:5900 I couldn't explain that such iptables' behaviour....is here anyone who can? Thank you, Fabrizio --------------------------------- Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino

1 0

Iptables bug?!
by Fabrizio Di Meo 20 Feb '03

20 Feb '03

Hi, I'm using suse 7.3 and iptables v1.2.2. Performing a prerouting operation like the folowing one: iptables -t nat -A PREROUTING -p tcp --dport 139 -i ppp0 -j DNAT --to 192.168.1.5:139 I got an anomaly because even though it's really working fine it goes on to forward the packets when removed by this: iptables -t nat -D PREROUTING -p tcp --dport 5900 -i ppp0 -j DNAT --to 192.168.1.5:5900 I couldn't explain that such iptables' behaviour....is here anyone who can? Thank you, Fabrizio --------------------------------- Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino

2 1

SuSEfirewall2 blocks dhcp client
by Stefan Nilsen 20 Feb '03

20 Feb '03

Hi. I have a customer using an ADSL connection, that gives the IP address using DHCP. The SuSE release is SuSE 8.1. All current YOU patches is installed. The customer is also running a local DHCP server to provide internal IP's to the other machines on the local network. As can be seen in the log here the firewall is blocking a broadcast from the providers DHCP server (if I'm not mistaken). The following fragment is repeated for each time i give the command "ifup-dhcp eth0". I have replaced the IP the customer get's when the firewall is not running with xxx.xxx.xxx.xxx in the log below. Feb 19 13:20:01 linux kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=00:40:f4:64:5e:31:00:02:3b:02:10:fc:08:00 SRC=10.0.0.1 DST=xxx.xxx.xxx.xxx LEN=180 TOS=0x00 PREC=0x00 TTL=62 ID=47999 PROTO=UDP SPT=53 DPT=1039 LEN=160 Feb 19 13:20:02 linux kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:05:5d:79:d1:b7:08:00 SRC=10.1.1.1 DST=255.255.255.255 LEN=308 TOS=0x00 PREC=0x00 TTL=64 ID=160 PROTO=UDP SPT=67 DPT=68 LEN=288 Feb 19 13:20:02 linux kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:05:5d:79:d1:b7:08:00 SRC=10.1.1.1 DST=255.255.255.255 LEN=299 TOS=0x00 PREC=0x00 TTL=64 ID=161 PROTO=UDP SPT=67 DPT=68 LEN=279 Feb 19 13:20:03 linux kernel: SuSE-FW-ILLEGAL-ROUTING IN=eth0 OUT=eth2 SRC=10.0.0.2 DST=192.168.4.2 LEN=148 TOS=0x00 PREC=0x00 TTL=61 ID=59750 PROTO=UDP SPT=53 DPT=12996 LEN=128 Feb 19 13:20:06 linux kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=00:40:f4:64:5e:31:00:02:3b:02:10:fc:08:00 SRC=10.0.0.2 DST=xxx.xxx.xxx.xxx LEN=203 TOS=0x00 PREC=0x00 TTL=62 ID=59797 PROTO=UDP SPT=53 DPT=1040 LEN=183 Feb 19 13:20:08 linux kernel: SuSE-FW-ILLEGAL-ROUTING IN=eth0 OUT=eth2 SRC=10.0.0.1 DST=192.168.4.2 LEN=148 TOS=0x00 PREC=0x00 TTL=61 ID=49609 PROTO=UDP SPT=53 DPT=12997 LEN=128 Feb 19 13:20:10 linux dhcpcd[9574]: timed out waiting for a valid DHCP server response Feb 19 13:20:11 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd to /etc/resolv.conf All nondefault settings in the /etc/sysconfig/SuSEfirewall2 below: FW_DEV_EXT="eth0" FW_DEV_INT="eth2" FW_DEV_DMZ="eth1" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_NETS="0/0" FW_SERVICES_EXT_TCP="ssh ntp 67 68" FW_SERVICES_EXT_UDP="ntp 67 68" FW_SERVICES_DMZ_TCP="ssh" FW_SERVICES_INT_TCP="ssh ntp" FW_SERVICES_INT_UDP="ntp" FW_TRUSTED_NETS="10.0.0.0/8,icmp 10.0.0.0/8,udp,68" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_DHCLIENT="yes" FW_SERVICE_DHCPD="yes" FW_LOG_DROP_ALL="yes" FW_KERNEL_SECURITY="no" I thought the FW_SERVICE_DHCLIENT="yes" should help me, but it did not. Anyone have any pointers to how I can fix this? -- Stefan Nilsen MILLNET AB 013-25 40 19 0736-330 382 stefan.nilsen(a)millnet.se http://www.millnet.se

1 1

NFS-mount thru firewall
by Ingo Doerrie 19 Feb '03

19 Feb '03

Hello, I have the need to mount a NFS-volume through a firewall. Sadly I was not able to find the ports to open and therefor I'd like to ask you wether anybody can answer the following question: Is SuSE-FW2 able to enable NFS-ports (login from my LX-box to the server) in a way that the MAC-adress is checked and the port is only available to this machine? This would shorten security risks I guess. Is there any alternative to this ? -- Freundliche Grüße kind regards Ingo

6 5

[suse-security] NFS-mount thru firewall
by Karl Brodowsky 18 Feb '03

18 Feb '03

Maybe VPN can help to have NFS-mount through firewall: Have NFS-server and NFS-client in two different physical networks, each one protected by a firewall. With VPN you can have a virtual secure TCP/IP tunnel connecting these two as if they were one network, with somewhat less performance.. Best regards Karl Brodowsky <bk1(a)elch.swb.de>

1 0

SuSE Security Announcement: mod_php4 (SuSE-SA:2003:0009)
by Thomas Biege 18 Feb '03

18 Feb '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: mod_php4 Announcement-ID: SuSE-SA:2003:0009 Date: Tuesday, Feb. 18th 2003 18:22 MET Affected products: 8.1 SuSE Linux Enterprise Server 8 Vulnerability Type: remote system compromise Severity (1-10): 2 SuSE default package: no Cross References: CAN-2002-1396 Content of this advisory: 1) security vulnerability resolved: buffer overflow problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - libmcrypt 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The Apache module mod_php4 supports the widely used Web scripting language PHP. Under some special circumstances a buffer overflow can be triggered in mod_php4's wordwrap() function. This buffer overflow can be used to overwrite heap memory and possibly can lead to remote system compromise. Just mod_php4 versions greater than 4.1.2 and less than 4.3.0 are vulnerable. This affects SuSE Linux 8.1 and all SuSE Linux Enterprise Server 8 based products. There is no temporary fix known. Please install the new packages from our FTP servers. After updating the mod_php4 module has to be reloaded by Apache. This can be done by restarting the apache webserver using the following command as root: rcapache restart 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/mod_php4-4.2.2-168.i58… 5a6c81dc2b214142dbea1dcef06d1fcf patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-4.2.2-168.i58… 8e95af112e690034e8e851143d63db46 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-core-4.2.2-16… 6c2931abeab4433c1c243b7a96505366 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-core-4.2.2-16… dacf9f57a098b292e62b9ddc25a84a40 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-devel-4.2.2-1… ddaa55a270c028fd0afd3159b1299f61 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-devel-4.2.2-1… 702c465ede7dbeb6c4652b2f3ea1c5f4 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-servlet-4.2.2… 87d7b9d5e5a3f5e25aa6096903979fdd patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-servlet-4.2.2… a1fef4f3966a83de8a11a36f395b9a82 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-aolserver-4.2… 9579610398d92fefbf859e33fd500401 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-aolserver-4.2… 1bd0367d2fef87ae1fc134825c17319b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/mod_php4-4.2.2-168.src.… 71d85b24a8c57a45a5a66fab56c7b1b8 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - libmcrypt Several buffer overflows in libmcrypt were discovered by Ilia Alshanetsky. The buffer overflows can lead to system compromise. New packages are currently being build. ______________________________________________________________________________ 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 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(a)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(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 announcements 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 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(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----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPlJsKney5gA9JdPZAQGrfwf9FgDHtj+9HSxWYSBjkKmg/5KXwUNih/JS 8K92UFyP3DTsqWlEzI+v+oUCtieKlOuOqDgdTp+vgpTZCn74dpPsVbNamtkxbx9i u0nyG3lvFmCunZcOLlzkrstoxMSFx5VeT1iKgYbdtJHgWqeRWch6q1OkI6xxDEQY i5XZNfUjDP4DOQpqaCzxg3qazxggHCcr+6vkQHOoove/63YQ8amkw3hjHFi6jR/X a7Fqzfa4WKajZkA8tvlTPcE3MjG3lW49uS/xLVcNeOcpE8n/Ml1HKdeG3P+o1PEc T3uvBIpdjK/5CelwClOwUjE7sIZ+mh09/ek3XBt4EzJ2Gy1q9XFq8w== =uvPL -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)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)

1 0

SuSE Security Announcement: imp (SuSE-SA:2003:0008)
by Thomas Biege 18 Feb '03

18 Feb '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: imp Announcement-ID: SuSE-SA:2003:0008 Date: Tuesday, Feb. 18th 2003 18:20 MET Affected products: 7.3, 8.0, 8.1 Vulnerability Type: remote system compromise Severity (1-10): 3 SuSE default package: no Cross References: CAN-2003-0025 Content of this advisory: 1) security vulnerability resolved: Multiple SQL-Injection problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - mod_php4 - libmcrypt - vim - pam_xauth - openldap2 - mpg123 - syslinux 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information IMP is a well known PHP-based web-mail system. Some SQL-injection vulnerabilities were found in IMP 2.x that allow an attacker to access the underlying database. No authentication is needed to exploit this bug. An attacker can gain access to protected information or, in conjunction with PostgreSQL, execute shell commands remotely. 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/imp-2.2.6-248.i586.rpm 17b26d9e48a75cc499b6d4da0c1067c3 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/imp-2.2.6-248.src.rpm 6e3e250a900070b1571f8f3b050616a8 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zima1/imp-2.2.6-246.i386.rpm d50ed25aecc357a720f901676a399def source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/imp-2.2.6-246.src.rpm 7e9fcc065b3096fc7f40f1c958ea9b0b SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zima1/imp-2.2.6-247.i386.rpm bf74d9df4b7e9b02d922609c226cff92 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/imp-2.2.6-247.src.rpm b858c113f66145fdc38d6629b1dbafb8 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zima1/imp-2.2.6-85.sparc.rpm b0bf87d69dfcd8aae2ec3d3a07d14899 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/imp-2.2.6-85.src.rpm bd236d18ab61c67fe4929be6ff7fa82a AXP Alpha Platform: PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zima1/imp-2.2.6-189.ppc.rpm 0e186259b4441dd1347e4e5e6f14aac9 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/imp-2.2.6-189.src.rpm 8688d0e39dae720267a568562a0548c3 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - mod_php4 A buffer overflow in the wordwrap() function has been reported. New packages will be prepared and should be available on our ftp servers soon. - libmcrypt Several buffer overflows in libmcrypt were discovered by Ilia Alshanetsky. The buffer overflows can lead to system compromise. New packages are currently being build. - vim Georgi Guninski <guninski(a)guninski.com> reported a security problem with vim's modeline support that allows the execution of commands when a malformed file was opened. This bug may even be exploited through MUAs like mutt. We recommend to turn off this feature globally by adding the line: set modelines=0 to the global configuration file /etc/vimrc. All currently supported SuSE products are affected by this problem. Modeline support is disabled by default in future version of SuSE Linux. - openldap2 The BER decoding routines of the openldap2 packages for SL 8.1 and SLES8 contained a bug which allowed remote attackers to mount a DoS attack against vulnerable OpenLDAP servers. It is necessary to update the openldap2-devel, openldap2-client and openldap2 packages in order to prevent such attack. New packages will be available on our FTP servers soon. - mpg123 Our update directories on our ftp server for the SuSE Linux distributions 7.3, 8.0 and 8.1 contain update packages for the mpg123 package. These updates fix a security problem with mpg123 that can result in the execution of arbitrary commands upon playing a specially crafted mpeg audio layer 3 file. Other versions of SuSE Linux than mentioned above do not contain a vulnerable version of the mpg123 mp3 player. - pam_xauth SuSE Linux starting with version 7.2 contain a PAM (Pluggable Authentication Module) called pam_xauth which can be used to pass on X11-authentification data (cookies, see "man Xsecurity") if a user uses /bin/su to assume the privileges of another user. Since the possession of the X11 authentification cookie grants access to the running X-server and all of its resources, this should be considered a security problem if the feature cannot be turned off by a non-root user. The presence of the pam_xauth PAM does not represent a threat such if it is not enabled by default. By default, the pam_xauth module is not enabled in all SuSE products. We recommend to use the /usr/X11R6/bin/sux wrapper script for the su command that comes with SuSE products to pass on X11 authentification data if so desired intentionally by the user. - syslinux The syslinux bootloader has been found vulnerable to a not closely named security weakness by Dan Hollis if the bootloader program is installed setuid root. We do not believe that elevated privileges are beneficial for a bootloader. The packages in SuSE Linux are not vulnerable to the weakness. ______________________________________________________________________________ 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 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(a)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(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 announcements 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 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(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----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPlJsHHey5gA9JdPZAQE+zwf+NyPbuB8KZRlx2060gz6rMIbEpEgD1Ac/ hicF2bXAcAMG1uQDJOdVEZ2byjCzPqvToBCtB+fxoZEny4rL+36zOrH2hiJ6tRzf ZEAL+tpFF2BOJWSez46Yhr1rbCi/pEeRT4k8zRsimIxKhAbKYh3eq29EaslKjbEX nQ4o602vsTzSKJYamoN1mhSr8159XPk2RHSwa6+uQgFOLys9oMfGaOR0v+dKGK8+ jykUCgcyb2VN3OH3Nq4umYayzAzweh4Z7Xw+5ubkIHK5yb+xHM84cx8vCnpu1ZWo qGd+ZNEZOee2q2V/3fkI/E5IxGKM+OYiSAWsAqKCciO8Nz3knLxKSA== =p9iC -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)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)

1 0

YOU error from SLES 8
by intraRedes 17 Feb '03

17 Feb '03

When trying to on-line update from SLES 8 I receive the following error Retrieving patch-3624: "Optional update for glibc" Error: Can't get files. No problems with others patches, could this be my problem ? -- Jorge D. Buchmann | jbuchmann(a)intraredes.com | intraRedes S.R.L. | http://www.intraredes.com

2 1

f-prot virusscanner for email ?
by MichaelHoeller＠t-online.de 16 Feb '03

16 Feb '03

Hello, until now I don't scan my Linux only system for viruses, but since I get more and more MS Word Documents which I open with OpenOffice I fear that I get macro viruses, since OO convertes quite well. Do I need to be afraid of these viruses? With Windows I used in the past f-prot (www.fprot.org) to scan my system, this is now also availabel for linux. How is the experience with this program? I thought of installing the f-prot start command in KMail so that the Mail directory will be scanned when a Mail is received. I this a good idea or is thee a better solution for a dialin connecton? Sorry when these questions are ot so prefessisonal - I still work on the bases of linux. Thanks a lot Michael

7 8

netdate/ntpdate/ntpd, was: [suse-security] gone - logout
by Ulrich Roth 16 Feb '03

16 Feb '03

Hi, > nah, you should use ntpdate instead of netdate: > > "netdate" will set ANY time it receives and > "ntpdate" will validate the time and moves the clock slowly > to the right time No, ntpdate gets the time from a time server and sets the clock to the time it just received from the server, no matter how much the difference is. ntpd (or xntpd) behaves like you described it. In the rcscript for ntpd first ntpdate is called once to set the correct time during the boot process, then ntpd is started to keep the time up to date. If you have a running system with a big time difference, and you want to correct it slowly and not at once, do NOT start ntpd using the rcscript, but start it manually (see which command they use in the rcscript in the "start" section). Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth(a)impact.de

3 2

Forwarding Problems
by Paul Dorn 12 Feb '03

12 Feb '03

I have a Suse 8.1 install. All of my addresses are public. The Suse machine is the firewall and behind a router. The problem seems to be that the Suse machine will not forward packets. It can talk to the router and to the local network but nothing crosses over. /proc/sys/net/ipv4/ip_forward is 1 I have tried this two ways. SuSEfirewall2 following ll prompts to attempt to setup an OPEN forwarding bridge (to test) and also with rules in place. Neither seem to work. I also installed firewall builder and tried to setup a routing firewall with that. I have been building firewalls in RedHat for a couple of years and have never tried to do this in SUSE and am quite stuck. There is a good deal of inertia regarding staying with SUSE so I would appreciate any suggestions you can make short of reverting to Redhat. Thanks! -- -Paul Dorn http://www.HelpdeskGenius.com Call for Linux support today: 866-365-7401

4 3

the kernel....
by J.Weewer 11 Feb '03

11 Feb '03

I was just reading this, but I'm just curious if the suse 8.1 kernel is vunarable for this... cause I saw 7.2 in the list... and only saw that 2.4.20 wasn't vunarable... and 8.1 uses 2.4.19 as kernel version... http://online.securityfocus.com/bid/6115/info/ Jacques

1 0

Appropriate place for port forward rules
by Daniel Bye 11 Feb '03

11 Feb '03

Hi all, I have just inherited a SuSE 8.0 firewall box and need to add a rule to allow our developers to gain direct access to various web servers out there in the wild. Not ordinarily a problem, except that we also use transparent proxying so our home workers don't need to reconfig their laptops to gain web access over the VPN or the LAN. So, we have added a rule so that the developers can point their browser at http://${hostname}:50000/ and it will be redirected by the firewall to http://${hostname}:80. It seems to work, and so in order not to lose the config, I am trying to figure out which config file is the best place to put the rule so it comes back at next boot time. Where would you recommend I put the rule? The custom config file at /etc/sysconfig/scripts/SuSEfirewall-custom seems the most obvious place to me, but I cannot decide which section it best belongs in. Again, based on pure guesswork, my inlination is to put it in the fw_custom_before_masq() section, but my iptables experience is not what it could be (coming from ipfw on FreeBSD, a much simpler tool, but equally not as flexible). I have read such documentation as I can find about SuSEfirewall2 configuration, but it has not brought me any closer to making the decision! Any insight would be much appreciated. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \

2 2

stability problem with VPN between SuSE 8.1 and Cisco PIX515
by Philipp Rusch 11 Feb '03

11 Feb '03

Hello all, we sucessfully setup up a VPN between two sites with a SuSE 8.1 system on one end and a Cisco PIX 515 on the other. I take care of the SuSE system ... I use FREES/WAN 1.98b, we had to use preshared keys because of the policy on the main site, we have a dial-up on our (remote ) site, with a fixed IP and a callback- setup via ISDN, we do BOD (2x64k) with ibod. Main site is having a leased line with 2 MBit and a subnet with 16 "real" ip adresses behind the router. The problem: IPSec is talking perfectly to the other site on the first startup. Tunnel is built up and we can use the systems on the other site perfectly. But: we have a timeout, so if the line is idle for more than 90 seconds, we take the dial-up link down. If we take it up now again, the tunnel is not renegotiated properly, that is, my logs show that freeswan tries, but does not get the right responses in time. The other site swears, that they are doing this correctly, I doubt this. As a workaround, I tried to include the "rcipsec restart" command in the IP-UP and "rcipsec stop" command in the IP-DOWN skripts of the ISDN link. But I dont think this is very elegant, I somehow miss a possibility to control the ISDN link from within FREES/WAN. Has anybody tried something similar and can advise ? Thank you in advance, Philipp Rusch

2 1

gone - logout
by Pep Serrano 11 Feb '03

11 Feb '03

Hello friends, I getting scared when I read the following lines on my "last": pep@montblanc:~> last pep pts/1 Sun Feb 2 20:02 still logged in pep pts/0 Sun Feb 2 20:00 still logged in P***(*** ****P***h*** ********P******* Thu Jan 1 01:00 gone - no logout pep pts/2 Sat Feb 1 23:43 - 23:44 (00:00) pep pts/2 Sat Feb 1 23:35 - 23:37 (00:01) pep pts/1 Sat Feb 1 23:34 - 23:44 (00:10) simon pts/0 pooladsl-a-25-7. Sat Feb 1 22:55 - 01:14 (02:19) camio pts/0 Sat Feb 1 20:59 - 21:55 (00:55) P***h*** ****P***(*** ***** Thu Jan 1 01:00 gone - no logout ... Anyone has any idea where does it come from? I'm going to research in detail in every log file. Any suggestions about what to look for? Thanks, Pep.

9 15

How to open a protocol with SuSEfirewall2
by T. Ermlich 09 Feb '03

09 Feb '03

Hello there, maybe I misunderstood the SuSEfirewall2 describtions, but how to open a protocol? Ports are opened eg. by the lines FW_SERVICES_EXT_TCP="..." FW_SERVICES_EXT_UDP="..." But how to handle protocols? Thanks in advance! c y Torsten

3 4

Re: [suse-security] apache log "GET http://irc.stealth.net:5558"
by Richard Barrington 09 Feb '03

09 Feb '03

Someone is seeing if your apache will proxy for them. If you are using virtual hosting, and have a default virtual host set, it likely returned that. >Hello, in my apache log I find > >**.**.***.*** - - [08/Feb/2003:21:23:46 +0100] "GET >http://irc.stealth.net:5558/ HTTP/1.1" 200 362 > >What is happening here? I don't host an irc server. How can apache return >a page that does not exist but is a website or irc server ((as judged by >the 200 response)? Is this an error in my setup? Thanks, Ruud

1 0