February 2003 - openSUSE Security - openSUSE Mailing Lists

how to keep nimda and code red from filling apache logs
by Mathias Homann 25 Sep '03

25 Sep '03

Hi all, here's a bit of a step-by-step description on how to keep nimda and codered from filling your apache logs. Parts used: - SuSE 7.2 Professional - SuSEfirewall2 - iptables 1.2.3 - linux kernel 2.4.13-pre5 steps: 1. install kernel sources for a kernel >> 2.4.9, running 2.4.13- pre5 here, works fine so far 2. get the sources for iptables 1.2.3 from http://netfilter.samba.org 3. unpack sources somewhere 4. export KERNEL_DIR=$(where you put the kernel tree) 5. cd into unpacked iptables sources, there's a subdirectory named patch-o-matic there 6. apply wanted patches by running ./runme $(name.of.patch)patch for this here You'll want the string patch You can also apply other patches, like the irc-conntrack patch 7. now there's a little bug in this patch... here's a diff: --- linux/net/ipv4/netfilter/ipt_string.c~ Sun Oct 21 00:16:29 2001 +++ linux/net/ipv4/netfilter/ipt_string.c Sun Oct 21 16:54:45 2001 @@ -62,7 +62,7 @@ sk = skip[haystack[right_end - i]]; sh = shift[i]; - right_end = max(int, right_end - i + sk, right_end + sh); + right_end = max(right_end - i + sk, right_end + sh); } return NULL; 8. now, make config/menuconfig/xconfig... as usual. You can import your running kernel's config first. 9. enable the experimental stuff 10. go to networking options->netfilter, there's an option there to enable string matching; set that to M 11. compile and install kernel as usual; remember to uncomment the export INSTALL_PATH=/boot in the main makefile. 12. now build a rpm file for the new iptables stuff by installing the source rpm which comes with suse, then edit the spec file, put the iptables source in /usr/src/packages/SOURCE and rebuild. 13. now there are some small changes to the firewall config files. a) uncomment the last line in /etc/rc.config.d/firewall2.rc.config: FW_CUSTOMRULES="/etc/rc.config.d/firewall2-custom.rc.config" b) edit that file, I got the following stuff in mine: for forbidden_string in root.exe cmd.exe .ida; do iptables -I input_ext -p tcp --dport http -m string \ --string $forbidden_string -m state \ --state ESTABLISHED -j REJECT --reject-with tcp-reset done put that in the last supfunction defined in the custom rc file. c) change the FW_LOG setting in firewall2.rc.config from reading -log-level warning to -log-level kernel.warning 14. last: some small changes to /sbin/SuSEfirewall2 search in the script for the parts where the modules are loaded and unloaded; be sure to add ipt_string (and the other new modules you created by patching the kernel and enabling them in make config) to the modules loading/unloading code there. 15. reboot 16. if you try now to access (from outside, of course) one of the nimda or codered URLS, all you get is a 'connection reset by peer', and the request doesn't show in apache log files. btw, no guarantees, and the usual YMMV :) bye [L]

7 7

problem with SQUID
by payam payami 02 Apr '03

02 Apr '03

Hi, I use suse 7.3 Internal network connect to internet by setting port 3128 in IE but when i set in squid.conf for authenticate_program that get windows login for users, IE don't get any windows and Internal network (clients) connect to internet normally without login I set these options in squid.conf: authenticate_program /usr/sbin/pam_auth acl password proxy_auth payam acl users src 192.168.1.0/255.255.252.0 http_access allow users http_access allow password Is here any problem with this configuration that IE can't get windows login when want to browsing? Thanks for your help, Payam __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

7 6

Fwd: RE: [suse-security] My SuSEFirewall blocks something than my LAM can not surfing in internet anymore.
by Ian David Laws 28 Feb '03

28 Feb '03

Hi You need to put in /etc/resolv.conf a DNS server! This is normally your ISP servers. Ian ---------- Forwarded Message ---------- Subject: RE: [suse-security] My SuSEFirewall blocks something than my LAM can not surfing in internet anymore. Date: Fri, 28 Feb 2003 08:15:46 -0800 (PST) From: Prabu Subroto <prabu_subroto(a)yahoo.com> To: SuSE Security Milis <suse-security(a)suse.com> Dear Stefan... (Now, I know your first name is Stefan...:D Chickle...) I found a mistype in your instruction. It should not be "DTP" but "DPT". Now, I got the output from my "/var/log/messages": " proxy:/var/log # cat /var/log/messages|grep DPT=80|grep -v DST=192.168.23.10 Feb 27 16:14:53 proxy kernel: SuSE-FW-ACCEPT IN=ippp0 OUT= MAC= SRC=145.254.192.34 DST=145.254.88.223 LEN=48 TOS=0x08 PREC=0x00 TTL=119 ID=14754 DF PROTO=TCP SPT=4215 DPT=80 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 27 16:14:54 proxy kernel: SuSE-FW-ACCEPT IN=ippp0 OUT= MAC= SRC=145.254.192.34 DST=145.254.88.223 LEN=48 TOS=0x08 PREC=0x00 TTL=119 ID=14825 DF PROTO=TCP SPT=4215 DPT=80 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 27 16:14:55 proxy kernel: SuSE-FW-ACCEPT IN=ippp0 OUT= MAC= SRC=145.254.192.34 DST=145.254.88.223 LEN=48 TOS=0x08 PREC=0x00 TTL=119 ID=14890 DF PROTO=TCP SPT=4215 DPT=80 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) proxy:/var/log # " Here is the error message in the internet browser of my LAN user while this problem is happening. " The requested URL could not be retrieved While trying to retrieve the URL: http://www.yahoo.com/ The following error was encountered: Unable to determine IP address from host name for www.yahoo.com The dnsserver returned: No DNS records This means that: The cache was not able to resolve the hostname presented in the URL. Check if the address is correct. Your cache administrator is webmaster. " Lookslike because of DNS server... But How and why? Please tell me..... --- Peer Stefan <stefan.peer(a)tiwag.at> wrote: > Hi Prabu, > > Sorry to say so, but this trace shows nothing more > than a connection-trace of your ssh-session (DPT=22 > ...). > Don't tail /var/log/messages, it's quite big and > gets filled really fast. > Do a "cat /var/log/messages|grep DTP=80|grep -v > DST=192.168.23.10" in order to get all the outgoing > http-stuff. > > so long, > Stefan > > btw. I'm called Stefan - it's a bit queer here in > Austria, we always put the last name in front ;-) > > > From: Prabu Subroto > > [mailto:prabu_subroto@yahoo.com] > > > Dear my friend, Peer... > > > > Today morning, it happened again. I follow your > > advice > > > and this is the 60 lines of my "/var/log/messages" > > file: > > " > > proxy:/var/log # tail -n 60 messages > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4343 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4344 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4345 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4346 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4347 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4348 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4349 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4350 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4351 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4352 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF7) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4353 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4354 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1B04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4355 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1C04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4356 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=18824 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1C04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4357 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=18824 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1C04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4358 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=18824 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1C04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4359 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=21720 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1C04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4360 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=24616 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1D04A2BFF8) > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4361 DF PROTO=TCP SPT=1132 > > DPT=22 > > > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > > (0101080A00097D1D04A2BFF9) > > Feb 27 14:04:51 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 === message truncated === __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ -- Check the headers for your unsubscription address 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

RE: [suse-security] My SuSEFirewall blocks something than my LAM can not surfing in internet anymore.
by Peer Stefan 28 Feb '03

28 Feb '03

Hi Prabu, Sorry to say so, but this trace shows nothing more than a connection-trace of your ssh-session (DPT=22 ...). Don't tail /var/log/messages, it's quite big and gets filled really fast. Do a "cat /var/log/messages|grep DTP=80|grep -v DST=192.168.23.10" in order to get all the outgoing http-stuff. so long, Stefan btw. I'm called Stefan - it's a bit queer here in Austria, we always put the last name in front ;-) > From: Prabu Subroto [mailto:prabu_subroto@yahoo.com] > Dear my friend, Peer... > > Today morning, it happened again. I follow your advice > and this is the 60 lines of my "/var/log/messages" > file: > " > proxy:/var/log # tail -n 60 messages > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4343 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4344 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4345 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4346 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4347 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4348 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4349 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4350 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4351 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4352 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF7) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4353 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4354 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1B04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4355 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=16192 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1C04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4356 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=18824 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1C04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4357 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=18824 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1C04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4358 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=18824 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1C04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4359 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=21720 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1C04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4360 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=24616 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1D04A2BFF8) > Feb 27 14:04:49 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4361 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097D1D04A2BFF9) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4362 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097DBA04A2BFF9) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4363 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097DBD04A2C09A) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4364 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097DCA04A2C09A) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4365 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097DCA04A2C0A6) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4366 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097DD804A2C0A6) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4367 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097DDB04A2C0B8) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4368 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097DF004A2C0B8) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4369 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097DF304A2C0CF) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4370 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097E1104A2C0CF) > Feb 27 14:04:51 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4371 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097E1504A2C0F1) > Feb 27 14:04:54 proxy kernel: SuSE-FW-ILLEGAL-TARGET > IN=eth0 OUT= > MAC=ff:ff:ff:ff:ff:ff:00:50:bf:77:77:f8:08:00 > SRC=192.168.23.238 DST=192.168.23.0 LEN=174 TOS=0x00 > PREC=0x00 TTL=64 ID=25437 DF PROTO=UDP SPT=631 DPT=631 > LEN=154 > Feb 27 14:04:56 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4372 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097FD004A2C0F1) > Feb 27 14:04:56 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4373 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097FD404A2C2B0) > Feb 27 14:04:56 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4374 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A00097FF804A2C2B0) > Feb 27 14:04:56 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4375 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A00097FFB04A2C2D8) > Feb 27 14:04:56 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4376 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009800C04A2C2D8) > Feb 27 14:04:57 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4377 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009800F04A2C2EB) > Feb 27 14:04:57 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4378 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009805304A2C2EB) > Feb 27 14:04:57 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4379 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009805704A2C333) > Feb 27 14:04:57 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4380 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009806F04A2C333) > Feb 27 14:04:57 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4381 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009806F04A2C34C) > Feb 27 14:04:58 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4382 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A000980A304A2C34C) > Feb 27 14:04:58 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4383 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A000980A604A2C382) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4384 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A000980EB04A2C382) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4385 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A000980ED04A2C3CA) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4386 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009810304A2C3CA) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4387 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009810604A2C3E2) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4388 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009811F04A2C3E2) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4389 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009812204A2C3FE) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4390 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009813304A2C3FE) > Feb 27 14:04:59 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4391 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009813604A2C412) > Feb 27 14:05:00 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4392 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009814304A2C412) > Feb 27 14:05:00 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4393 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009814604A2C422) > Feb 27 14:05:01 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4394 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A000981A204A2C422) > Feb 27 14:05:01 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4395 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A000981A504A2C481) > Feb 27 14:05:01 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4396 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A000981B204A2C481) > Feb 27 14:05:01 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4397 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A000981B504A2C491) > Feb 27 14:05:01 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4398 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A000981CD04A2C491) > Feb 27 14:05:01 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4399 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A000981CF04A2C4AC) > Feb 27 14:05:05 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=100 TOS=0x10 > PREC=0x00 TTL=64 ID=4400 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK PSH URGP=0 OPT > (0101080A0009835104A2C4AC) > Feb 27 14:05:05 proxy kernel: > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 TOS=0x10 > PREC=0x00 TTL=64 ID=4401 DF PROTO=TCP SPT=1132 DPT=22 > WINDOW=27512 RES=0x00 ACK URGP=0 OPT > (0101080A0009835104A2C62E) > proxy:/var/log # > " > > Please tell me your solution... Should I allow > "145.254.88.223"? But how? > > Thank you, Peer. > --- Peer Stefan <stefan.peer(a)tiwag.at> wrote: > > Hi > > > From: Prabu Subroto > > [mailto:prabu_subroto@yahoo.com] > > > Dear my collegues... > > > > > > I have SuSE Linux 8.1 with SuSEfirewall2, BIND 8, > > > ip-masquerading and squid server. This server use > > ISDN > > > dial up to arcor (www.arcor.de) > > > > > > Everything runs properly, I have opened "53 3128 > > 67 25 > > > 110". But after sometimes than my LAN User can not > > > surfing to internet anymore but they still can use > > > e-mail (pop and smtp) properly.I don't know when > > the > > > problem comes, lookslike after our ISP > > reset/change > > > the IP number of our ISDN card (I guess so). > > > > > > The LAN user can go to the internet only after I > > > restart my SuSEfirewall, such as: > > > " > > > SuSEfirewall2 stop > > > SuSEfirewall2 start > > > " > > > > > > Thank you very much. > > > > Have a look at /var/log/messages -> are there any > > entries which show dropped or rejected packages? > > > > > > > > ps. If I start my SuSEfirewall2 than comes this > > error > > > message: > > > " > > > proxy:~ # SuSEfirewall2 start > > > Warning: FW_SERVICE_DNS defined, but no DNS server > > > found running! > > > proxy:~ # > > > " > > > > Does your DNS crash sometimes? Again look at > > /var/log/messages, it's all in there ;-) > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Tax Center - forms, calculators, tips, more > http://taxes.yahoo.com/ > > -- > Check the headers for your unsubscription address > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > >

2 2

224.0.0.1 messages
by suse-sec＠orcaoffice.com 28 Feb '03

28 Feb '03

Hi, I have the following in my /var/log/warn file : Feb 28 13:51:37 plato kernel: SuSE-FW-ILLEGAL-TARGET IN=ppp0 OUT= MAC= SRC=xx.xx.xx.xx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=55846 PROTO=2 I've read that this message is basically a misconfigured router from my DSL supplier. However what I'd like to know is, what can I add to my SuSEFirewall config so that I can skip logging these messages (i.e. ignore any 224.0.0.1 messages )? Thanks CPH

3 3

Fwd: RE: [suse-security] My SuSEFirewall blocks something than my LAM can not surfing in internet anymore.
by Ian David Laws 28 Feb '03

28 Feb '03

Hi Prabu you see that it is ssh if you look at the destination port DST it is 22 or SSH . Ian ---------- Forwarded Message ---------- Subject: RE: [suse-security] My SuSEFirewall blocks something than my LAM can not surfing in internet anymore. Date: Fri, 28 Feb 2003 06:01:33 -0800 (PST) From: Prabu Subroto <prabu_subroto(a)yahoo.com> To: SuSE Security Milis <suse-security(a)suse.com> Dear Peer.... I tried the command line from you. But the output is empty... I grep nothing... I will repeat this threat from you if the problem comes again. Btw, how can you know that what I send to you was only ssh? Please help me, I am stucked... --- Peer Stefan <stefan.peer(a)tiwag.at> wrote: > Hi Prabu, > > Sorry to say so, but this trace shows nothing more > than a connection-trace of your ssh-session (DPT=22 > ...). > Don't tail /var/log/messages, it's quite big and > gets filled really fast. > Do a "cat /var/log/messages|grep DTP=80|grep -v > DST=192.168.23.10" in order to get all the outgoing > http-stuff. > > so long, > Stefan > > btw. I'm called Stefan - it's a bit queer here in > Austria, we always put the last name in front ;-) > > > From: Prabu Subroto > > [mailto:prabu_subroto@yahoo.com] > > > Dear my friend, Peer... > > > > Today morning, it happened again. I follow your > > advice > > > and this is the 60 lines of my "/var/log/messages" > > file: > > " > > proxy:/var/log # tail -n 60 messages > > Feb 27 14:04:49 proxy kernel: > > SuSE-FW-ACCEPT-ALL-INTERNAL IN=eth0 OUT= > > MAC=00:50:bf:77:77:d5:00:50:bf:77:80:49:08:00 > > SRC=192.168.23.237 DST=192.168.23.10 LEN=52 > > TOS=0x10 > > > PREC=0x00 TTL=64 ID=4343 DF PROTO=TCP SPT=1132 > > DPT=22 >

2 1

RE: [suse-security] My SuSEFirewall blocks something than my LAM can not surfing in internet anymore.
by Peer Stefan 28 Feb '03

28 Feb '03

Hi > From: Prabu Subroto [mailto:prabu_subroto@yahoo.com] > Dear my collegues... > > I have SuSE Linux 8.1 with SuSEfirewall2, BIND 8, > ip-masquerading and squid server. This server use ISDN > dial up to arcor (www.arcor.de) > > Everything runs properly, I have opened "53 3128 67 25 > 110". But after sometimes than my LAN User can not > surfing to internet anymore but they still can use > e-mail (pop and smtp) properly.I don't know when the > problem comes, lookslike after our ISP reset/change > the IP number of our ISDN card (I guess so). > > The LAN user can go to the internet only after I > restart my SuSEfirewall, such as: > " > SuSEfirewall2 stop > SuSEfirewall2 start > " > > Thank you very much. Have a look at /var/log/messages -> are there any entries which show dropped or rejected packages? > > ps. If I start my SuSEfirewall2 than comes this error > message: > " > proxy:~ # SuSEfirewall2 start > Warning: FW_SERVICE_DNS defined, but no DNS server > found running! > proxy:~ # > " Does your DNS crash sometimes? Again look at /var/log/messages, it's all in there ;-)

2 1

My LAN user can not surfing in internet after a couple of hours.
by Prabu Subroto 28 Feb '03

28 Feb '03

Dear my friends.... I am using SuSE Linux 8.1 for our internet gateway. I installed Squid, SuSEfirewall2 and ip-masquerading on the Linux-Box. It runs properly after a couple of hours in one day but than my LAN user can not surfing in internet anymore. If the problem comes, my LAN user still can use e-mail through IP-Masquerading but not http. If the problem comes than I have to restart the SuSEfirewall2 with: " SuSEfirewall2 stop SuSEfirewall2 start " After restarting the SuSEfirewall2 than my LAN user can surfing in internet back (again). If I restart my SuSEfirewall I got this error message: " proxy:~ # SuSEfirewall2 stop Removing filter rules ... SuSEfirewall2: clearing rules now ... done proxy:~ # SuSEfirewall2 start Warning: FW_SERVICE_DNS defined, but no DNS server found running! proxy:~ # " Here is my "/var/log/messages": " patrixlinux@patrix:~/arsip> tail -n 60 ./fromproxy Feb 27 13:14:17 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38389 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:14:17 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35450 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:23 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38390 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:14:23 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35451 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:24 proxy squid[8941]: idnsCheckQueue: ID 5c4: giving up after 35 tr ies and 310.0 seconds Feb 27 13:14:24 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=96 TOS=0x00 PREC=0x00 TTL=247 ID=38391 DF PROTO =UDP SPT=53 DPT=1096 LEN=76 Feb 27 13:14:24 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=246 ID=35452 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:14:28 proxy squid[8941]: idnsCheckQueue: ID 5c5: giving up after 34 tr ies and 302.7 seconds Feb 27 13:14:28 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38392 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:33 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=173 TOS= 0x00 PREC=0x00 TTL=64 ID=61439 DF PROTO=UDP SPT=631 DPT=631 LEN=153 Feb 27 13:14:33 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=173 TOS= 0x00 PREC=0x00 TTL=64 ID=61440 DF PROTO=UDP SPT=631 DPT=631 LEN=153 Feb 27 13:14:33 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=171 TOS= 0x00 PREC=0x00 TTL=64 ID=61441 DF PROTO=UDP SPT=631 DPT=631 LEN=151 Feb 27 13:14:33 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=174 TOS= 0x00 PREC=0x00 TTL=64 ID=61442 DF PROTO=UDP SPT=631 DPT=631 LEN=154 Feb 27 13:14:33 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38393 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:33 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=96 TOS=0x00 PREC=0x00 TTL=246 ID=35453 DF PROTO =UDP SPT=53 DPT=1096 LEN=76 Feb 27 13:14:35 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38394 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:14:35 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35454 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:40 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35455 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:44 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=96 TOS=0x00 PREC=0x00 TTL=247 ID=38395 DF PROTO =UDP SPT=53 DPT=1096 LEN=76 Feb 27 13:14:44 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=246 ID=35456 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:14:46 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38396 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:47 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=174 TOS= 0x00 PREC=0x00 TTL=64 ID=61555 DF PROTO=UDP SPT=631 DPT=631 LEN=154 Feb 27 13:14:51 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38397 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:51 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=96 TOS=0x00 PREC=0x00 TTL=246 ID=35457 DF PROTO =UDP SPT=53 DPT=1096 LEN=76 Feb 27 13:14:54 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38398 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:14:54 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35458 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:14:56 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35459 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:01 proxy squid[8941]: idnsCheckQueue: ID 5c6: giving up after 33 tr ies and 301.9 seconds Feb 27 13:15:01 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=246 ID=35460 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:15:04 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=173 TOS= 0x00 PREC=0x00 TTL=64 ID=61623 DF PROTO=UDP SPT=631 DPT=631 LEN=153 Feb 27 13:15:04 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=173 TOS= 0x00 PREC=0x00 TTL=64 ID=61624 DF PROTO=UDP SPT=631 DPT=631 LEN=153 Feb 27 13:15:04 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=171 TOS= 0x00 PREC=0x00 TTL=64 ID=61625 DF PROTO=UDP SPT=631 DPT=631 LEN=151 Feb 27 13:15:04 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=174 TOS= 0x00 PREC=0x00 TTL=64 ID=61626 DF PROTO=UDP SPT=631 DPT=631 LEN=154 Feb 27 13:15:05 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=217. 225.240.146 DST=145.254.88.223 LEN=60 TOS=0x00 PREC=0x00 TTL=54 ID=13525 DF PROT O=TCP SPT=2539 DPT=4662 WINDOW=15972 RES=0x00 SYN URGP=0 OPT (020405840402080A00 5A2CC70000000001030300) Feb 27 13:15:05 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38399 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:07 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38400 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:08 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=217. 225.240.146 DST=145.254.88.223 LEN=60 TOS=0x00 PREC=0x00 TTL=54 ID=13724 DF PROT O=TCP SPT=2539 DPT=4662 WINDOW=15972 RES=0x00 SYN URGP=0 OPT (020405840402080A00 5A2DF30000000001030300) Feb 27 13:15:11 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38401 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:15:11 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35461 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:11 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35462 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:14 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=217. 225.240.146 DST=145.254.88.223 LEN=60 TOS=0x00 PREC=0x00 TTL=54 ID=14050 DF PROT O=TCP SPT=2539 DPT=4662 WINDOW=15972 RES=0x00 SYN URGP=0 OPT (020405840402080A00 5A304B0000000001030300) Feb 27 13:15:17 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=246 ID=35463 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:15:18 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=174 TOS= 0x00 PREC=0x00 TTL=64 ID=61697 DF PROTO=UDP SPT=631 DPT=631 LEN=154 Feb 27 13:15:21 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38402 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:21 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38403 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:26 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=217. 225.240.146 DST=145.254.88.223 LEN=60 TOS=0x00 PREC=0x00 TTL=54 ID=14661 DF PROT O=TCP SPT=2539 DPT=4662 WINDOW=15972 RES=0x00 SYN URGP=0 OPT (020405840402080A00 5A34FB0000000001030300) Feb 27 13:15:28 proxy squid[8941]: idnsCheckQueue: ID 5c7: giving up after 34 tr ies and 303.1 seconds Feb 27 13:15:28 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38404 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:15:28 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35464 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:31 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195. 202.35.106 DST=145.254.88.223 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=4772 DF PROTO =TCP SPT=2896 DPT=4662 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (0204058601010402) Feb 27 13:15:34 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=246 ID=35465 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:15:34 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195. 202.35.106 DST=145.254.88.223 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=4891 DF PROTO =TCP SPT=2896 DPT=4662 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (0204058601010402) Feb 27 13:15:35 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=173 TOS= 0x00 PREC=0x00 TTL=64 ID=61792 DF PROTO=UDP SPT=631 DPT=631 LEN=153 Feb 27 13:15:35 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=173 TOS= 0x00 PREC=0x00 TTL=64 ID=61793 DF PROTO=UDP SPT=631 DPT=631 LEN=153 Feb 27 13:15:35 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=171 TOS= 0x00 PREC=0x00 TTL=64 ID=61794 DF PROTO=UDP SPT=631 DPT=631 LEN=151 Feb 27 13:15:35 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=eth0 OUT= MAC=ff:ff:ff:f f:ff:ff:00:50:bf:77:77:f8:08:00 SRC=192.168.23.238 DST=192.168.23.0 LEN=174 TOS= 0x00 PREC=0x00 TTL=64 ID=61795 DF PROTO=UDP SPT=631 DPT=631 LEN=154 Feb 27 13:15:39 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=247 ID=38405 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 Feb 27 13:15:40 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195. 202.35.106 DST=145.254.88.223 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=5137 DF PROTO =TCP SPT=2896 DPT=4662 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (0204058601010402) Feb 27 13:15:45 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.196 DST=145.254.88.223 LEN=117 TOS=0x00 PREC=0x00 TTL=247 ID=38406 DF PROT O=UDP SPT=53 DPT=1096 LEN=97 Feb 27 13:15:45 proxy kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=145. 253.2.139 DST=145.254.88.223 LEN=301 TOS=0x00 PREC=0x00 TTL=246 ID=35466 DF PROT O=UDP SPT=53 DPT=1096 LEN=281 patrixlinux@patrix:~/arsip> " Please help me to solve this problem. I still can not understand. Should I allow "145.254.88.223"? How? Thank you very much. Thank you very much in advance. __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/

1 0

SuSE Security Announcement: hypermail (SuSE-SA:2003:0012)
by Thomas Biege 27 Feb '03

27 Feb '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: hypermail Announcement-ID: SuSE-SA:2003:0012 Date: Thursday, Feb 27th 2003 18:30 MET Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 Vulnerability Type: remote system compromise Severity (1-10): 4 SuSE default package: no Cross References: CAN-2003-0025 Content of this advisory: 1) security vulnerability resolved: several bugs after source code review problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - vnc - w3m 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Hypermail is a tool to convert a Unix mail-box file to a set of cross- referenced HTML documents. During an internal source code review done by Thomas Biege several bugs where found in hypermail and its tools. These bugs allow remote code execution, local tmp race conditions, denial-of-service conditions and read access to files belonging to the host hypermail is running on. Additionally the mail CGI program can be abused by spammers as email- relay and should thus be disabled. There is no temporary fix known other then disabling hypermail. Please download and 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/hypermail-2.1.4-58.i58… a4b683703b65cb65d0d1b246c2bf652d patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/hypermail-2.1.4-58.i58… 9e087a97c250c8987dda03da43e0dd1e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/hypermail-2.1.4-58.src.… 9d95d9872a3ed98a4dbff25e952335d7 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap4/hypermail-2.1.3-234.i386.rpm 53bdfc3ca1ab0c504f460ac7a18ba42e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/hypermail-2.1.3-234.src.rpm be0df42b666fc59e38babd671479d2f1 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap2/hypermail-2.1.2-141.i386.rpm 81194dcbb3cf149f67eac9948dd79db9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/hypermail-2.1.2-141.src.rpm 9a02ce79e81bab281c418070fa91dbde SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap2/hypermail-2.1.0-91.i386.rpm d61f52df6c995b65e16a4141b1b7efa1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/hypermail-2.1.0-91.src.rpm 66b65eed8f2daefde8115abf77511bba SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/ap2/hypermail-2.0b29-59.i386.rpm 698338c7d9b8961ec3d4f4ab99ee2436 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/hypermail-2.0b29-59.src.rpm 8db31cd4981ee84a0333ec8200443bef Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap2/hypermail-2.1.2-40.sparc.r… 341757885457f2e4b018dbb132f1a8f8 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/hypermail-2.1.2-40.src.rpm cdc92a18900996524768914c79bf20d9 AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/ap2/hypermail-2.0b29-37.alpha.rpm 980f217c12affcb3c0a6d0fd916a5115 source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/hypermail-2.0b29-37.src.rpm a2242ecc8ba2a13c3d18ca94e6ba23f0 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap2/hypermail-2.1.2-98.ppc.rpm 6c7a197fe18a95b7594b2cd7b572837a source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/hypermail-2.1.2-98.src.rpm e370de5432545f06731c9f841bc84054 SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/ap2/hypermail-2.0b29-38.ppc.rpm 64b3be05678f4789985824e31f8335d2 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/hypermail-2.0b29-38.src.rpm 4cd2b65522738594d0b60333f807b8b2 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - vnc VNC (Virtual Network Computing) uses a weak cookie generation process which can be exploited by an attacker to bypass authentication. New packages are currently being tested and will be available on our FTP servers soon. - w3m The textbased web-browser w3m does not properly escape HTML tags. A malicious HTML page or img alt attribute may lead to information leakage. New packages will be available soon. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(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 iQEVAwUBPl5TD3ey5gA9JdPZAQEzPAgAgITAIC3FizXxoVcOHGcfAgQD/p409cFg Jllmi+VTQ+ytdPXGdILCPv7rVgbEaeTOcSohf2Fss8PwGQHhBTZ0ATdrPjO5yAeS 67YZh68UVPnZ+sQ3Dqvq+/ZFQp+fR8RP2p6mEL0jlYz7XCfRu0b0qb+pV8juWikW US7hdegN7rInMEykyXaJ2uQWwhrQdhm7N+ZHW2aTILa76FLH3x2hHuHupZ/jDsQy SfNQzn4ROMT/F26dzZ4/45UekHB5Q2+9FXSPUbECJwsEoGL7cB7xk6VB5Td9U6Iv H7+xBh2Ut5gbaAh5QLDGvvekuDAUxnGNmWQzOcJumDlcViRdWRfK1w== =ac7H -----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: openssl (SuSE-SA:2003:011)
by Roman Drahtmueller 27 Feb '03

27 Feb '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: openssl Announcement-ID: SuSE-SA:2003:011 Date: Wednesday, Feb. 26th 2003 15:20 MET Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7 SuSE Linux Enterprise Server 8 SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: remote attack on encryption Severity (1-10): 5 SuSE default package: yes Cross References: CAN-2003-0078 Content of this advisory: 1) security vulnerability resolved: openssl problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - vnc - w3m 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information OpenSSL is an implementation of the Secure Sockets Layer and Transport Layer Security protocols and provides strong cryptography for many applications in a Linux system. It is a default package in all SuSE products. A security weakness has been found, known as "Vaudenay timing attack on CBC", named after one of the discoverers (Brice Canvel (EPFL), Alain Hiltgen (UBS), Serge Vaudenay (EPFL), and Martin Vuagnoux (EPFL, Ilion)). The weakness may allow an attacker to obtain a plaintext data block by observing timing differences in response to two different error cases (cipher padding errors vs. MAC verification errors). In order to exploit this vulnerability, the attacker has to meet certain requirements: The network connection between client and server must be of high quality to be able to observe timing differences, the attacker must be able to perform a man-in-the-middle attack, the transactions must repeatedly contain the same (encrypted) plain text block (such as a pop password or alike), and decoding failures in the SSL layer must not be propagated to the application that is using the SSL connection. These exploitation conditions considerably reduce the security risk imposed by the vulnerability. However, we recommend to completely remedy this weakness by installing the update packages for your system according to the following guidelines. There does not exist any temporary workaround for this problem other than applying the update packages. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. SPECIAL INSTALLATION INSTRUCTIONS: ==================================== Please update your openssl package using the command rpm -Fhv <package.rpm> The operation of this command must not be interrupted! An interrupted update of the openssl package may cause large protions of your system to fail. After performing the update, it is adviseable to run the command "ldconfig" to update the shared library loading cache. After the update, running processes in your system will continue to use the shared libraries from the old package before the update. Generally, it is necessary to restart all of these processes to completely fix the vulnerability in your system. The command lsof -n 2>/dev/null | grep RPMDELETE can be used to find the binaries and processes that still use the old shared libraries. In all cases, the next reboot of the system will cause the old shared libraries to be completely removed from the system. Alternatively, a transition to runlevel 1 (single user mode) and back to the default runlevel will have the same effect. Intel i386 Platform: SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-55.i586… 7fbf4d975180a20ff8dedc8adbdecc59 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-55.i586… 6ed4321ec536aa718189702470c33091 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-55.src.r… 90fc753346dd2aff00eee4c530cea84a SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-83.i386.rpm d6246b820780993cc0e2b48597743a8f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-83.i386.pat… 2d933e913a9062de6a1fa35de969d211 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-83.src.rpm b4b887a7311e9734a14d11e1a380f76e SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssl-0.9.6b-154.i386.rpm d3c0f892441c09c8c5a689e2af04ba55 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-154.src.rpm 31ec962fe3549a713b9e6937190a88fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssl-0.9.6a-78.i386.rpm d14f67c34c589f168b750b18c9162508 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-78.src.rpm 2ba5a416d6ca3cb75c9aabb5a25bb532 SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/openssl-0.9.6a-78.i386.rpm c6b711573555982fadd31cfa179dd9dc source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/openssl-0.9.6a-78.src.rpm d00df30aa6ec6a3872c58da709181879 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/openssl-0.9.6b-87.sparc.r… 6a8f19a49a698b93e740121321f59e5d source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-87.src.rpm 50712c3fd35042278063622ad5cc77c7 AXP Alpha Platform: The packages for the 7.1-axp distribution will be published soon. PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssl-0.9.6b-147.ppc.rpm 051ef85d8e711819b2de38f55dc0023a source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-147.src.rpm 58631776b8fa88932eb57069a7f2878e SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/openssl-0.9.6a-28.ppc.rpm da5e7caa177316f3016dd98497e580de source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/openssl-0.9.6a-28.src.rpm b317144556c8f1890d15f304d95c5764 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - vnc VNC (Virtual Network Computing) uses a weak cookie generation process which can be exploited by an attacker to bypass authentication. New packages are currently being tested and will be available on our FTP servers soon. - w3m The textbased web-browser w3m does not properly escape HTML tags. A malicious HTML page or img alt attribute may lead to information leakage. New packages will be available soon. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(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.3in Charset: noconv iQEVAwUBPlzffney5gA9JdPZAQG3RQf6Aj55DN4eyOCKlKywqQITYHfvaFi1gzIX q05/9X8r4jfSQlbKYp61h6yO5DcfA2rr9tDIA30IAt9cnzMS+hybMOgyd53bdcJ3 as8QdCspVhDC+RJ7Nk5UZwu8t30kTAY8g2hvxsteFg/LRFX6id5cTS2frnFofHvq Mg1q2K0BoziYe0Yjx+k9MhuFKSPqR386OTmUknZqm2f7B0naK8yKW7z6p8GVc60z cjHDaWuutK/dEKqw5yQI/0E1CpcgyGAQ/4zlNP2xJ9GvndJpCdFvQv/AhvnRR87W 2MMPIuK1BziDsTifVZ4yz7GG9Ff7NJtKkhpHSrdevTXUVMD6yzwGFA== =u+n+ -----END PGP SIGNATURE----- -- - - | 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 | - -

2 2

AW: [suse-security] Backup software
by Volkan Yilmaz (MUC) 27 Feb '03

27 Feb '03

You can use www.rpmfind.net to locate the amanda rpm package for your system! regards volkan ------------------------------------ Volkan Yilmaz Project Executive, Network Security SC Service Concept Sued GmbH Gollierstrasse 70 A 4 80339 Munich / Germany Fon: +49 (0) 89 500323 - 0 Fax: +49 (0) 89 500323 - 99 E-Mail: vo.yilmaz(a)scgmbh.de Visit us: http://www.scgmbh.de ------------------------------------ Disclaimer This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. -----Ursprüngliche Nachricht----- Von: Miguel Rodríguez [mailto:mrodriguez@catenon.com] Gesendet: Donnerstag, 27. Februar 2003 13:01 An: Suse-Security Betreff: [suse-security] Backup software Hi list, Where can I download amanda-server? I have found amanda tgz in amanda.org, but this seems not to be the server, is this right? -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

1 0

My SuSEFirewall blocks something than my LAM can not surfing in internet anymore.
by Prabu Subroto 27 Feb '03

27 Feb '03

Dear my collegues... I have SuSE Linux 8.1 with SuSEfirewall2, BIND 8, ip-masquerading and squid server. This server use ISDN dial up to arcor (www.arcor.de) Everything runs properly, I have opened "53 3128 67 25 110". But after sometimes than my LAN User can not surfing to internet anymore but they still can use e-mail (pop and smtp) properly.I don't know when the problem comes, lookslike after our ISP reset/change the IP number of our ISDN card (I guess so). The LAN user can go to the internet only after I restart my SuSEfirewall, such as: " SuSEfirewall2 stop SuSEfirewall2 start " Thank you very much. ps. If I start my SuSEfirewall2 than comes this error message: " proxy:~ # SuSEfirewall2 start Warning: FW_SERVICE_DNS defined, but no DNS server found running! proxy:~ # " __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/

1 0

Backup software
by Miguel Rodríguez 27 Feb '03

27 Feb '03

Hi list, Where can I download amanda-server? I have found amanda tgz in amanda.org, but this seems not to be the server, is this right?

1 0

FW: [suse-multimedia] VPN CIPE
by Ruprecht Helms 27 Feb '03

27 Feb '03

Hi, sorry for german text, original posted in the wrong ml. Regards, Ruprecht -----FW: <C046B8B0A5BCD411B92500508BB07EFB021809BA(a)ssi-schaefer.de>----- Date: Thu, 27 Feb 2003 09:46:41 +0100 From: "Junge, Stefan" <Stefan.Junge(a)ssi-schaefer.de> To: "suse-multimedia(a)suse.com" <suse-multimedia(a)suse.com> Subject: [suse-multimedia] VPN CIPE Hallo zusammen ! gehört zwar nicht hier her, aber ... hat hier jemand mit CIPE Erfahrungen ? Ich muß Windows 2000 Clients an mein VPN Gateway anbinden. Leider funktioniert der Windows Client nicht so recht. Gruß Stefan -- Um die Liste abzubestellen, schicken Sie eine Mail an: suse-multimedia-unsubscribe(a)suse.com Um eine Liste aller verfügbaren Kommandos zu bekommen, schicken Sie eine Mail an: suse-multimedia-help(a)suse.com --------------End of forwarded message------------------------- ---------------------------------- Ruprecht Helms IT-Service und Softwareentwicklung Tel/Fax.: +49[0]7621 16 99 16 Homepage: http://www.rheyn.de email: info(a)rheyn.de ----------------------------------

1 0

Re: [suse-security] Problem installing update package
by GarUlbricht7＠netscape.net 27 Feb '03

27 Feb '03

Hi: > In trying to download Gnome2, I noticed there are patches for openssl-devel 0.9.6c and openssl-doc 0.9.6c --- could your problem be you need to update all your openssl Packages -- just a thought-- HTH > GarUlbricht7 wrote: >I just noticed this thread -- I am trying to figure how to install >the new Gnome2 packages -- so far no joy -- filesystem is still giving me problems --- Although I did find a read me I had missed on:<http://www.suse.de/en/private/download/gnomes/index.html> > >AFAYP, you might consider (after running rpm -v --checksig, to verify MD5sum, as Andreas suggested), putting "openssl" in a directory by itself, and then from a console as root in that directory runn simply: > rpm -Uvh *.rpm >-- it may be a package name is the problem -- >or dependency problem -- >(Sorry this is such a long reply, >I didn't have time to write a short one---) >~Gar > >Andreas Kyek <a.kyek(a)vodafone.com> wrote: >>On 26 Feb 2003 at 9:31, Mueller.F(a)loh-services.de wrote: >> >>> I want to install the new openssl package on SuSE Enterprise Server 8. >>> I downloaded the package from the maintenance web. When I try to >>> install it with "rpm -Fvh openssl-0.9.6g-55.i586.rpm" >>> I just get the message >>> "error: openssl-0.9.6g-55.i586.rpm cannot be installed" >>> >>> rpm -Uvh doesn't work either. >>> >>> Any solution? >> >> I think your copy of the package is damaged! >> verify it (perhaps with md5sum) and you will see that. >> >>Andreas >> > __________________________________________________________________ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

1 0

Re: [suse-security] Problem installing update package
by GarUlbricht7＠netscape.net 26 Feb '03

26 Feb '03

I just noticed this thread -- I am trying to figure how to install the new Gnome2 packages -- so far no joy -- filesystem is still giving me problems --- Although I did find a read me I had missed on:<http://www.suse.de/en/private/download/gnomes/index.html> AFAYP, you might consider (after running rpm -v --checksig, to verify MD5sum, as Andreas suggested), putting "openssl" in a directory by itself, and then from a console as root in that directory runn simply: rpm -Uvh *.rpm -- it may be a package name is the problem -- or dependency problem -- (Sorry this is such a long reply, I didn't have time to write a short one---) ~Gar Andreas Kyek <a.kyek(a)vodafone.com> wrote: >On 26 Feb 2003 at 9:31, Mueller.F(a)loh-services.de wrote: > >> I want to install the new openssl package on SuSE Enterprise Server 8. >> I downloaded the package from the maintenance web. When I try to >> install it with "rpm -Fvh openssl-0.9.6g-55.i586.rpm" >> I just get the message >> "error: openssl-0.9.6g-55.i586.rpm cannot be installed" >> >> rpm -Uvh doesn't work either. >> >> Any solution? > > I think your copy of the package is damaged! > verify it (perhaps with md5sum) and you will see that. > >Andreas > __________________________________________________________________ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

1 0

YOU on SuSE 8.1
by Bryan Smith 26 Feb '03

26 Feb '03

This may or may not be the list, but I'm sure everyone has gone through this. I have two 8.1 boxes and one 8.0 box. YOU on 8.1 does not want to work correctly. I've looked on the downloads/updates/patches site and manually updated the yast2 packages for YOU. However, this still doesn't seem to fix the error of hanging while "Initiallizing for HTTP/FTP..." Is this something to just live with or has someone worked past this issue? Thanks, -Bryan

19 31

SuSE Security Announcement: libmcrypt (SuSE-SA:2003:0010)
by Thomas Biege 26 Feb '03

26 Feb '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: libmcrypt Announcement-ID: SuSE-SA:2003:0010 Date: Wednesday, Feb. 26th 2003 11:20 MET Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 SuSE eMail Server 3.1 SuSE eMail Server III SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 SuSE Linux Enterprise Server 8 SuSE Linux Office Server Vulnerability Type: local privilege escalation remote denial-of-service Severity (1-10): 3 SuSE default package: no Cross References: CAN-2003-0031 CAN-2003-0032 Content of this advisory: 1) security vulnerability resolved: buffer overflow problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - openssl - vnc - w3m 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Libmcrypt is a data encryption library that is able to load crypto- modules at run-time by using libltdl. Versions of libmcrypt prior to 2.5.5 include several buffer overflows that can be triggered by passing very long input to the mcrypt_* functions. The way libmcrypt handles dynamic crypto-modules via libltdl leads to memory-leaks that can cause a Denial-of-Service condition. This Problem can just be solved by linking modules static. This security update does not solve the memory-leak problem to avoid compatibility problems. Future releases of libmcrypt will be linked statically. To add the new library to the shared library cache you have to run ldconfig(8) as root. Additionally every program that is linked with libmcrypt needs to be restarted. ldd(1) can be used to find out which libraries are used by a program. Another way to determine which process uses a shared library that had been deleted is: lsof -n 2>/dev/null | grep RPMDELETE | cut -d " " -f 1 | sort | uniq There is no temporary fix known. Please install the new packages from our FTP servers. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Intel i386 Platform: SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-2.5.2-48.i58… 6dc3127a069545b9cb00cafd9897021f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-2.5.2-48.i58… 3b88d2a7f1bf409ec6cdee4702c8dc40 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/libmcrypt-2.5.2-48.src.… 8feed7301cb26aaa27084baea4a1677e SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-devel-2.5.2-… 52bdf4a54df9fc698971fc1223b73d3d patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libmcrypt-devel-2.5.2-… 5ecc44d5b4d6f35a4f57db1d7092575e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/libmcrypt-2.5.2-48.src.… 8feed7301cb26aaa27084baea4a1677e SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec2/libmcrypt-2.4.20-114.i386.… 45997d80e97ce180a14b692b1f63b34b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec2/libmcrypt-2.4.20-114.i386.… 5ee228e095fbb3f53027a8a902978975 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/libmcrypt-2.4.20-114.src.rpm 6c189dcf7bcbffa7f271cdeb9065e212 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/d4/libmcrypt-devel-2.4.20-114.i… 36b45ac7281a3dd2ba94794e26012180 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/d4/libmcrypt-devel-2.4.20-114.i… 21ad28cb8dad5e418f0185b53470502c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/libmcrypt-2.4.20-114.src.rpm 6c189dcf7bcbffa7f271cdeb9065e212 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/libmcrypt-2.4.15-98.i386.r… f38972e593b79b8e22d5db86d9f75083 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/libmcrypt-2.4.15-98.src.rpm 8390dbcef0b58b3cca5141254f3af8ea SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/libmcrypt-devel-2.4.15-98.… 6c5df7c177d88509aa10868142262868 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/libmcrypt-2.4.15-98.src.rpm 8390dbcef0b58b3cca5141254f3af8ea SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/libmcrypt-2.4.10-59.i386.r… 5ff561010a642a26f92b1a491df6317c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/libmcrypt-2.4.10-59.src.rpm 5430bf5ca7f79c16248024cbd6eb735a SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/libmcrypt-devel-2.4.10-59.… 7afa785605e65106a3a250bd166ca2ef source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/libmcrypt-2.4.10-59.src.rpm 5430bf5ca7f79c16248024cbd6eb735a SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec2/libmcrypt-2.4.7-19.i386.rpm 4208d6905aa7c7dd13de30aa945f1693 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/libmcrypt-2.4.7-19.src.rpm d6c0a61d874869ee3927af3b58335ff4 SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec2/libmcrypt-devel-2.4.7-19.i… 03028dbcf99e6fe167a30cd9b2e6da0f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/libmcrypt-2.4.7-19.src.rpm d6c0a61d874869ee3927af3b58335ff4 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/libmcrypt-2.4.15-53.sparc… ae638ffb875f53df64325e8e0a148807 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/libmcrypt-2.4.15-53.src.rpm c6bdd14b370e0ca912e8ca7615580df0 SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/libmcrypt-devel-2.4.15-53… 846455cc24b212f7b7287332cababc06 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/libmcrypt-2.4.15-53.src.rpm c6bdd14b370e0ca912e8ca7615580df0 AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec2/libmcrypt-2.4.7-26.alpha.rpm 3789bb0a9411d85ec4514490f342a70f source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/libmcrypt-2.4.7-26.src.rpm c8dd2a18ccb249ed384df14359ba094e SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec2/libmcrypt-devel-2.4.7-26.al… fa61fea31359365d07ccf45a56b1ca80 source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/libmcrypt-2.4.7-26.src.rpm c8dd2a18ccb249ed384df14359ba094e PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/libmcrypt-2.4.15-89.ppc.rpm f75b386d8894c98fd0fa534d3560abbe source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/libmcrypt-2.4.15-89.src.rpm 5a3b3ce95652b81efb738b59aec1a7e4 SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/libmcrypt-devel-2.4.15-89.p… 6d3cea579e658b66ea62c97d4c58ce17 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/libmcrypt-2.4.15-89.src.rpm 5a3b3ce95652b81efb738b59aec1a7e4 SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec2/libmcrypt-2.4.7-23.ppc.rpm f097c1a2ce67b85cffb8f0076a6c09c3 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/libmcrypt-2.4.7-23.src.rpm 9df0c47eb030905edeed919750aec9df SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec2/libmcrypt-devel-2.4.7-23.pp… dc79a537365aae51c27d60dabb2615bf source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/libmcrypt-2.4.7-23.src.rpm 9df0c47eb030905edeed919750aec9df ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - OpenSSL Update packages for the recently found weakness in the openssl package are available on our ftp servers. An announcement concerning this issue follows this announcement. - VNC VNC (Virtual Network Computing) uses a weak cookie generation process which can be exploited by an attacker to bypass authentication. New packages are currently being tested and will be available on our FTP servers soon. - w3m The textbased web-browser w3m does not properly escape HTML tags. A malicious HTML page or img alt attribute may lead to information leakage. New packages will be available soon. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(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 iQEVAwUBPlyhyHey5gA9JdPZAQGrbQgAkRW6WfHLUlML05hHQvyU7BKErKmrUpIL reFsEgB/5dBq4TkagZ9lDmHR9PUOs1qUOzDdcIsKG6JWduXe+9s1owzkSOK5MsKQ xl7+OqNS/8aP/+uhN1DxUCagZXV01tBh7IDuKlnJIClawD6cFt3UDtFzIOoZ13XJ 1pGgDZ3OTJ7VJ9JY64j8jZ9qxHoxoaOlgFVCsXeNfzpeNAtMzQKfaHLIYkxXn2qf Rtb9aqx8rPpD7PRJQrlOPNfln1N9JaXUZZ76JrCOt3m6PaPxAEvoYt4AWQy3Oe55 uKMnCnOMpQg1j/JLyXq3y58FuThdeZDWIrOwQwDlf22YKsNv+zbLJQ== =JMk6 -----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

Problem installing update package
by Mueller.F＠loh-services.de 26 Feb '03

26 Feb '03

I want to install the new openssl package on SuSE Enterprise Server 8. I downloaded the package from the maintenance web. When I try to install it with "rpm -Fvh openssl-0.9.6g-55.i586.rpm" I just get the message "error: openssl-0.9.6g-55.i586.rpm cannot be installed" rpm -Uvh doesn't work either. Any solution?

2 1

SuSEfirewall2 errors on SuSE linux 8.1
by Fiorenza Meini 26 Feb '03

26 Feb '03

Hi there! On my SuSE Linux 8.1 professional box I configured the firewall and when I run SuSEfirewall2 I receive this kind of message: /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression expected /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression expected /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression expected /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression expected iptables v1.2.7a: Maximum prefix length 29 for --log-prefix Please, what does it mean? My firewall configuration is attached. Thanks Fiorenza <<SuSEfirewall2>>

2 1

(OT) RUXCON - 12/13 April, 2003. SYDNEY, Australia
by Adam Daniel 26 Feb '03

26 Feb '03

Anyone in Australia or the asia pacific region may want to check out this, I'll be there for sure. ----- Forwarded message from RuxCon <announce-con(a)ruxcon.org> ----- RUXCON - 12/13 April, 2003. SYDNEY, Australia. http://www.ruxcon.org RUXCON is a conference organized by the (sometimes underground) Australian security community. It is an attempt to bring together the individual talents of the Australian computer security sector, through live presentations, workshops and demonstrations, free of charge to the larger public community. RUXCON will be a two day conference. Live presentations and workshops will cover a full range of defensive and offensive security issues, varying from unpublished research to required reading for the public community. The presentation track will allocate one hour time slots per speaker. The workshops will be more hands-on, interactive, and in a less formal format. Activities and competitions will be available for entry by the public participants present at the conference. The venue of the conference is hosted by the UNIVERSITY OF TECHNOLOGY, SYDNEY [1]. It is for this reason in conjunction with the Australian computer security community, that the public has access, at no charge, to a world class security conference. For more information please visit http://www.ruxcon.org A call for papers is currently in progress. The speaker list will be finalized on the 1st March, 2003. All presentation submissions or inquiries should be sent to staff-con(a)ruxcon.org. Workshops are currently being organised, however members of the public are able to propose their own workshops. To do so, please send an e-mail to staff-con(a)ruxcon.org with your proposal. Before sending an inquiry please view the FAQ page for presentations and workshops at http://www.ruxcon.org/faq/ [1] http://www.uts.edu.au UTS is the venue, RUXCON is the conference. RUXCON is independent of UTS. The views expressed by RUXCON or at RUXCON are not endorsed or representing the views of UTS. -- RUXCON ----- End forwarded message ----- -- Technical Consultant ----------------------------------------------------------------------- FORENSIC DATA SERVICES PTY LIMITED http://www.forensicdata.com.au ------------------------------------------------------------------------ The information contained in this e-mail is confidential and is intended solely for the addressee. If you received this e-mail by mistake please notify us immediately and delete all copies of this message. You must not disclose or use in any way the information in the e-mail. It is the responsibility of the recipient to virus scan this e-mail and any attachments included.

1 0

installed 8.1 Kernel Update - System crashs KDE/X11
by Philipp Rusch 25 Feb '03

25 Feb '03

Hello list, I installed a kernel update for my 8.1 system as recommended last week by my YOU, when I did check for ISDN-updates because of my AVM card problems (timeouts and so on) I did change from k_athlon-i586-2.4.19.56 to something like k-athlon-i586-2.4.19.167 (?) (not at the system at the moment). My system is bootiung, ok, but I can't get any X11-config to run again. It blinks three times and that's it ! I exchanged my VGA card, put in an old Matrox, reconfigured, again - nothing else than three blinks. Do I have to reinstall ? Change back to the old kernel ? Whats going on here ? TIA, Philipp

2 2

R: [suse-security] SuSEfirewall2 errors on SuSE linux 8.1
by Fiorenza Meini 25 Feb '03

25 Feb '03

here is my conf. file: FW_QUICKMODE="no" FW_DEV_EXT="eth0" FW_DEV_INT="eth1" FW_DEV_DMZ="" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.0.0/16,0/0,tcp,110 10.10.0.0/16,0/0,tcp,21 10.10.0.0/16,0/0,tcp,80 10.10.0.0/16,0/0,tcp,25" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="" FW_SERVICES_EXT_UDP="" # Common: domain FW_SERVICES_EXT_IP="" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_SERVICES_QUICK_TCP="" FW_SERVICES_QUICK_UDP="" FW_SERVICES_QUICK_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="ftp-data" FW_ALLOW_INCOMING_HIGHPORTS_UDP="DNS" FW_SERVICE_AUTODETECT="no" # Autodetect the services below when starting FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SAMBA="no" FW_FORWARD="" # Beware to use this! FW_FORWARD_MASQ="" # Beware to use this! FW_REDIRECT="" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="no" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" FW_KERNEL_SECURITY="yes" FW_STOP_KEEP_ROUTING_STATE="no" FW_ALLOW_PING_FW="no" FW_ALLOW_PING_DMZ="no" FW_ALLOW_PING_EXT="no" FW_ALLOW_FW_TRACEROUTE="yes" FW_ALLOW_FW_SOURCEQUENCH="yes" FW_ALLOW_FW_BROADCAST="no" FW_IGNORE_FW_BROADCAST="yes" FW_ALLOW_CLASS_ROUTING="no" FW_CUSTOMRULES="" FW_REJECT="no" -----Messaggio originale----- Da: Peer Stefan [mailto:stefan.peer@tiwag.at] Inviato: martedì 25 febbraio 2003 14.46 A: Fiorenza Meini; Suse Security (E-mail) Oggetto: RE: [suse-security] SuSEfirewall2 errors on SuSE linux 8.1 Hi Fiorenza, > From: Fiorenza Meini [mailto:fmeini@robinson.it] > Hi there! > On my SuSE Linux 8.1 professional box I configured the > firewall and when I > run SuSEfirewall2 I receive this kind of message: > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > iptables v1.2.7a: Maximum prefix length 29 for --log-prefix > > Please, what does it mean? > > My firewall configuration is attached. No it's not - please include your configuration in the text (run 'cat /etc/sysconfig/SuSEfirewall2|grep -v "^#" | grep -v "^$"' to leave out all comments and empty lines). The last error "iptables v1.2.7a: Maximum prefix length 29 for --log-prefix" means that you cannot assign more than 29 characters as your log-prefix (a short description included in your log-message). Have a look at the directive FW_LOG="...." and especially check for the second ". Sounds like it got lost somewhere. > Thanks > Fiorenza > <<SuSEfirewall2>> regards, Stefan

3 2

RE: [suse-security] SuSEfirewall2 errors on SuSE linux 8.1
by Peer Stefan 25 Feb '03

25 Feb '03

Hi Fiorenza, > From: Fiorenza Meini [mailto:fmeini@robinson.it] > Hi there! > On my SuSE Linux 8.1 professional box I configured the > firewall and when I > run SuSEfirewall2 I receive this kind of message: > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > /sbin/SuSEfirewall2: line 696: test: 10.10.0.0/16: integer expression > expected > iptables v1.2.7a: Maximum prefix length 29 for --log-prefix > > Please, what does it mean? > > My firewall configuration is attached. No it's not - please include your configuration in the text (run 'cat /etc/sysconfig/SuSEfirewall2|grep -v "^#" | grep -v "^$"' to leave out all comments and empty lines). The last error "iptables v1.2.7a: Maximum prefix length 29 for --log-prefix" means that you cannot assign more than 29 characters as your log-prefix (a short description included in your log-message). Have a look at the directive FW_LOG="...." and especially check for the second ". Sounds like it got lost somewhere. > Thanks > Fiorenza > <<SuSEfirewall2>> regards, Stefan

1 0

Problem with SuSEfirewall2 configuration
by Christian Schneider 25 Feb '03

25 Feb '03

Hello, I have recently installed SuSE Linux 8.1 on an "old" computer to run as a Windows (and Linux) File- and Print-Server and to have access to the internet (ISDN card on server: no!!! dial on demand). Everything (samba, squid, bind9, ssh) seems to work correctly without the firewall running. But when the firewall is started, only working with ssh is possible. Perhaps these messages are interesting while the computer is booting: Starting Firewall Initialization (phase 3 of 3): No chain/target/match by that name iptables v1.2.7a: host/network 'ippp0' not found [...] iptables v1.2.7a: Maximum prefix length 29 for --log-prefix [...] Warning: FW_SERVICES_DNS defined, but no DNS server found running! Warning: FW_SERVICES_SQUID defined, but no Squid server found running! (DNS and Squid server are started a few seconds later.) Changes in /etc/sysconfig/SuSEfirewall2: FW_DEV_EXT="ippp0" FW_DEV_INT="eth0" FW_SERVICES_INT_TCP="domain 22 25 110 443 3128 137 138 139 901" FW_SERVICES_INT_UDP="domain 22 25 110 443 3128 137 138 139 901" FW_ALLOW_INCOMING_HIGHPORTS_UDP="no" FW_SERVICE_DNS="yes" FW_SERVICE_SQUID="yes" FW_SERVICE_SAMBA="yes" Is there a problem with the kind of internet connection I use (manual dialing)? Are all neccessary ports accessible from the clients (especially the samba ports)? Thank you for help. Cheers, Christian Schneider __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Bis zu 100 MB Speicher bei http://premiummail.yahoo.de

4 3

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