May 2001 - openSUSE Security - openSUSE Mailing Lists

SSH Authentication
by Joao Reis 18 Nov '02

18 Nov '02

Hi! I implemented a ssh conection from the outside to my intranet. This ssh requires a username and a password. In terms of security what is more secure: require authentication (username and password) or having the public key of each user that connects to our intranet in the authorized public key lists (in this case there is no need for username and password)? In the second case there is no need of authentication and only the users wich have the public keys in the list are allowed to enter in my intranet. This second solution is a good solution or that brings other security problems ? Thanks. -- Farewell. "Keep your friends close, but your enemies closer." "Do or do not. There is no try" - Yoda João Reis -------------------------------------------------------

2 1

RE: [suse-security] Strange apache log entry
by Peer Stefan 02 Jun '01

02 Jun '01

Ok, Microsoft Frontpages has several security flaws, but that does not automatically mean that every request for _vti_<whatever> is done by a hacker or a script-kiddy. Have a look at the browser the client is using, if it's "MSFrontPage/X.Y" then please don't worry. But do worry if it's the only request for a link containing _vti* or if there is only one client (if it's not a proxy) requesting this url. Watch your system, but don't worry to much. regards, Stefan Peer -----Ursprüngliche Nachricht----- Von: Soeren Todt [mailto:sworn@gmx.net] Gesendet: Donnerstag, 31. Mai 2001 15:30 An: suse-security(a)suse.com; Thorsten Marquardt Betreff: Re: [suse-security] Strange apache log entry Hi, ----- Original Message ----- From: "Thorsten Marquardt" <thom(a)kaupp.chemie.uni-oldenburg.de> To: <suse-security(a)suse.com> Sent: Thursday, May 31, 2001 1:45 PM Subject: [suse-security] Strange apache log entry > my logfiles reports 404 requests to /_vti_bin/shtml.exe/_vti_rpc and similar. > > Is this a kind of hacker attack? Maybe you find it out by yourself using a search engine: http://www.google.de/search?q=_vti_bin%2Fshtml.exe%2F_vti_rpc++crack&hl=de&s afe=off then you get results like this: http://www.insecure.org/sploits/Microsoft.frontpage.insecurities.html Ciao Sören --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

4 3

SuSEfirewall doesn't close some ports
by Vadim Kouzmine 01 Jun '01

01 Jun '01

SuSEfirewall 4.3-3 on SuSE 7.1 Zebra 0.91a opens ports for virtual terminals. `netstat -anp` show these ports as (is it IPv6 notation?): ---------- tcp 0 0 :::2604 :::* LISTEN 23643/ospfd tcp 0 0 :::2601 :::* LISTEN 23640/zebra ---------- I guess SuSEfirewall doesn't discover these ports as listening and doesn't close it, although FW_AUTOPROTECT_GLOBAL_SERVICES="yes". Also `SuSEfirewall -check` doesn't show these ports as unprotected. Thank you, Vadim

3 2

forcing use of proxy
by stephane parenton 01 Jun '01

01 Jun '01

Hi, We're using squid 2.2.stable5 as proxy on a SuSE 7.0 box and i would like ALL users to go through the proxy... I know we have some users that play with internet and disable their proxy parameters.... how can I ban "direct internet access" so only proxy connections pass through (whatever is configure on users win stations) ? Regards Stephane

6 6

Problems with kernel modules from cipe
by Guido Tschakert 31 May '01

31 May '01

Hi list, while trying to use cipe with 7.1 I run in the following troubles: The kernel module in the rpm of cipe is build for kernel version 2.4.0 but the 2.4-kernel on the distro is 2.4.0-4GB, so the module cannot be loaded. Next I tried to build cipe from the corresponding spm and hoped the module would be build for 2.4.0-4GB but it was copied to 2.4.0/misc and insmod/modprobe still says: You are using kernel 2.4.0-4GB, this module is for kernel 2.4.0, which is completely different :-( Is it possible just to rename the kernel (and if yes, how to do this exactly) or am I missing something while building cipe from th sources. (I used the command rpm -bi cipe.spec) Trying to use freeS/WAN I run in similar problems (module is for 2.2.18, I used kernel-udpdate 2.2.19). Mostly I want to use cipe with Kernel 2.2.19. BTW. In the last week I posted 2 or 3 other questions about VPN but didn't get much answers. Are my questions too trivial or doesn't nobody on this list uses vpns with linux? Hoping for some hints Guido --- ----------------- Guido Tschakert SRC GmbH, SysAd -----------------

4 6

sonicwall soho 2 passive ftp or active ftp?
by Philipp Snizek 31 May '01

31 May '01

Hi list-users, Does sonicwall soho 2 support passive or active ftp? Anybody got experience with that? thanx Philipp

1 0

Strange apache log entry
by Thorsten Marquardt 31 May '01

31 May '01

Hi, my logfiles reports 404 requests to /_vti_bin/shtml.exe/_vti_rpc and similar. Is this a kind of hacker attack? Thanks Thom -- ------------------------------------------------------------------- bye bye (c) by Thom | Thorsten Marquardt | EMail: THOM(a)kaupp.chemie.uni-oldenburg.de | Member of the pzt project. | http://kaupp.chemie.uni-oldenburg.de/pzt -------------------------------------------------------------------

3 2

[suse-security] Strange apache log entry: Such files are ms frontpage files that exist in ms frontpage webs on
by Bernhard Mueller 31 May '01

31 May '01

> Subject: [suse-security] Strange apache log entry > > Hi, > my logfiles reports 404 requests to /_vti_bin/shtml.exe/_vti_rpc and > similar. > > Is this a kind of hacker attack? > > > Thanks > NO, THIS IS NOT A KIND OF HACKER ATTACK. Just somebody requesting a file that does not exist on your server. Such files are ms frontpage files that exist in ms frontpage webs on frontpage-enabled webservers. Regards Dr. Bernhard Mueller University of Berne

1 0

Re: [suse-security] iptables simple script, but...
by Andreas Bätz 31 May '01

31 May '01

On Tuesday 29 May 2001 15:17, Pupeno wrote: > Yes, I'll use an iptables simple script or not so simple, it doesn't > matter, where should I place it and where should I call you (I'm an RH and > Mdk experienced user an suse it's a bit diferent, and partialy lost, that's > why I'm asking this). There is a file /etc/rc.d/skeleton which can be used as a template for your firewall script. You can copy it to /etc/rc.d/firewall and edit it to let it call your actual firewall script. In the easiest form you just need the "start" command to work to start your firewall when the system goes up and then leave it on forever. Then you can put "SXXfirewall" symlinks into the various runlevels (depends on your SuSE Version, normally 2 + 3 or 3 + 5) which point to your file. I would suggest to place several links, depending on your firewall script: The first one before the network goes up to have protection from the start. (This will eventually produce errors if you refer to certain interfaces in your script but it will set the policies at least) The last call to your firewall script should be made when all interfaces are up. If you have some interfaces that come up later (ppp,ippp) or if some ip-adresses change later (dynamic address while dialing in) you have to call your firewall script again. (e.g. from within /etc/ppp/ip-up). But that depends on your actual script, if it deals with that interfaces at all. Andreas ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been scanned for the presence of computer viruses. **********************************************************************

3 2

FW: SuSE Security Announcement: man (SuSE-SA:2001:019)
by Mike Bethune 31 May '01

31 May '01

Anyone else have problems upgrading to man-2.3.10d69s-194.i386.rpm on my 6.4 system: # rpm -Uvh man-2.3.10d69s-191.i386.rpm man ############unpacking of archive failed on file /usr/bin/man: cpio: chown failed - Bad file descriptor --and now i have no /usr/bin/man, how can i get it back? downgrade? on my 7.0 system: # rpm -Uvh man-2.3.10d69s-194.i386.rpm man ############warning: can't chown /usr/bin/man (Operation not permitted) ###############################warning: can't chown /var/cache/man (Operation not permitted) warning: can't chown /var/cache/man/X11R6 (Operation not permitted) warning: can't chown /var/cache/man/X11R6/cat1 (Operation not permitted) warning: can't chown /var/cache/man/X11R6/cat2 (Operation not permitted) warning: can't chown /var/cache/man/X11R6/cat3 (Operation not permitted) warning: can't chown /var/cache/man/X11R6/cat4 (Operation not permitted) warning: can't chown /var/cache/man/X11R6/cat5 (Operation not permitted) warning: can't chown /var/cache/man/X11R6/cat6 (Operation not permitted) ... etc for every file in /var/cache/man -----Original Message----- From: Roman Drahtmueller [mailto:draht@suse.de] Sent: Tuesday, May 29, 2001 11:53 AM To: bugtraq(a)securityfocus.com Subject: SuSE Security Announcement: man (SuSE-SA:2001:019) -----BEGIN PGP SIGNED MESSAGE----- ____________________________________________________________________________ __ SuSE Security Announcement Package: man Announcement-ID: SuSE-SA:2001:019 Date: Tuesday, May 29th 2001 20:30 MEST Affected SuSE versions: 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 4 SuSE default package: yes Other affected systems: most linux systems shipping the mandb package Content of this advisory: 1) security vulnerability resolved: man problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ____________________________________________________________________________ __ 1) problem description, brief discussion, solution, upgrade information Two vulnerabilities have been found in the man package that is installed by default in all SuSE Linux distributions. The first error is a format string bug in the error handling routine of the man command that can allow a local attacker to gain the privileges of the user "man" on SuSE Linux systems (the man command in /usr/bin is installed setuid man). After getting write access to the /usr/bin/man binary, an attacker can place a cuckook's egg into the executable, waiting for root to view manpages. The second problem is a segmentation fault that can be caused by the options "-S ::: foo" to the man command. On other Linux distributions, this problem has been found exploitable. On SuSE and Debian systems, the code responsible for the bug is different from the one found in other distributions and is not exploitable. We consider the existence of this bug a beauty flaw that will be fixed in future releases of the SuSE Linux distribution, but the fix was not included in the man packages that can be found on our ftp server. Since the error() format string bug was discovered earlier than we announced that the SuSE Linux distributions 6.0, 6.1 and 6.2 will be discontinued, we also provide fixed packages for the said distributions for the i386 Intel architecture. We strongly encourage our usership to upgrade their systems to a newer distribution. Both bugs are fixed in the upcoming release of SuSE Linux 7.2. A temporary workaround (as discussed in earlier SuSE security announcements) is to remove the setuid-bit of the /usr/bin/man file. This will cause errors to be printed when viewing a manpage, because the formatted manpages can't be saved to the /var/cache/man directories any longer. The sideeffects of this workaround are of mostly cosmetical nature on fast hardware. If you changed the file modes of the man command binary using the command chmod 755 /usr/bin/man , then please also change the occurrences of the same path in the files /etc/permissions*, provided you have set the variable CHECK_PERMISSIONS to "set" in /etc/rc.config. Download the update package from locations described below and check the authenticity of the rpm package file using a method as described in section 3) of this security announcement. Use the command `rpm -Uhv file.rpm' to apply the update. In some rare cases, the older man package contains files that conflict with the new version. This should not be considered a problem in this particular case of the man packge; use the options "--nodeps --force" to override. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/man-2.3.10d69s-190.i386.rpm bc914ab44fcdeb2fa809176d2b807bea source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/man-2.3.10d69s-190.src.rpm 96dfa2df00ae4a1045c6d038bd02290b SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/man-2.3.10d69s-194.i386.rpm 533fa405f82ef5bbcfb4b4a6c188d0da source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/man-2.3.10d69s-194.src.rpm b935e02d444a613beccec50db65c1cf7 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/man-2.3.10d69s-191.i386.rpm a7cd2aa52a72f739d7c0cac5073f546b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/man-2.3.10d69s-191.src.rpm e9fd012fbea95c2787de0ee0612da8ce SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/a1/man-2.3.10d69s-191.i386.rpm 807b23473f0813c9c6385d08cc55b698 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/man-2.3.10d69s-191.src.rpm 0ff51500ef8914870cb1785ae3b999b6 SuSE-6.2 ftp://ftp.suse.com/pub/suse/i386/update/6.2/a1/man-2.3.10d69i-19.i386.rpm edbbe4c94b18802dc23a823d55d59761 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.2/zq1/man-2.3.10d69i-19.src.rpm eeeed80772476bb306d256e48ad99f95 SuSE-6.1 ftp://ftp.suse.com/pub/suse/i386/update/6.1/a1/man-2.3.10-85.i386.rpm 775db984e6129f10ede2b091bf725f0d source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.1/zq1/man-2.3.10-85.src.rpm 5c4b93a1cf941adeb853bff9263ca3a5 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/man-2.3.10d69s-182.sparc.rpm 39e097e929dbf4ca7626d5c7dcaf4980 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/man-2.3.10d69s-182.src.rpm df6900385722e5a7ddae18338eb0ef4c SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/man-2.3.10d69s-182.sparc.rpm 6c3bda62c576bd92ff7b741a3124e64e source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/man-2.3.10d69s-182.src.rpm c42b095b229f6b4c45bf7814ae0e1498 AXP Alpha Platform: SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/man-2.3.10d69s-194.alpha.rpm 3d83a75ff11426bc56fd9663bccee9be source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/man-2.3.10d69s-194.src.rpm 2033a16bc31ec5d81136eabf2508fd6d SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/man-2.3.10d69s-191.alpha.rpm f1ee85f46386298748bdb3d76d69e9f2 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/man-2.3.10d69s-191.src.rpm 82792838d464a1fbb14b2c5d79f4d064 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/a1/man-2.3.10d69s-190.alpha.rpm 5334e0f9efe1de48d7905166ced83c1b source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/man-2.3.10d69s-190.src.rpm 43992649e6ab51000bed5ac4e2f8fcae PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/man-2.3.10d69s-162.ppc.rpm 5bff5425484c5076023235b3779f22c6 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/man-2.3.10d69s-162.src.rpm 5caba422258827b139e21f6dab7f9b39 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/man-2.3.10d69s-162.ppc.rpm 832b8078f1c6b2d8d6edae98d26c3d44 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/man-2.3.10d69s-162.src.rpm 4d5647b6276fb6d641410e7eddc106f9 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/man-2.3.10d69s-163.ppc.rpm 13afa53aacaa939fd1b9dd509d995c2d source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/man-2.3.10d69s-163.src.rpm 2ffd94df5356669d89c1490a326c205d ____________________________________________________________________________ __ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - netscape Netscape before Version 4.77 contains a bug that allows a remote attacker to store JavaScript code in the comment filed of GIF files that are contained in a viewed page. This code can be executed. Update packages for the SuSE Linux distributions 6.3, 6.4, 7.0 and 7.1 can be found on our ftp server at ftp://ftp.suse.com/pub/suse/i386/update/7.1/xap1/netscape-4.77-21.i386.rpm 1e2de825b3386d80a3731760b9e7f323 ftp://ftp.suse.com/pub/suse/i386/update/7.0/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.4/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.3/xap1/netscape-4.77-21.i386.rpm 13f303944c9ac0863591b03c4eb75501 The packages are gpg-signed. See the section above about downloading and verifying rpm packages. The complexity of the netscape browser suggests by nature that more security related problems will be found, we will not issue a dedicated security announcement for the netscape package any more. Security- inclined users may please see the future security announcements in section 2) for information about security related problems with the netscape package. - gpg/gnupg The gpg update package that can be found on our ftp server upgrade your installation of gpg to the version 1.0.5. We have experienced stability problems when the turkish locale was used. We recommened our users to wait for the official SuSE Security Announcement about gpg/gnupg before performing the upgrade since we expect more changes to the package. - pine Most of the supported distributions have pine update packages in the update area of the ftp server that update the pine package to version 4.33. Many vulnerabilities have been found in versions before 4.33, and it is recommended to perform the upgrade. Please note that not all packages have been built yet. See the update directory for your distribution (like i386/update/7.0/n1) for pine-4.33 packages. - dqs dex(a)raza-mexicana.org has found an exploitable buffer overflow bug in the dsh program from the dqs package on SuSE Linux distributions. To workaround the problem, do "chmod -s /usr/bin/dsh" and change the files /etc/permissions* to reflect the change. If you do not need the dqs package, then deinstall it (rpm -e dqs). We are working on update packages that fix the problem. - samba Insecure temporary file handling is the cause for a new samba version 2.0.9 that can be found as rpm packages in the n1/ directory of your distribution. It is recommended to install the update package if your users have local shell access to your samba server (this bug is not remotely exploitable). We are currently investigating some oddity in the behaviour of the samba package and will send a security announcement as soon as we have clarified the problems. The problems were present in earlier releases/versions of the samba package as well. By consequence, the installation of the update package is of low risk for the functionality of your system. ____________________________________________________________________________ __ 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 --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =================================================== SuSE's security contact is <security(a)suse.com>. The <security(a)suse.com> public key is listed below. =================================================== Regards, Roman Drahtmueller <draht(a)suse.de>. - - | Roman Drahtmüller <draht(a)suse.de> // "The best way to pay for a | SuSE GmbH - Security Phone: // lovely moment is to enjoy it." | Nürnberg, Germany +49-911-740530 // - Richard Bach | - - ____________________________________________________________________________ __ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org 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 L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA== =rVRn - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOxPuI3ey5gA9JdPZAQFQ6Af/RQcFiRc+py8vrcWHVefHS4QslSfR2TeL XNe0rX/RtrqYUhOWpJyyZgUNi90kr4scohpYlN0xJSrwGrRdWToHPYTUl78iETdJ G24O34XVBuIn4qab31v48yphYlCvrKgc+zXhjZ+JdEAZFnmgOUQ7s2ICu/Xfk2DV gB/YpiVNB6GeQUmEm8wODBinlzNX/XexxO04z24QH2BWwOFPXhUU47KAMeCexnj4 kzcczKx004CQKcHLgsFaBp22mpZDRRaxvoXYWFAuPJuOGlrvJZ1FB4Xy3T3R84bu qO9oSR/CWPjzRoAdI/HbwIQLml2GSO+bynx/OyGYFjMR+lzpBHWGZQ== =Pqq3 -----END PGP SIGNATURE-----

2 1

Re: [suse-security] forcing use of proxy
by Markus Gaugusch 31 May '01

31 May '01

See http://www.squid-cache.org/Doc/FAQ/FAQ-17.html#ss17.3 > We're using squid 2.2.stable5 as proxy on a SuSE 7.0 box and i would like ALL users to go through the proxy... I know we have some users that play with internet and disable their proxy parameters.... how can I ban "direct internet access" so only proxy > connections pass through (whatever is configure on users win stations) ? -- _____________________________ /"\ Markus Gaugusch ICQ 11374583 \ / ASCII Ribbon Campaign markus(a)gaugusch.dhs.org X Against HTML Mail / \

1 0

AW: [suse-security] forcing use of proxy
by Hirsch Wolfgang 31 May '01

31 May '01

I'd disable port 80 at the box and on client side you have to insert the port of squid (normally 3128). Regards wolfgang > -----Ursprüngliche Nachricht----- > Von: stephane parenton [mailto:sparenton@experia.com] > Gesendet: Donnerstag, 31. Mai 2001 11:56 > An: SuSE secure > Betreff: [suse-security] forcing use of proxy > > > Hi, > > We're using squid 2.2.stable5 as proxy on a SuSE 7.0 box and > i would like ALL users to go through the proxy... I know we > have some users that play with internet and disable their > proxy parameters.... how can I ban "direct internet access" > so only proxy > connections pass through (whatever is configure on users win > stations) ? > > Regards > Stephane > > --------------------------------------------------------------------- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com >

1 0

nice ssh-problem...
by Daniel Quappe 31 May '01

31 May '01

hi list, today i've got a problem while testing a system for rsyncing two systems via ssh. the external ssh-server normally wants to get request with a privileged port (eg. 1023). but i want to connect via my internal server which is masq. by my gateway/firewall. after this masq. the privileged request transforms into an un- privileged one...;-( are there any ideas somewhere out there...;-)?? many thanks in advance, bye daniel -- Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1! http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

3 2

OT: OpenSSL Rant :/
by Bill Jones 31 May '01

31 May '01

Probably off-topic, but I need to rant anyways: I do not see where nor any How-To on the procedure for installing my own self-signed certificate. I even did a new tarball d/l from OpenSSL's site itself: OpenSSL 0.9.6a 5 Apr 2001 built on: Mon May 28 00:19:23 EDT 2001 platform: linux-sparcv9 options: bn(64,32) md2(int) rc4(ptr,char) des(idx,cisc,16,long) idea(int) blowfish(ptr) compiler: gcc -DTHREADS -D_REENTRANT -mcpu=ultrasparc -DB_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall -Wa,-Av8plus -DULTRASPARC -DBN_DIV2W -DMD5_ASM It was successful, as was: /usr/ssl/misc/CA.pl -newca /usr/ssl/misc/CA.pl -newreq /usr/ssl/misc/CA.pl -signreq /usr/ssl/misc/CA.pl -pkcs12 "InSecurity.Org" I suppose my real issue is I wish I knew what I was doing more than just the 'trial and error' development approach... Thx for listening; -Sneex- :] ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

7 14

Fw: [suse-security] SuSEFirewall fails on system startup
by Suse_Mail_List 30 May '01

30 May '01

----- Original Message ----- From: al To: suse-security(a)suse.com Sent: Wednesday, May 30, 2001 4:35 PM Subject: Re: [suse-security] SuSEFirewall fails on system startup I am NEW to SuSE 7.1 and Linux in general, and have since become an avid user (also due to getting my system wacked by someone, which has prompted me to solidify my security) ... :) So alas I am here. In short I can not get my fore wall to start. I am using STATIC IP addresses so the follow up to this thread { [suse-security] SuSEfirewall does not start Stephan Dankers (Thu Apr 05 2001 - 11:48:58 CDT) a.. Re: [suse-security] SuSEfirewall does not start marsaro(a)interearth.com (Thu Apr 05 2001 - 14:13:33 CDT) } has not helped... below is an excerpt from my bootlog.... Starting Firewall Init........ No interfaces active! exiting ... SuSEfirewall: clearing rules now ... done failed Initializing random number generator done Setting up network device eth0 done Setting up network device eth1 done Setting up routing (using /etc/route.conf) done Starting Firewall Initialization: (phase 2 of 3) ............. ......... .... Starting inetd done Starting Firewall Initialization: (phase 3 of 3) Master Resource Control: runlevel 3 has been reached Failed services in runlevel 3: SuSEfirewall_init SuSEfirewall_setup SuSEfirewall_final Any input as always would be greatly appreciated, and also any security tips on the subject of TRIPWIRE (implementing soon), and an SSH-telnet and FTP client for 2K,NT and ME would be neat :) Thanks Aaron

1 0

bandwidth management
by michael.ryan＠storm.ie 30 May '01

30 May '01

Hi all, A little off-topic but can anyone recommend a bandwidth management tool for SuSE 6.4 ... (I'd like to restrict bandwidth usage for certain machines on our internal net) Thanks in advance, Michael

3 2

SuSE Security Announcement: man (SuSE-SA:2001:019)
by Roman Drahtmueller 30 May '01

30 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: man Announcement-ID: SuSE-SA:2001:019 Date: Tuesday, May 29th 2001 20:30 MEST Affected SuSE versions: 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 4 SuSE default package: yes Other affected systems: most linux systems shipping the mandb package Content of this advisory: 1) security vulnerability resolved: man problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Two vulnerabilities have been found in the man package that is installed by default in all SuSE Linux distributions. The first error is a format string bug in the error handling routine of the man command that can allow a local attacker to gain the privileges of the user "man" on SuSE Linux systems (the man command in /usr/bin is installed setuid man). After getting write access to the /usr/bin/man binary, an attacker can place a cuckook's egg into the executable, waiting for root to view manpages. The second problem is a segmentation fault that can be caused by the options "-S ::: foo" to the man command. On other Linux distributions, this problem has been found exploitable. On SuSE and Debian systems, the code responsible for the bug is different from the one found in other distributions and is not exploitable. We consider the existence of this bug a beauty flaw that will be fixed in future releases of the SuSE Linux distribution, but the fix was not included in the man packages that can be found on our ftp server. Since the error() format string bug was discovered earlier than we announced that the SuSE Linux distributions 6.0, 6.1 and 6.2 will be discontinued, we also provide fixed packages for the said distributions for the i386 Intel architecture. We strongly encourage our usership to upgrade their systems to a newer distribution. Both bugs are fixed in the upcoming release of SuSE Linux 7.2. A temporary workaround (as discussed in earlier SuSE security announcements) is to remove the setuid-bit of the /usr/bin/man file. This will cause errors to be printed when viewing a manpage, because the formatted manpages can't be saved to the /var/cache/man directories any longer. The sideeffects of this workaround are of mostly cosmetical nature on fast hardware. If you changed the file modes of the man command binary using the command chmod 755 /usr/bin/man , then please also change the occurrences of the same path in the files /etc/permissions*, provided you have set the variable CHECK_PERMISSIONS to "set" in /etc/rc.config. Download the update package from locations described below and check the authenticity of the rpm package file using a method as described in section 3) of this security announcement. Use the command `rpm -Uhv file.rpm' to apply the update. In some rare cases, the older man package contains files that conflict with the new version. This should not be considered a problem in this particular case of the man packge; use the options "--nodeps --force" to override. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/man-2.3.10d69s-190.i386.rpm bc914ab44fcdeb2fa809176d2b807bea source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/man-2.3.10d69s-190.src.rpm 96dfa2df00ae4a1045c6d038bd02290b SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/man-2.3.10d69s-194.i386.rpm 533fa405f82ef5bbcfb4b4a6c188d0da source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/man-2.3.10d69s-194.src.rpm b935e02d444a613beccec50db65c1cf7 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/man-2.3.10d69s-191.i386.rpm a7cd2aa52a72f739d7c0cac5073f546b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/man-2.3.10d69s-191.src.rpm e9fd012fbea95c2787de0ee0612da8ce SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/a1/man-2.3.10d69s-191.i386.rpm 807b23473f0813c9c6385d08cc55b698 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/man-2.3.10d69s-191.src.rpm 0ff51500ef8914870cb1785ae3b999b6 SuSE-6.2 ftp://ftp.suse.com/pub/suse/i386/update/6.2/a1/man-2.3.10d69i-19.i386.rpm edbbe4c94b18802dc23a823d55d59761 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.2/zq1/man-2.3.10d69i-19.src.rpm eeeed80772476bb306d256e48ad99f95 SuSE-6.1 ftp://ftp.suse.com/pub/suse/i386/update/6.1/a1/man-2.3.10-85.i386.rpm 775db984e6129f10ede2b091bf725f0d source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.1/zq1/man-2.3.10-85.src.rpm 5c4b93a1cf941adeb853bff9263ca3a5 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/man-2.3.10d69s-182.sparc.rpm 39e097e929dbf4ca7626d5c7dcaf4980 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/man-2.3.10d69s-182.src.rpm df6900385722e5a7ddae18338eb0ef4c SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/man-2.3.10d69s-182.sparc.rpm 6c3bda62c576bd92ff7b741a3124e64e source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/man-2.3.10d69s-182.src.rpm c42b095b229f6b4c45bf7814ae0e1498 AXP Alpha Platform: SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/man-2.3.10d69s-194.alpha.rpm 3d83a75ff11426bc56fd9663bccee9be source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/man-2.3.10d69s-194.src.rpm 2033a16bc31ec5d81136eabf2508fd6d SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/man-2.3.10d69s-191.alpha.rpm f1ee85f46386298748bdb3d76d69e9f2 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/man-2.3.10d69s-191.src.rpm 82792838d464a1fbb14b2c5d79f4d064 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/a1/man-2.3.10d69s-190.alpha.rpm 5334e0f9efe1de48d7905166ced83c1b source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/man-2.3.10d69s-190.src.rpm 43992649e6ab51000bed5ac4e2f8fcae PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/man-2.3.10d69s-162.ppc.rpm 5bff5425484c5076023235b3779f22c6 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/man-2.3.10d69s-162.src.rpm 5caba422258827b139e21f6dab7f9b39 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/man-2.3.10d69s-162.ppc.rpm 832b8078f1c6b2d8d6edae98d26c3d44 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/man-2.3.10d69s-162.src.rpm 4d5647b6276fb6d641410e7eddc106f9 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/man-2.3.10d69s-163.ppc.rpm 13afa53aacaa939fd1b9dd509d995c2d source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/man-2.3.10d69s-163.src.rpm 2ffd94df5356669d89c1490a326c205d ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - netscape Netscape before Version 4.77 contains a bug that allows a remote attacker to store JavaScript code in the comment filed of GIF files that are contained in a viewed page. This code can be executed. Update packages for the SuSE Linux distributions 6.3, 6.4, 7.0 and 7.1 can be found on our ftp server at ftp://ftp.suse.com/pub/suse/i386/update/7.1/xap1/netscape-4.77-21.i386.rpm 1e2de825b3386d80a3731760b9e7f323 ftp://ftp.suse.com/pub/suse/i386/update/7.0/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.4/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.3/xap1/netscape-4.77-21.i386.rpm 13f303944c9ac0863591b03c4eb75501 The packages are gpg-signed. See the section above about downloading and verifying rpm packages. The complexity of the netscape browser suggests by nature that more security related problems will be found, we will not issue a dedicated security announcement for the netscape package any more. Security- inclined users may please see the future security announcements in section 2) for information about security related problems with the netscape package. - gpg/gnupg The gpg update package that can be found on our ftp server upgrade your installation of gpg to the version 1.0.5. We have experienced stability problems when the turkish locale was used. We recommened our users to wait for the official SuSE Security Announcement about gpg/gnupg before performing the upgrade since we expect more changes to the package. - pine Most of the supported distributions have pine update packages in the update area of the ftp server that update the pine package to version 4.33. Many vulnerabilities have been found in versions before 4.33, and it is recommended to perform the upgrade. Please note that not all packages have been built yet. See the update directory for your distribution (like i386/update/7.0/n1) for pine-4.33 packages. - dqs dex(a)raza-mexicana.org has found an exploitable buffer overflow bug in the dsh program from the dqs package on SuSE Linux distributions. To workaround the problem, do "chmod -s /usr/bin/dsh" and change the files /etc/permissions* to reflect the change. If you do not need the dqs package, then deinstall it (rpm -e dqs). We are working on update packages that fix the problem. - samba Insecure temporary file handling is the cause for a new samba version 2.0.9 that can be found as rpm packages in the n1/ directory of your distribution. It is recommended to install the update package if your users have local shell access to your samba server (this bug is not remotely exploitable). We are currently investigating some oddity in the behaviour of the samba package and will send a security announcement as soon as we have clarified the problems. The problems were present in earlier releases/versions of the samba package as well. By consequence, the installation of the update package is of low risk for the functionality of your system. ______________________________________________________________________________ 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 --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =================================================== SuSE's security contact is <security(a)suse.com>. The <security(a)suse.com> public key is listed below. =================================================== Regards, Roman Drahtmueller <draht(a)suse.de>. - - | Roman Drahtmüller <draht(a)suse.de> // "The best way to pay for a | SuSE GmbH - Security Phone: // lovely moment is to enjoy it." | Nürnberg, Germany +49-911-740530 // - Richard Bach | - - ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org 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 L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA== =rVRn - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOxPuI3ey5gA9JdPZAQFQ6Af/RQcFiRc+py8vrcWHVefHS4QslSfR2TeL XNe0rX/RtrqYUhOWpJyyZgUNi90kr4scohpYlN0xJSrwGrRdWToHPYTUl78iETdJ G24O34XVBuIn4qab31v48yphYlCvrKgc+zXhjZ+JdEAZFnmgOUQ7s2ICu/Xfk2DV gB/YpiVNB6GeQUmEm8wODBinlzNX/XexxO04z24QH2BWwOFPXhUU47KAMeCexnj4 kzcczKx004CQKcHLgsFaBp22mpZDRRaxvoXYWFAuPJuOGlrvJZ1FB4Xy3T3R84bu qO9oSR/CWPjzRoAdI/HbwIQLml2GSO+bynx/OyGYFjMR+lzpBHWGZQ== =Pqq3 -----END PGP SIGNATURE-----

1 1

freeSwan with kernel 2.2.19
by Guido Tschakert 30 May '01

30 May '01

Hello list, I want to use FreeS/WAN 1.8 with SuSE7.1. The problem is, that I have updated the Kernel to 2.2.19 and the IPSEC-Module is compiled for Kernel 2.2.18.(insmod does not load the module). Is there an easy solution to use this module with the 2.2.19-Kernel or do I have to compile this module. (And how can I do it in a simple way without compiling all modules or the whole FreeS/WAN-packet) TIA Guido I -- ----------------- Guido Tschakert SRC GmbH, SysAd -----------------

1 0

(offtopic) "Should-be Dead" shell sessions still alive
by RoMaN SoFt / LLFB!! 30 May '01

30 May '01

Sorry for writing to this ml, but I didn't want to subscribe the other Suse ml only for asking this Q. In my SuSE 6.4 boxes when a shell session is broken (the user doesn't issue the normal "logout" command but disconnect telnet/ssh, for example) the bash login process keeps alive forever. I think this doesn't happen on 7.0-*. Do I have to update some package or change any configuration line at /etc/*? Example: game1:/usr/local/apache/conf # who davnav pts/2 Apr 3 17:26 (192.168.0.233) parker pts/3 Apr 6 12:07 (192.168.0.68) parker pts/5 Apr 6 12:34 (192.168.0.68) parker pts/6 Apr 17 10:57 (192.168.0.69) parker pts/7 Apr 17 13:58 (192.168.0.69) parker pts/10 Apr 26 13:34 (juan.herreraii) parker pts/12 May 8 10:23 (juan.herreraii) parker pts/13 May 9 09:54 (juan.herreraii) parker pts/14 May 10 08:12 (juan.herreraii) roman pts/15 May 9 14:53 (roman) roman pts/16 May 10 09:24 (roman) game1:/usr/local/apache/conf # \ps aux | grep parker parker 32722 0.0 0.2 2248 1324 pts/3 S Apr06 0:00 -bash parker 304 0.0 0.2 2248 1312 pts/5 S Apr06 0:00 -bash parker 23811 0.0 0.2 2252 1316 pts/6 S Apr17 0:00 -bash parker 24161 0.0 0.2 2252 1316 pts/7 S Apr17 0:00 -bash parker 15142 0.0 0.2 2256 1320 pts/10 S Apr26 0:00 -bash parker 9671 0.0 0.2 2256 1320 pts/12 S May08 0:00 -bash parker 11943 0.0 0.2 2256 1320 pts/13 S May09 0:00 -bash parker 20885 0.0 0.2 2256 1320 pts/14 S 08:12 0:00 -bash parker 21117 0.0 0.2 1992 1296 ? S 09:55 0:00 proftpd: parker - juan.herreraII: IDLE root 21121 0.0 0.0 1136 444 pts/16 S 09:56 0:00 grep parker game1:/usr/local/apache/conf # cat /etc/SuSE-release SuSE Linux 6.4 (i386) VERSION = 6.4 game1:/usr/local/apache/conf # Thanks in advance ;) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** RoMaN SoFt / LLFB ** roman(a)madrid.com http://pagina.de/romansoft ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 1

Problems compiling freeswan 1.4
by audun.fosselie.hansen＠satcom.nera.no 30 May '01

30 May '01

Audun-Fosselie Hansen/NOSAT/NERA 2001-05-29 14:09 To: suse-security(a)suse.com cc: Subject: Problems compiling freeswan 1.4 I know version 1.4 is old, but it is for testing and not for use in the real world. I have installed the freeswan source file from Suse 7.0 and are running rpm -bc SPECS/freeswan.specs. The compiling ends with the following messages: + test -e /usr/src/linux/.config + grep CONFIG_IPSEC /usr/src/linux/.config CONFIG_IPSEC=m + yes '' + make -C /usr/src/linux oldconfig make: Entering directory `/usr/src/linux-2.2.16' make: *** No rule to make target `oldconfig'. Stop. make: Leaving directory `/usr/src/linux-2.2.16' Bad exit status from /var/tmp/rpm-tmp.96871 (%prep) Anyone who can tell me what to do?? I am not too experienced in this kind of problems. Audun Hansen

2 1

problems with my mylex card
by Magus Ba'al 30 May '01

30 May '01

I'm running into a problem with my Mylex 1100 scsi raid controller. I have SuSE 7.0 Pro installed. The problem I ran into earlier today was an error running modprobe. It would spit back an error: modprobe DAC960 modprobe: line 5: Invalid dependency /* For struct iovec */ This happened for all modules during boot, which was a giant pain to manually load the driver using insmod, then restart some services. I found a workaround: insmod DAC960 Using /lib/modules/2.2.16/block/DAC960.o But I couldn't use the mylex card, all other cards seemed to work just fine. The mylex card worked fine until I rebooted. I fixed this problem by upgrading to the 2.2.19 kernel, with all the updates needed to upgrade the kernel (libc, libd, nssv1, shlibs) and now I don't have any problems running modprobe. What I'm running into now is I can't get the system to mount the arrays. modprobe DAC960 mount /dev/rd/c0d0p1 /blah mount: /dev/rd/c0d0p1 is not a valid block device lsmod Module Size Used by DAC960 58372 0 (unused) nfsd 182888 4 (autoclean) autofs 9644 2 (autoclean) eepro100 17432 1 (autoclean) memstat 1540 0 (unused) serial 42804 0 (autoclean) aic7xxx 105024 0 (unused) I've already rebooted, cold boot, even reseated the card for giggles. The card's bios info shows during boot, so the card didn't just magically die at the same time (I hope...). The only thing I can think of is I do have a problematic drive (being replaced soon) that will sometimes not respond. But it shouldn't take down the entire card (i think...). Other than that, nothing has been changed on the box. Any thoughts, ideas, suggestions, pointers, etc. would be greatly appreciated. TIA Steve "I am the Illustrious Postmaster and Grand Poobah of Electronic Transmissions" -Unknown

2 1

Sendmail (SASL)
by Sp0oKeR 29 May '01

29 May '01

I'm trying to do auth in my sendmail with SASL. I try to do my sendmail.cf file, but it's no so right. Always that I start mey sendmail, I get this message. Warning: Option: AuthMechanisms requires SASL support (-DSASL) Warning: Option: DefaultAuthInfo requires SASL support (-DSASL) I tried to add some lines in mu spooker.mc, but I didn't give success. Can somebody help? Does anyone know another solution? Regards ... -- #=============================# # Rodrigo Ribeiro Montoro # # Network Services Center # # rodrigo(a)nscenter.com.br # # http://www.nscenter.com.br # # Sao Paulo - SP # #=============================#

2 1

Antwort: [suse-security] iptables-save, iptables-restore
by Stefan_Walther＠gehag-dsk.de 29 May '01

29 May '01

you can write your own restore-scripts by using any text-editor. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: +4930/89786448 Funk: +49172/3943961

1 0

Antwort: [suse-security] iptables simple script, but...
by Stefan_Walther＠gehag-dsk.de 29 May '01

29 May '01

Hi Pupeno, since SuSE7.1 the directory structure is nearly the same like RH or Mandrake. You can add the file to /etc/rc.d/ and link it to the different runlevels (if you want to start it as deamon). On the other hand you can put it to /root and run it as root wheneveryou want. for disabling any rules flushing the rules and set them to ACCEPT. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: +4930/89786448 Funk: +49172/3943961

1 0

iptables-save, iptables-restore
by Pupeno 29 May '01

29 May '01

Are this programs on SuSE ? In Mandrake a RedHat, they came with iptables, and the starting script is build around them. -- Pupeno: pupeno(a)pupeno.com.ar http://www.pupeno.com.ar

1 0

iptables simple script, but...
by Pupeno 29 May '01

29 May '01

Yes, I'll use an iptables simple script or not so simple, it doesn't matter, where should I place it and where should I call you (I'm an RH and Mdk experienced user an suse it's a bit diferent, and partialy lost, that's why I'm asking this). -- Pupeno: pupeno(a)pupeno.com.ar http://www.pupeno.com.ar

1 0

Openssh + PAM
by José Luis Ledesma 29 May '01

29 May '01

I wanna use pam with openssh using ssh2... openssh version is 2.5.1p1 (Suse 7.1) and pam works when I use ssh1 client, but it does not work using ssh2 as client... Thankyou José Luis Ledesma Technology Dep. _____________________ COMPETITIVENESS Parque Tecnológico del Vallés 08290 Barcelona - Spain http://www.competitiveness.com Tel.: +34 66 986 55 17 Fax: +34 93 582 01 59

1 0

ipx and apache (maybe OT, maybe hole)
by Christian Lox 29 May '01

29 May '01

Hi everyone! Maybe this one is off topic but I am not sure... We have a SuSE box acting as a webserver. Now I noticed during one of our regular nmaps that ipx ports is open. But: gw:/usr/src/linux # grep IPX .config # CONFIG_IPX is not set The other day I noticed somehting like rpc-sometime or similar. I immediately did stop all not 100% necessary processes and this one did vanish. Maybe this belongs to our tests with Sybase?! Any hint appreciated, Christian

3 3

suspicious named-udp-port?
by Daniel Quappe 29 May '01

29 May '01

hi list, today i found an open unprivileged udp-port on my server listening on 0.0.0.0 which i detected to be related to my named-server 8.2.3-REL (update done...;-) if i shut down the named and restart it another (possibly random) high udp-port is used in addition to the privileged udp-port 53 listening on my "real" interfaces. is this something to worry about?! a nervous list-reader...;-) daniel -- Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1! http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

2 1

application fw or ipchains based ones
by kaldewey 29 May '01

29 May '01

Hallo , I have used ipchains in Suse 7.0 to protect my network but now I want to protect our intranet server safer -more features and more confortable . I read about TIS ,Sinus ,seattle firewall ,firestarter ..... Can someone offert on ? Thanx Frank

2 1

SuSEfirewall and Kernel 2.4.0
by Benjamin Grogg 29 May '01

29 May '01

Hi folks I read that SuSEfirewall on SuSE 7.1 (Kernel 2.4.0 (Standard)) is not supported? Is there any script who supported iptables? Or I have to recompile the 2.4.0 Kernel with ipchains support? Thanks Benny

3 2

IP-alias
by Jussi Jääskeläinen 29 May '01

29 May '01

Hi! I'm not sure is this right area for next question but.. I have defined: ifconfig eth0 10.113.1.211 # main address ifconfig eth0:0 10.113.1.210 #alias address so normaly all outgoing trafic have that .211 as source address. Question is.. Is it possible (when it is needed) to open connection to outside so that source address is .210 (alias-address)... Without changing eth0 address.. -- Jussi Jääskeläinen Email: jussi.jaaskelainen(a)audioriders.fi Audio Riders Oy Tel: +358-9-276 6820 direct: +358-9-276 68212 Järvihaantie 4 Mobile: +358-40-554 3689 FIN-01800 KLAUKKALA Fax: +358-9-879 8045 FINLAND WWW: http://www.audioriders.fi

1 0

Antwort: RE: [suse-security] Antwort: [suse-security] configuring firewalls with iptables
by Stefan_Walther＠gehag-dsk.de 29 May '01

29 May '01

Hi Matt, hi Pupeno I haven't disabled SuSEfirewall. I haven't installed it. I tried it a long time ago, but it doesn't work at my dsl-router. As I had to reinstall the Distribution (I switch from ISDN-dialup to DSL), I let SuSEfirewall untouched as rpm on the cd's. First I used IPCHAINS because ISDN doesn't want to work with kernel 2.4.x. As I get DSL I switch from IPCHAINS to IPTABLES. First I had to reconfigure the firewall at my firm, then at home. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: +4930/89786448 Funk: +49172/3943961

1 0

PHP, mod_perl, Apache ???
by Bill Jones 29 May '01

29 May '01

Btw: I do not know who the original poster was, but this was recently seen during my studies concerning using both OpenSSL and Apache (SSL/443) on a SuSE 7.1 Ultrasparc (2.4.2) server: http://www.faqts.com/knowledge_base/view.phtml/aid/8223/fid/30 Please forward to original poster if anyone here remembers who. HTH; -Sneex- :] Please see: http://cis4dl.sourceforge.net/ and/or http://sourceforge.net/docman/display_doc.php?docid=4818&group _id=26707 ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

1 0

Fwd: RE: [suse-security] Orginal firewall.rc.config file ?
by Faessen-Goden Jean-Paul en Rowena 29 May '01

29 May '01

---------- Forwarded Message ---------- Subject: RE: [suse-security] Orginal firewall.rc.config file ? Date: Sun, 27 May 2001 11:35:06 +0100 From: "Matt" <matt(a)import-it.co.uk> Coul I use http://www.linux-firewall-tools.com/cgi-bin/firewall.cgi Would the config there be ok and does SuSE work on the same process ? Regards Matt -----Original Message----- From: Matt [mailto:matt@import-it.co.uk] Sent: 27 May 2001 10:30 To: suse-security(a)suse.com Subject: [suse-security] Orginal firewall.rc.config file ? Hi, Now that I am having all these problems with firewalls etc and maybe messed up my orginal firewall.rc.config file does any one have an orginal one that I could use as a template please ? Regards Matt -----Original Message----- From: Matt [mailto:matt@import-it.co.uk] Sent: 27 May 2001 02:34 To: suse-security(a)suse.com Subject: [suse-security] SuSEfirewall configuration help SuSEfirewall config... Please could someone send me an example of one with the following settings enabled please.. I use SAMBA, telnet, rlogin, ftp and vnc, ping, traceroute on 3 my machines 192.168.0.2 (SuSE 7.0, 192.168.0.3 (SuSE 6.4) and use my win2000 box to work on (192.168.0.1). these are all on eth0 with win2000 used to dialup on. I would like to set up 192.168.0.2 as my gateway/router but at the moment I have configured my win2000 box. However whilst setting up SuSEfirewall my system hung on the firewall first run initialisation. I can neither login or do anything on reboot. I could login in single user mode but I don't know how to do that ant directions ? Regards Matt --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com ------------------------------------------------------- Matt; Never change your system without taking note of what you did. Look into the SuSE Handbook,provided with SuSE professional. The standard configuration is there. Jean-Paul Faessen

1 0

Re: [Re: [suse-security] [Re: Auth]]
by Bill Jones 29 May '01

29 May '01

Hmmm... Don't know about AUTH, but I know that the file /etc/mail/relay-domains should be empty and the file /etc/mail/access should say something like: # Examples: # #cyberspammer.com ERROR:"550 We don't accept mail from spammers" #sendmail.org OK #192.168 RELAY # # Extensions: # # See /usr/share/sendmail/README for the FEATURE `blacklist_recipients'. # # Default for loop back is RELAY 127 RELAY What does your's say??? -Sneex- :] Sp0oKeR <spooker(a)bol.com.br> wrote: > Many times a day, people are using my mail server to do > spam. With auth e intend to stop this. ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

1 0

Auth
by Sp0oKeR 29 May '01

29 May '01

I'm doing problems with spam in my mail server. I'm using sendmail. Trying to resolve this problem, I will try sendmail auth. Does anybody can help? What program i need to use? Regards .... -- #=============================# # Rodrigo Ribeiro Montoro # # Network Services Center # # rodrigo(a)nscenter.com.br # # http://www.nscenter.com.br # # Sao Paulo - SP # #=============================#

1 0

[Re: Auth]
by Bill Jones 29 May '01

29 May '01

Sp0oKeR <spooker(a)bol.com.br> wrote: > I'm doing problems with spam in my mail server. I'm using sendmail. > Trying to resolve this problem, I will try sendmail auth. Does > anybody can help? What program i need to use? > > Regards .... Spam? Do you mean relaying or final delivery? ??? -Sneex- :] ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

1 0

Newbies, Lists, and helping ( Was: OT ... Rant :/ )
by Bill Jones 29 May '01

29 May '01

In Cyberspace, two entities spake - > The SuSE mailing list is by far the best I've found. I have > not experienced any real derogatory remarks or comments > from the Linux vets. As for the "what the experience user > won't see", I understand this also. > > Help yourself and others by contributing and not just consuming! I agree, and I apologize for the OT rant earlier. I myself should know better as I am IT professional with 22 yrs experience. I even teach Internet related technologies at a local community college and I am always warning my students about how they should spent more time trying to find the answers themselves BEFORE posting what may amount to FAQs to any list... However, as hard as it may be to believe even I am human and sometimes even I find that I just want it to work :) I guess 22 yrs hasn't turned me into a machine yet, Thank GOD! Best; -Sneex- :] ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

1 0

self compiled kernel 2.2.19 problems
by Frederik Ferner 28 May '01

28 May '01

Hi All, some time ago I downloaded lx_sus22-2.2.19.SuSE-25.i386.rpm and tried to install it to compile it myself. Everything work fine except that the kernel sometimes freezes my computer completely, ie I have to reset it. There is nothing in the lockfiles, but then it might not be written to the disc :-( This happens on my SuSE 6.3 with all security related updates. I tried to run a precompiled kernel from SuSE (k_i386-2.2.19-12.i386.rpm) and didn't have any problems there so far. But I don't want all the stuff that is in there (like raid, lvm...). I'd really like to have my kernel as small as possible for the machine sitting directly on the web. Any hints how I could get around this problem? Sysrq doesn't seem to work on my computer. At least I haven't managed to get any results with sysrq. Bye, Frederik

2 1

RE: [suse-security] Samba with iptables
by Stefan_Walther＠gehag-dsk.de 28 May '01

28 May '01

samba is using netbios. you have to open the ports from 137 to 139. if you have a dns server in your local lan, you should open port 53 too. because you can find and access the samba-server much faster than without using a nameserver. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: 030/89786448 Funk: 0172/3943961

1 0

Samba with iptables
by zonionz＠gmx.net 28 May '01

28 May '01

Hi I´ve got a server with Suse 7.1 and kernel 2.42, samba and iptables and some client machines with win95. Now I want to make rules for iptables to allow a local connection between the clients and the server using Samba, I think Samba uses Port 137,138 and 53 (default police is drop) Has anybody a working filtering rule for that? Thanks! Sylvain -- Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1! http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

1 0

New security articel on SuSE Knowledge Portal
by Thomas Biege 28 May '01

28 May '01

Hi ppl, just a short note: The first part of my paper about security bugs in source code was released on SuSE's Knowledge Portal. english: http://portal.suse.de/en/content.php?3occccccccccccccccccccmccccccccccocccc… german: http://portal.suse.de/de/content.php?3occccccccccccccccccccmccccccccccocccc… The original paper with all it's typos and in german language can be found on http://www.suse.de/~thomas/papers/index.html I hope you all enjoy reading it. ;-) I would be happy if you report mistakes/errors/typos I made. And again, thanks to the portal team. :-) Bye, Thomas -- Thomas Biege, SuSE GmbH, Schanzaeckerstr. 10, 90443 Nuernberg E@mail: thomas(a)suse.de Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/thomas.pgp | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 84

2 2

iptable and pop3, long response time
by Henri Valeins 28 May '01

28 May '01

Hi, I use iptable with a kernel 2.4.2 with this rules for pop3 and DNS # ---------------------------------------------------------------------------- # DNS client (53) # --------------- iptables -A INPUT -p udp \ -s $NAMESERVER_1 --sport 53 \ -d $IPADDR --dport $UNPRIVPORTS -j ACCEPT iptables -A OUTPUT -p udp \ -s $IPADDR --sport $UNPRIVPORTS \ -d $NAMESERVER_1 --dport 53 -j ACCEPT iptables -A INPUT -p tcp ! --syn \ -s $NAMESERVER_1 --sport 53 \ -d $IPADDR --dport $UNPRIVPORTS -j ACCEPT iptables -A OUTPUT -p tcp \ -s $IPADDR --sport $UNPRIVPORTS \ -d $NAMESERVER_1 --dport 53 -j ACCEPT # ------------------------------------------------------------------ # POP server (110) # Acces pour : # ---------------- iptables -A INPUT -p tcp \ -s $popclient --sport $UNPRIVPORTS \ -d $IPADDR --dport 110 -j ACCEPT iptables -A OUTPUT -p tcp ! --syn \ -s $IPADDR --sport 110 \ -d $popclient --dport $UNPRIVPORTS -j ACCEPT with $IPADDR = ip adress for localhost $popclient = ip adresse for the pop client $UNPRIVPORTS="1024:65535" $NAMESERVER_1 = ip adress dor the name server -****************************************************************- with this rules I have 10 seconds for the response time, without iptables it's immediatly. WHat is wrong ? -- Henri Valeins Résonance Magnétique des Systèmes Biologiques UMR 5536 CNRS/Université Victor Segalen Bordeaux 2 146 rue Léo-Saignat (case 93) 33076 BORDEAUX cedex tel 33 (0)5 57 57 17 85 fax 33 (0)5 57 57 45 56

2 1

IP Routing based on fwmark
by Mark O. Stitson 28 May '01

28 May '01

Hi there, I have just set up my 2.4 kernel here on our router and I am trying to allocate different services to our two internet connections. I want all of our smtp traffic to go via our normal leased line and all other traffic to go via our faster, but less reliable ADSL line. I have set the default route to go via the ADSL line and added a ip routing table for the mail: popper:~ # ip route list 213.210.21.240/29 dev eth2 proto kernel scope link src 213.210.21.242 213.38.116.168/29 dev eth1 proto kernel scope link src 213.38.116.170 10.0.0.0/16 dev eth0 proto kernel scope link src 10.0.0.2 127.0.0.0/8 dev lo scope link default via 213.210.21.241 dev eth2 popper:~ # ip route list table mail.out default via 213.38.116.170 dev eth1 Then I have set up ip rules: popper:~ # ip rule list 0: from all lookup local ... 32761: from all fwmark 3 lookup mail.out ... 32766: from all lookup main 32767: from all lookup default Then I have added a mangling rule: popper:~ # iptables -A PREROUTING -t mangle -p tcp --dport 25 -j MARK --set-mark 3 All the traffic from the internal network happily obeys the rules and goes via the leased line, but any traffic originating from the router itself on port 25 just goes via the ADSL line and seems not to get marked. Is there a way to implement policy based routing for the router as well? Mark ---------------------------------------------------------------- Dr Mark O. Stitson, Senior Systems Administrator Yospace Ltd, 7 The Courtyard, High Street, Staines, UK, TW18 4DP Tel: +44 1784 466388 Fax: +44 1784 466387 WWW: http://www.yospace.com

1 0

OpenSSH on SuSE 6.3 --> 'PAM adding faulty module: /lib/security/pam_pwcheck.so'
by Alex Liesch 28 May '01

28 May '01

Hi! I've updated one of my older linux servers running SuSE 6.3 to openssh (2.3.0p1) from "the" ssh. Now I have the following entries in messages each time a user logs in: May 27 16:47:25 r100 sshd[16621]: PAM unable to dlopen(/lib/security/pam_pwcheck.so) May 27 16:47:25 r100 sshd[16621]: PAM [dlerror: /lib/security/pam_pwcheck.so: cannot open shared object file: No such file or directory] May 27 16:47:25 r100 sshd[16621]: PAM adding faulty module: /lib/security/pam_pwcheck.so What is 'pam_pwcheck.so' for? My SuSE 7.0 box does have one. Yast did not show any unfulfilled dependencies. Alex. -- Alexander Liesch http://www.alexliesch.de/alex/ Lichtwiesenweg 9 Phone: +49 (0)6151 154715 64287 Darmstadt Fax/UMS: +49 (0)1212 5 10309699 Germany GnuPG/PGP-Key: 0xBC985C75

3 3

SuSEFirewall and bridged network
by Norbert Preining 28 May '01

28 May '01

Hi! Is it possible to use SuSEfirewall with a bridged/ipchains network? I use the bridge patches to filter in br0, but the SuSEfirewall always need more interface etc. Best wishes Norbert -- ciao norb +-------------------------------------------------------------------+ | Norbert Preining http://www.logic.at/people/preining | | University of Technology Vienna, Austria preining(a)logic.at | | DSA: 0x09C5B094 (RSA: 0xCF1FA165) mail subject: get [DSA|RSA]-key | +-------------------------------------------------------------------+

1 0

configuring firewalls with iptables
by Pupeno 28 May '01

28 May '01

Which is the standard way in SuSE to configure a firewall without using SuSEfirewall, just plain IPtables, or how can I do it (I don't wanna do a dirty script and put it anywhere and run it at anytime). thank you. Carpe diem! -- Pupeno: pupeno(a)pupeno.com.ar http://www.pupeno.com.ar

3 2

How to close ports...
by Faessen-Goden Jean-Paul en Rowena 28 May '01

28 May '01

Hi, Using SuSE 7.0 with Suse Firewall. should like to close some ports like port 12345,12346 etc... How to set this in the SuSE Firewall (I use Yast 1 to configure...) and how to test? In windows I had an option in IE to block a sender.How to do this in SuSE?Both konqueror and Netscape... Yhanks Jean-Paul faessen

2 1

Antwort: [suse-security] configuring firewalls with iptables
by Stefan_Walther＠gehag-dsk.de 28 May '01

28 May '01

You can use a simple script, where you enter the rules you want to have. I have done the same. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: 030/89786448 Funk: 0172/3943961

1 0

copying users/pwd from one box to another
by stephane parenton 28 May '01

28 May '01

hi, I'm running some servers and I would like to change one of the server with another box, that is more "up-to-date" regarding the CPU/Memory/Disk and OS... The old box is run by a RH6.0 and the new one will be a SuSE 7.0... the question is, how can I move all the users if i tell you that i don't want the passwords to be changed... The box existed long before I was here, so i don't know every password (especially our customers password). Is it possible to copy one password file from one box to another in order to keep the same passwords for all the users ?.... and is there a sure way to transfer all users once for all whithout any doubt ?... TIA Stephane Parenton

2 1

RE: [suse-security] copying users/pwd from one box to another
by José Luis Ledesma 28 May '01

28 May '01

Copy /etc/passwd /etc/shadow /etc/group I think that only with that will work, but be careful if your RH6.0 have shadowing or not. Check if in the redhat exists the file /etc/shadow, if doesn't install the shadowing package or put the passwords of shadow in passwd. Regards José Luis Ledesma Technology Dep. _____________________ COMPETITIVENESS Parque Tecnológico del Vallés 08290 Barcelona - Spain http://www.competitiveness.com Tel.: +34 66 986 55 17 Fax: +34 93 582 01 59 -----Original Message----- From: stephane parenton [mailto:sparenton@experia.com] Sent: lunes 28 de mayo de 2001 12:29 To: suse-security(a)suse.com Subject: [suse-security] copying users/pwd from one box to another hi, I'm running some servers and I would like to change one of the server with another box, that is more "up-to-date" regarding the CPU/Memory/Disk and OS... The old box is run by a RH6.0 and the new one will be a SuSE 7.0... the question is, how can I move all the users if i tell you that i don't want the passwords to be changed... The box existed long before I was here, so i don't know every password (especially our customers password). Is it possible to copy one password file from one box to another in order to keep the same passwords for all the users ?.... and is there a sure way to transfer all users once for all whithout any doubt ?... TIA Stephane Parenton --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

FW: [suse-security] OpenSSH on SuSE 6.3 --> 'PAM adding faulty mo dule: /lib/security/pam_pwcheck.so'
by José Luis Ledesma 28 May '01

28 May '01

In the /etc/pam.d/ you have the security libs you use for telnet, ftp, and openssh too. Probably you don't have the file /lib/security/pam_pwcheck.so on your linux. You can copy it from SuSE 7.0, or you can try to modify the openssh pam file... Regards José Luis Ledesma Technology Dep. _____________________ COMPETITIVENESS Parque Tecnológico del Vallés 08290 Barcelona - Spain http://www.competitiveness.com Tel.: +34 66 986 55 17 Fax: +34 93 582 01 59 -----Original Message----- From: Alex Liesch [mailto:aliesch@web.de] Sent: domingo 27 de mayo de 2001 16:54 To: suse-security(a)suse.com Subject: [suse-security] OpenSSH on SuSE 6.3 --> 'PAM adding faulty module: /lib/security/pam_pwcheck.so' Hi! I've updated one of my older linux servers running SuSE 6.3 to openssh (2.3.0p1) from "the" ssh. Now I have the following entries in messages each time a user logs in: May 27 16:47:25 r100 sshd[16621]: PAM unable to dlopen(/lib/security/pam_pwcheck.so) May 27 16:47:25 r100 sshd[16621]: PAM [dlerror: /lib/security/pam_pwcheck.so: cannot open shared object file: No such file or directory] May 27 16:47:25 r100 sshd[16621]: PAM adding faulty module: /lib/security/pam_pwcheck.so What is 'pam_pwcheck.so' for? My SuSE 7.0 box does have one. Yast did not show any unfulfilled dependencies. Alex. -- Alexander Liesch http://www.alexliesch.de/alex/ Lichtwiesenweg 9 Phone: +49 (0)6151 154715 64287 Darmstadt Fax/UMS: +49 (0)1212 5 10309699 Germany GnuPG/PGP-Key: 0xBC985C75 --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

some kind of attack?
by Daniel Quappe 28 May '01

28 May '01

hi list, got this message some minutes ago May 2 12:25:55 server kernel: Packet log: input DENY eth0 PROTO=1 192.168.0.2:3 this.is.my.ip:1 L=88 S=0x00 I=52687 F=0x000 0 T=243 where eth0 is the outbound-interface which is protected by ipchains from ip-spoofing. some kind of attack?! any ideas are appreciated...;-) many thanks in advance, bye, daniel

5 6

Antwort: [suse-security] configuring firewalls with iptables
by Stefan_Walther＠gehag-dsk.de 27 May '01

27 May '01

#!/bin/sh echo "starting firewall" # interfaces EXT="ippp+" # external interface (maybe a tokenring-card or anthing else; point to the internet) INT="eth+" # internal interface (point to your lan) LO="lo" # loopbackinterface # IP-adresses INTIP="192.168.0.1" # your local ip for your lan (internal ip) ANY="0.0.0.0/0" # all other ip's (maybe you need it in further times) # ports PRIVP="0:1023" # priviliged ports UNPRI="1024:65535" # unpriviliged ports # SYNFLOODING echo 1 > /proc/sys/net/ipv4/tcp_syncookies # Source Address Verification on for f in /proc/sys/net/ipv4/conf/*/rp_filter; do echo 1 > f done # IP-forwarding on echo 1 > /proc/sys/net/ipv4/ip_forward iptables -P INPUT DROP # drop all incoming packets iptables -P OUTPUT DROP # drop all outcoming packets iptables -P FORWARD DROP # drop all forwarded packets iptables -X # delete all userdefined tables iptables -F # flushing tables iptables -t nat -F # flushing nat-tables iptables -t nat -X # deleting userdefined nat-tables # ignore waste coming from your windowslan # netbios (drop it before writing these messages into your firewall-logfile) iptables -A INPUT -i $EXT -p tcp --sport 137:139 -j DROP iptables -A INPUT -i $EXT -p tcp --dport 137:139 -j DROP # droping bootp and tftp connections (if you have thin clients or some boxes booting from a server via bootrom) iptables -A INPUT -p tcp --sport 67:68 -j DROP iptables -A INPUT -p tcp --dport 67:68 -j DROP # no limits for connections comming from your lan (maybe specify some single rules ex.: SSH, DNS, HTTP...) iptables -A INPUT -i $INT -j ACCEPT iptables -A OUTPUT -o $INT -j ACCEPT # no limits for your LOOPBACK-device iptables -A INPUT -i $LO -j ACCEPT iptables -A OUTPUT -o $LO -j ACCEPT # do want to ping from your firewall iptables -A INPUT -p icmp -j ACCEPT iptables -A OUTPUT -p icmp -j ACCEPT iptables -A FORWARD -p icmp -j ACCEPT ########################################################################## # NAT (MASQUERADING) # replace your local-ip from lan with the offical Internet-IP you got from your ISP ########################################################################## echo "NAT" iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE iptables -A FORWARD -i $EXT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -i $EXT -m state --state NEW -j ACCEPT ########################################################################## # DNS # allows you to connect to an DNS-Server of your ISP or other ########################################################################## echo "DNS" iptables -A OUTPUT -o $EXT -p udp --sport 1024:65535 --dport 53 -j ACCEPT iptables -A INPUT -i $EXT -p udp --sport 53 --dport 1024:65535 -j ACCEPT iptables -A OUTPUT -o $EXT -p tcp --sport $UNPRI --dport 53 -j ACCEPT iptables -A INPUT -i $EXT -p tcp --sport 53 --dport $UNPRI -j ACCEPT # LOG anything else with setting som prefixes infront of any message in your firewall-log # you should add one of the following line to your syslog.conf in /etc # kern.* /dev/tty11 # most tty11 is unused and you see a blank screen when switching (same tty12) # or/and # kern.* /var/log/firewall # here you write every message comming from the kernel in the file firewall iptables -A INPUT -j LOG --log-prefix "input " iptables -A OUTPUT -j LOG --log-prefix "output " iptables -A FORWARD -j LOG --log-prefix "forward " echo "READY" MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: 030/89786448 Funk: 0172/3943961

2 1

cannot ping using firewall
by Pupeno 27 May '01

27 May '01

I download SuSEfirewall 2 because I'm running on kernel 2.4. I installed and configured it (configuration file attached), I don't know why, nobody can ping me and I cannot ping nobody (not even me: 127.0.0.1). >From the internal network, they can telnet me, I can see samba shares on internal computers, fetching mail from internal network works good, but www is very slow!!! Is there any way to just configure iptables, not using this, but using a SuSE compatible way (I know, I can just write a script and put it anywhere and run it at start up, but, when I use a distribution I like doing the things in the distribution way). Thank you. -- Pupeno: pupeno(a)pupeno.com.ar http://www.pupeno.com.ar -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

1 0

[suse-security] iptables-logging
by da_bug 27 May '01

27 May '01

Hi! With ipchains I could have a rule like this: ipchains -A INPUT ... -j DENY -l <- and because of the "-l" I had log-messages of this rule in my /var/log/messages. How can this be done with iptables? Bye.

4 4

how to close "pending" connections: SYN_RECV
by N. Aust 27 May '01

27 May '01

after being syn flooded two weeks ago I still have nearly two hundred of pending connections ( 'netstat' gives the state: SYN_RECV ) on port 80 of my machine from abusive foreign hosts. Is there a way to close just these pending connections without affecting the "proper" ESTABLISHED ones to port 80 ? Regards, Nick

1 0

Re: [suse-security] WTF ???
by Jörg Mayer 27 May '01

27 May '01

You didn't search the kernel sources, did you? When I search my i386 SuSE 2.4.2 source tree, it looks like this: jmayer@alice:/usr/src/linux > grep -r '\\__U_/' . ./arch/sparc/kernel/traps.c:" \\__U_/\n"); ./arch/sparc64/kernel/traps.c:" \\__U_/\n"); > In my /var/log/firewall I see - > > May 24 08:50:18 sneex kernel: \|/ ____ \|/ > May 24 08:50:18 sneex kernel: "@'/ .. \`@" > May 24 08:50:18 sneex kernel: /_| \__/ |_\ > May 24 08:50:18 sneex kernel: \__U_/ > > What is that ??? -- Jörg Mayer <jmayer(a)loplof.de> Signature fault, brain dumped

1 0

Libraries missing pam.rpm (pam_pwdb.so)
by Alexander Topolanek 27 May '01

27 May '01

Hi, I tried to install Samba 2.2 on my SuSE 7.1, but I cannot log in. The system looks for a /lib/security/pam_pwdb.so, which is missing in the pam.rpm from SuSE. Has anyone ideas or a workaround? I dont want to install a generic pam.rpm and find myself locked out... thanks Alexander Topolanek Propst Peitlstr. 85 2103 Langenzersdorf Austria Phone: +43-2244-33633-633 Fax: +43-2244-33633-55 GSM: +43-676-5702852 email: atopo(a)ocv.org

2 2

Re: [suse-security] diffence between portfw and mfw
by William Preston 27 May '01

27 May '01

Togan Muftuoglu wrote: > > Hi > > What are the main differences between portfw and mfw in ipmasqadm. For > example Marc prefers mfw in the SuSEfirewall script but on the other > hand I have seen scripts were portfw is used only. The only thing I > saw was im portfw you need the specify the protoc also tcp / udp. > > Sorry until my book arrives there will be more questions coming. Ah > yes when it arrives expect more to come :-) > > Have a nice Sunday > > -- > Togan Muftuoglu > I find the packet marking stuff very useful for simplifying things. e.g. if we want 3 clients to see different webservers, then all we have to do is use the one address for any client and add the following rules; ipchains -I $INPUTCHAIN -p tcp -y -s $CLIENTA --dport 80 -m 1 ipchains -I $INPUTCHAIN -p tcp -y -s $CLIENTB --dport 80 -m 2 ipchains -I $INPUTCHAIN -p tcp -y -s $CLIENTC --dport 80 -m 3 ipmasqadm mfw -I -m 1 -r $WEBSERVER1 80 ipmasqadm mfw -I -m 2 -r $WEBSERVER2 80 ipmasqadm mfw -I -m 3 -r $WEBSERVER2 8080 This doesn't provide much security in itself though... ...you still really need password protection etc. It just makes it easier for the clients to find what they're looking for quickly. William

3 2

SuSEfirewall configuration help
by Matt 27 May '01

27 May '01

SuSEfirewall config... Please could someone send me an example of one with the following settings enabled please.. I use SAMBA, telnet, rlogin, ftp and vnc, ping, traceroute on 3 my machines 192.168.0.2 (SuSE 7.0, 192.168.0.3 (SuSE 6.4) and use my win2000 box to work on (192.168.0.1). these are all on eth0 with win2000 used to dialup on. I would like to set up 192.168.0.2 as my gateway/router but at the moment I have configured my win2000 box. However whilst setting up SuSEfirewall my system hung on the firewall first run initialisation. I can neither login or do anything on reboot. I could login in single user mode but I don't know how to do that ant directions ? Regards Matt

1 0

Download problem
by Luis José Fabbiani B. (SOPORTE) 27 May '01

27 May '01

Hi list, I tried to download for two week the k_deflt-2.2.19-11.i386.rpm kernel and it's impossible. I tried with two path: ftp://ftp.suse.com/pub/suse/i386/update/7.0/kernel/RPMs/ And ftp.suse.com/pub/suse/i386/update/7.0/kernel/2.2.19/ How can I get that ? Are there other way? Thanks! LF

3 2

diffence between portfw and mfw
by Togan Muftuoglu 26 May '01

26 May '01

Hi What are the main differences between portfw and mfw in ipmasqadm. For example Marc prefers mfw in the SuSEfirewall script but on the other hand I have seen scripts were portfw is used only. The only thing I saw was im portfw you need the specify the protoc also tcp / udp. Sorry until my book arrives there will be more questions coming. Ah yes when it arrives expect more to come :-) Have a nice Sunday -- Togan Muftuoglu

2 1

WTF ???
by Bill Jones 26 May '01

26 May '01

In my /var/log/firewall I see - May 24 08:50:18 sneex kernel: \|/ ____ \|/ May 24 08:50:18 sneex kernel: "@'/ .. \`@" May 24 08:50:18 sneex kernel: /_| \__/ |_\ May 24 08:50:18 sneex kernel: \__U_/ What is that ??? I have suse-sparc, 64-bit, Ultra 10; I am running the Standard 2.4.2 kernel. Thx; -Sneex- :] ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

2 1

Finding out what shared libs are used by a programm?
by Thomas Schweikle 26 May '01

26 May '01

Hallo ! How can I fast find out what shared libraries a given program uses? -- Thomas

2 1

convert ips from inet to ip's of my intranet/isp, iptables and nat?
by Ramon Acedo 25 May '01

25 May '01

Hello, we'd like a good way of allowing trusted ip's from the internet to use some services that we have in our intranet. We need to simulate that certain ip's of the inet seem to be ip's assigned by our ISP to access to some services that only are allowed the users conected to our ISP The first idea was to use a gateway with some iptables rules: iptables -t nat -A POSTROUTING -s "trusted_ip" -o eth0 -j SNAT --to 1.2.3.4 for change the incoming ip's and for returning: iptables -t nat -A PREROUTING -s 1.2.3.4 -i eth0 -j DNAT --to "trusted_ip" So if we ping the "trusted_ip" from the intranet we get answer and if we ping the 1.2.3.4 from the trusted ip we get answer too. Note that the intranet is not an actual intranet becuse it has well-known-to-the-internet ip's -we've got a little ISP- But this limit us because the "trusted_ip" must have as default gateway the box that has the iptables rules. As the trusted ips are dynamic addresses from inet wich are trusted just for some time and then removed from the iptables rules, so it is not possible to make everyone to change its default gateway just for access to our intranet for a while. With the system I mentioned before we got some troubles with ftp's, as I said we could ping from each side of the gateway/firewall to each other, but when I connected to a ftp server of my intranet with a client from outside and the ip converted with iptables, we could login but not make data transfers, the ftp after login opens the port 20 with the client to establish the data connection, I think it shouldnt have any problem but the client complains about bind or network reaching or something I cant remenber -sorry :) - May be there is another way of doing it, but we NEED to change the source ip's because in the intranet we have lots of services that validate just for the IP's of the intranet, and it is very difficult to make dynamic ips validations.

1 0

Re: [suse-security] Finding out what shared libs are used by a programm?
by Nick LeRoy 25 May '01

25 May '01

Hello... > Hallo ! > > How can I fast find out what shared libraries a given program uses? Use ldd. For example: $ldd /bin/ls libc.so.6 => /lib/libc.so.6 (0x4001b000) /lib/ld-linux.so.2 => lib/ld-linux.so.2 (0x40000000) -Nick -- Get your free email from www.linuxmail.org Powered by Outblaze

1 0

Securing 7.1
by Geoffrey T. Sanders 25 May '01

25 May '01

Have noticed that there is not a hardsuse.rpm package for the 'current' sec1 directory, but one exists for the 7.0 version. Have there been changes in 7.1 to negate the need for this package? If not, would I still be able to implement the hardsuse.rpm and seccheck.rpm packages on 7.1? Thanks in advance. G. Sanders San Diego, CA

3 2

weird request from port 53 to 2049
by Togan Muftuoglu 25 May '01

25 May '01

Hi, can someone give me any reason why a nameserver would make a request to 2049 which is nfs Packet log: input DENY ppp0 PROTO=17 212.156.4.20:53 212.156.196.114:2049 L=137 S=0x00 I=5423 F=0x0000 T=27 (#39) Packet log: input DENY ppp0 PROTO=17 212.156.4.20:53 212.156.196.114:2049 L=137 S=0x00 I=5574 F=0x0000 T=27 (#39) Packet log: input DENY ppp0 PROTO=17 212.156.4.20:53 212.156.196.114:2049 L=137 S=0x00 I=5738 F=0x0000 T=27 (#39) -- Togan Muftuoglu

7 14

Detect a portscan attac
by patric illi 25 May '01

25 May '01

Cheers List ! I am thinking about a solution to disallow access to my server for all those who have made a portscan. I would like to insert their IP's into the /etc/host.deny file. Does anybody know a way how to detect whether someone does a portscan ? would be kind ! cheers & thx in advanced patric illi

4 3

Kernel update packages not gpg signed?
by Muralito 25 May '01

25 May '01

Hi. Kernel update packages lx_sus22-2.2.19.SuSE-25.i386.rpm and lx_doc22-2.2.19.SuSE-25.i386.rpm are not gpg signed. Is this right? Thanks, Muralito

2 1

2.4 kernel is dropping tcp connections
by Kaupo Palo 24 May '01

24 May '01

Does anybody have an idea why under kernel 2.4.x I am experiencing dropping of TCP connections. (No packet filters). With packet captures I saw that my computer send out SYN, I get back SYN-ACK and then my computer responds with RST. Some hosts can regularly be connected, some are regularly dropped although occasionally the connection is established. It never happened with 2.2.x kernel. I am using the suse kernel 2.4.2 currently (2.4.0 had the same problem). The packet contents didn't reveal anything suspicious to my mind. The SYN-ACK packets looked quite similar in both cases. Does anybody have an idea? Kaupo -- Kaupo Palo, Evotec OAI, Instituudi tee 11, Harku EE76902, Estonia E-mail: palo(a)ebi.ee______________________Phone & Fax: 372-6560601

2 1

secure connection with IPSEC etc.
by Guido Tschakert 24 May '01

24 May '01

Hello list I have to connect two lan's via ISDN. Certainly the connection should be secure. I think about a linux-box in each lan with ISDN-cards, which act as routers with a VPN-connection beetween them. Now I am looking for some information about these things (ISDN, VPN and how to bring them together). So I want you to ask which kind of VPN-implemantation (CIPE, FREESWAN) would you use or maybe you can tell me some sources of information about this. I've already gone through the HOWTO's and the Manual-pages. TIA Guido PS: I'm sorry that this is not a"real" question. Maybe you can sent me the information directly and not via the list. -- ----------------- Guido Tschakert SRC GmbH, SysAd -----------------

2 1

Question about Local Daily Security check
by Markus Gaugusch 24 May '01

24 May '01

Hello List! I often get these entries in my security check (secchk.rpm): * Changes (+: new entries, -: removed entries): - kerstin:/home on /misc/khome type nfs (rw,Ì×ÿ¿|Øÿ¿¸Øÿ¿kerstin:/home,addr=192.168.10.1) + kerstin:/home on /misc/khome type nfs (rw,¬×ÿ¿\Øÿ¿¸lØÿ¿kerstin:/home,addr=192.168.10.1) I'm using autofs (from /etc/auto.misc): khome -fstype=nfs kerstin:/home Any idea, why I get those weird characters? thank you Markus -- _____________________________ /"\ Markus Gaugusch ICQ 11374583 \ / ASCII Ribbon Campaign markus(a)gaugusch.dhs.org X Against HTML Mail / \

1 0

Certified Information Systems Security Professional (CISSPT) - Qu estion
by Steven Thompson 24 May '01

24 May '01

Hi All Has any one writen the the "Certified Information Systems Security Professional" exam. Would anyone recomend it. The following books are recommended on their site are any of them good or are there better. https://www.isc2.org/cissp_studyguide#reference Thanks in Advance Steven

1 0

Re: [suse-security] scanrpm: script to check system for known vulnerable packages
by Bob Vickers 24 May '01

24 May '01

Dear All, I just thought I would respond to some of the points people made about my scanrpm script. A couple of people mentioned that it ought to handle ranges of vulnerable versions rather than just single ones. This was certainly my intention originally, but then I looked at the possible forms that version strings can take and realised that parsing and comparing them could be tricky. Probably still possible, but difficult to cover all the cases. And the script at present has the great virtue of simplicity (only 55 non-comment lines at present)...more complexibility means more bugs and more unexpected behaviour. A compromise would be to allow regular expressions in the comparison; this should be easy to implement. Another idea is for keys such as "SEVERITY=x" [x=1..10] and "INFO='Remote Root Exploit'" to give you more information about the exploit...good idea. Felix Huber mentioned autoupdate (http://www.mat.univie.ac.at/~gerald/ftp/autoupdate/ ), which I see as a useful but complementary tool. In particular autoupdate only helps if a fixed package is already available...sometimes the only solution is to remove a package. The problem this script is trying to address is that it is currently very hard to be confident that you have acted on all the security alerts relevant to a release. You have to plough through a long series of alerts, some of them referring to updates which no longer exist. Any solution to this problem MUST involve SuSE producing a machine-readable list of either vulnerabilities or security fixes or (preferably) both. Bob -- ============================================================== Bob Vickers R.Vickers(a)cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691

1 0

Re: [suse-security] scanrpm: script to check system for known vulnerable packages
by Felix Huber 24 May '01

24 May '01

Hi Bob, I mean AutoUpdate from Gerald Teschl - you find it here http://www.mat.univie.ac.at/~gerald/ftp/autoupdate/ But I would no recommend this solution. A updated XML with all necessary information would be much better. Regards, Felix Huber ------------------------------------------------------- Felix Huber, Web Application Programmer, Webtopia Guendlinger Str.2, 79241 Ihringen - Germany huberfelix(a)webtopia.de (07668) 951 156 (phone) http://www.webtopia.de (07668) 951 157 (fax) (01792) 205 724 (mobile) ------------------------------------------------------- > Felix, > > Well I thought the idea couldn't be new, but a quick search on the net > didn't find what I wanted. Do you have something specific in mind? > > Bob > > On Wed, 23 May 2001, Felix Huber wrote: > > > > Hi Bob, > > > > this idea is not so new - there is already a similar tool for RPM releases > > on FTP server in general. > > But a XML file with up-to-date information (dependencies etc) would make > > life much easier. > > > > MfG > > Felix Huber

1 0

WG: [suse-security] SuSEFirewall fails on system startup
by Ragucci＠t-online.de 24 May '01

24 May '01

ReHi folks, the Script you've to download is on that page: http://www.suse.de/~marc/SuSE.html You've to download the SuSEfirewall v4.6 - 29th April 2001 <SuSEfirewall-4.6.tar.gz> Script unless you want to work with iptables (I think so...). In my Opinion the failures are a result of the bootup sequence, means that the fw-script (or parts of it) is loaded BEFORE the devices (eth0, ippp0 etc.) have been initialized! Maybe you've to make new symbolic links! Instead of "S01SuSEfirewall....." try "S25SuSEfirewall" or something like that! But remember that there's no protection between initializing the devices and loading the script! I prefer downloading the newest Script! Maybe some people have to deinstall the old Script (but the new script will do that, won't it?). I'm sure it works, I've spent some days before I got rid of that problem! If you can't get rid of it, try the "ipchains -L" command, to see if the rules have been set correctly! Bye, Mario PS: Sorry because of my bad english!

1 0

Re: [suse-security] firewalling canna port 5680
by Joss Winn 23 May '01

23 May '01

just for the record, these commands worked in the end :-) thanks to all that helped. nmap still shows the port open, but I guess this is good enough. iptables -A INPUT -s 127.0.0.1 -d 127.0.0.1 -p tcp --dport 5680 -i lo -j ACCEPT iptables -A INPUT -d 127.0.0.1 -p tcp --dport 5680 -j DROP -- http://www.josswinn.org

1 0

Re[2]: AW: [suse-security] ipchains masq + active ftp / OR NETFILTER/IPTABLES...
by da_bug 23 May '01

23 May '01

hi! S> You can use ipchains with kernel 2.4 . You should recompile your S> kernel with ipchains support ou for just tests, insmod ipchains. I do S> the second option to tests and my ipchains work very well. I know that I can use ipchains with kernel 2.4.x but it seems to me (right or not?) that I cannot use this special ipchains-module "ip_masq_ftp.o" with kernel 2.4.x ... >> >> Hi! >> >> CU> I think you need the module ip_masq_ftp.o to masquarade active ftp with >> CU> ipchains, aren't you? So it works fine for me. Perhaps take a look at >> CU> http://www.linux-firewall-tools.com/linux/. >> >> CU> Hope thats you are looking for! >> >> CU> Christian >> >> ..ip_masq_ftp.o would be a good solution, but it seems to me that it >> just works with kernel 2.2.x and not with 2.4.x .. !? >> If there is a possibilty to use it with 2.4.x (ipchains-compatibility) I >> would like to know about... >> Meanwhile I also took a look at Netfilter/Iptables and set up a >> masquerading-rule that works fine so far... but I have the same >> ftp-problem: ;-) >> How can I realize active ftp-connections from the clients behind a >> netfilter/iptables-gateway-pc? >> >> Bye.

1 0

How do I get loopback encryption working with 2.2.19?
by Paul Elliott 23 May '01

23 May '01

How do I get loopback encryption filesystems working with 2.2.19? I note the .config file created by make xconfig has lines with: CONFIG_BLK_DEV_LOOP CONFIG_CIPHER_TWOFISH ftp.kernel.org does not have a patch listed for 2.2.19 Thank You. -- Paul Elliott 1(512)837-9345 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

4 4

lost in icmp filtering
by Togan Muftuoglu 23 May '01

23 May '01

Hi, I am trying to tighten up my ipchains firewallon my adsl router/firewall box . But looks like I am a litle bit lost. I have read previous mails backing to 2000 May and I am still lost.Maybe too much info is not good) Below is what I have done. Is there anything I should be carefull with if [ -e /proc/sys/net/ipv4/conf/all/rp_filter ] then for f in /proc/sys/net/ipv4/conf/*/rp_filter do echo 1 > $f done fi if [ -e /proc/sys/net/ipv4/tcp_syncookies ] then echo 1 > /proc/sys/net/ipv4/tcp_syncookies fi # echo "1" > /proc/sys/net/ipv4/ip_dynaddr echo "1" > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts echo "1" > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses for file in /proc/sys/net/ipv4/conf/*/accept_redirects; do echo "0" > $file done for file in /proc/sys/net/ipv4/conf/*/log_martians; do echo "1" > $file done $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type echo-reply -l $IPCHAINSs -A input -j REJECT -i $OUTERIF -p tcp -s $OUTERNET -d $OUTERIP 33434 -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p udp -s $OUTERNET -d $OUTERIP 33434 -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d OUTERIP --icmp-type destination-unreachable -l IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type destination-unreachable -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type redirect -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type echo-request -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type time-exceeded -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type parameter-problem -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type timestamp-request -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type timestamp-reply -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type address-mask-request -l $IPCHAINS -A input -j REJECT -i $OUTERIF -p icmp -s $REMOTENET -d $OUTERIP --icmp-type address-mask-reply -l -- Togan Muftuoglu

1 0

Re: How do I get loopback encryption working with 2.2.19?
by Paul Elliott 23 May '01

23 May '01

On Wed, May 23, 2001 at 01:04:44PM +0200, Hubert Mantel wrote: > Hi, > > On Tue, May 22, Paul Elliott wrote: > > > How do I get loopback encryption filesystems working with 2.2.19? > > It's quite easy. You just need a recent losetup binary. Please note that > losetup as of SuSE Linux 7.1 is recent enough ;) > Does this mean I can just grab a 7.1 binary and use it on a 7.0 2.2.19 system? Will there be library incompatabilities? Do I have to get the source and rebuild? -- Paul Elliott 1(512)837-9345 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

1 0

scanrpm: script to check system for known vulnerable packages
by Bob Vickers 23 May '01

23 May '01

Dear All, I had an idea for a utility to make it easier to check a system is up-to-date with patches. I assumed that someone else must have had the idea already, but I couldn't find it on the web so I wrote the utility myself. For this utility to work it needs someone (and I think that someone really needs to be SuSE) to maintain a machine-readable list of packages known to have security holes. All the utility does is reads such a list and then reports any vulnerable packages it finds on the system. So you would use it something like wget -O - ftp://ftp.suse.com/vulnerabilities.txt | scanrpm The vulnerability file should contain lines like openssh VERSION=8.3.0p2 RELEASE=98 where the uppercase keywords correspond to rpm query tags. Do people think this is useful? If so, are SuSE willing to take it on? Of course, the utility would be useful for bad guys as well as good guys, but we are used to that. Current version of the scanrpm utility can be found at http://www.cs.rhul.ac.uk/home/bobv/utils/scanrpm Nothing in the utility is SuSE-specific, but I guess the database would be. Bob ============================================================== Bob Vickers R.Vickers(a)cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691

3 2

Re: [suse-security] Rinetd
by Sp0oKeR 23 May '01

23 May '01

Redir is the same tha Redirect4All? Because I'm using this do redirect my ftp. But in my webservers I'm using rinetd. The question is: I have about 6000 hits a day, then, I'm with a interface with 2 ips, this ips were from my NT. And I do the redirects. Can a big number os hits down my rinetd? Do you think a should use redir to webserver too ? Regards ... > > ---------- Início da mensagem original ----------- > De: "Kurt Seifried" <listuser(a)seifried.org> > Para: "Sp0oKeR" <spooker(a)bol.com.br>, <suse- security(a)suse.com> > Cc: > Data: Tue, 22 May 2001 21:01:11 -0600 > Assunto: Re: [suse-security] Rinetd > If you want to do this in user space you can use redir which is pretty > reliable in my experience. If you are willing to muck around with your > kernel/etc you can use ipportforwarding, this is covered in the firewall howto > I believe. > > Kurt Seifried, seifried(a)securityportal.com > Securityportal - your focal point for security on the 'net > > > > ----- Original Message ----- > From: "Sp0oKeR" <spooker(a)bol.com.br> > To: <suse-security(a)suse.com> > Sent: Tuesday, May 22, 2001 8:50 PM > Subject: [suse-security] Rinetd > > > Hi all... > I'm using rinetd to bind de port 80, and redirect > to my NT Servers. But the problem é o seguinte: my > rinetd is going down. I'm using SuSE 7.0 and I have been > instaled rinetd from my cd's. > I'using ipchains and masquerading too. > Can somebody help-me? > > Sp0oKeR - NsC > spooker(a)bol.com.br > Powered By Linux - SuSe > > > _________________________________________________________ _________________ > Acesso pelo menor preço do mercado! R$ 14,90 nos 3 primeiros meses! > ASSINE AGORA! http://www.bol.com.br/acessobol/ > > > > ------------------------------------------------------- -------------- > To unsubscribe, e-mail: suse-security- unsubscribe(a)suse.com > For additional commands, e-mail: suse-security- help(a)suse.com > > > > ------------------------------------------------------- -------------- > To unsubscribe, e-mail: suse-security- unsubscribe(a)suse.com > For additional commands, e-mail: suse-security- help(a)suse.com > > Sp0oKeR - NsC spooker(a)bol.com.br Powered By Linux - SuSe & Slackware __________________________________________________________________________ Acesso pelo menor preço do mercado! R$ 14,90 nos 3 primeiros meses! ASSINE AGORA! http://www.bol.com.br/acessobol/

2 1

Bind Problem
by Sp0oKeR 23 May '01

23 May '01

I'm using SuSE Linux 7.0 with Bind 8.2.3. My problem, is : My bind is always stopping , I don't know way. This occurs about 1 or 2 times a day. Then , I need to restart it everytime. Can somebody help me? Regards -- #=============================# # Rodrigo Ribeiro Montoro # # Network Services Center # # rodrigo(a)nscenter.com.br # # http://www.nscenter.com.br # # Sao Paulo - SP # #=============================#

4 3

[suse-security] ipchains masq + active ftp
by da_bug 23 May '01

23 May '01

Hi! I want to use active-ftp with some clients behind my gateway-pc (ipchains-masquerading)... (passive ftp works) How do I configure my ipchains-firewall to allow this? I hope someone can help me... Bye.

4 6

SINUS Firewall on SuSE 7.1?
by Benjamin Grogg 23 May '01

23 May '01

Hi folks, Anyone have experience with Sinus Firewall on SuSE 7.1? How it works on SuSE? Thanks a lot for your comments :) Benny

1 0

firewalling canna port 5680
by Joss Winn 23 May '01

23 May '01

Hello again, well, I have had good feedback from SUSE and other users of the Japanese language server, Canna. As far as security at a software level is concerened, I think it is secure. However, it still shows as an open port 5680 when tested with nmap. I have been told that while the software settings are secure, if I want to make it invisible to nmap, I would need kernel level firewalling. I have Firewall2 set up on my dialup ppp box. Can anyone tell me what settings I need to change in YaST to enable firewalling on port 5680 and make it invisible to the outside? I thought that blocking high ports would do it, but it still shows up on nmap. thanks very much This is more a learning process than a real world security threat, but I appreciate your help all the same. cheers Joss

2 2

Upgrades via mirror and yast2
by Martin Sckopke 23 May '01

23 May '01

Hi all, since version 7.1 YAST2 enables me to automatically update via Internet. I tried to use this feature with a mirror of ftp.suse.com, but YAST2 would not work. What has to be in the mirror directories for YAST2 to work? Thanks for your great support, Martin -- The three golden rules to ensure computer security are: Do not own a computer; do not power it on; and do not use it (Robert (Bob) T.Morris) GiS - Gesellschaft fuer integrierte Systemplanung mbH Martin Sckopke Tel. +49-6201-503-74 Junkersstr. 2 Fax +49-6201-503-66 D-69469 Weinheim m.sckopke(a)gis-systemhaus.de

1 0

RE: [suse-security] Re: OT(?): Apache segfaults after update to 7 .1
by Pini Remo 23 May '01

23 May '01

Updating everything (apache, ssl, mod_php) to the newest version available through ftp (funnily enough NOT through YOU -> why not!?), the problem disappeared... seems to have been a version mismatch. greets and thanx for the help, remo > > After the long due update from 6.4 to 7.1, apache (child-procs only) > > segfaults upon page requests. > > I would say you should try the updated apache 1.3.19

1 0

AW: [suse-security] SuSEFirewall fails on system startup
by Ragucci＠t-online.de 23 May '01

23 May '01

Hi Guys, I had the same problems... But there's no problem, 'cause the Script will produce the ipchain rules! The only thing you've to do ist downloading the newest version of the ipchain script at marcs homepage (www.suse.de/~marc) With that one, there'll be no more failure messages at bootup! Bye, Mario -----Ursprüngliche Nachricht----- Von: Ulrich Schneider [mailto:ulrich_schneider@uni.de] Gesendet: Dienstag, 22. Mai 2001 08:39 An: suse-security(a)suse.com Betreff: [suse-security] SuSEFirewall fails on system startup When switching to runlevel 3 the firewall is going to be initialized. Normally I get the green done message when a service is startet or the red failed message. But the firewall-initalisation-steps 1-3 produce neither the green nor the red message. At the end of system startup the system tells me: Failure services in runlevel 3: SuSEfirewall_init, SuSEfirewall_setup, SuSEfirewall_final. But the file /etc/rc.config.d/firewall.rc.config is cinfigured in the right way ! --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

2 1

Rinetd
by Sp0oKeR 23 May '01

23 May '01

Hi all... I'm using rinetd to bind de port 80, and redirect to my NT Servers. But the problem é o seguinte: my rinetd is going down. I'm using SuSE 7.0 and I have been instaled rinetd from my cd's. I'using ipchains and masquerading too. Can somebody help-me? Sp0oKeR - NsC spooker(a)bol.com.br Powered By Linux - SuSe __________________________________________________________________________ Acesso pelo menor preço do mercado! R$ 14,90 nos 3 primeiros meses! ASSINE AGORA! http://www.bol.com.br/acessobol/

2 1

ftp
by nicemice＠gmx.de 22 May '01

22 May '01

Hi there, Does anybody know how to configure ProFTP to access an internal server = inside a firewall?? The server should be accessible from outside only = with one user ('ftpuser'), but I'd like to use all other user accounts = intern. For this reason at the moment the server is using a different = user and group file. Maybe the problem can also be found in the SUSEfirewall configuration. = Any hints ? Thanx a lot in advance :-)

1 0

gpg
by Roman Drahtmueller 22 May '01

22 May '01

Hi together, the gpg updates to 1.0.5 are available for testing on ftp.suse.de (for SuSE-6.3, 6.4 and 7.0) and ftp.suse.com (7.1 and up). Get the gpgaddon packages as well (for pgp compatibility). All packages are signed using the build(a)suse.de key. Here it is (I've signed it using security(a)suse.de) Thanks, Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.5 (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+D0BuQIN BDnu9JIQCACEkdBN6Mxf5WvqDWkcMRy6wnrd9DYJ8UUTmIT2iQf07tRUKJJ9v0JX fx2Z4d08IQSMNRaq4VgSe+PdYgIy0fbj23Via5/gO7fJEpD2hd2f+pMnOWvH2rOO IbeYfuhzAc6BQjAKtmgR0ERUTafTM9Wb6F13CNZZNZfDqnFDP6L12w3z3F7FFXkz 07Rs3AIto1ZfYZd4sCSpMr/0S5nLrHbIvGLp271hhQBeRmmoGEKO2JRelGgUJ2CU zOdtwDIKT0LbCpvaP8PVnYF5IFoYJIWRHqlEt5ucTXstZy7vYjL6vTP4l5xs+LIO kNmPhqmfsgLzVo0UaLt80hOwc4NvDCOLAAMGB/9g+9V3ORzw4LvO1pwRYJqfDKUq /EJ0rNMMD4N8RLpZRhKHKJUm9nNHLbksnlZwrbSTM5LpC/U6sheLP+l0bLVoq0lm sCcUSyh+mY6PxWirLIWCn/IAZAGnXb6Zd6TtIJlGG6pqUN8QxGJYQnonl0uTJKHJ ENbI9sWHQdcTtBMc34gorHFCo1Bcvpnc1LFLrWn7mfoGx6INQjf3HGQpMXAWuSBQ hzkazY6vaWFpa8bBJ+gKbBuySWzNm3rFtT5HRKMWpO+M9bHp4d+puY0L1YwN1OMa tcMMpcWnZpiWiR83oi32+xtWUY2U7Ae38mMag8zFbpeqPQUsDv9V7CAJ1dbriEwE GBECAAwFAjnu9JIFCQPCZwAACgkQqE7a6JyACspLIgCbBQd/++0pB9yZWDhqxHtT pdCXRsAAnik7bYHlTxQfohiXYsEJcWrDn7l8 =wtNS -----END PGP PUBLIC KEY BLOCK-----

3 4

NetMeeting
by Roland Hilkenbach 22 May '01

22 May '01

Hi list, a coworker of mine needs to work with NetMeeting including audio and video streams. Since we use a T-DSL connection this should be ok. Most of the setup is working fine but there's a catch: her streams are going out but she's not able to _receive_ the other streams. The manual states you have to open UDP transfer to and from the workstation for _every_ other participating computer _and_ port combination! That's since it is not known in advance what IP-adresses the communication partner uses and what ports will be chosen by that software. As far as I've understood the Real-time Transfer Protokol RTP there is an initial connection going to port 1503 and each subsequent datapacket includes the portnumber where to send the next packet. So I figure only stateful firewalls will be able to handle that correctly. My question: Is it possible to archive such a connection with a masquerading Linux-Gateway with a T-DSL connection? Thank you Roland Hilkenbach

1 0

SuSEFirewall2
by Christian Lox 22 May '01

22 May '01

Hi everyone, hope this is the right place (is it, Marc?). I just downloaded SuSEFirewall2 to give it a try. Seems to work great, no serious problems found. One thing annoys me: I did set ping_ext (dont konw the exact name right now) to yes. So ping to the internet should be allowed. But I dont get anything back, not even DENYs in the log. Christian -- we reject: kings, presidents, religions we accept: working code

2 1

SuSEFirewall fails on system startup
by Ulrich Schneider 22 May '01

22 May '01

When switching to runlevel 3 the firewall is going to be initialized. Normally I get the green done message when a service is startet or the red failed message. But the firewall-initalisation-steps 1-3 produce neither the green nor the red message. At the end of system startup the system tells me: Failure services in runlevel 3: SuSEfirewall_init, SuSEfirewall_setup, SuSEfirewall_final. But the file /etc/rc.config.d/firewall.rc.config is cinfigured in the right way !

2 1

closing ports (canna, squid and sendmail)
by Joss Winn 22 May '01

22 May '01

Hello, I am reviewing the security on my home desktop and have a question which I hope is simple to answer. I should say that I am on a 56k dial up PPP connection and offer no services to anyone. I am the only user and root. Simple. In fact, I think my security measures are probably over-the-top, but still it sems like good practice and makes interesting learning. I have hardened the system using Marc's hardening script and have set up Firewall2. Now, when I scan my ports with nmap, I have 'canna', 'smtp' and 'squid' showing open. Canna is my Japanese language server and I have squid running to cache pages for web browsing. I also opened up the smtp/sendmail service so I can use fetchmail to fetch my mail. My questions are: 1. Can I close the canna port and still use canna? I see no reason why it should be sitting open to external connections when I am the only person that needs to use it. How do I close it? 2. Is it necessary for squid to be sitting open, when I do not serve any web pages. Can I close the port and still have squid cache pages for my browsing? 3. I fetch mail with fetchmail which requires sendmail to send the mail to my account. Must I have sendmail running as a daemon or can I invoke sendmail when fetchmail needs it. If I shut down sendmail/smtp, I can sendmail, with sendmail -q but fetchmail fails. Basically, how do I close the smtp port but still use fetchmail? I'd be grateful for any help. And if I appear to be barking up the wrong tree, then please do let me know! :-) thanks Joss

3 4

OT(?): Apache segfaults after update to 7.1
by Pini Remo 21 May '01

21 May '01

After the long due update from 6.4 to 7.1, apache (child-procs only) segfaults upon page requests. booting: Starting httpd [ SSL PHP4 mod_perl contrib ] done log (after page request): # more httpd.error.log [Mon May 21 18:33:59 2001] [notice] Apache/1.3.14 (Unix) (SuSE/Linux) mod_fastcgi/2.2.2 mod_perl/1.24 PHP/4.0.4pl1 mod_ssl/2.7.1 OpenSSL/0.9.6 configured -- resuming normal operations [Mon May 21 18:33:59 2001] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Mon May 21 18:35:35 2001] [notice] child pid 14729 exit signal Segmentation fault (11) ... kernel: 2.2.18-SMP apache: Server version: Apache/1.3.14 (Unix) (SuSE/Linux) / Jan 19 2001 14:00:47 any hints? greets, remo pini ps: index page is default suse index page pps: if you think this message is inapropriate for this forum, ignore it or tell me privately, this list has already seen it's fair share of bull/flame/educative remarks.

2 1

Re: AW: [suse-security] ipchains masq + active ftp
by Sp0oKeR 21 May '01

21 May '01

Try modprobe ip_masq_ftp I think that you forgot this only ... Regards ... Sp0oKeR > > ---------- Início da mensagem original ----------- > De: Christian Uhde <mail(a)christian-uhde.de> > Para: suse-security(a)suse.com > Cc: > Data: Mon, 21 May 2001 23:17:50 +0200 > Assunto: Re: AW: [suse-security] ipchains masq + active ftp > Hi! > I think you need the module ip_masq_ftp.o to masquarade active ftp with > ipchains, aren't you? So it works fine for me. Perhaps take a look at > http://www.linux-firewall-tools.com/linux/. > > Hope thats you are looking for! > > Christian > > > Am Montag, 21. Mai 2001 10:09 schrieben Sie: > > Hi! > > > > >> I want to use active-ftp with some clients behind my gateway-pc > > >> (ipchains-masquerading)... (passive ftp works) > > >> How do I configure my ipchains-firewall to allow this? > > >> > > >> I hope someone can help me... > > > > PS> Deconfigure all passive ftp components and open your firewall for > > PS> tcp/20,21,1024: > > > > That didn't work for me... > > I have "allow-all-rules" for input, ouput and forward and I didn't > > deny tcp/20,21,1024... > > > > I have just deny-rules for some ports and one forwarding rule: > > ipchains -A forward -s 0.0.0.0/0.0.0.0 -d ! 192.168.0.0/255.255.0.0 -j MASQ > > > > With this I can do passive ftp - but active ftp sucks... :-( > > > > Bye. > > > > > > ----------------------------------------------------- ---------------- > > To unsubscribe, e-mail: suse-security- unsubscribe(a)suse.com > > For additional commands, e-mail: suse-security- help(a)suse.com > > ------------------------------------------------------- -------------- > To unsubscribe, e-mail: suse-security- unsubscribe(a)suse.com > For additional commands, e-mail: suse-security- help(a)suse.com > > Sp0oKeR - NsC spooker(a)bol.com.br Powered By Linux - SuSe & Slackware __________________________________________________________________________ Acesso pelo menor preço do mercado! R$ 14,90 nos 3 primeiros meses! ASSINE AGORA! http://www.bol.com.br/acessobol/

1 0

Suse 7.1 knfsd
by Selcuk Ozturk 21 May '01

21 May '01

Hi, I just installed 7.1 on a new machine and became aware of the fact that in this version the kernel nfs daemon has not been compiled with the netgroup support unlike 7.0. Is there any particular reason to this? I am using the stock 2.2.18 kernel that came on the CD. Is the updated 2.2.19 different? Is there a simple way to fix it? Thanks, Selcuk

3 3

what is the better solution?!
by Daniel Quappe 21 May '01

21 May '01

hi list, what is the more secure opportunity to "redirect" e.g. web-requests on the firewall to a dmz-webserver: - FW_FORWARD_TCP or - using the ipmasqadm-package i read about the FW_FORWARD_TCP-param in my home-7.0-firewall-suse-config. don't know the SuSEfirewall-version... are there any problems with that command?! the comment above this directive was a little bit nervous about using this...;-) many thanks in advance, bye, daniel -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

2 1

2.4.2 kernel problems
by Marko Kaening 21 May '01

21 May '01

Hi, I tried to upgrade my 2.2.17 kernel to 2.4.2. Unfortunately now the system couldn't find any module. I did a 'depmod -a', but for some reason it didn't work... Can it be that the 2.4.* kernel is not working with old (2.2.*) depmod? I noticed that the 2.4.* has a different directory structure in the /lib/modules and when I copied those modules by hand in directories like in 2.2.* I got depmod working properly. I would like to run a 2.4.* kernel because of security issues and also because I would be able to use the PROMISE IDE controller in UltraDMA mode. But it looks like compiling the kernel is not enough this time... Did anyone get into such a problem? Marko P.S.: I am sorry if this is not 100% security related! -- O _ O 0 0 ------------------m-\o/-m------------------------------------------ Dr. Marko K"aning Tel/Fax: +49-3834 554 442 / -3834 554 301 INP Greifswald email : kaening(a)inp-greifswald.de

5 5

kernel2.2.19 cannot find modules.dep
by Iain Gray 21 May '01

21 May '01

I recently ran the prescribed upgrade (i am running suse 7.0 with SMP), and although the machine ( a webserver) rebooted, it did not load the ethernet drivers (eepro100), complaining of being unable to find modules.dep. I fixed this by running depmod -a, but should I have needed to do this, or did i do stg wrong to cause this problem. I'm keen to avoid this happening again, as i'm about to move it to a colocation facility 2 hours drive away ;) ! If this needs to be done again, should i run depmod-a before reboot, just to be sure? Any ideas? thanks, Iain Gray

2 1

Ftp Problem with Suse Firewall
by Andreas M�ller 20 May '01

20 May '01

Hello NG, I've installed the WU FTPD on my Suse 7.1 Box. The ftp connect to localhost is successfull. I can list directorys, create and delete them. But if I try to to connect from the Internet to my linux box, then I can login but the LIST command is not successfull, the ftp process from the client is hanging. I think it's a problem with the firewall. In the logfile there is the following entry: May 20 17:43:42 dolly kernel: Packet log: input DENY eth1 PROTO=6 111.111.111.111: 20 217.4.191.240:65415 L=60 S=0x08 I=57760 F=0x4000 T=64 SYN (#91) But I have configured FW_FORWARD_TCP="0/0,111.111.111.111,21" I think it's no problem with active and passive ftp, because have probed the ftp command in active and passive mode, everything the same. Hope that anybody could help. Best Regards Andreas Müller

3 2

SuSE 7.1 machine hanging at the line "Starting kernel based NFS server"
by Aboubacar Dramé 20 May '01

20 May '01

HI, I added the line /sbin/ipchains-restore < /etc/ipchains.rules to the /etc/init.d/boot.local script at boot, my first machine(SuSE7.1) booted ok, and the ipchains policy restored fine, but the second test machine is hanging at the line "Starting kernel based NFS server",. What can I do to fix the problem ? Thanks again, Abou. > -----Original Message----- > From: Roman Drahtmueller > Sent: Friday, May 18, 2001 7:11 PM > To: Aboubacar Dramé > Cc: 'suse-security(a)suse.com' > Subject: Re: [suse-security] ipchains-restore script > > > > > Hi > > I'd like to run a script to retore ipchains rolls saved using > ipchains-save > > There is any sample script made for SuSE 7.1, I can run at boot to > call > > the file and restore the policy in ipchains-restore ? > > In wich directory of my SuSE linux 7.1 the script will be to get ruuned > at > > boot ? > > The scripts you're looking at are > > /sbin/ipchains-restore > /sbin/ipchains-save > > they read and write to stdio, so save your rules with > > /sbin/ipchains-save > /etc/ipchains.rules > > and read the rules at startup like > > /sbin/ipchains-restore < /etc/ipchains.rules > > the script to do that would be /etc/init.d/boot.local for a 7.1. It runs > before any network interface is up and running, which ipchains doesn't > care about and which is a good idea because you will not have some packets > getting through when your machine boots. > > > Thanks > > Abou. > > Thanks, > Roman. > -- > - - > | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | > SuSE GmbH - Security Phone: // not enable user to fly." > | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | > - -

1 0

SuSE Security Announcement: kernel (SuSE-SA:2001:18)
by Roman Drahtmueller 19 May '01

19 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: kernel Announcement-ID: SuSE-SA:2001:18 Date: Thursday, May 17th, 2000 16:40 MET Affected SuSE versions: (6.1, 6.2), 6.3, 6.4, 7.0, 7.1 Vulnerability Type: local root compromise Severity (1-10): 7 SuSE default package: yes Other affected systems: All Linux systems using a v2.2 kernel Content of this advisory: 1) security vulnerability resolved: kernel Problem, Workaround, Recommended solution, Instructions, Notes, Verification 2) Acknowledgements 3) standard appendix (further information) ______________________________________________________________________________ 1) The Problem, Workaround, Recommended solution, Instructions, Notes, Verification The Problem: The SuSE Linux kernel is a standard kernel, enhanced with a set of additional drivers and other improvements, to suit the end-user's demand for a great variety of drivers for all kind of hardware. Multiple security vulnerabilities have been found in all Linux kernels of version 2.2 before version 2.2.19. Most of the found errors allow a local attacker to gain root privileges. None of the found errors in the v2.2 linux kernel make it possible for a remote attacker to gain access to the system or to elevate privileges from the outside of the system. Thanks to Alan Cox, a summary of these errors can be found at http://www.linux.org.uk/VERSION/relnotes.2219.html . One of the numerous features in the SuSE Linux kernels is support for reiserfs, a fast, stable logging filesystem. In addition to the bugs listed at www.linux.org.uk, the SuSE Linux kernel contains a fix for a race condition between mmap(2) and write(2) in reiserfs that can expose raw data from the disk to an unprivileged user (this problem affected the ufs and ext2fs drivers in FreeBSD systems, see FreeBSD-SA-01:30.ufs-ext2fs at http://www.freebsd.org/security/) Please see the acknowledgement section 2) below for credits on hunting these bugs and fixing them. Workarounds: In order to solve the security problems, it is recommended to update the kernel to version 2.2.19. Some problems (ptrace race) can be circumvented by removing all suid and sgid bits from all binaries in the system. Since this does not help against the other errors, there is no appropriate temporary workaround against all of the known problems except for locking out users with shell access. Advanced Linux users may decide to compile and install the 2.2.19 kernel themselves by hand. This requires some experience on behalf of the administrator and may not be all satisfying because the standard 2.2.19 kernel does not contain some of the drivers that are included in the SuSE kernel (ppp over ethernet, hardware health monitoring (SMBus), reiserfs, graphics hardware acceleration modules (DRI), ...). Recommended solution: SuSE have chosen to provide update packages for the supported distributions to the newest kernels instead of supplying patched update kernel packages of the same kernel version in order to avoid confusion about whether a vulnerable version of a kernel is installed on a system or not. In addition to the clarifying effect of a visible new kernel version that is known to have all publically known security problems fixed, SAP LinuxLab (http://www.sap.com/linux/) have certified this release of the SuSE-enhanced Linux kernel version 2.2.19 with respect to stability and performance. We expect that our usership will benefit from this achievement. Currently, only kernel update packages for the Intel i386 distributions are available. The other supported architectures will have their kernel updates in their respective update directories on our ftp server. The SuSE Linux distribution 6.0 was shipped with a kernel of version 2.0. All of the SuSE Linux distributions 6.1, 6.2, 6.3, 6.4, 7.0 and 7.1 are ready for a kernel of version 2.2.19. However, since update support for the SuSE Linux distributions 6.0, 6.1 and 6.2 has been discontinued, we strongly encourage all users of these distributions to update their systems to a newer version of the SuSE Linux distribution. Please know that the full distribution can be installed from our ftp server or one of its mirrors. Experienced Linux users may choose to update their kernels by hand to the latest version 2.2.19. Step-By-Step Installation Instructions: The kernel of a Linux/Un*x system is the most critical component with relation to stability, reliability and security. By consequence, an update of that component requires some care and full attention to succeed. The following paragraphs will guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, you decide if the paragraph is needed for you or not. Please read through all of the steps down to the end. All of the commands that need to be executed are required to be run as the superuser (root). Each step relies on the steps before to be successfully completed. **** Step 1: Determine the needed RPM package Use the command rpm -qf `awk -F= '/image/{print $2}' < /etc/lilo.conf` to find the name of the kernel RPM package that is installed on your system. Get the respective kernel RPM package from the following location: ftp://ftp.suse.com/pub/suse/i386/update/<DIST>/kernel/2.2.19/ where <DIST> is the distribution version of your system (one out of 6.3, 6.4, 7.0 or 7.1). Most installations are likely to run a k_deflt kernel. To verify the integrity of the files that you need to download, see the section "Verification" near the end of this announcement. In SuSE-6.3 distributions, the above command can produce inconclusive results. This is caused by a different kernel installation procedure in this version of the SuSE Linux distribution. To select your kernel type, choose from the following options: k_eide - should be used for "exotic" IDE chipsets, mostly found on additional IDE interface adapters to PCI or ISA bus systems. k_laptop - should be used for laptops. This kernel has APM support configured. k_i386 - a kernel that should run on most i386 processors. Use this kernel package if the k_pentiu kernel will not boot. k_smp - kernel for multiprocessor systems (SMP) k_pentiu - the standard kernel. It should run on most systems. In the case that you have a self-compiled kernel running on your system, please note that most kernels for the newer distributions have APM configured. This obsoletes the need for a particular laptop kernel. k_deflt (after SuSE-6.3) should do on most modern hardware. **** Step 2: SuSE-6.3 special If you have a SuSE-6.3 system, continue to read this paragraph, otherwise jump to Step 3. In SuSE Linux version 6.3, the kernel and the kernel modules are packaged in two different packages. Both packages must be downloaded and installed. On SMP systems, the packages kernmods (-> kernmod-SMP) and k_smp are needed. On single processor systems, get the kernmod package plus the package as determined by the description in Step 1. **** Step 3: Installation of the RPM package Install the rpm package using the command rpm -Uhv <K_FILE.RPM> where <K_FILE.RPM> is the rpm package you downloaded in Step 1 (for 6.3 also Step 2, two packages!). If the RPM command complains about conflicting files or unfulfilled dependencies, use the options "--nodeps" and "--force". In this case there is no risk for the consistency of the packages on your system. **** Step 4: aic7xxx If you use an Adaptec aic7xxx SCSI host adapter, continue to read this paragraph, otherwise jump to Step 5. The new kernel comes with two versions for the Adaptec aic7xxx driver. If you have such a card, you should see the driver listed in the output from the command lsmod or you should see the adapter in the output of the command lspci The new driver is known to work reliably. However, if you encounter any problems with CDROM drives or other removeable devices (CD-RW drives, tapes, etc) after this kernel upgrade, then you should try to use the old driver which is called aic7xxx_old instead of aic7xxx. If you decide to make this change, then the steps 6 and 7 are mandatory for the update to succeed, regardless if you get back to this paragraph after your first reboot or not. To use the old driver, please use your favourite editor to edit the file /etc/rc.config. Change aic7xxx into aic7xxx_old at the line that starts with INITRD_MODULES. You should find it near the top of the file. Do not forget to save your changes. Then go to Steps 6 and 7. If you want to use the new driver, then do not change anything. **** Step 5: LVM If you use LVM, then continue to read this paragraph, otherwise jump to Step 6. If you use LVM (Logical Volume Manager) in your installation of SuSE Linux, then you need the updated lvm package from the kernel/2.2.19/ directory for your distribution as well. The package contains the userspace utilities to manage the Logical Volume Manager driver. An update package is needed because the LVM data format/structure on disk has changed with the new version of the LVM kernel driver. Install the package as usual using the command rpm -Uhv lvm-0.9.1_beta4-12.i386.rpm Be sure you have downloaded the package for the explicit version of your SuSE Linux Installation. The package names are identical for all distribution versions. WARNING: After the first boot with the new kernel you will not be able to downgrade to older versions of LVM any more. **** Step 6: initrd Upon kernel boot (after lilo runs), the kernel needs to use the drivers for the device (disk/raid) where the root filesystem is located. If this driver is not compiled into the kernel, it is supplied as a kernel module that must be loaded _before_ the root filesystem is mounted. This is done using a ramdisk that is loaded along with the kernel by lilo (See next Step). This ramdisk, called "initrd", must be generated using the command mk_initrd The modules as configured in the variable INITRD_MODULES from /etc/rc.config (See Step 4) are being added to the initrd. Without the "mk_initrd"-call your system might not boot any more. **** Step 7: lilo lilo is responsible for loading the kernel image and the initrd ramdisk image into the system and for transferring control over the system to the kernel. Therefore, a proper installation of the bootloader (by calling the program lilo) is essential for the system to boot (!). Manually changed settings in /etc/lilo.conf require the admin to make sure that /boot/vmlinuz is listed in the first "image" line in that file. Verify that the line starting with initrd= is set to initrd=/boot/initrd Execute lilo and you should see your label in an output like Added linux * Every other output should be considered an error and requires attention. If your system managed to reboot before the upgrade, you should not see any additional output from lilo at this stage. **** Step 8: SuSE-7.0 special If you have a SuSE Linux 7.0 distribution, then continue to read this paragraph, otherwise jump to Step 9. During testing of the 2.2.19-SuSE Linux kernel, we have found an error in the glibc (shlibs) package of the SuSE Linux 7.0 distribution. The error might result in readdir(3) calls to return -EIO to the user program due to incorrect handling of the return value of getdents(2) from the kernel. This bug mostly appears on NFS-mounted filesystems when commands such as tar(1) are used. We have prepared update packages that solve this specific problem. Former security updates are included in this package, of course. Determine which packages you need: See the output of the command rpm -q shlibs libc libd nssv1 It should not be necessary to update a package that is not installed. Select the needed update packages and download them from the following list of URLs ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/shlibs-2.1.3-193.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/nssv1-2.1.3-193.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/7.0/d1/libc-2.1.3-193.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/7.0/d2/libd-2.1.3-193.i386.rpm !!! !!! WARNING: !!! !!! After download and before installation of the glibc packages, the system should be brought to single user mode ("init 1"). If this is not suitable for operational reasons, then please keep the system as calm as at all possible during the update of the shlibs and nssv1 packages. In particular, do not run any shell scripts or any other processes that execute other binaries. Stop the cron and at services, and shut down your MTA. Suspend the execution of active processes by killing them with the -STOP signal and let them resume their work after the installation of the shlibs and nssv1 packages with a -CONT signal. After verifying that the right conditions are in place, install the packages using the command rpm -Fhv nssv*.rpm shlibs*.rpm rpm -Fhv <rest> Afterwards, execute the command ldconfig to update the cache for the dynamic linker. NOTE: updating shared libraries in the running system requires enough space on the root and /usr filesystem to keep both versions of the shared libraries on the disk. The old libraries will be deleted, but the files continue to use diskspace until they are not used by any processes any more. (See Step 9). Similar considerations apply for the the memory consumption of the system. **** Step 9: reboot Reboot your machine for the new kernel to boot and therefore become active. Make sure that all of the above steps have completed successfully. Shutdown and reboot using the command shutdown -r now or init 6 Notes: a) After the upgrade, you might notice kernel messages upon execution of an NFS mount command: silence kernel: nfs warning: mount version older than kernel These messages are complaints that the mount(8) command needs to be upgraded. The mount(8) command is contained in the package "util" ("util-linux" for SuSE-7.1) - we will provide update packages for the "util" ("util-linux" for SuSE-7.1) package. The change is mostly a cosmetic nature and does not have any impact on the security or the stability of the system. b) The kernel sources are contained in the RPM kernel/2.2.19/lx_sus22-2.2.19.SuSE-25.i386.rpm in each distribution update tree. The kernel documentation is in the package kernel/2.2.19/lx_doc22-2.2.19.SuSE-25.i386.rpm and installs to the base path /usr/share/doc/kernel/. c) The directory kernel/misc/ in each distribution tree contains the .config files, the spec and changes file as well as the compilation output for the respective kernel, each in a directory where it belongs to. In addition, the sources for the lvm package can be found in the lvm directory as appropriate. Known problems: * The kernel modules for the cipe and the freeswan packages are not contained in the kernel RPM packages. If you use these packages, then you should wait with the kernel update until the kernel modules for these packages are available, or you could recompile the kernel modules yourself (See section Notes b). Please read the section 2) of the upcoming SuSE security announcements for the location of the cipecb.o and ipsec.o kernel modules. Verification: All RPM packages are gpg-signed using the build(a)suse.de SuSE packaging key that can be found in the toplevel directory of the first CD on SuSE-7.1 and younger, as well as at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de (this key is signed by security(a)suse.de) All files that are needed or referred to in this announcement have their md5 sums listed in the file ftp://ftp.suse.com/pub/suse/i386/update/<dist>/kernel/MD5SUMS . These files are signed by security(a)suse.de in the file MD5SUMS.sig. Since there are 150 files, we do not send the md5sums with the mail this time. ______________________________________________________________________________ 2) Acknowledgements SuSE Security wishes to express their gratitude for the following people who have invested their time for the bugs that are subject of this announcement: Chris Evans Solar Designer Alan Cox David Miller for spotting and fixing the problems as listed in the 2.2.19 release notes Chris Mason for fixing the reiserfs mmap/write race condition Sven Berkvens and Marc Olzheim for spotting the mmap/write race condition in FreeBSD drivers that affects reiserfs in Linux ______________________________________________________________________________ 3) standard appendix: SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =============================================== SuSE's security contact is <security(a)suse.com>. =============================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 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 iQEVAwUBOwPjCney5gA9JdPZAQHnowf/Z4oGIAWzSdnXcxhoUot4UABzH8X2rUfD 9caheLboumIR+gJ8XwuJzxkgl06wfZ6+4SF+WyKovEzJNYN2NjrZOtVYVukc/h9l txnJ5MQ0vtllge45eBGI5r+MZnfk5l107U/Az5/7hZuw7bUTZP991HCPHfnlUDAd YErqQ1KkSg2waTd5dqUjjSXGNjHP8dXG4RAwzqEXQ7PyQmVfwh6YQ0JpJLqXSKM/ Fx9sRaQXVX+Ujx7GI4TA/nPt7SIrLJhBKloV/En2tjHYcq6HiPiyO0a3jwD70wBf 9J3FYdPyWrarwKRqETBDfy+d7mWxgYmisPcZTeGgmK4ekakUSZfcEg== =uQx9 -----END PGP SIGNATURE-----

4 3

ipchains-restore script
by Aboubacar Dramé 18 May '01

18 May '01

Hi I'd like to run a script to retore ipchains rolls saved using ipchains-save There is any sample script made for SuSE 7.1, I can run at boot to call the file and restore the policy in ipchains-restore ? In wich directory of my SuSE linux 7.1 the script will be to get ruuned at boot ? Thanks Abou.

2 1

suspicious apache-log-entries?
by Daniel Quappe 18 May '01

18 May '01

hi list, got this logs in my apache-logs MANY, MANY times...;-) (>1000) "GET / HTTP/1.1Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/msword, application/vnd.ms-excel, application/vnd.ms-powerpoint, */*" any ideas about this (hack-attempt)?! greets and bye, daniel -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

3 2

ping over a masquerading firewall
by Guido 18 May '01

18 May '01

Hello List, I'm trying to build a firewall with ipchains which also should masqerade an internal net. The problem is that I can't ping from inside to the outside. I was able to ping from the inside to the firewall and from the firewall to the outside. If I use a "firewall" like ipchains -F ipchains -P input ACCEPT ipchains -P output ACCEPT ipchains -P forward ACCEPT ipchains -A forward -i $EXTERNAL_INTERFACE -s $INTERN -j MASQ I'm able to ping from inside to outside. In my "real" firewall, I tried it the same way like ssh, which works fine, but ssh has tcp as protokoll and not icmp like ping. My configuration for ssh is the following which works fine ipchains -A input -i $INTERNAL_INTERFACE -p tcp -s $INTERN $SSH_PORTS \ -d $ANYWHERE 22 -j ACCEPT ipchains -A output -i $INTERNAL_INTERFACE -p tcp ! -y -s $ANYWHERE 22 \ -d $INTERN $SSH_PORTS -j ACCEPT ipchains -A output -i $EXTERNAL_INTERFACE -p tcp -s $EXT_IPADDR $UNPRIVPORTS \ -d $ANYWHERE 22 -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p tcp ! -y -s $ANYWHERE 22 \ -d $EXT_IPADDR $UNPRIVPORTS -j ACCEPT ipchains -A forward -i $EXTERNAL_INTERFACE -p tcp -s $INTERN $SSH_PORTS \ -d $ANYWHERE 22 -j MASQ I don't want to use a general rule like ipchains -A forward -i $EXTERNAL_INTERFACE -s $INTERN -j MASQ, And converting the rule from ssh/tcp to ping/icmp doesn't work. (I think it's also because of sending ICMP 8 and receiving ICMP0) TIA Guido

1 0

copy of passwd ...
by Thorsten Marquardt 18 May '01

18 May '01

Hi, what from etc do I have to copy to a second machine to get all the user-accounts accessable without doing further changes? Thanx Thom -- ------------------------------------------------------------------- bye bye (c) by Thom | Thorsten Marquardt | EMail: THOM(a)kaupp.chemie.uni-oldenburg.de | Member of the pzt project. | http://kaupp.chemie.uni-oldenburg.de/pzt -------------------------------------------------------------------

5 5

mod_ssl Update for S.u.S.E. Linux 7.0 available?
by Michael Ströder 18 May '01

18 May '01

HI! I'm using S.u.S.E. Linux 7.0. I've downloaded updated RPMs of Apache 1.3.19 and several modules but I can't find a mod_ssl RPM which fits that version of Apache. Am I missing something? Ciao, Michael.

2 4

problems with DoS part II
by Gediminas Grigas [home] 18 May '01

18 May '01

Hello, Thanks to all for responses. That kiddie still abuses my server like 10 queries/sec. It seems like its not proxy`ing - Hes somehow fakes his IP`s, becouse its endless list, and some of those IP`s (~8-10%) basicly does not exists (or does not respond to ping/traceroute; I hardly can belive that somebody closed ICMP and left open proxy or even worse...) So, i made my script to recognize his calls, and exit fast, so damage is now kind of minimal (like 5% of CPU and full logs of trash). However its sad to think that there is not much i can do, except wait when this guy gets bored. Is there ANY chances fight against spoofed IP`s? Its surely one way call, however, server is very vulnerable to this. What if such guy gets on leased line - not on dial-up. He could make 100 calls/second with almost no chance to trace. Is there any tool to block/recognize/delay/check for spoofed IP`s? Maybe those spoofed packets could be logged on he`s ISP`s gw router? (I think i know which ISP`s service he`s using) Still i cant understand why that router routes such packets becouse none of them belongs to that network. I`m not a big expert in routing, but its seems weird to me. Original story was: ----------------------------------------------------------------- Hello, I`m recently under heavy attack from an l33t hax0r kiddie. Hes using lots of proxies to access my banner exchange (i mean real lots - hundrets and hundrets) - he was able to add new hosts faster than i was able to lock them out wit ipchains (like 10 hosts/min or so). So its ended by that i changed input policy to DENY and set ACCEPT only for lithuanian ISP`s (about 40 major subnets). But thats not solution, becouse system is now locked from outside Lithuania. However that kiddie started abusing my exchange from his real IP (an biggest ISP dial-up service). I cannot lock-out this ISP becouse i would lock 10.000 users as well. So i`m forced to monitor whats happening everytime and lock him once in a while, or server load will jump from 0.4 to 10.00 on my P-III 1Ghz host. I connot do anything in legal way - becouse we dont have anything in our law system against "l33t hax0rs", besides that isp has terrible support and monopoly, so it will probably even dont bother to respond to my requests. My question would be - is there an tool which could run with apache to automaticly lock host for some time if it tryies access system more that 10 times per minute or so? Could anybody pass me an idea how to fight against such attacks? On other hand - i remember someone once said that he has an "legal request to ISP against hackers" or so... some nice warning text to send to ISP on detection of intrusion or DoS. Could you please refer me to it? Sorry for my broken english. Hope you got the matter. P.S. Host running SuSE 7.1 with 2.2.x kernel Thanks ---------------------------------------------------------------------- -- Best regards, Gediminas mailto:gedas@kryptis.lt

3 2

WAY OFFTOPIC! Job Opportunity for Matrix 2 & 3!
by Nix 18 May '01

18 May '01

This has nothing to do with SuSE Security, but this is a post that went to the Sydney Linux Users Group mailing list a few minutes ago. The money is ok but not brilliant, but if there is anyone who wants something VERY cool for their resume, this looks like a load of fun. For reference, Fox Studios is about 5-10 min from central Sydney.... Cheers -Nix >Delivered-To: slug(a)slug.org.au >From: "Steve Cronan" <steve(a)webdev.net.au> >To: <slug(a)slug.org.au> >X-Mailer: Microsoft Outlook Express 5.50.4133.2400 >Subject: [SLUG] Job Opportunity for Matrix 2 & 3! >Sender: slug-admin(a)slug.org.au >X-BeenThere: slug(a)slug.org.au >X-Mailman-Version: 2.0.4 >List-Help: <mailto:slug-request@slug.org.au?subject=help> >List-Post: <mailto:slug@slug.org.au> >List-Subscribe: <http://lists.slug.org.au/listinfo/slug>, > <mailto:slug-request@slug.org.au?subject=subscribe> >List-Id: General Discussions <slug.slug.org.au> >List-Unsubscribe: <http://lists.slug.org.au/listinfo/slug>, > <mailto:slug-request@slug.org.au?subject=unsubscribe> >List-Archive: <http://lists.slug.org.au/archives/slug/> >X-Original-Date: Fri, 18 May 2001 17:16:45 +1000 >Date: Fri, 18 May 2001 17:16:45 +1000 > >Hi Everyone >Been on the list a long time, but never posted! > >I'm currently working at fox studios on the next 2 matrix movies >and I'm looking for someone to assist me. > >It will involve support of a network containing Pc's, Mac's & a couple >Linux servers (Redhat & FreeBSD). >The opportunity to program in php and mysql as well as leaning every >aspect of the movie industry. > >I'm looking for someone with network support, programming and database >experience as well as having the right personality. > >It will be a contract for a year, working 8am-6:30pm at fox studios for >$50-$60K depending on experience. >Its a small IT department so you will have to be very organised! > >Please email me your CV's asap because I'm look to start someone in about >a week. > >Thanks >Steve Cronan > >Digital Assets Manager >Matrix 2 Productions Viel Spaß Nix - nix(a)susesecurity.com http://www.susesecurity.com

1 0

firewall2
by Alexander Grujic 18 May '01

18 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi List :-) I have a problem with firwall2 for iptables. When I run the final Susefirewall2_final start script i get the following error messages : Starting Firewall Initialization: (phase 3 of 3) iptables v1.1.2: Unknown arg `--syn' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--sport' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--syn' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--sport' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--syn' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--sport' Try `iptables -h' or 'iptables --help' for more information. the manpage says --sport is an alias for --source-port and --syn should be ok too. My firewall2.rc.config is attached to this mail ... it is still under construction but i have no idea what causes the above error messages :-( Help would be appreciated, Ciao, Alex. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7A9G6X1OUiCutGtcRApjuAJ4gc+NhcaOXMh8te7a1201J4nhJAACcDf/p Z/Spv0xcLJOyUDLirkozZ28= =d304 -----END PGP SIGNATURE-----

2 1

RE: [suse-security] problems with DoS part II
by Reckhard, Tobias 18 May '01

18 May '01

> Is there ANY chances fight against spoofed IP`s? > Not really on your side, unfortunately. You can exclude large portions of the possible IPv4 address space as they are reserved -- there's a list on the same FTP site as the definitive assigned port listings, but I'm not sure how accurate it actually is.. -- but the attacker can still pick valid IP addresses at will that you don't want to simply deny access to your server. The only real way to stop spoofing is for everyone to perform egress filtering to stop spoofed packets from leaving one's network. If I've got 1.2.3.4/24 assigned to me, then only packets with a source address of 1.2.3.0 through 1.2.3.255 should be allowed to leave my network (actually those two probably shouldn't, but anything between them should). This is something ISPs should do as well and that's where you could perhaps succeed. > Its surely one way > call, however, server is very vulnerable to this. > What if such guy gets on leased line - not on dial-up. He could make > 100 calls/second with almost no chance to trace. > What if he uses a DDoS with many well-connected zombies? You are right, you are experiencing a real problem. But unfortunately, you can't solve it on your end, you need the cooperation of his ISP, I'm afraid. > Is there any tool to block/recognize/delay/check for spoofed IP`s? > Well, if they're not actually assigned or are unused at the time, they won't respond to the SYN/ACK packet your server sends back to it and the connection will time out after a while. However, this causes resource consumption on your server, as the half-open connection is kept in the TCP state table until the timeout expires. Perhaps that timeout can be reduced. However I'm not sure if that is your problem or if the packets are saturating your link to your ISP. In the latter case, there's nothing you can do. The packets would need to be dropped before they reach your suspectedly small pipe, i.e. at his ISP or at your's. Of these two, only his ISP can effectively (and easily, for the matter) identify the spoofed packets, so that's the natural point where the operation should take place. > Maybe those spoofed packets could be logged on he`s ISP`s gw router? (I > think i know which ISP`s service he`s using) > If his ISP is using Cisco routers, then a simple ACL (access control list) such as: access-list 1 permit 10.20.30.0 0.255.255.255 interface BRI0 ip access-group 1 in would allow the subnet 10.20.30.0/24, which I assume him to have, into the router and the implicit deny rule would drop anything else. > Still i cant understand why that router routes such packets becouse > none of them belongs to that network. > I`m not a big expert in routing, but its seems weird to me. > It's very unfortunate from a security point of view and the only argument against the egress filtering on their border routers (or those that border their 'peering transit zones') is the hit in performance associated with access lists. However, people like your friend can happily abuse the absence of filtering and create illegal packets that cause load on the ISP's equipment as well... Good luck Tobias

1 0

Re: [suse-security] SuSE Security Announcement: kernel (SuSE-SA:2001:18) (fwd)
by Roman Drahtmueller 17 May '01

17 May '01

---------- Forwarded message ---------- From: Roman Drahtmueller <draht(a)suse.de> To: Jacobo González Simón <jacobo(a)tyc.es> Date: Thu, 17 May 2001 22:21:41 +0200 (MEST) Subject: Re: [suse-security] SuSE Security Announcement: kernel (SuSE-SA:2001:18) > > Where is lvm-0.9.1_beta4-12.i386.rpm ?. I have suse 7.0 and i can´t find > it. I only can find lvm-0.8-0.i386.rpm at > ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1. It's in the same directory as the kernel RPMs. ftp://ftp.suse.com/pub/suse/i386/update/7.0/kernel/2.2.19 > > Thanks > You're welcome. Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> "Caution: Cape does not | SuSE GmbH - Security enable user to fly." | Nürnberg, Germany (Batman Costume warning label) | - -

1 0

[suse-security] Open Port
by Markus Kohli 16 May '01

16 May '01

Hi List! I just ran a "nmap -sS localhost", and what I got was the following: Starting nmap V. 2.53 by fyodor(a)insecure.org ( www.insecure.org/nmap/ ) Interesting ports on localhost (127.0.0.1): (The 1519 ports scanned but not shown below are in state: closed) Port State Service 22/tcp open ssh 80/tcp open http 631/tcp open unknown 6000/tcp open X11 Nmap run completed -- 1 IP address (1 host up) scanned in 0 seconds Now my question: what is that port 631 -> unknown. What could this be? Is it something I should take care of, or is it "normal"? Thanks in advance! Markus P.S: Have a look @ www.handybutler.ch __________________________________________________________________________ I believe the technical term is "Oops!"

4 3

somebody subscribed in the list has list in spam filter
by Michael Rauter 16 May '01

16 May '01

Hello after my last posting, I received this mail. Maybe this person (olaf.kionka(a)trianet.de) should be removed from list, because list postings will be rejected... Regards M. Rauter -----Ursprüngliche Nachricht----- Von: FETCHMAIL-DAEMON(a)localhost.trianet.de [mailto:FETCHMAIL-DAEMON@localhost.trianet.de] Gesendet: Mittwoch, 16. Mai 2001 10:44 Our spam filter rejected this transaction.

3 3

SuSE Security Announcement: cron (SuSE-SA:2001:17) (resent)
by Roman Drahtmueller 16 May '01

16 May '01

-----BEGIN PGP SIGNED MESSAGE----- As a result of a package rebuild, the package for the SuSE-7.1 Intel i386 distribution is not available under the URL as listed below. The listed package was named "cron-3.0.1-297.i386.rpm". This package also fixed the mentioned problems with the package. We are resending this announcement with the correct pathnames and md5sums. Thank you for your understanding, Roman Drahtmüller. ______________________________________________________________________________ SuSE Security Announcement Package: cron-3.0.1-296 Announcement-ID: SuSE-SA:2001:17 (resent) Date: Tuesday, May 15th, 2001 15:30:00 CEST Affected SuSE versions: 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 7 SuSE default package: yes Other affected systems: All UN*X systems using this package Content of this advisory: 1) security vulnerability resolved: crontab problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The crontab program is running setuser-id root and invokes the editor specified in the EDITOR environment variable, usually vi. If crontab discovers that the format of the edited file is incorrect, it executes the editor again but fails to drop its root privileges before. Therefore it is possible to execute arbitrary commands as root. It has been fixed by properly dropping the privileges before executing the editor. This bug was found by Sebastian Krahmer. A possible temporary workaround is to remove the suid bit of the /usr/bin/crontab program: chmod -s /usr/bin/crontab. If you change the mode, you should also do so in the files /etc/permissions*. A permanent solution for the problem is to update the cron package from our ftp server. Download the update package from locations desribed below and install the package with the command `rpm -Uhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig file.rpm', independently from the md5 signatures below. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/cron-3.0.1-335.i386.rpm 606d2c5d67a851ce4e1907146a184cd4 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/cron-3.0.1-335.src.rpm 57805850a0f4fcf8afa99326d3071fd0 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/cron-3.0.1-316.sparc.rpm 4db292d0276badc0ae58fd6aeaab64c0 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/cron-3.0.1-316.src.rpm 16facdbbce03d43fa05d540b810d8636 AXP Alpha Platform: The SuSE-7.1 AXP-Alpha Edition does not suffer from this problem. PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/cron-3.0.1-295.ppc.rpm 589e8575bbbee29a07319f5c5ada9bcc source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/cron-3.0.1-295.src.rpm ff747e2aee85a53e3a30827b33383a7d ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - The man program running setuser-id 'man' suffers from format string and bufferoverflow bugs. Updates are available on the ftp server at the usual location, the announcement will follow shortly. ______________________________________________________________________________ 3) standard appendix: SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =============================================== SuSE's security contact is <security(a)suse.com>. =============================================== Regards, Sebastian Krahmer ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 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 iQEVAwUBOwEziXey5gA9JdPZAQFgmQf/cQz+X/6/iNYOSs7DxN5jK+j5Z2nc83LY 1knhQlpNvgMxeG8m8G1mi8b1B8cKaZStr9dPd9M4EnOzB9KAzdf2Xeajn9+CcLhW LhhVc3lcZfhhBE0L/ZPlu2Cz78vCP3jDu9XaD4e4f2h/rcL9Efs/ezAePP2x5tFP luyXP6BEd4xwMyaLUAesVUxyjPlBH1PhMDj04mX1T+M/3gV2F4GHDzqjPYtlAmE3 qYAFJxg/5g9X0D8ehBiwnBC6ccPLzQqvnM31GyDzwomWnTRp0rQoNVq5uT63Q4Jc rRHQQeTk8Al7TEcufUFblkTo1WGplgPsJGX8yUTfh5pHuFGcCdVqaA== =PTuO -----END PGP SIGNATURE-----

4 6

kernel source for k_deflt-2.2.19
by jan meyer 16 May '01

16 May '01

hi, does somebody know if/when the kernel source for the recently updated k_deflt-2.2.19 SuSE-Kernel is available/will be released ? I've searched the ftp-servers with no result. thanx jan meyer

5 4

scanlogd messages
by Togan Muftuoglu 16 May '01

16 May '01

I am receiving scanlogd messages from ftp.gwdg.de there is a wget ftp download scrip there is running yet this is the first time I am getting messages like this the downloading machine is masquared should the inner ip be as my real ip. Can someone give a guidance what to check for TIA -- Togan Muftuoglu Unusual System Events =-=-=-=-=-=-=-=-=-=-= May 16 15:41:34 gardiyan scanlogd: 134.76.11.100:20 to 192.168.1.3 ports 2549, 2550, 2551, 2552, 2553, 2554, 2555, ..., ??r??uxy, TOS 08, TTL 41 @15:40:50 May 16 15:52:11 gardiyan scanlogd: 134.76.11.100:20 to 192.168.1.3 ports 2715, 2716, 2717, 2718, 2719, 2720, 2721, ..., ??r??uxy, TOS 08, TTL 41 @15:51:26 May 16 15:53:12 gardiyan scanlogd: 134.76.11.100:20 to 192.168.1.3 ports 2744, 2745, 2746, 2747, 2748, 2749, 2750, ..., ??r??uxy, TOS 08, TTL 41 @15:52:28 May 16 15:59:00 gardiyan /USR/SBIN/CRON[10460]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) ----- End forwarded message ----- -- Togan Muftuoglu

2 2

mail-messup
by Roman Drahtmueller 16 May '01

16 May '01

Sorry for the mess with the mails that went to the list. Sebastian and I were discussing the accident that happened with the cron announcement. Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -

1 0

problems with TLD ...
by patric illi 16 May '01

16 May '01

Cheers Linux freaks I have a general question about TLD and ccTLD ( top level domains ), I am sorry for this post but I found no other resource to ask ! We have a two DNS Servers ( ns1.intersoft-networks.ch and ns2.intersoft-networks.ch ). Till now we only registered ".ch" domains. That was working fine. Some days ago I unsuccessfully tried to register a ".net" domain. The output always shows me an Error. My question now; is it possible that a TLD can't point to a ccTLD Nameserver ? So would it work if I register a TLD and configure it as master server ? thx in advance ! patric illi

1 0

SuSE Firewall
by Faessen Jean-Paul 16 May '01

16 May '01

Hi; Finally started (had to find out how first) my SuSE Firewall in SuSE 7.0. Of course,want to configure. So tried to run/open config in Vim and in text console. /etc/rc.conf.d/firewall.rc.config in text console: access debnied. So I run chmod u+x /etc/rc.conf.d/firewall.rc.config nothing happens. Went to Vim doesn't know /etc/ So,how to configure my freshstarted Firewall? Can I use kfirewall to do this? thank's..; Jean-Paul

4 5

do I need util-linux-2.11b-15.i386.rpm?
by omar castillo 16 May '01

16 May '01

i'm upgrading to the new 2.2.19 kernel due to security reasons. do I need util-linux-2.11b-15.i386.rpm?

3 2

Unwanted guest is trying to relay
by Togan Muftuoglu 16 May '01

16 May '01

I had this in my logs isguzar sendmail[5670]: f4FKqSd05670: ruleset=check_rcpt, arg1=<telu(a)telus.net>, relay=user115.mdi.ca [207.230.250.115], reject=550 5.7.1 <telu(a)telus.net>... Relaying denied Ok AFAIU he couldnot get the relay and from=<j6hd6hegh34(a)yahoo.com>, size=0, class=0, nrcpts=0, proto=SMTP, daemon=MTA, relay=user115.mdi.ca [207.230.250.115] but this one I did not get did he managed to use me as his relay or not. If he did what steps can I take to make life harder to outsiders I am using the sednmail 8.11.2-4 that comes with 7.1 -- Togan Muftuoglu

2 2

RE: [suse-security] somebody subscribed in the list has list in s pam filter
by Franziskus Scharpff 16 May '01

16 May '01

Hello Michael, maybe your Provider uses an open Relay for Maildelivery. I had this also a year ago, when Isend some mails via Strato to an account wich checks for open relay for Spam-Preventing. Franziskus > -----Original Message----- > From: Michael Rauter [mailto:rauter@ctos.de] > Sent: Mittwoch, 16. Mai 2001 10:59 > To: suse-security(a)suse.com > Subject: [suse-security] somebody subscribed in the list has list in > spam filter > > > Hello > > after my last posting, I received this mail. Maybe this > person (olaf.kionka(a)trianet.de) should be removed from list, > because list postings will be rejected... > > Regards > M. Rauter > > -----Ursprüngliche Nachricht----- > Von: FETCHMAIL-DAEMON(a)localhost.trianet.de > [mailto:FETCHMAIL-DAEMON@localhost.trianet.de] > Gesendet: Mittwoch, 16. Mai 2001 10:44 > > > Our spam filter rejected this transaction. > >

1 0

Re: [suse-security] Unwanted guest is trying to relay
by Togan Muftuoglu 16 May '01

16 May '01

* Paul Miles <paul.miles(a)padlondon.com> [010516 01:14]: > Throw away sendmail and install Exim. (http://www.exim.org) > > Exim is so much easier to setup, hence more likely to configure a secure > setup/ Many thanks for the informative answer to my question After checking my logs and reading the sendmail op.txt that was located in the docs directory I do not now think the person was able to do send a mail since SuSE sendmail is compiled with no relay option the unwanted guest could not achieved what he dreamed. -- Togan Muftuoglu

1 0

vanished user accounts?
by Night Watcher 15 May '01

15 May '01

Hi all, i have the following problem on my three suse 7.0 and one 7.1 box, after a while when i wanted to log in under my test account, the message was, cannot switch to homedir (no access or something) i relogged in under my root account and then i wanted to correct this problem, i used midnight commander to look where the directory and user permissions of the /home/test account were, these stuff were correctly displayed: i found out that all the permissions still belonged to user test, this was very strange in my opinion, i thought well that is not right but reinstall might help, so i did that, and then my other three boxes suddenly displayed the same problem, all after 2 to 3 weeks, i am pretty sure that i didn't change the userpermissions on the machines ( i can make an mistake but not on 4 machines :)*) so i am guessing that it's an bug, removing the users and readding them does NOT work, so anyone, can u help me? or someone of the SuSE team : is this correcT? met vriendelijke groeten, with kind regards, Remko JC @ irc.super-chat.nl (tech-Admin) NightWatcher @ irc.grunn.org / irc2.grunn.org (IRCoperator) [DrL] Member [Grunn] Coders [Zyber] /* hope the day after you die is an nice one */ niets uit deze mail mag worden gecopieerd of aan derden gelezen laten worden zonder toestemming van de auteur. al deze emails vallen onder briefgeheim. wetboek van strafrecht. Nothing from this mail may be duplicated of may be read by others then the target name. you need authorization from the owner to duplicate it. these mails are secure and restricted confirming the dutch book of law _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

4 5

pop3 endcodes mail with netscape and suse7.x
by ingo＠cimdata.de 15 May '01

15 May '01

hi list, heare in my brillant english, a question: Wher coud I find some infos over: how I encodes the pop3 protocol (ssh?) so that I coud use encode mail with netscape? I coud'nt find something over it at www.obenssh.org, isint it the right cryptosoftwaere? -- []___¸ ######-\ O_-_-_O-\

3 2

ip_masq_h323
by Togan Muftuoglu 15 May '01

15 May '01

Hi, Suse kernel's do not have the ip_masq_h323 module, although someother distribution do have it. Is there any security reasons that the others have not noticed yet or is it just a preference by SuSE. If I compile it byself will I create headaches for myself if the answer to the first part is by preference. TIA -- Togan Muftuoglu

2 3

ipchains problem ?
by stephane parenton 15 May '01

15 May '01

hi, I have a SuSE 7.0 linux box that runs as DNS, filter and gateway. The filter is quite simple. and I 'experiencing troubles... The public ip adress is 62.161.161.253, and the internal lan is nat'ed and use the 192.168.0.x adresses. The computers from the lan can see almost all the internet except the sites that have ip's beginning with 62.*... What can be the trouble ?.... here's the filter i use. #!/bin/sh echo 1 > /proc/sys/net/ipv4/ip_forward /sbin/ipchains -F forward /sbin/ipchains -P forward DENY route add -net 62.161.161.192 netmask 255.255.255.224 gw 62.161.161.222 tr0:0 route add 192.168.0.3 gw 62.161.161.253 route add default gw 62.161.161.254 /sbin/ipchains -A forward -s 0.0.0.0/0.0.0.0 -d 62.161.161.194/255.255.255.255 -j ACCEPT /sbin/ipchains -A forward -s 0.0.0.0/0.0.0.0 -d 62.161.161.195/255.255.255.255 -j ACCEPT /sbin/ipchains -A forward -s 62.161.161.194/255.255.255.255 -d 0.0.0.0/0.0.0.0 -j ACCEPT /sbin/ipchains -A forward -s 62.161.161.195/255.255.255.255 -d 0.0.0.0/0.0.0.0 -j ACCEPT /sbin/ipchains -A forward -s 192.168.0.0/255.255.0.0 -d 0.0.0.0/0.0.0.0 -j MASQ TIA Stephane Parenton

3 2

Re: [suse-security-announce] SuSE Security Announcement: cron
by Nix 15 May '01

15 May '01

At 10:48 PM 15/05/2001, you wrote: > Sebastian Krahmer has found the bug. It has been fixed by properly > dropping > the privileges before executing the editor. Nice work Sebastian. I've been waiting for the SuSE announcement since I saw your name on bugtraq. Good to see that SuSE's extra auditing pays off. Viel Spaß Nix - nix(a)susesecurity.com http://www.susesecurity.com

1 0

SuSE Security Announcement: cron
by Sebastian Krahmer 15 May '01

15 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: cron-3.0.1-296 Announcement-ID: SuSE-SA:2001:17 Date: Tuesday, May 15th, 2001 14:30:00 CEST Affected SuSE versions: 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 7 SuSE default package: yes Other affected systems: All UN*X systems using this package Content of this advisory: 1) security vulnerability resolved: crontab problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The crontab program is running setuser-id root and invokes the editor specified in the EDITOR environment variable, usually vi. If crontab discovers that the format of the edited file is incorrect, it executes the editor again but fails to drop its root privileges before. Therefore it is possible to execute arbitrary commands as root. Sebastian Krahmer has found the bug. It has been fixed by properly dropping the privileges before executing the editor. A possible temporary workaround is to remove the suid bit of the /usr/bin/crontab program: chmod -s /usr/bin/crontab. If you change the mode, you should also do so in the files /etc/permissions*. A permanent solution for the problem is to update the cron package from our ftp server. Download the update package from locations desribed below and install the package with the command `rpm -Uhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig --nogpg file.rpm', independently from the md5 signatures below. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/cron-3.0.1-297.i386.rpm b51f3331fff5dac8474a51a1e7d22454 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/cron-3.0.1-297.src.rpm 495f7f5df30d28a0c6b078a9773fc799 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/cron-3.0.1-316.sparc.rpm 4db292d0276badc0ae58fd6aeaab64c0 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/cron-3.0.1-316.src.rpm 16facdbbce03d43fa05d540b810d8636 AXP Alpha Platform: The SuSE-7.1 AXP-Alpha Edition does not suffer from this problem. PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/cron-3.0.1-295.ppc.rpm 589e8575bbbee29a07319f5c5ada9bcc source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/cron-3.0.1-295.src.rpm ff747e2aee85a53e3a30827b33383a7d ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - The man program running setuser-id 'man' suffers from format string and bufferoverflow bugs. Updates are currently being built. ______________________________________________________________________________ 3) standard appendix: SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =============================================== SuSE's security contact is <security(a)suse.com>. =============================================== Regards, Sebastian Krahmer ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 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 iQEVAwUBOwElIney5gA9JdPZAQHJ+Qf/Z6Q8ofh8j807uLChfv42lCkWmvOCfJLb S4Vg32n3P5oyFcb1J2qHUt+Dv1NlLuGGqsiUlCTNa6xqlt7pWBWQPtyRGnBUGDNh t+VjFBDzILMdIA5A1U25+JtChPXUXYJsvl/KCefoxfXpbiae3J5xqT9lPwe/Djez ZLBdsowmUV7s5lJKUyxrmHhTapLT4ksnunJ5bCmo/z86NMFFGvefeclcEFZ9/q7n rFX48x3vh4psCTJqRVFJoSFAYVfHuXDNuMj59p17JbK3TlVV63rFlk/+zSB+HlnU ddnacjnYfsQhdOhY/QJ68byk/GsusJTbDSHDFobFNgbEVyUmUFC3QQ== =OH6U -----END PGP SIGNATURE-----

3 4

Antwort: Re: [suse-security] Kernel security
by Alexander Schwartz 15 May '01

15 May '01

I think SuSE has the problem that is uses a patched (enhanced) kernel with IPSEC etc. enabled that make it more complicated than necessary. There are distributions like debian who keep things simple and that came up with a recent kernel a long time ago. Using debian, you can update your system with two command (apt-get update / apt-get upgrade) -- never seen that working on a SuSE-machine. Makes administration easy and reduces TOC. Mit freundlichen Grüßen Alexander Schwartz

2 1

Re: [suse-security] Driver Licence
by Alexander Schwartz 15 May '01

15 May '01

Hmm... a driver licencse covers use of cars on normal roads and in cities. But when you "drive" your "box" on the internet, its more like driving in the sahara and rainforest at the same time. A.

1 0

problems with DoS
by Gediminas Grigas [home] 15 May '01

15 May '01

Hello, I`m recently under heavy attack from an l33t hax0r kiddie. Hes using lots of proxies to access my banner exchange (i mean real lots - hundrets and hundrets) - he was able to add new hosts faster than i was able to lock them out wit ipchains (like 10 hosts/min or so). So its ended by that i changed input policy to DENY and set ACCEPT only for lithuanian ISP`s (about 40 major subnets). But thats not solution, becouse system is now locked from outside Lithuania. However that kiddie started abusing my exchange from his real IP (an biggest ISP dial-up service). I cannot lock-out this ISP becouse i would lock 10.000 users as well. So i`m forced to monitor whats happening everytime and lock him once in a while, or server load will jump from 0.4 to 10.00 on my P-III 1Ghz host. I connot do anything in legal way - becouse we dont have anything in our law system against "l33t hax0rs", besides that isp has terrible support and monopoly, so it will probably even dont bother to respond to my requests. My question would be - is there an tool which could run with apache to automaticly lock host for some time if it tryies access system more that 10 times per minute or so? Could anybody pass me an idea how to fight against such attacks? On other hand - i remember someone once said that he has an "legal request to ISP against hackers" or so... some nice warning text to send to ISP on detection of intrusion or DoS. Could you please refer me to it? Sorry for my broken english. Hope you got the matter. P.S. Host running SuSE 7.1 with 2.2.x kernel Thanks -- Best regards, Gediminas Grigas Tel.: (2)226036; (86) 55362 Techninis direktorius Fax.: (2)627986 UAB "Dizaino kryptis" A.Jaksto 9-233, Vilnius, Lietuva 2001 mailto:gedas@kryptis.lt

5 4

man segfault
by Togan Muftuoglu 15 May '01

15 May '01

Hi I have read this on the securityfocus >Heap Based Overflow of man via -S option gives GID man. > Due to a slight error in a length check, the -S option to > man can cause a buffer overflow on the heap, allowing redirection of > execution into user supplied code. > man -S `perl -e 'print ":" x 100'` >redhat 7.0 with man-1.5h1-10 (default > package) and earlier. but running it on suse with man-2.3.10d69s-190 I also get the same thing $ man -S `perl -e 'print ":" x 100'` sometext Segmentation fault -- Togan Muftuoglu

1 0

Using SuSEfirewall for the internal lan
by Togan Muftuoglu 15 May '01

15 May '01

Hi I am getting 1 of probes to port 80 since yesterday to my home network which consists of SuSE 7.1 firewall/router serving 3 1 which are also running SuSE 7.1 and 1 Windows 98 laptop. Although firewall/router has ipchains blocking for all ports except forwarding port 25 can using ipchains firewall in the masquareded 5 increase my security and if so how will it affect the performance. I am planning to use Marc's SuSEfirewall-4.6 but I could not figure out what is my dev_world if I just say eth0 then it will get the address of the NIC but that is not how the packets are coming to the 0 lan since it is masquared. Any guidance is 0 TIA -- Togan Muftuoglu

1 0

Obtuse smtp
by Togan Muftuoglu 14 May '01

14 May '01

Hi I have enabled fort portwarding for port 25 on the firewall. I have the sendmail running on the masquareded machine 192.168.1.3. I have edited the inetd.conf as it says in the INSTALL smtp stream nowait root /usr/sbin/smtpd smtpd I have restarted inetd started smtpfwdd and this is what I am receiving in the messages smtp/tcp(2) bind:adress already in use ???? 1)I have chagned the sendmail option to -q10m in sendmail.rc.config 2) I could not find an init script for smtpfwdd 3) In order to use the anitspam rules it says smtpd should be compiled with CHECK_ADDRESS=1 is this the case for Suse TIA -- Togan Muftuoglu

2 2

Re: [suse-security] Kernel RPMs
by Roman Drahtmueller 14 May '01

14 May '01

> > Hi together, > > ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/RPMs/ > > 7. To avoid complaints from the kernel about an old mount, update the > > util-linux (util for 7.0 and older), too, using rpm -Uhv <packname>. > > is the util-package "util-2.11b-0.i386.rpm" correctly packaged? > I'm missing 'setserial' after update. Right. This needs to be changed. Thanks for the note. > > Peter Wiersig > Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> "Caution: Cape does not | SuSE GmbH - Security enable user to fly." | Nürnberg, Germany (Batman Costume warning label) | - -

3 3

RE: [suse-security] vanished user accounts?
by Marco van Beek 14 May '01

14 May '01

You may also find that the system is saving the username/group as a number, and simply recreating the user doesn't mean they inherit the old permissions. I have noticed that when using YaST it often deletes and re-adds when you edit a username or group. Marco van Beek. -----Original Message----- From: Peer-Christoph Mettelem [SMTP:Peer-Christoph.Mettelem@bezreg-muenster.nrw.de] Sent: Monday, May 14, 2001 11:53 AM To: suse-security Subject: RE: [suse-security] vanished user accounts? never use test as username, dirname or something. It's a command and may cause problems. -----Original Message----- From: Night Watcher [mailto:theeagle84@hotmail.com] Sent: Monday, May 14, 2001 12:43 PM To: suse-security(a)suse.com Subject: [suse-security] vanished user accounts? Hi all, i have the following problem on my three suse 7.0 and one 7.1 box, after a while when i wanted to log in under my test account, the message was, cannot switch to homedir (no access or something) i relogged in under my root account and then i wanted to correct this problem, i used midnight commander to look where the directory and user permissions of the /home/test account were, these stuff were correctly displayed: i found out that all the permissions still belonged to user test, this was very strange in my opinion, i thought well that is not right but reinstall might help, so i did that, and then my other three boxes suddenly displayed the same problem, all after 2 to 3 weeks, i am pretty sure that i didn't change the userpermissions on the machines ( i can make an mistake but not on 4 machines :)*) so i am guessing that it's an bug, removing the users and readding them does NOT work, so anyone, can u help me? or someone of the SuSE team : is this correcT? met vriendelijke groeten, with kind regards, Remko JC @ irc.super-chat.nl (tech-Admin) NightWatcher @ irc.grunn.org / irc2.grunn.org (IRCoperator) [DrL] Member [Grunn] Coders [Zyber] /* hope the day after you die is an nice one */ niets uit deze mail mag worden gecopieerd of aan derden gelezen laten worden zonder toestemming van de auteur. al deze emails vallen onder briefgeheim. wetboek van strafrecht. Nothing from this mail may be duplicated of may be read by others then the target name. you need authorization from the owner to duplicate it. these mails are secure and restricted confirming the dutch book of law _________________________________________________________________ ________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. ----------------------------------------------------------------- ---- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

The curiose Mysql Problems
by Thomas Nowak 14 May '01

14 May '01

Hi list, May its a little bit OT but I don't understand the follow facts: First of all I usinig SuSE 6.4 and mysql. A nice feature of SuSE is the cleaning script which deletes file from the /tmp directory if they are not owned by root. The first Problem is, that mysql has in the standard installation his socket file in this location which is owned by the mysql user so this file is removed after one week. ( I havend found this error in the SuSE Support DB ! ) So I have put the socket file to /var/run ( In my opinion it should the perfect place ) :-) With "/sbin/init.d/mysql start" all is OK, but after each restart mysql will not automatic start. I had found that this is becaus the /var/run directory ist owned by root.uucp and has 775 pemissions, so mysql can't create the socket file as user mysql! But what is the great difference betwwen the start of the script /sbin/init.d/mysql from init and by "hand" as root In both cases I should be root or not? Bye Thomas

1 0

Kernel RPMs
by Roman Drahtmueller 14 May '01

14 May '01

Hi together, As some of you may have seen, I've just put the kernel RPMs for the Intel i386 distributions 6.3, 6.4, 7.0 and 7.1 in place. You can find them at ftp://ftp.suse.com/pub/suse/i386/update/6.3/kernel/RPMs/ ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/RPMs/ ftp://ftp.suse.com/pub/suse/i386/update/7.0/kernel/RPMs/ ftp://ftp.suse.com/pub/suse/i386/update/7.1/kernel/RPMs/ for download. The announcement is waiting to be published, but you get the preliminary version. A kernel update is not rocket science, but it is more sensitive than exchanging a package that you have never heard of for a stupid tempfile race. You should carefully follow each step before you reboot your machine for the freshly installed kernel to become active. We decided to update the kernel packages on all supported distributions to the most recent version 2.2.19 instead of fixing the known security bugs with patches. Tons of other problems have been fixed with the release of the 2.2.19 kernel, and we believe that this is the most stable kernel in the 2.2 release row. To find out which package to download use the command rpm -qf `awk '/^image =/ { print $3 }' < /etc/lilo.conf` Additional stuff can be found in the respective misc/ directory under ftp://ftp.suse.com/pub/suse/i386/update/<distvers>/kernel/misc, such as the .config used for kernel configuration, the output of the compile run and the specfile for the RPM packages. To install the kernel, proceed as follows: 1. Download the kernel rpm for your installation. 2. Install the kernel using the command rpm -Uhv k_deflt.rpm or whatever the command necessary for your installation (see above). It may be necessary to either deinstall the old kernel package and modules package or to use the "--force --nodeps" commandline options for rpm in addition to -Uhv. 3. If you use an Adaptec aic7xxx scsi host adapter, please change "aic7xxx" in INITRD_MODULES on top of /etc/rc.config to read "aic7xxx_old". 4. Execute mk_initrd An error indicates that the initrd is not written to disk. It is possible that your machine will not boot if you have a scsi system. 5. Execute lilo If you did not change the line starting with "initrd" in /etc/lilo.conf, then the freshly created init-Ramdisk will be loaded together with the kernel by lilo upon system boot. This initrd contains the drivers that are necessary for the kernel to mount the root filesystem of the system. On scsi systems, you can't boot without the modules contained in the initrd. 6. If you use lvm, update the lvm package as well. It is contained in the same directory as the kernel rpms. 7. To avoid complaints from the kernel about an old mount, update the util-linux (util for 7.0 and older), too, using rpm -Uhv <packname>. 8. The 7.0 distribution contained a bug in the glibc that is triggered by 2.2.19. The bug may result in mounted nfs filesystems to report -EIO when listing directories in some rare cases. Get the update package for shlibs (the other sub-packages are not needed) from i386/update/7.0/a1/shlibs.rpm, and install it, again, using "rpm -Uhv <packname>". Keep your machine in a quiet state during this upgrade; if at all possible, bring the machine into single user mode, using the command "init 1" Execute "ldconfig" after completion of the rpm command. 9. Execute init 6 or shutdown -r now # which is the same without warning ...and if it fails, drop me a mail, please. Thanks, Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -

7 15

https
by Dietmar Strasdat 14 May '01

14 May '01

Hello suse-security-list, i have installed a suse 7.0 with squid 2.3 stable 3 and Marcs firewall script 4.5. For ftp is proxy suite installed and so long it works fine. But i can t connect to a https url. in firewall.rc.config: FW_SERVICES_INTERNAL_TCP="22 25 53 80 110 119 443 3128" Any hints? -- Best regards, Dietmar mailto:earthmate@gmx.net

1 0

Re: [suse-security] shadow doesn't work anymore with kernel 2.2.19
by Togan Muftuoglu <toganm 13 May '01

13 May '01

* Thomas Schweikle <tschweikle(a)fiducia.de> [010514 02:30]: > In this case someting must have gone wrong updating KDE, Kernel, and X. Any > hint, where I might look? I do not know the answer and its better to hit reply all so the list gets the mail as well incerasing your chance to get answer -- Togan Muftuoglu

1 0

shadow doesn't work anymore with kernel 2.2.19
by Thomas Schweikle 13 May '01

13 May '01

Hi! I've noticed shadow not working anymore since I've installed kernel 2.2.19. Passwords changed will be entered into /etc/passwd directly, even if the shadow-package is installed. Anyone else noticed this? -- Thomas

2 1

Re: [suse-security] Kernel RPMs
by Nix 13 May '01

13 May '01

I just like to congratulate Roman, Hubert and SuSE for a job well done. I have just applied the kernel update rpms to a couple of my machines including my Toshiba Notebook, which if anything was going to have problems, it would have, and everything went perfectly smoothly. I didn't even have to do a --force etc Note: I am actually running self compiled 2.4.4 kernels on all boxes, so I would not have been surprised to have something complain. As some of you may have noticed, Roman's email had a timestamp of "Date: Sat, 12 May 2001 06:32:57 +0200 (MEST)" It is this level of dedication that SuSE should be praised for, and is the reason why I recommend SuSE Linux to anyone I meet. Roman, (unlike some previous announcements) your email had a step by step installation procedure taking into account several different possibilities. This i great, and it's exactly this level of attention to detail that puts SuSE linux above any other OS that I had the misfortune to have to use. (Including some "other" Linux distros that exhibit almost as many unexplainable quirks as the Microsoft world.) Many Thanks --- Nix - nix(a)susesecurity.com http://www.susesecurity.com

2 1

2.2.19 kernels out - apparently - md5sum please
by dproc 12 May '01

12 May '01

I see that a set of 2.2.19 kernel (and module) rpms and source rpms just arrived in the update/6.3/kernel of ftp.suse.com (Although I guess it will be 24h wait to see it on the sourceforge mirror, and ftp.suse.com is VERY busy tonight.) I wait for a signed md5sum to be posted so I can verify I am not a victim of dns poisoning and a fake site+binary. When will this be posted? (I think the rpms are themselves now signed , but I can't figure out how to use rpm --checksig with my pgp keyring, so I want to verify the old way.) HALOF, dproc

2 2

FTP Server and Updates, a little bit OT
by Torsten Mueller 12 May '01

12 May '01

Hey, i have only a little point which i can't understand. In my local LAN i provide a FTP Server with the the Suse install dirs to easily install other clients with Suse. To always have the most up to date binaries i mirror the changes from a mirror-Server of ftp.suse.com (the update dir) Are there problems, if i copy the update rpm's directly into the "ftp install hierarchy" ? And if there are no problems, wouldn't it be better to handle it also on the public ftp servers ? I know it's a little bit OT, but everyone want the newest and more secure software as simple as possible. Sorry for my english. Greetings Torsten

1 0

Re: [suse-security] Kernel security
by Martin Peikert 11 May '01

11 May '01

Martin Fahlgren <martin(a)as3-1-1.hn.g.bonet.se> wrote: > > > On 8 May 2001, Martin Peikert wrote: > >> Martin Fahlgren <martin(a)as3-1-1.hn.g.bonet.se> wrote: > >> > This is probably the "worst" exploit up to now and a big problem >> > for all networks with many login accounts (web sites, schools, >> > universities etc). >> > >> > So the options I have are >> > 1) Compile and install my own kernel >> > 2) Disable logins until SuSE comes with a new kernel >> > 3) Switch to a distribution which provides the necessary updates >> >> You are kidding, aren't you? > > Why do you think that I'm kidding? We are talking about a very nasty > exploit which I already has been used in practice, and measures > must be taken to stop it. > > Do you have other options better than "my" 3 alternatives. I can > see another alternative: Kernel 2.4. It has also problems, but > should not be directly vulnerable to the eploit we are discussing now. As H D Moore wrote: It's your own fault if you get rooted. If you are not able to compile a kernel by yourself with the patches you need, go and read the Kernel-HOWTO, the files in /usr/src/linux/Documentation and some man pages instead of moaning in public. Martin -- martin.peikert(a)innominate.com innominate AG project manager the linux architects dipl. math. http://www.innominate.com tel: +49-30-308806-0 fax: -77 gpg: http://innominate.org/gpg/mpe.gpg

16 32

RE: [suse-security] tripwire
by Marco van Beek 11 May '01

11 May '01

Nothing, I suspect, other than you might have preset mount options set in fstab that conflict, and you might confuse everybody when they can't find the CD-ROM when mount tells them it is already mounted !!! I seem to remember that there was a wire you could cut/switch on older hard drive cables that would turn a disk into read-only. A friend of mine used it to turn an old PC into a sort of diskless set-up. If that still works, you could use an old HD on a spare IDE channel, with a key or hidden switch, mount it in the right place, and be able to update the tripwire database at will. BTW, running tripwire does involve a certain amount of upkeep if you try to cover too much, of have a lot of file (legitimate) changes, like users uploading to web space. Regards, Marco -----Original Message----- From: Gerhard Sittig [SMTP:Gerhard.Sittig@gmx.net] Sent: Friday, May 11, 2001 7:44 AM To: 'suse-security(a)suse.com' Subject: Re: [suse-security] tripwire On Thu, May 10, 2001 at 21:18 +0100, Marco van Beek wrote: > > I have installed Tripwire on a SuSE 7.1 server, and found that > tw-config needs to end up in /var/adm/tripwire, and after > initialising, the database needs to be moved from > /var/adm/tripwire/bin/databases to /var/adm/tripwire/db for the > command to work without any additional commands. You wouldn't > run a production machine like this, you would add a switch to > the command line after moving the db to some read only media. What keeps you from mounting the media with the tripwire database as well as the configuration under this very directory? :> virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig(a)gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

Samba 2.0.9 für 7.1
by Sven Hansen 11 May '01

11 May '01

Hi, wo bleibt eigentlich das neue Samba für 7.1? Auf dem Server ist es nur für 7.0 und ältere Versionen. Soll wohl ein Security-Fix sein. -- _, Regards, (_ ,_)ven Hansen.

2 1

strange seccheck result
by Bjoern Engels 11 May '01

11 May '01

Hi this is a result of Marc's daily seccheck script (on a SuSE 7.0 / kernel 2.2.16): ... * Changes (+: new entries, -: removed entries): - ipchains root UDP *:3828 * Changes (+: new entries, -: removed entries): + squid root UDP *:4441 ... Why should ipchains be able to open a udp port ? Do you think this a sign of being cracked and the ipchains executable being tampered with evil code ? Bjoern Engels LANWORKS AG --------------------------------------------- E-Mail: Bjoern Engels <bengels(a)lanworks.de> www.lanworks.de ---------------------------------------------

1 0

RE: [suse-security] tripwire
by Marco van Beek 11 May '01

11 May '01

I have installed Tripwire on a SuSE 7.1 server, and found that tw-config needs to end up in /var/adm/tripwire, and after initialising, the database needs to be moved from /var/adm/tripwire/bin/databases to /var/adm/tripwire/db for the command to work without any additional commands. You wouldn't run a production machine like this, you would add a switch to the command line after moving the db to some read only media. Hope this helps, Regards, Marco van Beek -----Original Message----- From: root [SMTP:schoenborn-boehm@t-online.de] Sent: Thursday, May 10, 2001 7:24 PM To: 'suse-security(a)suse.com' Subject: [suse-security] tripwire Hello, can anyone help me, install tripwire_ASR_1.3.1-1 on SuSE 7.1? I just get on the point where to initialize tripwire. Than an error occurs??? like this: "couldn`t open /tripwire/config/tw-config no such file or directory. Permission is just set to 755. In graphical login (KDE2) I can see my files.What`s the matter with this? perhaps OSI 8 ???? schoenborn-boehm(a)t-online.de --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

2 1

user authentication on sendmail
by Philipp Snizek 11 May '01

11 May '01

Hi all, How can user authentication be set up on a sendmail server? Thank you Philipp

2 1

Re: [suse-security] Kernel security
by Harold ! 10 May '01

10 May '01

While were on this subject is there a Linux equiv of a MCSE for Linux? > > > Martin > P.S.: I like your car example. If you want to drive a car, you >need > a driving license ;-) > >Drivers Licenses only cover how to USE the car. Not how to fix it. > >-Kurt > > >--------------------------------------------------------------------- To >unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional >commands, e-mail: suse-security-help(a)suse.com > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

2 1

Re: [suse-security] suse-firewall?!?
by Armin Schöch 10 May '01

10 May '01

Hei Jesse ! No, this is not my script and I don't deserve any praise for it (and I'm not working for SuSE though I think they are definitely doing a very good job !!). This script is by Marc Heuse from SuSE who is the maintainer of the firewall scripts. It says so at the end of the homepage but only in very small letters. Sorry for not pointing you to the start page of Marc Heuse's homepage: http://www.suse.com/~marc/ Once more, Marc Heuse deserves your thank yous, not me ! Bye, Armin > Hey! Hey! This is great! > Thanks a lot Armin, by the way is this your script? > ...well seems like it from your page, i loved your > page and your buddy's too. Keep up the good work for > SuSE. I'm a die hard fan of SuSE so i'm always > interested in learning anything that's about SuSE... > once again thanks for your help! > > --- Armin_Schöch <armin.schoech(a)mail1.uni-rostock.de> > wrote: > > > > Hello Jesse ! > > > > > I just want to know how to access the > > > suse-firewall. I currently use ipchains and a few > > > other tools. I wonder if SuSE-Firewall is better, > > if > > > so i would like to try it. So if anyone can tell > > me > > > how to access it and put it up or some > > > informaiton/docs/text on it, it would be highly > > > apriciated. > > > > Have a look at http://www.suse.com/~marc/SuSE.html > > There you will find the newest versions of the SuSE > > firewall > > scripts. There is also a link to some documentation. > > > > Good luck ! > > > > Armin ------------------------------------------------------------------------ Armin Schöch at the office: Institut für Atmosphärenphysik Ziolkowskistr. 10 / 63 Schlossstraße 6 D-18059 Rostock D-18225 Kühlungsborn Tel. +49-(0)381-4005781 Tel. +49-(0)38293-68-102

1 0

suse-firewall?!?
by Jesse yep 10 May '01

10 May '01

Hi, all I just want to know how to access the suse-firewall. I currently use ipchains and a few other tools. I wonder if SuSE-Firewall is better, if so i would like to try it. So if anyone can tell me how to access it and put it up or some informaiton/docs/text on it, it would be highly apriciated. __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/

2 1

tripwire
by schoenborn-boehm＠t-online.de 10 May '01

10 May '01

Hello, can anyone help me, install tripwire_ASR_1.3.1-1 on SuSE 7.1? I just get on the point where to initialize tripwire. Than an error occurs??? like this: "couldn`t open /tripwire/config/tw-config no such file or directory. Permission is just set to 755. In graphical login (KDE2) I can see my files.What`s the matter with this? perhaps OSI 8 ???? schoenborn-boehm(a)t-online.de

1 0

RE: [suse-security] SuSEfirewall2 & port forwarding
by Reckhard, Tobias 10 May '01

10 May '01

> When I´m right, it must be an PREROUTING SNATchain not a POSTROUTING to > forward incomming e.g http to your server. > Better yet, use PREROUTING DNAT. SNAT is POSTROUTING only. Cheers, Tobias

2 1

suse-linux vs commerical firewall
by Guenther Sommer 10 May '01

10 May '01

is suse-linux equipped with squid, free/swan, ... compareable (in security) with an commerical firewall like checkpoint, raptor, ... yes, i know, the question is not very exactly, but i'd be interested in your humble opinion. greetings, guenther sommer.

2 1

Help, please?
by Geordon VanTassle 10 May '01

10 May '01

I know that this is an ICMP packet, but what kind is it? I've got about 75 of these things coming in, and I'd like to know what they are. TIA Geordon Ok, here is the IPChains log bit: May 9 22:50:29 moat kernel: Packet log: input REJECT eth0 PROTO=1 [remoteIP]:12 [localIP]:0 L=56 S=0x00 I=2630 F=0x0000 T=28 (#71)

2 1

SuSEfirewall2 & port forwarding
by Greisberger Christophe 10 May '01

10 May '01

Hi! I have 4 web servers, and want to move them behind a firewall. I want to give their IP to the firewall, and then redirect the incoming requests to the servers, which would have non-official IP addresses (e.g. 192.168.0.x) Is there any possibility to do this with SuSEfirewall2? Backward masquerading doesn't allow to specify interfaces, so that the traffic on one interface would be redirected to an IP, and the traffic on another interface should be redirected to another one. Else, is there any possibility to add user rules to SuSEfirewall? I think that something like this should work, right? iptables -t nat -A POSTROUTING -o eth1 \ --to-source <public_address_1>:80 --to-destination <private_addr_1>:80 -j SNAT Thanks in advance Christophe

3 2

Re: [suse-security] Message Log Question
by Martin Brecher 09 May '01

09 May '01

Dear Mr. Seifried, - I know that you are far more expertised on security related topics than I may ever be, but that's not a reason to flame off people which are new on this list (at least at active posting) and still unexperienced. Apart from the fact that I actually read the howtos and a lot of documents (maybe I've overseen s.th., maybe because English is not my native language), all the howtos do not include the _opinions_ and _tips_ of all those expertised people on this list (which are often quite helpful! - thanks). >I'm not offended by you looking for knowledge. I am offended by you badgerting >the list when many fine documents exist that, oddly enough, are what I used to >learn from. ipmasq howto, firewall howto, you may want to read them. I will no longer reply to this thread, but wanted to make clear what my intention was. Please, if you find me offending, ignore my posts. If someone things I am disturbing the list or am employing wrong means in my mails, please tell me privately and I will quit asking dump questions on this list. Sincerly, Martin Brecher --- And you all know, security Is mortals' chiefest enemy. (Shakespeare, Macbeth)

1 0

Re: [suse-security] Please help for FreesWan VPN script setup on SuSe 7.1
by idallen＠freenet.carleton.ca 09 May '01

09 May '01

>From: Aboubacar Dramé <abodr(a)xchg.medisys.ca> May 9, 10:45 >I use the sample script below (writed for the Red Hat distribution) [...] ># Copyright (C) 1997, 1998, 1999 Robert L. Ziegler Salut! Be careful with the Ziegler scripts. They contain many errors, including typing mistakes in variable names. You will find these by running the scripts using "sh -u" or by changing "#!/bin/sh" to "#!/bin/sh -u". Ziegler's 2000 book on building Linux firewalls had extensive errata that made many (most?) of the tables in the book useless unless you applied all the corrections. I haven't checked the script you posted; but, the firewall script used in his book, posted on his web site (a year old), still hadn't been fixed when I looked in January. -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen(a)ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/ College professor at: http://www.algonquincollege.com/~alleni/ Board Member, TeleCommunities CANADA http://www.tc.ca/

1 0

Re: [suse-security] Message Log Question
by Martin Brecher 09 May '01

09 May '01

On Wed, 9 May 2001 12:20:05 +0200 (CEST), Markus Gaugusch wrote: >> IMHO a packet filter like ipchains can only decide what to do with a >> packet by looking at this very packet. So if you get a packet without >> SYN Flag set from somewhere to , say, port 61500, how can ipchains >> know if it's a response to a masqueraded request or a response to a >> request from al local app using this port ? >It is not decided by ipchains, but the kernel. The kernel knows the >masqueraded connections, and can differ between local and masqueraded >connections therefore. But the input chain will be called, too. If you want to filter masq'd connections and local connections on the firewall box seperately (i.e. to heavily restrict direct access to and from the firewall machine) having them in the same port range makes no sense, or am I wrong somehow? - Martin > >hth >Markus > >-- >_____________________________ /"\ >Markus Gaugusch ICQ 11374583 \ / ASCII Ribbon Campaign >markus(a)gaugusch.dhs.org X Against HTML Mail > / \ > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com > > --- The Internet was invented as a highly dependable, high-speed, distributed, secure, and powerful network so that in the event of a nuclear crisis, military officials would always have access to pornography.

2 2

Please help for FreesWan VPN script setup on SuSe 7.1
by Aboubacar Dramé 09 May '01

09 May '01

Hi ! I am trying to configure a script to securise a Linux FreesWan on SuSE 7.1 Professional edition , I use the sample script below (writed for the Red Hat distribution), I use the script to replace the /etc/rc.config.d/firewall.rc.config, but it does not work, what changes can I do on the script to adapt it for the SuSe 7.1 version to make the ipchains work ? Thanks for your help. Aboubacar Dramé Montreal, Quebec, Canada #!/bin/sh # # ---------------------------------------------------------------------------- # Last modified by Gerhard Mourani: 10-10-2000 # ---------------------------------------------------------------------------- # Copyright (C) 1997, 1998, 1999 Robert L. Ziegler # # Permission to use, copy, modify, and distribute this software and its # documentation for educational, research, private and non-profit purposes, # without fee, and without a written agreement is hereby granted. # This software is provided as an example and basis for individual firewall # development. This software is provided without warranty. # # Any material furnished by Robert L. Ziegler is furnished on an # "as is" basis. He makes no warranties of any kind, either expressed # or implied as to any matter including, but not limited to, warranty # of fitness for a particular purpose, exclusivity or results obtained # from use of the material. # ---------------------------------------------------------------------------- # # Invoked from /etc/rc.d/init.d/firewall. # chkconfig: - 60 95 # description: Starts and stops the IPCHAINS Firewall \ # used to provide Firewall network services. # Source function library. . /etc/rc.d/init.d/functions # Source networking configuration. . /etc/sysconfig/network # Check that networking is up. if [ ${NETWORKING} = "no" ] then exit 0 fi if [ ! -x /sbin/ipchains ]; then exit 0 fi # See how we were called. case "$1" in start) echo -n "Starting Firewalling Services: " # Some definitions for easy maintenance. # ---------------------------------------------------------------------------- # EDIT THESE TO SUIT YOUR SYSTEM AND ISP. EXTERNAL_INTERFACE="eth0" # Internet connected interface # LOCAL_INTERFACE_1="eth1" # Internal LAN interface # LOOPBACK_INTERFACE="lo" # Your local naming convention IPADDR="my.ip.address" # Your IP address # LOCALNET_1="192.168.1.0/24" # Whatever private range you use IPSECSG="my.ipsecsg.address" # Space separated list of remote VPN gateways FREESWANVI="ipsec0" # Space separated list of virtual interfaces ANYWHERE="any/0" # Match any IP address # NAMESERVER_1="my.name.server.1" # Everyone must have at least one # NAMESERVER_2="my.name.server.2" # Your secondary name server # ------------------------------------------------------------------ # OUTGOING TRACEROUTE # ------------------- #ipchains -A output -i $EXTERNAL_INTERFACE -p udp \ # -s $IPADDR $TRACEROUTE_SRC_PORTS \ #-d $ANYWHERE $TRACEROUTE_DEST_PORTS -j ACCEPT # ---------------------------------------------------------------------------- # Unlimited traffic within the local network. # All internal machines have access to the firewall machine. # ipchains -A input -i $LOCAL_INTERFACE_1 -s $LOCALNET_1 -j ACCEPT # ipchains -A output -i $LOCAL_INTERFACE_1 -d $LOCALNET_1 -j ACCEPT # ---------------------------------------------------------------------------- # FreeS/WAN IPSec VPN # ------------------- # If you are using the FreeSWAN IPSec VPN, you will need to fill in the # addresses of the gateways in the IPSECSG and the virtual interfaces for # FreeS/Wan IPSEC in the FREESWANVI parameters. Look at the beginning of # this firewall script rules file to set the parameters. # IPSECSG is a Space separated list of remote gateways. FREESWANVI is a # Space separated list of virtual interfaces for FreeS/Wan IPSEC # implementation. Only include those that are actually used. # Allow IPSEC protocol from remote gateways on external interface # IPSEC uses three main types of packet: # IKE uses the UDP protocol and port 500, # ESP use the protocol number 50, and # AH use the protocol number 51 ipchains -A input -i $EXTERNAL_INTERFACE -p udp \ -s $IPSECSG -j ACCEPT ipchains -A output -i $EXTERNAL_INTERFACE -p udp \ -d $IPSECSG -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p 50 \ -s $IPSECSG -j ACCEPT ipchains -A output -i $EXTERNAL_INTERFACE -p 50 \ -d $IPSECSG -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p 51 \ -s $IPSECSG -j ACCEPT ipchains -A output -i $EXTERNAL_INTERFACE -p 51 \ -d $IPSECSG -j ACCEPT # Allow all traffic to FreeS/WAN Virtual Interface ipchains -A input -i $FREESWANVI \ -s $ANYWHERE \ -d $ANYWHERE -j ACCEPT ipchains -A output -i $FREESWANVI \ -s $ANYWHERE \ -d $ANYWHERE -j ACCEPT # Forward anything from the FreeS/WAN virtual interface IPSEC tunnel ipchains -A forward -i $FREESWANVI \ -s $ANYWHERE \ -d $ANYWHERE -j ACCEPT # Disable IP spoofing protection to allow IPSEC to work properly echo 0 > /proc/sys/net/ipv4/conf/ipsec0/rp_filter echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter # ---------------------------------------------------------------------------- ;; stop) echo -n "Shutting Firewalling Services: " # Remove all existing rules belonging to this filter ipchains -F # Delete all user-defined chain to this filter ipchains -X # Reset the default policy of the filter to accept. ipchains -P input ACCEPT ipchains -P output ACCEPT ipchains -P forward ACCEPT ;; status) status firewall ;; restart|reload) $0 stop $0 start ;; *) echo "Usage: firewall {start|stop|status|restart|reload}" exit 1 esac exit 0

1 0

Re: [suse-security] Kernel security
by christian.burri＠synecta.ch 09 May '01

09 May '01

mmmhkay let me add my babbling =) IMHO, one of the best solutions to have *good* security on a box is someone watching its logfiles and maybe have running a network traffic analyzer. I do have a box on the internet, and I do have a few users on it (basically, I give away shells, sometimes, for those poor ppl that are stuck with a dialup connection), and there were few attempts to root my box. Neverthless, every single try to root the box was defended either by myself watching the culprit, or by my co-admin. If you have a trustworthy coadmin that can keep an eye on your box while you cannot (work, school, whatever..), that might be worth more then spending 100'000 bucks on the latest stateful firewall (and another 30k to train your network engineers on it). Also, I found it very crucial to be careful about *who is granted shell access. If you dont run many services on your box, surely no portmapper or suchlike, then your chance of getting rooted has already reduced by an order of magnitude. Infact, almost all the root attempts I had came from local users. The very first time one of my boxen got rooted was because I like gave out an account. It took them dudes like 45 seconds to gain root (rootcron.sh on a SuSE 6.2....h0h0h0!). But like, because I was using the elite "w" command, I was instantly able to spot that there were two logins from different IPs to the account I gave out, so a lill "shutdown", followed by a reinstall from trusted media solved my problem ;-) So, as for a conclusion: 1) get a trustworthy co-admin 2) be careful about who gets shell accounts on your box NB: I like to thank Marc from SuSE (I think it was him, correct me if Im wrong =) for auditing the SuSE version of wu-ftpd! Cheers Chris Burri jun. Systems- & Network Engineer Synecta Informatik AG Zwinglistrasse 3 9000 St. Gallen Switzerland .-. /v\ L I N U X // \\ >Phear the Penguin< /( )\ ^^-^^

1 0

Re: [suse-security] Message Log Question
by Andreas Bätz 09 May '01

09 May '01

On Wednesday 09 May 2001 12:20, Markus Gaugusch wrote: > > IMHO a packet filter like ipchains can only decide what to do with a > > packet by looking at this very packet. So if you get a packet without > > SYN Flag set from somewhere to , say, port 61500, how can ipchains > > know if it's a response to a masqueraded request or a response to a > > request from al local app using this port ? > > It is not decided by ipchains, but the kernel. The kernel knows the > masqueraded connections, and can differ between local and masqueraded > connections therefore. Yes, but given the following scenario: 1) A client behind a firewall is masqeraded, and it uses a program that connects to a server outside (masqueraded by the firewall). The reply from the server goes to the port which is used by the firewall kernel for masquerading (say 61500). In my input chain on the firewall I have to ACCEPT packets to this port. 2) On the firewall there is a program which tries to connect to the internet, but should not be allowed to (for whatever reason, may be a backdoor or trojan or what or even just for added security). Now, say this program uses the local port 61500 for outbound connection (assuming it is not used by the masquerading this time). If I want to block responses to this program, on the input chain I have to DENY packets to this port. So, in my firewall script I have no possibility to decide if an incoming packet to a port in this range is to be allowed or not. If I have seperate port ranges for local and masqueraded connection, this decision can be based on the port range. OTOH, I don't know if a program cannot be told to use a port outside the local portrange. I suppose it can, in which case this discussion would be somewhat useless. Andreas Baetz ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been scanned for the presence of computer viruses. **********************************************************************

2 1

RE: [suse-security] SuSEfirewall2 & port forwarding
by Greisberger Christophe 09 May '01

09 May '01

Hum, thanks. It would have been easier to tell me to read the IP-Masquerade-HOWTO :-) But that's not what I wanted. This documentation is for ipportfw & ipchains, not netfilter... and I wanted to know if it's possible to use the SuSEfirewall2 to achieve this... Again, thank you anyway. Christophe

1 0

Kernel 2.4.0 to 2.4.4 update Doku?
by Mueller, Thomas 09 May '01

09 May '01

Hi list, hope anyone can help a newbie like me updating my Kernel 2.4.0 under SuSE Linux 7.1 to 2.4.4 and compiling it? Or is there any documentation out there on the net where I can help myself? Any help, tipps and hints are appreciatet Thanx in Advance Tom

1 0

Re: [suse-security] SuSEfirewall2 & port forwarding
by Oscar Garcia 09 May '01

09 May '01

>From: "Greisberger Christophe" <greisby(a)zenon-media.com> >To: <suse-security(a)suse.com> >Subject: [suse-security] SuSEfirewall2 & port forwarding >Date: Wed, 9 May 2001 14:26:00 +0200 > >Hi! > >I have 4 web servers, and want to move them behind a firewall. >I want to give their IP to the firewall, and then redirect >the incoming requests to the servers, which would have >non-official IP addresses (e.g. 192.168.0.x) >Is there any possibility to do this with SuSEfirewall2? > >Backward masquerading doesn't allow to specify interfaces, so >that the traffic on one interface would be redirected to an IP, >and the traffic on another interface should be redirected to >another one. > >Else, is there any possibility to add user rules to SuSEfirewall? >I think that something like this should work, right? > > iptables -t nat -A POSTROUTING -o eth1 \ > --to-source <public_address_1>:80 > --to-destination <private_addr_1>:80 -j SNAT > >Thanks in advance >Christophe > >--------------------------------------------------------------------- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com Next Previous Contents -------------------------------------------------------------------------------- 6. Other IP Masquerade Issues and Software Support 6.1 Problems with IP Masquerade Some TCP/IP application protocols will not currently work with Linux IP Masquerading because they either assume things about port numbers or encode TCP/IP addresses and/or port numbers in their data stream. These latter protocols need specific proxies or IP MASQ modules built into the masquerading code to make them work. 6.2 Incoming services By default, Linux IP Masquerading cannot handle incoming services at all but there are a few ways of allowing them. If you do not require high levels of security then you can simply forward or redirect IP ports. There are various ways of doing this though the most stable method is to use IPPORTFW. For more information, please see the Forwarders section. If you wish to have some level of authorization on incoming connections then you will need to either configure TCP-wrappers or Xinetd to then allow only specific IP addresses through. The TIS Firewall Toolkit is a good place to look for tools and information. More details on incoming security can be found in the TrinityOS document and at IP Masquerade Resource. 6.3 Supported Client Software and Other Setup Notes ** The Linux Masquerade Application list has a lot of good information regarding applications that work through Linux IP masquerading. This site was recently taken over by Steve Grevemeyer who implimented it with a full database backend. Its a great resource! Generally, any application that uses standard TCP and UDP should work. If you have any suggestion, hints, etc., please see the IP Masquerade Resource for more details. Network Clients that -Work- with IP Masquerade General Clients: Archie all supported platforms, file searching client (not all archie clients are supported) FTP all supported platforms, with the ip_masq_ftp.o kernel module for active FTP connections. Gopher client all supported platforms HTTP all supported platforms, WWW surfing IRC all IRC clients on various supported platforms, DCC is supported via the ip_masq_irc.o module NNTP (USENET) all supported platforms, USENET news client PING all platforms, with ICMP Masquerading kernel option POP3 all supported platforms, email clients SSH all supported platforms, Secure TELNET/FTP clients SMTP all supported platforms, email servers like Sendmail, Qmail, PostFix, etc. TELNET all supported platforms, remote session TRACEROUTE UNIX and Windows based platforms , some variations may not work VRML Windows(possibly all supported platforms), virtual reality surfing WAIS client all supported platforms Multimedia and Communication Clients: All H.323 programs - MS Netmeeting, Intel Internet Phone Beta , and other H.323 applications - There are now two solutions to get this to work through IPMASQed connections: There is a stable BETA module available on the MASQ WWW site or at http://www.coritel.it/projects/sofia/nat.html to work with Microsoft Netmeeting v3.x code on 2.2.x kernels. There is also another module version on the MASQ WWW site specifically for Netmeeting 2.x with 2.0.x kernels but it doesn't support Netmeeting v3.x. Another commercial solution is the Equivalence's PhonePatch H.323 gateway. Alpha Worlds Windows, Client-Server 3D chat program CU-SeeMe all supported platforms, with the ip_masq_cuseeme module loaded, please see the CuSeeme section for more details. ICQ all supported clients. Requires the Linux kernel to be compiled with IPPORTFW support and ICQ is configured to be behind a NON-SOCKS proxy. A full description of this configuration is in the ICQ section. Internet Phone 3.2 Windows, Peer-to-peer audio communications, people can reach you only if you initiate the call, but people cannot call you without a specific port forwarding setup. See the Forwarders section for more details. Internet Wave Player Windows, network streaming audio Powwow Windows, Peer-to-peer Text audio whiteboard communications, people can reach you only if you initiate the call, but people cannot call you without a specific port forwarding setup. See the Forwarders se ction for more details. Real Audio Player Windows, network streaming audio, higher quality available with the ip_masq_raudio UDP module True Speech Player 1.1b Windows, network streaming audio VDOLive Windows, with the ip_masq_vdolive patch Worlds Chat 0.9a Windows, Client-Server 3D chat program Games - See the LooseUDP section for more details on the LooseUDP patch Battle.net Works but requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. See the Forwarders section for more details. Please note that FSGS and Bnetd servers still require IPPORTFW since they haven't been re-written to be NAT-friendly. BattleZone 1.4 Works with LooseUDP patch and new NAT-friendly .DLLs from Activision Dark Reign 1.4 Works with LooseUDP patch or requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. See the Forwarders section for more details. Diablo Works with LooseUDP patch or requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. Newer versions of Diablo use only TCP port 6112 and UDP port 6112. See the Forwarders section for more details. Heavy Gear 2 Works with LooseUDP patch or requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. See the Forwarders section for more details. Quake I/II/III Works right out of the box but requires the ip_masq_quake module if there are more than one Quake I/II/III player behind a MASQ box. Also, this module only supports Quake I and QuakeWorld by default. If you need to support Quake II or non-default server ports, please see the module install section of the rc.firewall-2.0.x and rc.firewall-2.2.x rulesets. StarCraft Works with the LooseUDP patch and IPPORTFWing TCP and UDP ports 6112 to the internal MASQed game machine. See the Forwarders section for more details. WorldCraft Works with LooseUDP patch Other Clients: Linux net-acct package Linux, network administration-account package NCSA Telnet 2.3.08 DOS, a suite containing telnet, ftp, ping, etc. PC-anywhere for Windows MS-Windows, Remotely controls a PC over TCP/IP, only work if it is a client but not a host without a specific port forwarding setup. See the Forwarders section for more details. Socket Watch uses NTP - network time protocol Clients that do not have full support in IP MASQ: Intel Streaming Media Viewer Beta 1 Cannot connect to server Netscape CoolTalk Cannot connect to opposite side WebPhone Cannot work at present (it makes invalid assumptions about addresses). 6.4 Stronger IP Firewall (IPFWADM) Rulesets This section provides a more in-depth guide on using the 2.0.x firewall tool, IPFWADM. See below for IPCHAINS rulesets This example is for a firewall/masquerade system behind a PPP link with a static PPP address (dynamic PPP instructions are included but disabled). The trusted interface is 192.168.0.1 and the PPP interface IP address has been changed to protect the guilty :). I have listed each incoming and outgoing interface individually to catch IP spoofing as well as stuffed routing and/or masquerading. Anything not explicitly allowed is FORBIDDEN (well.. rejected actually). If your IP MASQ box breaks after implementing this rc.firewall script, be sure that you edited it for your configuration and check your /var/log/messages or /var/adm/messages SYSLOG file for any firewall errors. For more comprehensive examples of a strong IP Masqueraded IPFWADM rulesets for PPP, Cablemodem users, etc., please see TrinityOS - Section 10 and GreatCircle's Firewall WWW page NOTE: If you get a dynamically assigned TCP/IP address from your ISP (PPP, ADSL, Cablemodems, etc.), you CANNOT load this strong ruleset upon boot. You will either need to reload this firewall ruleset EVERY TIME you get a new IP address or make your /etc/rc.d/rc.firewall ruleset more intelligent. To do this for PPP users, carefully read and un-comment out the properly lines in the "Dynamic PPP IP fetch" section below. You can also find more details in the TrinityOS - Section 10 doc for more details on Strong rulesets and Dynamic IP addresses. Please also be aware that there are several GUI Firewall creation tools available as well. Please see the FAQ section for full details. Lastly, if you are using a STATIC PPP IP address, change the "ppp_ip="your.static.PPP.address"" line to reflect your address. ---------------------------------------------------------------- #!/bin/sh # # /etc/rc.d/rc.firewall: An example of a semi-STRONG IPFWADM firewall ruleset # PATH=/sbin:/bin:/usr/sbin:/usr/bin # testing, wait a bit then clear all firewall rules. # uncomment following lines if you want the firewall to automatically # disable after 10 minutes. # (sleep 600; \ # ipfwadm -I -f; \ # ipfwadm -I -p accept; \ # ipfwadm -O -f; \ # ipfwadm -O -p accept; \ # ipfwadm -F -f; \ # ipfwadm -F -p accept; \ # ) & # Load all required IP MASQ modules # # NOTE: Only load the IP MASQ modules you need. All current IP MASQ modules # are shown below but are commented from loading. # Needed to initially load modules # /sbin/depmod -a # Supports the proper masquerading of FTP file transfers using the PORT method # /sbin/modprobe ip_masq_ftp # Supports the masquerading of RealAudio over UDP. Without this module, # RealAudio WILL function but in TCP mode. This can cause a reduction # in sound quality # #/sbin/modprobe ip_masq_raudio # Supports the masquerading of IRC DCC file transfers # #/sbin/modprobe ip_masq_irc # Supports the masquerading of Quake and QuakeWorld by default. This modules is # for for multiple users behind the Linux MASQ server. If you are going to # play Quake I, II, and III, use the second example. # # NOTE: If you get ERRORs loading the QUAKE module, you are running an old # ----- kernel that has bugs in it. Please upgrade to the newest kernel. # #Quake I / QuakeWorld (ports 26000 and 27000) #/sbin/modprobe ip_masq_quake # #Quake I/II/III / QuakeWorld (ports 26000, 27000, 27910, 27960) #/sbin/modprobe ip_masq_quake 26000,27000,27910,27960 # Supports the masquerading of the CuSeeme video conferencing software # #/sbin/modprobe ip_masq_cuseeme #Supports the masquerading of the VDO-live video conferencing software # #/sbin/modprobe ip_masq_vdolive #CRITICAL: Enable IP forwarding since it is disabled by default since # # Redhat Users: you may try changing the options in /etc/sysconfig/network from: # # FORWARD_IPV4=false # to # FORWARD_IPV4=true # echo "1" > /proc/sys/net/ipv4/ip_forward #CRITICAL: Enable automatic IP defragmenting since it is disabled by default # in 2.2.x kernels # # This used to be a compile-time option but the behavior was changed # in 2.2.12 # echo "1" > /proc/sys/net/ipv4/ip_always_defrag # Dynamic IP users: # # If you get your IP address dynamically from SLIP, PPP, or DHCP, enable this # following option. This enables dynamic-ip address hacking in IP MASQ, # making the life with Diald and similar programs much easier. # #echo "1" > /proc/sys/net/ipv4/ip_dynaddr # Specify your Static IP address here. # # If you have a DYNAMIC IP address, you need to make this ruleset understand # your IP address everytime you get a new IP. To do this, enable the # following one-line script. (Please note that the different single and # double quote characters MATTER). # # # DHCP users: # ----------- # If you get your TCP/IP address via DHCP, **you will need ** to enable the # #ed out command below underneath the PPP section AND replace the word # "ppp0" with the name of your EXTERNAL Internet connection (eth0, eth1, # etc). It should be also noted that the DHCP server can change IP # addresses on you. To fix this, users should configure their DHCP client # to re-run the firewall ruleset everytime the DHCP lease is renewed. # # NOTE #1: Some DHCP clients like the older version of "pump" (the newer # versions have been fixed) did NOT have the ability to run # scripts after a lease-renew. Because of this, you need to # replace it with something like "dhcpcd" or "dhclient". # # NOTE #2: The syntax for "dhcpcd" has changed in recent versions. # # Older versions used syntax like: # dhcpcd -c /etc/rc.d/rc.firewall eth0 # # Newer versions use syntax like: # dhcpcd eth0 /etc/rc.d/rc.firewall # # NOTE #3: For Pump users, put the following line in /etc/pump.conf: # # script /etc/rc.d/rc.firewall # # PPP users: # ---------- # If you aren't already aware, the /etc/ppp/ip-up script is always run when # a PPP connection comes up. Because of this, we can make the ruleset go # and get the new PPP IP address and update the strong firewall ruleset. # # If the /etc/ppp/ip-up file already exists, you should edit it and add a line # containing "/etc/rc.d/rc.firewall" near the end of the file. # # If you don't already have a /etc/ppp/ip-up sccript, you need to create the # following link to run the /etc/rc.d/rc.firewall script. # # ln -s /etc/rc.d/rc.firewall /etc/ppp/ip-up # # * You then want to enable the #ed out shell command below * # # # PPP and DHCP Users: # ------------------- # Remove the # on the line below and place a # in front of the line after that. # #ppp_ip="`/sbin/ifconfig ppp0 | grep 'inet addr' | awk '{print $2}' | sed -e 's/.*://'`" # ppp_ip="your.static.PPP.address" # MASQ timeouts # # 2 hrs timeout for TCP session timeouts # 10 sec timeout for traffic after the TCP/IP "FIN" packet is received # 60 sec timeout for UDP traffic (MASQ'ed ICQ users must enable a 30sec firewall timeout in ICQ itself) # /sbin/ipfwadm -M -s 7200 10 60 ############################################################################# # Incoming, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # /sbin/ipfwadm -I -f /sbin/ipfwadm -I -p reject # local interface, local machines, going anywhere is valid # /sbin/ipfwadm -I -a accept -V 192.168.0.1 -S 192.168.0.0/24 -D 0.0.0.0/0 # remote interface, claiming to be local machines, IP spoofing, get lost # /sbin/ipfwadm -I -a reject -V $ppp_ip -S 192.168.0.0/24 -D 0.0.0.0/0 -o # remote interface, any source, going to permanent PPP address is valid # /sbin/ipfwadm -I -a accept -V $ppp_ip -S 0.0.0.0/0 -D $ppp_ip/32 # loopback interface is valid. # /sbin/ipfwadm -I -a accept -V 127.0.0.1 -S 0.0.0.0/0 -D 0.0.0.0/0 # catch all rule, all other incoming is denied and logged. pity there is no # log option on the policy but this does the job instead. # /sbin/ipfwadm -I -a reject -S 0.0.0.0/0 -D 0.0.0.0/0 -o ############################################################################# # Outgoing, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # /sbin/ipfwadm -O -f /sbin/ipfwadm -O -p reject # local interface, any source going to local net is valid # /sbin/ipfwadm -O -a accept -V 192.168.0.1 -S 0.0.0.0/0 -D 192.168.0.0/24 # outgoing to local net on remote interface, stuffed routing, deny # /sbin/ipfwadm -O -a reject -V $ppp_ip -S 0.0.0.0/0 -D 192.168.0.0/24 -o # outgoing from local net on remote interface, stuffed masquerading, deny # /sbin/ipfwadm -O -a reject -V $ppp_ip -S 192.168.0.0/24 -D 0.0.0.0/0 -o # outgoing from local net on remote interface, stuffed masquerading, deny # /sbin/ipfwadm -O -a reject -V $ppp_ip -S 0.0.0.0/0 -D 192.168.0.0/24 -o # anything else outgoing on remote interface is valid # /sbin/ipfwadm -O -a accept -V $ppp_ip -S $ppp_ip/32 -D 0.0.0.0/0 # loopback interface is valid. # /sbin/ipfwadm -O -a accept -V 127.0.0.1 -S 0.0.0.0/0 -D 0.0.0.0/0 # catch all rule, all other outgoing is denied and logged. pity there is no # log option on the policy but this does the job instead. # /sbin/ipfwadm -O -a reject -S 0.0.0.0/0 -D 0.0.0.0/0 -o ############################################################################# # Forwarding, flush and set default policy of deny. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # /sbin/ipfwadm -F -f /sbin/ipfwadm -F -p deny # Masquerade from local net on local interface to anywhere. # /sbin/ipfwadm -F -a masquerade -W ppp0 -S 192.168.0.0/24 -D 0.0.0.0/0 # # catch all rule, all other forwarding is denied and logged. pity there is no # log option on the policy but this does the job instead. # /sbin/ipfwadm -F -a reject -S 0.0.0.0/0 -D 0.0.0.0/0 -o #End of file. With IPFWADM, you can block traffic to a particular site using the -I, -O or -F rules. Remember that the set of rules are scanned top to bottom and "-a" tells IPFWADM to "append" this new rule to the existing set of rules. So with this in mind, any specific restrictions need to come before global rules. For example: Using -I (input ) rules: Probably the fastest and most efficient method to block traffic but it only stops the MASQed machines and NOT the the firewall machine itself. Of course you might want to allow that combination. Anyway, to block 204.50.10.13: In the /etc/rc.d/rc.firewall ruleset: ... start of -I rules ... # reject and log local interface, local machines going to 204.50.10.13 # /sbin/ipfwadm -I -a reject -V 192.168.0.1 -S 192.168.0.0/24 -D 204.50.10.13/32 -o # local interface, local machines, going anywhere is valid # /sbin/ipfwadm -I -a accept -V 192.168.0.1 -S 192.168.0.0/24 -D 0.0.0.0/0 ... end of -I rules ... Using -O (output) rules: This is the slower method to block traffic because the packets go through masquerading first before they are dropped. Yet, this rule even stops the firewall machine from accessing the forbidden site. ... start of -O rules ... # reject and log outgoing to 204.50.10.13 # /sbin/ipfwadm -O -a reject -V $ppp_ip -S $ppp_ip/32 -D 204.50.10.13/32 -o # anything else outgoing on remote interface is valid # /sbin/ipfwadm -O -a accept -V $ppp_ip -S $ppp_ip/32 -D 0.0.0.0/0 ... end of -O rules ... Using -F (forward) rules: Probably slower than -I (input) rules for blocking traffic, this still only stops masqueraded machines (e.g. internal machines). The firewall machine can still reach forbidden site(s). ... start of -F rules ... # Reject and log from local net on PPP interface to 204.50.10.13. # /sbin/ipfwadm -F -a reject -W ppp0 -S 192.168.0.0/24 -D 204.50.10.13/32 -o # Masquerade from local net on local interface to anywhere. # /sbin/ipfwadm -F -a masquerade -W ppp0 -S 192.168.0.0/24 -D 0.0.0.0/0 ... end of -F rules ... There is no need for a special rule to allow machines on the 192.168.0.0/24 network to go to 204.50.11.0. Why? It is already covered by the global MASQ rule. NOTE: There is more than one way of coding the interfaces in the above rules. For example instead of "-V 192.168.255.1" you can code "-W eth0", instead of "-V $ppp_ip" , you can use "-W ppp0". The "-V" method was phased out with the imgration to IPCHAINS but for IPFWADM users, its personal choice and documentation more than anything. 6.5 Stronger IP Firewall (IPCHAINS) rulesets This section provides a more in-depth guide on using the 2.2.x firewall tool, IPCHAINS. See above for IPFWADM rulesets. This example is for a firewall/masquerade system behind a PPP link with a static PPP address (dynamic PPP instructions are included but disabled). The trusted interface is 192.168.0.1 and the PPP interface IP address has been changed to protect the guilty :). I have listed each incoming and outgoing interface individually to catch IP spoofing as well as stuffed routing and/or masquerading. A nything not explicitly allowed is FORBIDDEN (well.. rejected actually). If your IP MASQ box breaks after implementing this rc.firewall script, be sure that you edited it for your configuration and check your /var/log/messages or /var/adm/messages SYSLOG file for any firewall errors. For more comprehensive examples of a strong IP Masqueraded IPFWADM rulesets for PPP, Cablemodem users, etc., please see TrinityOS - Section 10 and GreatCircle's Firewall WWW page NOTE #1: Linux 2.2.x kernels less than 2.2.16 have a TCP root exploit vunerability and versions less than 2.2.11 have a IPCHAINS fragmentation bug. Because of this, people running strong IPCHAINS rulesets are open to attack. Please upgrade your kernel to a fixed version. NOTE #2: If you get a dynamically assigned TCP/IP address from your ISP (PPP, ADSL, Cablemodems, etc.), you CANNOT load this strong ruleset upon boot. You will either need to reload this firewall ruleset EVERY TIME you get a new IP address or make your /etc/rc.d/rc.firewall ruleset more intelligent. To do this for PPP users, carefully read and un-comment out the properly lines in the "Dynamic PPP IP fetch" section below. You can also find more details in the TrinityOS - Section 10 doc for more details on Strong rulesets and Dynamic IP addresses. Please also be aware that there are several GUI Firewall creation tools available as well. Please see the FAQ section for full details. Lastly, if you are using a STATIC PPP IP address, change the "ppp_ip="your.static.PPP.address"" line to reflect your address. ---------------------------------------------------------------- #!/bin/sh # # /etc/rc.d/rc.firewall: An example of a Semi-Strong IPCHAINS firewall ruleset. # PATH=/sbin:/bin:/usr/sbin:/usr/bin # Load all required IP MASQ modules # # NOTE: Only load the IP MASQ modules you need. All current IP MASQ modules # are shown below but are commented from loading. # Needed to initially load modules # /sbin/depmod -a # Supports the proper masquerading of FTP file transfers using the PORT method # /sbin/modprobe ip_masq_ftp # Supports the masquerading of RealAudio over UDP. Without this module, # RealAudio WILL function but in TCP mode. This can cause a reduction # in sound quality # /sbin/modprobe ip_masq_raudio # Supports the masquerading of IRC DCC file transfers # #/sbin/modprobe ip_masq_irc # Supports the masquerading of Quake and QuakeWorld by default. This modules is # for for multiple users behind the Linux MASQ server. If you are going to # play Quake I, II, and III, use the second example. # # NOTE: If you get ERRORs loading the QUAKE module, you are running an old # ----- kernel that has bugs in it. Please upgrade to the newest kernel. # #Quake I / QuakeWorld (ports 26000 and 27000) #/sbin/modprobe ip_masq_quake # #Quake I/II/III / QuakeWorld (ports 26000, 27000, 27910, 27960) #/sbin/modprobe ip_masq_quake 26000,27000,27910,27960 # Supports the masquerading of the CuSeeme video conferencing software # #/sbin/modprobe ip_masq_cuseeme #Supports the masquerading of the VDO-live video conferencing software # #/sbin/modprobe ip_masq_vdolive #CRITICAL: Enable IP forwarding since it is disabled by default since # # Redhat Users: you may try changing the options in # /etc/sysconfig/network from: # # FORWARD_IPV4=false # to # FORWARD_IPV4=true # echo "1" > /proc/sys/net/ipv4/ip_forward #CRITICAL: Enable automatic IP defragmenting since it is disabled by default # in 2.2.x kernels # # This used to be a compile-time option but the behavior was changed # in 2.2.12. It should also be noted that some distributions have # removed this option from the /proc table. If this entry isn't # present in your /proc, don't worry about it. # echo "1" > /proc/sys/net/ipv4/ip_always_defrag # Dynamic IP users: # # If you get your IP address dynamically from SLIP, PPP, or DHCP, enable this # following option. This enables dynamic-ip address hacking in IP MASQ, # making the life with Diald and similar programs much easier. # #echo "1" > /proc/sys/net/ipv4/ip_dynaddr # Enable the LooseUDP patch which some Internet-based games require # # If you are trying to get an Internet game to work through your IP MASQ box, # and you have set it up to the best of your ability without it working, try # enabling this option (delete the "#" character). This option is disabled # by default due to possible internal machine UDP port scanning # vunerabilities. # #echo "1" > /proc/sys/net/ipv4/ip_masq_udp_dloose # Specify your Static IP address here. # # If you have a DYNAMIC IP address, you need to make this ruleset understand # your IP address everytime you get a new IP. To do this, enable the # following one-line script. (Please note that the different single and # double quote characters MATTER). # # # DHCP users: # ----------- # If you get your TCP/IP address via DHCP, **you will need ** to enable the # #ed out command below underneath the PPP section AND replace the word # "ppp0" with the name of your EXTERNAL Internet connection (eth0, eth1, etc) # on the lines for "ppp-ip" and "extip". It should be also noted that the # DHCP server can change IP addresses on you. To fix this, users should # configure their DHCP client to re-run the firewall ruleset everytime the # DHCP lease is renewed. # # NOTE #1: Some DHCP clients like the original "pump" (the newer # versions have been fixed) did NOT have the ability to run # scripts after a lease-renew. Because of this, you need to # replace it with something like "dhcpcd" or "dhclient". # # NOTE #2: The syntax for "dhcpcd" has changed in recent versions. # # Older versions used syntax like: # dhcpcd -c /etc/rc.d/rc.firewall eth0 # # Newer versions use syntax like: # dhcpcd eth0 /etc/rc.d/rc.firewall # # NOTE #3: For Pump users, put the following line in /etc/pump.conf: # # script /etc/rc.d/rc.firewall # # PPP users: # ---------- # If you aren't already aware, the /etc/ppp/ip-up script is always run when # a PPP connection comes up. Because of this, we can make the ruleset go and # get the new PPP IP address and update the strong firewall ruleset. # # If the /etc/ppp/ip-up file already exists, you should edit it and add a line # containing "/etc/rc.d/rc.firewall" near the end of the file. # # If you don't already have a /etc/ppp/ip-up sccript, you need to create the # following link to run the /etc/rc.d/rc.firewall script. # # ln -s /etc/rc.d/rc.firewall /etc/ppp/ip-up # # * You then want to enable the #ed out shell command below * # # # PPP and DHCP Users: # ------------------- # Remove the # on the line below and place a # in front of the line after that. # #extip="`/sbin/ifconfig ppp0 | grep 'inet addr' | awk '{print $2}' | sed -e 's/.*://'`" # For PPP users with STATIC IP addresses: # extip="your.static.PPP.address" # ALL PPP and DHCP users must set this for the correct EXTERNAL interface name extint="ppp0" # Assign the internal IP intint="eth0" intnet="192.168.0.0/24" # MASQ timeouts # # 2 hrs timeout for TCP session timeouts # 10 sec timeout for traffic after the TCP/IP "FIN" packet is received # 60 sec timeout for UDP traffic (MASQ'ed ICQ users must enable a 30sec firewall timeout in ICQ itself) # ipchains -M -S 7200 10 60 ############################################################################# # Incoming, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # ipchains -F input ipchains -P input REJECT # local interface, local machines, going anywhere is valid # ipchains -A input -i $intint -s $intnet -d 0.0.0.0/0 -j ACCEPT # remote interface, claiming to be local machines, IP spoofing, get lost # ipchains -A input -i $extint -s $intnet -d 0.0.0.0/0 -l -j REJECT # remote interface, any source, going to permanent PPP address is valid # ipchains -A input -i $extint -s 0.0.0.0/0 -d $extip/32 -j ACCEPT # loopback interface is valid. # ipchains -A input -i lo -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT # catch all rule, all other incoming is denied and logged. pity there is no # log option on the policy but this does the job instead. # ipchains -A input -s 0.0.0.0/0 -d 0.0.0.0/0 -l -j REJECT ############################################################################# # Outgoing, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # ipchains -F output ipchains -P output REJECT # local interface, any source going to local net is valid # ipchains -A output -i $intint -s 0.0.0.0/0 -d $intnet -j ACCEPT # outgoing to local net on remote interface, stuffed routing, deny # ipchains -A output -i $extint -s 0.0.0.0/0 -d $intnet -l -j REJECT # outgoing from local net on remote interface, stuffed masquerading, deny # ipchains -A output -i $extint -s $intnet -d 0.0.0.0/0 -l -j REJECT # anything else outgoing on remote interface is valid # ipchains -A output -i $extint -s $extip/32 -d 0.0.0.0/0 -j ACCEPT # loopback interface is valid. # ipchains -A output -i lo -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT # catch all rule, all other outgoing is denied and logged. pity there is no # log option on the policy but this does the job instead. # ipchains -A output -s 0.0.0.0/0 -d 0.0.0.0/0 -l -j REJECT ############################################################################# # Forwarding, flush and set default policy of deny. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # ipchains -F forward ipchains -P forward DENY # Masquerade from local net on local interface to anywhere. # ipchains -A forward -i $extint -s $intnet -d 0.0.0.0/0 -j MASQ # # catch all rule, all other forwarding is denied and logged. pity there is no # log option on the policy but this does the job instead. # ipchains -A forward -s 0.0.0.0/0 -d 0.0.0.0/0 -l -j REJECT #End of file. With IPCHAINS, you can block traffic to a particular site using the "input", "output", and/or "forward" rules. Remember that the set of rules are scanned t op to bottom and "-A" tells IPCHIANS to "append" this new rule to the existing set of rules. So with this in mind, any specific restrictions need to come bef ore global rules. For example: Using "input" rules: Probably the fastest and most efficient method to block traffic but it only stops the MASQed machines and NOT the firewall machine itself. Of course you might want to allow that combination. Anyway, to block 204.50.10.13: In the /etc/rc.d/rc.firewall ruleset: ... start of "input" rules ... # reject and log local interface, local machines going to 204.50.10.13 # ipchains -A input -s 192.168.0.0/24 -d 204.50.10.13/32 -l -j REJECT # local interface, local machines, going anywhere is valid # ipchains -A input -s 192.168.0.0/24 -d 0.0.0.0/0 -l -j ACCEPT ... end of "input" rules ... Using "output" rules: This is the slower method to block traffic because the packets must go through masquerading first before they are dropped. Yet, this rule even stops the firewall machine from accessing the forbidden site. ... start of "output" rules ... # reject and log outgoing to 204.50.10.13 # ipchains -A output -s $ppp_ip/32 -d 204.50.10.13/32 -l -j REJECT # anything else outgoing on remote interface is valid # ipchains -A output -s $ppp_ip/32 -d 0.0.0.0/0 -l -j ACCEPT ... end of "output" rules ... Using "forward" rules: Probably slower than "input" rules for blocking traffic, this still only stops masqueraded machines (e.g. internal machines). The firewall machine can still reach forbidden site(s). ... start of "forward" rules ... # Reject and log from local net on PPP interface to 204.50.10.13. # ipchains -A forward -i ppp0 -s 192.168.0.0/24 -d 204.50.10.13/32 -l -j REJECT # Masquerade from local net on local interface to anywhere. # ipchains -A forward -i ppp0 -s 192.168.0.0/24 -d 0.0.0.0/0 -j MASQ ... end of "forward" rules ... No need for a special rule to allow machines on the 192.168.0.0/24 network to go to 204.50.11.0. Why? It is already covered by the global MASQ rule. NOTE: Unlike IPFWADM, IPCHIANS has only one way of coding the interfaces name. IPCHAINS uses the "-i eth0" option where as IPFWADM had both "-W" for the interface name and "-V" for the interface's IP address. 6.6 IP Masquerading multiple internal networks Masquerading more than one internal network is fairly simple. You need to first make sure that all of your networks are running correctly (both internal and external). You then need to enable traffic to pass to both the other internal interfaces and to be MASQed to the Internet. Next, you need to enable Masquerading on the INTERNAL interfaces. This example uses a total of THREE interfaces: eth0 is the EXTERNAL connection to the Internet, eth1 is the 192.168.0.0 network, and eth2 is the 192.168.1.0 network. Both eth1 and eth2 will be MASQed out of interface eth0. In your rc.firewall ruleset next to the existing MASQ enable line, add the following: 2.2.x kernels with IPCHAINS #Enable internal interfaces to communication between each other /sbin/ipchains -A forward -i eth1 -d 192.168.0.0/24 /sbin/ipchains -A forward -i eth2 -d 192.168.1.0/24 #Enable internal interfaces to MASQ out to the Internet /sbin/ipchains -A forward -j MASQ -i eth0 -s 192.168.0.0/24 -d 0.0.0.0/0 /sbin/ipchains -A forward -j MASQ -i eth0 -s 192.168.1.0/24 -d 0.0.0.0/0 2.0.x kernels with IPFWADM #Enable internal interfaces to communication between each other /sbin/ipfwadm -F -a accept -V 192.168.0.1 -D 192.168.1.0/24 /sbin/ipfwadm -F -a accept -V 192.168.1.1 -D 192.168.0.0/24 #Enable internal interfaces to MASQ out to the Internet /sbin/ipfwadm -F -a masq -W eth0 -S 192.168.0.0/24 -D 0.0.0.0/0 /sbin/ipfwadm -F -a masq -W eth0 -S 192.168.1.0/24 -D 0.0.0.0/0 Please note that it is CORRECT to have "eth0" specified multiple times for the exmples shown above. The reason for this is the Linux kernel needs to know which interface is used for OUTGOING traffic. Since eth0 in the above examples is the Internet connection, it is listed for each internal interface. 6.7 IP Masquerade and Dial-on-Demand Connections If you would like to setup your network to automatically dial up the Internet, ether the Diald demand dial-up or new versions of the PPPd packages will be of great utility. Diald is the recommended solution due to its more granular configuration. To setup Diald, please check out the Setting Up Diald for Linux Page or TrinityOS - Section 23 Once Diald and IP Masq have been setup properly, any MASQed client machines that initiate a web, telnet or ftp session will make the Linux box dynamically bring up its Internet link. There is a timeout that will occur with the first connection. This is inevitable if you are using analog modems. The time taken to establish the modem link and the PPP connections may cause your client program (WWW browser, etc.). This isn't common though. If this does happen, just retry that Internet traffic request (say a WWW page) again and it should come up fine. You can also try setting echo "1" > /proc/sys/net/ipv4/ip_dynaddr kernel option to help with this initial setup. 6.8 IPPORTFW, IPMASQADM, IPAUTOFW, REDIR, UDPRED, and other Port Forwarding tools IPPORTFW, IPAUTOFW, REDIR, UDPRED, and other programs are generic TCP and/or UDP port forwarding tools for Linux IP Masquerade. These tools are typically used with or as a replacement for specific IP MASQ modules like the current ones for FTP, Quake, etc. With port forwarders, you can now re-direct data connections from the Internet to an internal, privately addressed machine behind your IP MASQ server. This forwarding ability includes network protocols such as TELNET, WWW, SMTP, FTP (with a special patch - see below), ICQ, and many others. NOTE: If you are just looking to do simple port forwarding without IP Masquerading support, you will STILL NEED to enable IP Masquerading in both the kernel AND in either your IPFWADM or IPCHAINS ruleset to then be able to use Linux's port forwarding tools. So why all the different choices? IPAUTOFW, REDIR, and UDPRED (all URLs are in the 2.0.x-Requirements section) were the first tools available to IP MASQ users to allow this functionality. Later, as Linux IP Masquerade matured, these tools were eventually replaced by IPPORTFW which is a more intelligent solution. Because of the availablity of the newer tools, it is *HIGHLY DISCOURAGED* to use the old tools such as IPAUTOFW and REDIR because they don't properly notify the Linux kernel of their presence and can ultimately CRASH your Linux server with extreme use. It should also be noted that there is also the newest method, MFW. MFW's major benefit its its tigher integration with the IPCHAINS tool. With this solution, you use a IPCHAINS ruleset to "Mark" a specific packet and then create a different chain to then do the proper forwarding. Currently, this method isn't covered in the HOWTO. NOTE #2: With PORTFW in 2.2.x kernels, internal machines CANNOT use the same PORTFWed IP address to access an internal machine though it works fine with external computers on the Internet. If this is an issue for you, you can ALSO impliment the REDIR portfw tool to let internal machines get redirected to the internal server. One good think to note is the upcoming NetFilter toolset solves this issue. If you would like a technical explination of why this internal/external forwarding doesn't work, please page down towards the bottom of the 2.2.x PORTFW section for a note from Juan. NOTE #3: The forwarding of FTP server traffic to an internal MASQed FTP server, known as PORTFW FTP, is now supported for both the 2.2.x and 2.2.x kernels. This is possible either through the patching the Linux kernel sources though the support is not currently built into the main Linux kernel or using an external FTP proxy program. It should be noted that the kernel module code is still experimental and some people get better results with ACTIVE FTP sessions compared to PASSIVE connections. Interestingly enough, other people have seen the exact opposite behavior. Please let us know what your results are like. More about this is covered below in both the 2.2.x and 2.0.x sections as the solutions use different patches. Before jumping right into installing either the 2.0.x IPPORTFW or 2.2.x version of IPMASQADM with IPPORTFW support, network security can be an issue with any port forwarder. The reason for this is because these tools basically create a hole in the packet firewall for the forwarded TCP/UDP ports. Though this doesn't pose any threat to your Linux machine, it might be an issue to the internal machine that this traffic is being forwarded to. No worries though, this is what Steven Clarke (the author of IPPORTFW) had to say about that: "Port Forwarding is only called within masquerading functions so it fits inside the same IPFWADM/IPCHAINS rules. Masquerading is an extension to IP forwarding. Therefore, ipportfw only sees a packet if it fits both the input and masquerading ipfwadm rule sets." With this said, it's important to have a strong firewall ruleset. Please see the Strong-IPFWADM-Rulesets and Strong-IPCHAINS-Rulesets sections for more details on strong rulesets. So, to install IPPORTFW forwarding support for either a 2.2.x or 2.0.x kernel, you need to re-compile the Linux kernel to support IPPORTFW. 2.2.x kernel users will already have the IPPORTFW kernel option available via IPMASQADM 2.0.x users will need to apply a simple kernel option patch IPMASQADM with IPPORTFW support on 2.2.x kernels First, make sure you have the newest 2.2.x kernel uncompressed into /usr/src/linux. If you haven't already done this, please see the Kernel-Compile section for full details. Next, download the "ipmasqadm.c" program from the 2.2.x-Requirements section into the /usr/src/ directory. Next, you'll need to compile the 2.2.x kernel as shown in the Kernel-Compile section. Be sure to say YES to the IPPORTFW option when you configure the kernel. Once the kernel compile is complete and you have rebooted, return to this section. Now, compile and install the IPMASQADM tool: cd /usr/src tar xzvf ipmasqadm-x.tgz cd ipmasqadm-x make make install Now, for this example, we are going to allow ALL WWW Internet traffic (port 80) hitting your Internet TCP/IP address to then be forwarded to the internal Masqueraded machine at IP address 192.168.0.10. PORTFW FTP: As mentioned above, there are two solutions for forwarding FTP server traffic to an internal MASQed PC. The first solution *IS* a BETA level IP_MASQ_FTP module for 2.2.x kernels to PORT Forward FTP connections to an internal MASQed FTP server. The other method is using a FTP proxy program (the URL is in the 2.2.x-Requirements section. It should also be noted that the FTP kernel module also supports the adding of additional PORTFW FTP ports on the fly without the requirement of unloading and reloaded the IP_MASQ_FTP module and thus breaking any existing FTP transfers. You can find more about this new code at the IPMASQ WWW site at http://ipmasq.cjb.net. There is also examples and some more information about PORTFWed FTP connection below in the 2.0.x. kernel section. NOTE: Once you enable a port forwarder on port 80, that port can no longer be used by the Linux IP Masquerade server. To be more specific, if you have a WWW server already running on the MASQ server, a port forward will now give all Internet users the WWW pages from the -INTERNAL- WWW server and not the pages on your IP MASQ server. Anyway, to enable port forwarding, edit the /etc/rc.d/rc.firewall ruleset. Add the follow lines but be sure to replace the word "$extip" with your Internet IP address. NOTE: If you use get a DYNAMIC TCP/IP address from your ISP (PPP, ADSL, Cablemodems, etc.), you will NEED to make your /etc/rc.d/rc.firewall ruleset more intelligent. To do this, please see the Strong-IPCHAINS-Rulesets section from above or TrinityOS - Section 10 for more details on strong rulesets and Dynamic IP addresses. I'll give you a hint though: /etc/ppp/ip-up for PPP users. /etc/rc.d/rc.firewall -- #echo "Enabling IPPORTFW Redirection on the external LAN.." # /usr/sbin/ipmasqadm portfw -f /usr/sbin/ipmasqadm portfw -a -P tcp -L $extip 80 -R 192.168.0.10 80 -- That's it! Just re-run your /etc/rc.d/rc.firewall ruleset and test it out! If you get the error message "ipchains: setsockopt failed: Protocol not available", you AREN'T running your new kernel. Make sure that you moved the new kernel over, re-run LILO, and then reboot again. If you are sure you are running your new kernel, run the command "ls /proc/net/ip_masq" and make sure the "portfw" file exists. If it doesn't, you must have made an error when configuring your kernel. Try again. For those who want to understand why PORTFW cannot redirect traffic for both external and internal interfaces, here is an email from Juanjo that better explains it: -------------------------------------------------------------------------------- >From Juanjo Ciarlante -- >If I use: > >ipmasqadm portfw -a -P tcp -L 1.2.3.4 80 -R 192.168.2.3 80 > >Everything works great from the outside but internal requests for the same >1.2.3.4 address fail. Are there chains that will allow a machine on >localnet 192.168.2.0 to accesss www.periapt.com without using a proxy? Actually not. I usually setup a ipmasqadm rule for outside, *AND* a port redirector for inside. This works because ipmasqadm hooks before redir will get the eventual outside connection, _but_ leaves things ok if not (stated by APPROPIATE rules). The actual "conceptual" problem comes from the TRUE client (peer) IP goal (thanks to masq) being in same net as target server. The failing scenario for "local masq" is : client: 192.168.2.100 masq: 192.168.2.1 serv: 192.168.2.10 1)client->server packet a) client: 192.168.2.100:1025 -> 192.168.2.1:80 [SYN] b) (masq): 192.168.2.100:1025 -> 192.168.2.10:80 [SYN] (and keep 192.168.2.1:61000 192.168.2.100:1025 related) c) serv: gets masqed packet (1b) 2)server->client packet a) serv: 192.168.2.10:80 -> 192.168.2.100:1025 [SYN,ACK] b) client: 192.168.2.100:1025 -> 192.168.2.10:80 [RST] Now take a moment to compare (1a) with (2a). You see, the server replied DIRECTLY to client bypassing masq (not letting masq to UNDO the packet hacking) because it is in SAME net, so the client resets the connection. hope I helped. Warm regards Juanjo -------------------------------------------------------------------------------- IPPORTFW on 2.0.x kernels First, make sure you have the newest 2.0.x kernel uncompressed into /usr/src/linux. If you haven't already done this, please see the Kernel-Compile section for full details. Next, download the "ipportfw.c" program and the "subs-patch-x.gz" kernel patch from the 2.0.x-Requirements section into the /usr/src/ directory. NOTE: Please replace the "x" in the "subs-patch-x.gz" file name with the most current version available on the site. Next, if you plan on port forwarding FTP traffic to an internal server, you will have to apply an additional NEW IP_MASQ_FTP module patch found in the 2.0.x-Requirements section. More details regarding this are later in this section. Please note that this is NOT the same patch as for the 2.2.x kernels so some functionality such as the dynamic FTP PORT functionality is not present. Now, copy the IPPORTFW patch (subs-patch-x.gz) into the Linux directory cp /usr/src/subs-patch-1.37.gz /usr/src/linux Next, apply the kernel patch to create the IPPORTFW kernel option: cd /usr/src/linux zcat subs-patch-1.3x.gz | patch -p1 Ok, time to compile the kernel as shown in the Kernel-Compile section. Be sure to say YES to the IPPORTFW option now available when you configure the kernel. Once the compile is complete and you have rebooted, return to this section. Now with a newly compiled kernel, please compile and install the actual "IPPORTFW" program cd /usr/src gcc ipportfw.c -o ipportfw mv ipportfw /usr/local/sbin Now, for this example, we are going to allow ALL WWW Internet traffic (port 80) hitting your Internet TCP/IP address to then be forwarded to the internal Masqueraded machine at IP address 192.168.0.10. NOTE: Once you enable a port forwarder on port 80, that port can no longer be used by the Linux IP Masquerade server. To be more specific, if you have a WWW server already running on the MASQ server and then you port forward port 80 to an internal MASQed computer, ALL internet users will see the WWW pages pages from the -INTERNAL- WWW server and not the pages on your IP MASQ server. The only work around for this is to port forward some other port, say 8080, to your internal MASQ machine. Though this will work, all Internet users will have to append :8080 to the URL to then contact the internal MASQed WWW server. Anyway, to enable port forwarding, edit the /etc/rc.d/rc.firewall ruleset. Add the follow lines but be sure to replace the word "$extip" with your Internet IP address. NOTE: If you use get a DYNAMIC TCP/IP address from your ISP (PPP, ADSL, Cablemodems, etc.), you will NEED to make your /etc/rc.d/rc.firewall ruleset more intelligent. To do this, please see the Strong-IPCHAINS-Rulesets section from above or TrinityOS - Section 10 for more details on strong rulesets and Dynamic IP addresses. I'll give you a hint though: /etc/ppp/ip-up for PPP users. /etc/rc.d/rc.firewall -- #echo "Enabling IPPORTFW Redirection on the external LAN.." # /usr/local/sbin/ipportfw -C /usr/local/sbin/ipportfw -A -t$extip/80 -R 192.168.0.10/80 #Please note that PORTFWing port 20 is NOT required for ACTIVE # connections as the internal FTP server will initiate this # port 20 connection and it will be properly handled by the # classic MASQ mechanisms. -- That's it! Just re-run your /etc/rc.d/rc.firewall ruleset and test it out! If you get the error message "ipfwadm: setsockopt failed: Protocol not available", you AREN'T running your new kernel. Make sure that you moved the new kernel over, re-run LILO, and then reboot again. Port Forwarding FTP servers: If you plan on port forwarding FTP to an internal machine, things get more complicated. The reason for this is because the standard IP_MASQ_FTP kernel module wasn't written for this though some users report that it works without any problems. Personally, without the patch, I've heard that extended file transfers in excess of 30 minutes will fail without the patch while other people swear that it works flawlessly. Anyway, I recommend that you try the following PORTFW instruction with the STOCK ip_masq_ftp module and see if it works for you. If it doesn't, try using the modified ip_masq_ftp module. For those who need the module, Fred Viles wrote a modified IP_MASQ_FTP module to make things work. If you are curious what EXACTLY is the issues, download the following archive since Fred documents it quite well. Also understand that this patch is somewhat experimental and should be treated as such. It should be also noted that this patch is ONLY available for the 2.0.x kernels though there is a different patch available for 2.2.x kernels. So, to get the 2.0.x patch working, you need to: Apply the IPPORTFW kernel patch as shown earlier in this section FIRST. Download the "msqsrv-patch-36" from Fred Viles's FTP server in the 2.0.x-Requirements section and put it into /usr/src/linux. Patch the kernel with this new code by running "cat msqsrv-patch-36 | patch -p1" Next, replace the original "ip_masq_ftp.c" kernel module with the new one mv /usr/src/linux/net/ipv4/ip_masq_ftp.c /usr/src/linux/net/ipv4/ip_masq_ftp.c.orig mv /usr/src/linux/ip_masq_ftp.c /usr/src/linux/net/ipv4/ip_masq_ftp.c Lastly build and install the kernel with this new code in place. Once this is complete, edit the /etc/rc.d/rc.firewall ruleset and add the follow lines but be sure to replace the word "$extip" with your Internet IP address. This example, like above, will allow ALL FTP Internet traffic (port 21) hitting your Internet TCP/IP address to then be forwarded to the internal Masqueraded machine at IP address 192.168.0.10. NOTE: Once you enable a port forwarder on port 21, that port can no longer be used by the Linux IP Masquerade server. To be more specific, if you have a FTP server already running on the MASQ server, a port forward will now give all Internet users the FTP files from the -INTERNAL- FTP server and not the files on your IP MASQ server. /etc/rc.d/rc.firewall -- #echo "Enabling IPPORTFW Redirection on the external LAN.." # /usr/local/sbin/ipportfw -C /usr/local/sbin/ipportfw -A -t$extip/21 -R 192.168.0.10/21 #NOTE: If you are using multiple local port numbers to PORTFW # to multuple internal FTP servers (say, 21, 2121, 2112, # etc, you need to configure the ip_masq_ftp nodule to # listen to these ports. To do this, edit the # /etc/rc.d/rc.firewall script as shown in this HOWTO # to look like: # # /sbin/modprobe ip_masq_ftp ports=21,2121,2112 # # Re-run the /etc/rc.d/rc.firewall script for these changes to # take effect. #Please note that PORTFWing port 20 is probably NOT required # for ACTIVE connections as the internal FTP server will # initiate this port 20 connection and it will be properly # handled by the classic MASQ mechanisms. -- That's it! Just re-run your /etc/rc.d/rc.firewall ruleset and test it out! If you get the error message "ipchains: setsockopt failed: Protocol not available", you AREN'T running your new kernel. Make sure that you moved the new kernel over, re-run LILO, and then reboot again. If you are sure you are running your new kernel, run the command "ls /proc/net" and make sure the "ip_portfw" file exists. If it doesn't, you must have made an error when configuring your kernel. Try again. 6.9 CU-SeeMe and Linux IP-Masquerade Linux IP Masquerade supports CuSeeme via the "ip_masq_cuseeme" kernel module. This kernel modules should be loaded in the /etc/rc.d/rc.firewall script. Once the "ip_masq_cuseeme" module is installed, you should be able to both initiate and receive CuSeeme connections to remote reflectors and/or users. NOTE: It is recommended to use the IPPORTFW tool instead of the old IPAUTOFW tool for running CuSeeme. If you need more explicit information on configuring CuSeeme, see Michael Owings's CuSeeMe page for a Mini-HOWTO or The IP Masquerade Resources for a mirror of the Mini-HOWTO. 6.10 Mirabilis ICQ There are two methods of getting ICQ to work behind a Linux MASQ server. One solution is to use a new ICQ Masq module and the other solution is to use IPPORTFW. The ICQ module has some benefits. It allows for simple setup of multiple ICQ users behind a MASQ server. It also doesn't require any special changes to the ICQ client(s). Recently, the 2.2.x version of the module was updated to support file transfer and read-time chat. Yet, for the 2.0.x kernel module, file transfers and real-time chat still isn't fully supported. Anyway, I now feel this is the PREFERRED method to get ICQ working with IP Masq running on 2.2.x+ kernels. With the IPPORTFW setup, you will have to make some changes on both Linux and ICQ clients but all ICQ messaging, URLs, chat, file transfer, etc. work. If you are interested in Andrew Deryabin's djsf(a)usa.net ICQ IP Masq module for the 2.2.x kernels. Please see the 2.2.x-Requirements section for details. If you rather use the classic method of getting ICQ to run behind a MASQ server, follow these steps: First, you need to be running a Linux kernel with IPPPORTFW enabled. Please see the Forwarders section for more details. Next, you need to add the following lines to your /etc/rc.d/rc.firewall file. This example assumes that 10.1.2.3 is your external Internet IP address and your internal MASQed ICQ machine is 192.168.0.10: The following example is for a 2.0.x kernel with IPFWADM: I have included two examples here for the user: Either once works fine: Example #1 -- /usr/local/sbin/ipportfw -A -t10.1.2.3/2000 -R 192.168.0.10/2000 /usr/local/sbin/ipportfw -A -t10.1.2.3/2001 -R 192.168.0.10/2001 /usr/local/sbin/ipportfw -A -t10.1.2.3/2002 -R 192.168.0.10/2002 /usr/local/sbin/ipportfw -A -t10.1.2.3/2003 -R 192.168.0.10/2003 /usr/local/sbin/ipportfw -A -t10.1.2.3/2004 -R 192.168.0.10/2004 /usr/local/sbin/ipportfw -A -t10.1.2.3/2005 -R 192.168.0.10/2005 /usr/local/sbin/ipportfw -A -t10.1.2.3/2006 -R 192.168.0.10/2006 /usr/local/sbin/ipportfw -A -t10.1.2.3/2007 -R 192.168.0.10/2007 /usr/local/sbin/ipportfw -A -t10.1.2.3/2008 -R 192.168.0.10/2008 /usr/local/sbin/ipportfw -A -t10.1.2.3/2009 -R 192.168.0.10/2009 /usr/local/sbin/ipportfw -A -t10.1.2.3/2010 -R 192.168.0.10/2010 /usr/local/sbin/ipportfw -A -t10.1.2.3/2011 -R 192.168.0.10/2011 /usr/local/sbin/ipportfw -A -t10.1.2.3/2012 -R 192.168.0.10/2012 /usr/local/sbin/ipportfw -A -t10.1.2.3/2013 -R 192.168.0.10/2013 /usr/local/sbin/ipportfw -A -t10.1.2.3/2014 -R 192.168.0.10/2014 /usr/local/sbin/ipportfw -A -t10.1.2.3/2015 -R 192.168.0.10/2015 /usr/local/sbin/ipportfw -A -t10.1.2.3/2016 -R 192.168.0.10/2016 /usr/local/sbin/ipportfw -A -t10.1.2.3/2017 -R 192.168.0.10/2017 /usr/local/sbin/ipportfw -A -t10.1.2.3/2018 -R 192.168.0.10/2018 /usr/local/sbin/ipportfw -A -t10.1.2.3/2019 -R 192.168.0.10/2019 /usr/local/sbin/ipportfw -A -t10.1.2.3/2020 -R 192.168.0.10/2020 -- Example #2 -- port=2000 while [ $port -le 2020 ] do /usr/local/sbin/ipportfw -A t10.1.2.3/$port -R 192.168.0.10/$port port=$((port+1)) done -- The following example is for a 2.2.x kernel with IPCHAINS: I have included two examples here for the user: Either once works fine: Example #1 -- /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2000 -R 192.168.0.10 2000 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2001 -R 192.168.0.10 2001 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2002 -R 192.168.0.10 2002 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2003 -R 192.168.0.10 2003 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2004 -R 192.168.0.10 2004 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2005 -R 192.168.0.10 2005 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2006 -R 192.168.0.10 2006 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2007 -R 192.168.0.10 2007 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2008 -R 192.168.0.10 2008 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2009 -R 192.168.0.10 2009 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2010 -R 192.168.0.10 2010 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2011 -R 192.168.0.10 2011 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2012 -R 192.168.0.10 2012 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2013 -R 192.168.0.10 2013 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2014 -R 192.168.0.10 2014 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2015 -R 192.168.0.10 2015 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2016 -R 192.168.0.10 2016 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2017 -R 192.168.0.10 2017 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2018 -R 192.168.0.10 2018 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2019 -R 192.168.0.10 2019 /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 2020 -R 192.168.0.10 2020 -- Example #2 -- port=2000 while [ $port -le 2020 ] do /usr/local/sbin/ipmasqadm portfw -a -P tcp -L 10.1.2.3 $port -R 192.168.0.10 $port port=$((port+1)) done -- Once your new rc.firewall is ready, reload the ruleset to make sure things are ok by simple typing in "/etc/rc.d/rc.firewall". If you get any errors, you either don't have IPPORTFW support in the kernel or you made a typo in the rc.firewall file. Now, in ICQ's Preferences-->Connection, configure it to be "Behind a LAN" and "Behind a firewall or Proxy". Now, click on "Firewall Settings" and configure it to be "I don't use a SOCK5 proxy". Also note that it was repviously recommended to change ICQ's "Firewall session timeouts" to "30" seconds BUT many users have found that ICQ becomes unreliable. It has been found that ICQ is more reliable with its stock timeout setting (don't enable that ICQ option) and simply change MASQ's timeout to 160 seconds. You can see how to change this timeout in the rc.firewall-2.0.x and rc.firewall-2.2.x rulesets. Finally, click on Next and configure ICQ to "Use the following TCP listen ports.." from "2000" to "2020". Now click done. Now ICQ will tell you that you have to restart ICQ for the changes to take effect. To be honest, I had to REBOOT the Windows9x machine to get things to work right but other people say otherwise. So.. try it both ways. It should also be noted that one user told me that simply portforwarding port 4000 to his ICQ machine worked best. He reported that everything worked fine (chat, file transfers, etc) WITHOUT re-configuring ICQ from its default settings. Your mileage might vary on this topic but I though you might like to hear about this alternative configuration. 6.11 Gamers: The LooseUDP patch The LooseUDP patch allows NAT-friendly games that usually use UDP connections to both WORK and perform quite well behind a Linux IP Masquerade server. Currently, LooseUDP is available as a patch for 2.0.36+ kernels and it is already built into 2.2.3+ kernels though it is now DISABLED by DEFAULT in 2.2.16+. To get LooseUDP running on a 2.0.x kernel, follow the following steps: Have the newest 2.0.x kernel sources uncompressed in the /usr/src/linux directory ABSOLUTELY REQUIRED for v2.0.x: Download and install the IPPORTFW patch from the 2.0.x-Requirements section and as described in the Forwarders Section of the HOWTO. Download the LooseUDP patch from the 2.0.x-Requirements section Now, put the LooseUDP patch in the /usr/src/linux directory. Once this is done, type in: For a compressed patch file: zcat loose-udp-2.0.36.patch.gz | patch -p1 For a NON-compressed patch file: cat loose-udp-2.0.36.patch | patch -p1 Now, depending on your version of "patch", You will then see the following text: patching file `CREDITS' patching file `Documentation/Configure.help' patching file `include/net/ip_masq.h' patching file `net/ipv4/Config.in' patching file `net/ipv4/ip_masq.c' If you see the text "Hunk FAILED" only ONCE and ONLY ONCE at the very beginning of the patching, don't be alarmed. You probably have an old patch file (this as been fixed) but it still works. If it fails completely, make sure you have applied the IPPORTFW kernel patch FIRST. Once the patch is installed, re-configure the kernel as shown in the Kernel-Compile section and be sure to say "Y" to the "IP: loose UDP port managing (EXPERIMENTAL) (CONFIG_IP_MASQ_LOOSE_UDP) [Y/n/?]" option. To get LooseUDP running on a 2.2.x kernel, follow the following steps: In the /etc/rc.d/rc.firewall script, goto the BOTTOM of the file and find the LooseUDP section. Change the "0" in the line: echo "0" > /proc/sys/net/ipv4/ip_masq_udp_dloose to a "1" and re-run the rc.firewall ruleset. An example of this is given in both the rc.firewall-2.2.x example and the stronger-rc.firewall-2.2.x example. Once you are running the new LooseUDP enabled kernel, you should be good to go for most NAT-friendly games. Some URLs have been given for patches to make games like BattleZone and others NAT friendly. Please see the Game-Clients section for more details. -------------------------------------------------------------------------------- Next Previous Contents mail script Te respondo personalmente, y con copia a la lista, ya que me parece que varias veces lei que algunos preguntaban como hacer esto. Espero que les sirva de algo, igualmente lean el howto del ipchains, y vayan pensando en aprender de nuevo cuando el kernel 2.4 se generalice, porque cambian un poco las cosas. Configuracion en los clientes windows: - Supongamos que la IP itnerna del linux es 192.168.1.250, entonces lo unico que tendrias que configurar en los clientes windows es el efault gateway, que tendria que apuntar a esa IP. Configuracion del linux Lo que queres hacer se hace con el ipchains (si no lo tenes buscalo en el cd el suse que tiene que estar para instalar), una utilidad para configurar el packet filtering, esto lo hace directamente el kernel, asi que lo tenes que tener compilado con soporte para firewalling (no me acuerdo bien la opcion, pero esta en la parte de networking) Para hacer simplemente un masquerading de todo lo que pase por el 'firewall', con ejecutar el siguiente comando seria suficiente: 'ipchains -P forward MASQ' si no tenes ninguna otra regla o cadenas definidas, tendria que funcionar. Lo que hace es habilitar el masquerading para todo lo que pase por la cadena forward (si no entendes bien como funciona esto, leete el howto http://www.linux.org/docs/ldp/howto/IPCHAINS-HOWTO.html que realmente te va a servir, aunque en mi caso recien lo entendi del todo la cuarta o quinta vez que lo lei ;-). Bueno, con esto ya tendrias definido el masquerading, ahora tenes que ejecutar 'echo 1 > /proc/sys/net/ipv4/ip_forward' con esto habilitas el forwarding en el kernel. Si quere hacer ftp, vas a tener que cargar un modulo especial, ya que parece que hacer msquerading del ftp es medio complicado, esto lo habilitas con: 'insmod ip_masq_ftp' asi como tenes este modulo, hay algunos otros especiales para real audio, etc. No los conozco porque en la empresa nadie los usa, y en casa no me puse a jugar con esto, habra que investigar... Todas estas configuraciones permanecen en memoria, asi que cuando reinicies la maquina var a perder todo esto. Por eso te conviene hacer algun script que se ejecute cuando inicies la maquina. Por ejemplo, algo asi: #!/bin/bash /sbin/ipchains -P forward MASQ echo 1 > /proc/sys/net/ipv4/ip_forward insmod ip_masq_ftp GOOD LUCK It s working 100%.I am 1 server and 6 term all with masquerading. SHOTGUN SEE LATER!!!! _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

1 0

RE: [suse-security] sorry, very OT: No such file or directory
by Freudenberger Joerg 09 May '01

09 May '01

> > another thing is with dos-files: if the script is in DOS format, the > > interpreter can't be found, too > > That must have been it - I copied and pasted all the 2243 > lines into a new > file - and now it's running. If you use vim (the SuSE vi is a vim) it is more easy. :help ff to convert a file brute force at end of edit session :set ff=unix :wq at Beginning of edit session :set ff=unix :w :e! Yours Jörg

1 0

sorry, very OT: No such file or directory
by Bjoern Engels 09 May '01

09 May '01

Sorry for being so OT, but maybe somebody can point me to the correct mailing list (if there is one) or somewhere else where I can get help... The problem I'm having sounds ridiculous: I'm trying to call a shell script and get a "No such file or directory" error. The file IS there and executable and I DID put a ./ in front of it ;) First I thought the script contains a command or library call that's not being found or something, so I straced it: svr1:/cdrom/accmgnt/Linux/setup # ./nds-install bash: ./nds-install: No such file or directory svr1:/cdrom/accmgnt/Linux/setup # svr1:/cdrom/accmgnt/Linux/setup # strace ./nds-install execve("./nds-install", ["./nds-install"], [/* 59 vars */]) = 0 strace: exec: No such file or directory svr1:/cdrom/accmgnt/Linux/setup # Any idea where to get help on this ? (It's Novell's EDirectory I'm trying to install, but the guys in Provo are still asleep now, I think ;) Bjoern Engels --------------------------------------------- E-Mail: Bjoern Engels <bengels(a)lanworks.de> Date: 09-May-01 Time: 10:39:12 www.lanworks.de ---------------------------------------------

3 3

Message Log Question
by Derik Whittaker 09 May '01

09 May '01

I have been monitering my /var/log/message file and came across an entry that reads localhost portmap[9415]: connect from 63.237.56.1 to dump(): request from unauthorized host. Does this mean that some one has gotten into my system? I am running red hat 6.1 using ipchains and portsentry as a firewall. Any insight would be great. Derik Whittaker derik(a)graudo.com

8 11

2.2.19 rtl8139 test
by Roman Drahtmueller 09 May '01

09 May '01

Hi together, the kernel security update is underway. At ftp://ftp.suse.com/pub/people/mantel/next/ there is a 2.2.19 tarball. Could anybody who has a rtl8139 NIC check and see if the driver from the 2.2.19 tarball works properly for this NIC? We've had a report that the driver hangs the machine, but it couldn't be verified. Please report directly to me. In case something unusual turns out, I'll summarize. Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -

1 0

RE: [suse-security] stateful and dynamic inspection
by Reckhard, Tobias 09 May '01

09 May '01

> does ipchains support stateful inspection and dynamic filtering in kernel > 2.2.18? > No, the 2.2.x kernel packet filtering code (configured by ipchains) is not stateful. Note that the term "stateful inspection" belongs to the company Check Point, makers of the Firewall-1 line of products, so nothing besides Check Point's software supports "stateful inspection", strictly speaking. > whats about kernel 2.4.x and iptables? > Yes, the 2.4.x kernel PF code (netfilter, which is configured with the iptables tool) is stateful. > I found nothing on the web which > describes > the different filter functions on different network layers. > Hmm, have you read the Netfilter documentation? And do you know what stateful filtering is? If you've got in-depth questions, there's the netfilter mailing list and the ultimate reference: the source code itself. > Could anyone > give me a > short description which functions are implemented in kernels 2.2.1x and > 2.4.x, > or give me a link about these topics? > Well, the reference site is http://netfilter.kernelnotes.org, but I can't establish a connection at the moment. Just input "netfilter linux 2.4 iptables" to your favourite search engine and you should get enough hits to keep yourself busy for a while. HTH Tobias

1 0

stateful and dynamic inspection
by Christian Osterbrink 08 May '01

08 May '01

Hello, does ipchains support stateful inspection and dynamic filtering in kernel 2.2.18? whats about kernel 2.4.x and iptables? I found nothing on the web which describes the different filter functions on different network layers. Could anyone give me a short description which functions are implemented in kernels 2.2.1x and 2.4.x, or give me a link about these topics? Thanks Christian

2 1

Re: [suse-security] Kernel security
by Martin Fahlgren 08 May '01

08 May '01

Serveral distributors have already published updates... What is the problem with SuSE? A crisis? This is probably the "worst" exploit up to now and a big problem for all networks with many login accounts (web sites, schools, universities etc). So the options I have are 1) Compile and install my own kernel 2) Disable logins until SuSE comes with a new kernel 3) Switch to a distribution which provides the necessary updates Not funny at all Best regards Martin

3 2

Kernel security
by Martin Fahlgren 07 May '01

07 May '01

Warning! There are serious problems with all Linux kernels prior to version 2.2.19. Among these are possibilities for local denial of service or root exploits by exercising race conditions between the ptrace, exec, and/or suid system calls. Programs which exploit these problems have existed since middle of april. See www.securityfocus.com/bugtraq/archive for more info. A SuSE Security Announcement and a new kernel rpm are needed! Best regards Martin

3 2

Apache log entry
by Phil Schrettenbrunner 07 May '01

07 May '01

Good morning, today I have found a pretty strange entry in my Apache access.log. I run a SuSE Linux 7.1/Apache 1.3.14 on a box with DSL that is up most of the time. This is in my log : --- cut --- 207.33.111.32 - - [01/May/2001:10:20:41 +0200] "HEAD%00 /%20HTTP/1.0%0D%0A%0D%0AAccept%3A%20hzwllekiww/../../index.html%3fyzhwpxdpqqt=/. ./lfspjgqdafroxyzmqeispzlifdknzswkphpwbxympterothgnnrefekenoedtvutrueqxavfamhqak gqlkhgvtxorcexhkamivmrutqcttwdtgjowguhfvucfnvcuosbycwsxoxlcuhbaothdvorozuylagkjg xcltvmijhqhobzeqiyeyhvdcmewgypgwoquonegtbpsyzctqcjmexujwrdhonducylgugrpojgjspzvq fnelrjzfvzluaazetwmjlntmnhalhnbyvhohnzuivzigwzntbzfjdztwanypiiuqjmqcqzhvsulzkjgw uucluiizzwwwiyhzbclqdqeehgrwxnprvdjnybeaaxauoscurjpsiwwrkdpzffqxscrueusjseiaexqe uyyvubgpkixksnztaxcncrkuqbohdjqfwsaldgjjphfbdcpvsxoghxsntmyeznfspgxtjhomdqeddbme zgusewcueuyydyapgudfztiiyicoqcjwxknmuorxcstavughbneygwtdyptizplytraycfedeliukxkj cuoytcnnkrucjkfjbufsabssfjtvyvxdduxmlmuxsucqfyoklposnayxzcgirqvsewnzqyhrvvbdvris rggwwupwvhwtrogkhirehsoyrarsztkxsiksmvtqtnjmmbkytxxvqqjaguszamymgskwlihmsdincvqu aqrcnwaekqchrnqswrerjlqbzxypymunwslpdmfxtezkormnkvhndatghpdhfzkvnehfcuxhiwudtoic rqqjkazjpornbqeggtjzrbeuthuhndkqougdmvrmpdiggchgjhoikthefooyfrwuaxczpgijwwgnnmbq zfpqjicskqpfajntqegvbdyrrdrfrsrikqiisqvuonowcyjxfqotsoarsznlgsejqthnlhytzgnrbnlw ungkegdomoecaoftupfzblrybjxcfnkpzionfpuovfaslpuclrbqrewqtljfjgtdsdkawpoamughityq lksslzynqlfgakkvhrxluarjdhgtvqqvosreqevbtrzigdpruvseggjqvvyqbmlnccdksobcqnlkjvwr ngosejplxykhamphsuyyfdmkqumeondxnuktknmavayeljskmlfslqyophmgghqolwbnmougnowmiibi pkyeoxsodogpqynmczourpqytbblrhgajfbmusvagnmrisiyhrbwusaahammcbnsgmbwkwdtvqjjviwg phrszbxiisubpfcgpblfkvrnpjidtfvjjonlvdskelfxxilgyttxqhafxggjlqniyxgxhupthqlsvjom njbkdcdraizjltfyxifklmzgqvlqpnzyawdpzwzuykcqkmfsuejkfcjcnoalebpptymjegylsfyegvmh qnqfbvfezbuyehszciv/.././%4d%59%4c%4f%47%2e%50%48%54%4d%4c HTTP/1.0" 501 1911 --- cut --- and it shows up every second for a 15 Minutes period. The entries differ from each other. Does anyone know what this? Thank you very much! regards | phil -- Das einzige Backup, das Sie je brauchen werden, ist das, für das Sie keine Zeit hatten.

1 0

help :(
by Jesse yep 06 May '01

06 May '01

Hi, I'm new to this kernel 2.4.x and my ipchains don't seem to work i get an error like protocol unavailable or something, any idea how i can fix it. Or is there a better tool then ipchains? I don't have any kind of security at this point, I own SuSE 7.1 with kernel 2.4.0. Any idea how i can get some security on this box? __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/

3 2

OpenSSH versus SSH
by Marko Kaening 06 May '01

06 May '01

Hi, looks like I didn't notice that SSH seems to be really commercial now. Is this right? Do I need to pay for it if I am still using it? Is OpenSSH a full-featured substitute for SSH? Are there major problems in configuration to expect if I try to deinstall SSH and go for OpenSSH? Marko

10 15

SuSE Linux 7.1 / Kernel 2.4 and freeswan
by Thomas Stinner 06 May '01

06 May '01

Hello, i tried using Kernel 2.4 together with FreeSWAN under SuSE 7.1. Is it correct that there is no module for Kernel 2.4.x yet? -- Mit freundlichem Gruß Thomas Stinner - billiton internet services GmbH Geschäftsleitung -------------------------------------------------------------- direct phone: 0271/30386-11 direct mail: t.stinner(a)billiton.de Weitere Informationen finden Sie unter http://www.billiton.de/

2 1

port-scan-blocker
by Daniel Quappe 04 May '01

04 May '01

hey list, does anybody know an opportunity to block port-scans with ipchains etc. like some commerical firewalls do?! any solution is appreciated...;-) bye, daniel -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

4 4

missing mc update file
by Bob Vickers 04 May '01

04 May '01

Hello, The file ftp://ftp.suse.com/pub/suse/i386/update/7.1/ap1/mc-4.5.51-1.i386.rpm referenced in http://www.suse.de/de/support/security/2001_011_mc.txt seems to have gone missing...is it being updated? Bob ============================================================== Bob Vickers R.Vickers(a)cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691

2 1

SuSE Security Announcement: sgmltool
by Sebastian Krahmer 04 May '01

04 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: sgmltool-1.0.9-266 Announcement-ID: SuSE-SA:2001:16 Date: Friday, May 4th, 14:55:35 CEST 2001 Affected SuSE versions: 6.3, 6.4, 7.0, 7.1 Vulnerability Type: local fileaccess problem Severity (1-10): 2 SuSE default package: yes Other affected systems: All UN*X systems using this package Content of this advisory: 1) security vulnerability resolved: sgmltool problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The sgmltool programs ("sgml2html" and others) are used to convert SGML-files into various other formats. During operation, the underlying SGML perlmodule creates temporary files in an insecure way. This allows attackers to destroy arbitrary files owned by the user who invoked the sgmltool program. The problem has been fixed by creating temporary files with the exclusive (O_EXCL) option upon opening them. Download the update package from locations desribed below and install the package with the command `rpm -Uhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig --nogpg file.rpm', independently from the md5 signatures below. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/sgm1/sgmltool-1.0.9-302.i386.rpm bdedaefb82dc2bb8ff0a522607b80ac3 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/sgmltool-1.0.9-302.src.rpm dc5612aa475c5d6dcaaeee86e6bf985f SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/sgm1/sgmltool-1.0.9-301.i386.rpm 916953307d466d3bd8d26fb0655ce55a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/sgmltool-1.0.9-301.src.rpm 5e11b85a494e1033ee2a83839cb296fe SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/sgm1/sgmltool-1.0.9-300.i386.rpm a489acc5c3dce4c44915e47b3ee64790 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/sgmltool-1.0.9-300.src.rpm efdb6b08988b689127600a954ebe2e2f SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/sgm1/sgmltool-1.0.9-300.i386.rpm 9c1e5da161b67248935cbc7f485dfd40 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/sgmltool-1.0.9-300.src.rpm a2deae294821e73ed24429636b20ed2a Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/sgm1/sgmltool-1.0.9-283.sparc.… b3e0ec269392fb3d77c37cc698f77d16 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/sgmltool-1.0.9-283.src.rpm eb80b6efe08f40139ec181fed7ccc832 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/sgm1/sgmltool-1.0.9-284.sparc.… 8312ac046de5df7a47008dba32f1a7e8 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/sgmltool-1.0.9-284.src.rpm a7e48214ae01f4f720240c1204120927 AXP Alpha Platform: SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/sgm1/sgmltool-1.0.9-283.alpha.rpm 06348dc4b669098d80bc16a8cc836123 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/sgmltool-1.0.9-283.src.rpm c7c7ff5507f7a510d615235323f9f636 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/sgm1/sgmltool-1.0.9-281.alpha.rpm ee6bb4dd45c90ba716f0d825fba7bbca source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/sgmltool-1.0.9-281.src.rpm 44366d7edcace3448a606aff0c73026f SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/sgm1/sgmltool-1.0.9-281.alpha.rpm 2c2450e3dfdde9066269add9cfb0757b source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/sgmltool-1.0.9-281.src.rpm 66a9d60866a5ebbb2e0682a2056f2528 PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sgm1/sgmltool-1.0.9-216.ppc.rpm 01bda0ee0edfa1e1036d27b2bb3de352 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/sgmltool-1.0.9-216.src.rpm 1c6668d3ccc1b27bb3d5a4f84b308323 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/sgm1/sgmltool-1.0.9-216.ppc.rpm e9b7161fe3a10624790ce65d9909165d source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/sgmltool-1.0.9-216.src.rpm 15b8204b9378f8e833e6bac263bbacdd SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/sgm1/sgmltool-1.0.9-216.ppc.rpm 6af30c53d022866df5dd69ae053eeeea source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/sgmltool-1.0.9-216.src.rpm 35aa3ab2a86498c5e6ad145c0c7e378a ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - Marcus Meissner (Caldera) found a bug in KDE 2.1.*'s kdesu program which allows attackers to gather private information. This is due to insecure local filehandling by the kdesu program. Please update to the newest packages. - minicom format string vulnerabilities have been found in the minicom package. If /usr/bin/minicom is installed suid, the vulnerability may be exploited to gain elevated privileges. Please note that this is not the case in SuSE distributions. If you decided to make /usr/bin/minicom suid uucp or even suid root, please make sure that you grant access to the execution of minicom to trusted users only. - cfingerd The package has been found vulnerable to a remotely exploitable weakness. SuSE Linux distributions do not ship this version of fingerd. - webmin Insecure handling of temporary files has been found in webmin, a comprehensive administration webinterface. SuSE distributions do not contain the webmin package and therefore are not vulnerable to the found vulnerabilities by default. We urge administrators who use webmin to upgrade to the latest version of webmin available. - gnupg/gpg, openssl Several weaknesses have been found in gnupg/gpg that can reduce the strength of encrypted data. We will provide updates for the gnupg/gpg package. The updates are currently being tested. ______________________________________________________________________________ 3) standard appendix: SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =============================================== SuSE's security contact is <security(a)suse.com>. =============================================== Regards, Sebastian Krahmer ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 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 iQEVAwUBOvKmBHey5gA9JdPZAQFNrQf/WNKH2qdtejRaCkmkqO0h2zMSKrhWDmqA v0vhSI/iG+Ax+SXq2Jt7hhGbi8qNBGEGQI4Pm1gA66prJgDsh6azwqCCDU33Q8AK nQ0smS65VaFJsc5inSM/KIa33mpA82uwkihmTFUxrt0zh96Pqgbdu4ayr2BqlGCD G7QRQD79RFzJwMDlmrAZjAHslKe3RlXwXcyXfUgWZnkNW+Ehv6Pd1Zqj/EyIDHhg T6f5t5+QxCoIKiw1aVbW8UZ4Kpk0wMzfoU0A/INS8omEgDZFPxdm7woNDXYvlrfp l7MS1/fqt9LqFZOW+XGFvVJOrKhSbDPxQ96W8Oft6mAx8XhH5se3Mw== =WRNV -----END PGP SIGNATURE-----

1 0

IPSec on linux 2.4.4
by RoMaN SoFt / LLFB!! 04 May '01

04 May '01

Hi. I want to make an encrypted VPN and I'd like you to advice some free (linux) solutions. My 1st try was FreeSwan but it doesn't build on 2.4.4 kernel (tested with both freeswan latest versions: stable and today's snapshot). I'm having a look to other alternatives (listed in "Other approaches to VPNs for Linux" from freeswan doc). Just right now I'm going to have a look to CIPE. As usual I'd like to hear some words from you (which solution do you recommend and/or have tested for my kernel, ...). Greetings to the ml :) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** RoMaN SoFt / LLFB ** roman(a)madrid.com http://pagina.de/romansoft ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4 5

New gnpg version. Will SuSE do an upgraded rpm?
by Paul Elliott 04 May '01

04 May '01

I have noted that the gnpg people have made a new release that fix several potential security problems. Will SuSE provide an upgraded RPM or should I get the tar file from the gnpg people?? Viel Spaß -- Paul Elliott 1(512)837-9345 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

2 1

security-control.sh
by wolfgang tinhofer 04 May '01

04 May '01

greetings! a reboot this morning caused 5 D prozesses after the cron.daily/aaa_base_rotate_logs 3300 ? D 0:00 cp /var/log/messages /var/log/messages.o 11506 ? D 0:02 pico messages 17222 ? D 0:00 /usr/local/bin/logtail /var/log/messages 22112 ? D 0:00 tailf messages 30305 ? D 0:00 tail messages as this script worked for a long time and works for others, maybe someone could give me a hint, where to search for reasons for this strange behavior (not the script behavior) thanks wolfgang tinhofer

2 1

harden suse log
by Togan Muftuoglu 04 May '01

04 May '01

Hi, Hope this is not a FAQ but I have questions I did run harden_suse yes since this is a firewall/router box. Output from harden_suse v3.2 run on Fri May 4 09:07:42 EEST 2001 1) If this is a firewall router pc why disabling IP Forwarding I thought it was necessary Found /etc/rc.config, working on it ... Disabled IP Forwarding. 2) If ADSL is disabled how am I suppose to connect the Internet ? Disabled service ADSL. 3) Why disable IDS or issue a warning for a similiar? Warning: I'm leaving SCANLOGD enabled! Disabled service SNORT. 4) the only difference I see is use of cracklib whats the importance or benefit having it enabled ATTENTION: You have modified /etc/pam.d/sshd. Leaving it untouched... You can find my version in /etc/pam.d/sshd.SuSEconfig... -- Togan Muftuoglu

1 0

Re: [suse-security] kernel 2.4.2 and (new) IP MasQ configuration
by Harold ! 04 May '01

04 May '01

Ashley and other helpful list posters: Yes, please do. I appreciate your help in this matter. I am new to linux (less then 6 months serious exp) and want to keep my local lan secure. For you others: I apoligise if I intruded on your security discussions. I did NOT see a listserv for "idiots". I had no intentions of disturbing your "world" I only seek to learn what is (IMHO) a much better netowrking OS. In the short time I've used it, I'm inpressed. No, my real name does not appear in my emails sent. If ya really must know it's Bramton (NorDak Internet) >From: Ashley <ashleyg(a)dnai.com> >To: suse-security(a)suse.com >Subject: Re: [suse-security] kernel 2.4.2 and (new) IP MasQ configuration >Date: Thu, 3 May 2001 11:00:47 -0700 >MIME-Version: 1.0 >Received: from [202.58.118.3] by hotmail.com (3.2) with ESMTP id >MHotMailBCBAF530002040043251CA3A76030B230; Thu May 03 11:57:53 2001 >Received: (qmail 14470 invoked by alias); 3 May 2001 18:57:20 -0000 >Received: (qmail 14449 invoked from network); 3 May 2001 18:57:19 -0000 >From suse-security-return-7039-ambrosius1972 Thu May 03 11:58:44 2001 >Mailing-List: contact suse-security-help(a)suse.com; run by ezmlm >Precedence: bulk >X-No-Archive: yes >list-help: <mailto:suse-security-help@lists.suse.com> >list-unsubscribe: <mailto:suse-security-unsubscribe@lists.suse.com> >list-post: <mailto:suse-security@suse.com> >X-Mailinglist: suse-security >Delivered-To: mailing list suse-security(a)lists.suse.com >Message-ID: <20010503110047.E32593(a)rose.ashnet> >Mail-Followup-To: suse-security(a)suse.com >References: <F219hQdOgl4rhYQYx3G00012142(a)hotmail.com> >User-Agent: Mutt/1.3.12i >In-Reply-To: <F219hQdOgl4rhYQYx3G00012142(a)hotmail.com>; from >ambrosius1972(a)hotmail.com on Thu, May 03, 2001 at 02:36:19AM -0500 > >SuSEfirewall does not support iptables as shipped with 7.1, But it does >recognized if you are using the 2.2.18 or 2.4 kernel and does the >appropriate thing to setup ipchains. > >I was just playing with netfilter yesterday (and the day before that, >and the day before that... ). I'm masquerading a subnet behind a >dynamic ppp link. I hacked together a SuSEesque >init script and iptables rules script to setup up a iptables >firewall for a stock 7.1 system. I will send it to you if you are >interested. > >Some good sites for netfilter: >http://va.samba.org/netfilter/ >http://www.BoingWorld.com/workshops/linux/iptables-tutorial/ >http://ods.dyndns.org/ipt_flow.html >http://www.cs.princeton.edu/~jns/security/iptables/ >http://www.kalamazoolinux.org/presentations/20010417 > > >On Thu, May 03, 2001 at 02:36:19AM -0500, Harold ! wrote: > > Has anyone setup Connection sharing with kernel 2.4.2-4suse ?? > > I use a dialup connection and share it currently with IP Masq. Looking > > forward to migrating to netfilter's con sharing... > > > > I am currently running ManDrake 7.2 on my "server" box, and and to >replace > > it with SuSE (running the updated kernel. I know that IP Masq has been > > replaced with netfilter. My questions are as follows: > > > > 1. Is the neccessary utils bundled with SuSE 7.1 Pro (updated)? > > 2. Does the SuSEFirewall utility set this up? > > 3. If not Where can I find Idiot instructions? > > > > Thank you for your time. > > Ambrosius1972(a)hotmail.com > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-security-help(a)suse.com > > > >-- >-ashley > > One of these days I'm going to completely organize my life. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

2 1

ashley's netfilter firewall scripts for SuSE7.1
by Ashley 04 May '01

04 May '01

Several people asked me for these scripts, so I'm posting them. Perhaps frittering my week on this was not a waste after all. But really I should be out looking for a job. Take a look. I'm very open to comments. My sh skills are rough. To make the init script part of the SuSE init system, I added a var in /etc/rc.config: START_IPTABLES_FW, I made links in /etc/init.d/rc#.d and a link for rciptables in /use/sbin: root@rose:~ >ls -l /usr/sbin/rciptables lrwxrwxrwx 1 root root 20 May 2 11:06 /usr/sbin/rciptables -> /etc/init.d/iptables root@rose:~ >ls -lR /etc/init.d/rc*.d/*iptables lrwxrwxrwx 1 root root 11 May 2 10:27 /etc/init.d/rc2.d/K17iptables -> ../iptables lrwxrwxrwx 1 root root 11 May 2 10:28 /etc/init.d/rc2.d/S04iptables -> ../iptables lrwxrwxrwx 1 root root 11 May 2 11:02 /etc/init.d/rc3.d/K17iptables -> ../iptables lrwxrwxrwx 1 root root 11 May 2 11:01 /etc/init.d/rc3.d/S04iptables -> ../iptables root@rose:~ >grep FW /etc/rc.config START_FW="no" START_IPTABLES_FW="yes" And definately have a look at James Stephen's iptables tutorial: http://www.cs.princeton.edu/~jns/security/iptables/ #!/bin/sh #set -x # # ================================================================== # # Iptables startup script # /etc/init.d/iptables # # For use on rose.ashnet SuSE7.1 # by ashley 4/30/2001 IPTABLES=/usr/sbin/iptables IPTABLES_CONFIG=/sbin/iptables.rules . /etc/rc.config # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} # Force execution if not called by a runlevel directory. # I added a var in /etc/rc.config test $link = $base && START_FW=yes test "$START_IPTABLES_FW" = yes && START_FW="yes" test "$START_FW" = yes || exit 0 # Let's test that everything is in place echo "Ashley's iptables firewall: " return=$rc_done # check we have the iptables executable if [ ! -x $IPTABLES ]; then echo " Can't find $IPTABLES:$rc_failed" return=$rc_failed && exit 1 fi # check we have the right kernel version KERNELMAJ=`uname -r | sed -e 's,\..*,,'` KERNELMIN=`uname -r | sed -e 's,[^\.]*\.,,' -e 's,\..*,,'` if [ "$KERNELMAJ" -lt 2 ] || [ "$KERNELMAJ" -eq 2 -a "$KERNELMIN" -lt 3 ] ; then echo " No iptables support in kernel `uname -r`:$rc_failed" return=$rc_failed && exit 1 fi # Check if ipchains is already running if /sbin/lsmod 2>/dev/null |grep -q ipchains ; then echo " module ipchains already loaded:$rcfailed" return=$rc_failed && exit 1 fi # Check if iptables modules are already loaded iptables_loaded="no" if /sbin/lsmod 2>/dev/null |grep -q ip_tables ; then iptables_loaded="yes" fi # Looks good, let's get started case "$1" in start | restart) # We don't have the rules script? if [ ! -f $IPTABLES_CONFIG ]; then echo -n " Can't find firewall rules file $IPTABLES_CONFIG: " return=$rc_failed else echo -n " Loading rules: " $IPTABLES_CONFIG > /dev/null 2>&1 || return=$rcfailed fi echo -e "$return" ;; stop) if [ $iptables_loaded = yes ]; then echo " Flushing all chains, removing user defined chains and" echo " Resetting built-in chains to the default ACCEPT policy:" echo -n " The filter table: " $IPTABLES -P INPUT ACCEPT $IPTABLES -P OUTPUT ACCEPT $IPTABLES -P FORWARD ACCEPT $IPTABLES -F $IPTABLES -X $IPTABLES -Z echo -e "$rc_done" echo -n " The nat table: " $IPTABLES -t nat -P PREROUTING ACCEPT $IPTABLES -t nat -P OUTPUT ACCEPT $IPTABLES -t nat -P POSTROUTING ACCEPT $IPTABLES -t nat -F $IPTABLES -t nat -X $IPTABLES -t nat -Z echo -e "$rc_done" # Not in use #echo -n " The mangle table: " #$IPTABLES -t mangle -P PREROUTING ACCEPT #$IPTABLES -t mangle -P OUTPUT ACCEPT #$IPTABLES -t mangle -F #$IPTABLES -t mangle -X #$IPTABLES -t mangle -Z #echo -e "$rc_done" #echo -n " Stop forwarding and unload all the iptables modules: " #echo 0 > /proc/sys/net/ipv4/ip_forward #/sbin/rmmod `lsmod | awk '{print $1}' | grep '^ip'` #echo -e "$rc_done" else echo " No iptables modules loaded." fi ;; status) # I recommend piping this to `less` if [ $iptables_loaded = yes ]; then echo echo ' FILTER TABLE' echo $IPTABLES -t filter -L -v --line-numbers echo echo ' NAT TABLE' echo $IPTABLES -t nat -L -v --line-numbers echo #echo ' MANGLE TABLE' #echo #$IPTABLES -t mangle -L -v --line-numbers #echo else echo " No iptables modules loaded." fi ;; panic) if [ $iptables_loaded = yes ]; then echo " PANIC! Change all target policies to DROP: " echo -n " The filter table: " $IPTABLES -P INPUT DROP $IPTABLES -P OUTPUT DROP $IPTABLES -P FORWARD DROP $IPTABLES -F $IPTABLES -X $IPTABLES -Z echo -e "$rc_done" echo -n " The nat table: " $IPTABLES -t nat -P PREROUTING DROP $IPTABLES -t nat -P OUTPUT DROP $IPTABLES -t nat -P POSTROUTING DROP $IPTABLES -t nat -F $IPTABLES -t nat -X $IPTABLES -t nat -Z echo -e "$rc_done" # Not in use #echo -n " The mangle table: " #$IPTABLES -t mangle -P PREROUTING DROP #$IPTABLES -t mangle -P OUTPUT DROP #$IPTABLES -t mangle -F #$IPTABLES -t mangle -X #$IPTABLES -t mangle -Z #echo -e "$rc_done" echo -n " Stop forwarding and unload all the iptables modules: " echo 0 > /proc/sys/net/ipv4/ip_forward /sbin/rmmod `lsmod | awk '{print $1}' | grep '^ip'` echo -e "$rc_done" else echo " No iptables modules loaded." fi ;; *) echo "Usage: $0 {start|stop|restart|status|panic}" exit 1 esac # Inform the caller not only verbosely and set an exit status. test "$return" = "$rc_done" || exit 1 exit 0 #!/bin/bash ##============================================================ # Iptables firewall rules loading script # /sbin/iptables.rules # ##ag Adapted form the tutorial by James C. Stephens <jns(a)gfdl.noaa.gov> ##ag for use on rose.ashnet 4/30/2001 by ashley. ##ag My comments look like this ##ag # ##ag This is the K I S S version. ##ag I cut out James' wonderful comments for readablity. ##ag Look for full documentation at James' site: ##ag http://www.cs.princeton.edu/~jns/security/iptables/ IPTABLES=/usr/sbin/iptables MODPROBE=/sbin/modprobe ECHO=/bin/echo # Load appropriate modules. #$MODPROBE ip_tables #$MODPROBE ip_conntrack #$MODPROBE ip_conntrack_ftp ##ag The above calls aren't needed if the MASQ module is loaded; ##ag it brings them with it. $MODPROBE ipt_MASQUERADE # Flush rules $IPTABLES -F $IPTABLES -X $IPTABLES -Z $IPTABLES -t nat -F $IPTABLES -t nat -X $IPTABLES -t nat -Z # Default policy $IPTABLES -P INPUT DROP $IPTABLES -P FORWARD DROP $IPTABLES -P OUTPUT DROP $IPTABLES -t nat -P PREROUTING ACCEPT $IPTABLES -t nat -P OUTPUT ACCEPT $IPTABLES -t nat -P POSTROUTING ACCEPT ## =========================================================== ## Some definitions: ##ag ashnet locals INT_NET="192.168.0.0/24" INT_IPADDR="198.168.0.1" INT_IFACE="eth0" EXT_IFACE="ppp0" INT_MAIL="192.168.0.2" ##ag my isp stuff NAMESERVER_1="207.172.3.10" NAMESERVER_2="207.172.3.11" POP3_HOST="208.59.199.22" SMTP_MAIL_RELAY= ##ag general P_PORTS="0:1023" UP_PORTS="1024:65535" TR_SRC_PORTS="32769:65535" TR_DEST_PORTS="33434:33523" ## ============================================================ ## Kernel flags #echo kernel flags $ECHO "1" > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts $ECHO "0" > /proc/sys/net/ipv4/conf/all/accept_source_route $ECHO "0" > /proc/sys/net/ipv4/conf/all/accept_redirects $ECHO "1" > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses ##ag Don't I need to do this _after_ my ppp0 interface comes up? #for interface in /proc/sys/net/ipv4/conf/*/rp_filter; do # $ECHO "1" > ${interface} #done ##ag Instead I'll just do the 'all' version $ECHO "1" > /proc/sys/net/ipv4/conf/all/rp_filter $ECHO "1" > /proc/sys/net/ipv4/conf/all/log_martians $ECHO "1" > /proc/sys/net/ipv4/ip_forward ## ============================================================ # RULES #=================================================================== ## The FORWARD chain #echo The FORWARD chain # I'm masquerading everything from my internal lan $IPTABLES -t nat -A POSTROUTING -o $EXT_IFACE -j MASQUERADE #$IPTABLES -A FORWARD -i $INT_IFACE -m state --state NEW,RELATED,ESTABLISHED -j LOG --log-prefix "ACCEPT FORWARD --state NEW,E,R:" $IPTABLES -A FORWARD -i $INT_IFACE -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT #$IPTABLES -A FORWARD -i $EXT_IFACE -m state --state RELATED,ESTABLISHED -j LOG --log-prefix "ACCEPT FORWARD --state E,R:" $IPTABLES -A FORWARD -i $EXT_IFACE -m state --state RELATED,ESTABLISHED -j ACCEPT # Log the losers $IPTABLES -A FORWARD -i $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -j LOG --log-prefix "DROP FORWARD IN-PPP0: " $IPTABLES -A FORWARD -i $EXT_IFACE -j DROP #============================================================================== # Local Processes on Rose #echo Local Processes on Rose ## LOOPBACK #echo LOOPBACK $IPTABLES -A INPUT -i lo -j ACCEPT $IPTABLES -A OUTPUT -o lo -j ACCEPT ## SYN-FLOODING PROTECTION #echo SYN-FLOODING PROTECTION ##ag Probably I don't need this, as I have no servers running. $IPTABLES -N syn-flood $IPTABLES -A INPUT -p tcp --syn -j syn-flood $IPTABLES -A syn-flood -m limit --limit 1/s --limit-burst 4 -j RETURN $IPTABLES -A syn-flood -j DROP ## Make sure NEW tcp connections are SYN packets $IPTABLES -A INPUT -p tcp ! --syn -m state --state NEW -j DROP ## FRAGMENTS #echo FRAGMENTS # Log fragments just to see if we get any, and deny them too. $IPTABLES -A INPUT -f -j LOG --log-prefix "IPTABLES FRAGMENTS: " $IPTABLES -A INPUT -f -j DROP ## SPOOFING ##ag I cut out this section ##ag I'll rely on the kernel flags ## DNS #echo DNS # Allow UDP packets in for DNS client from nameservers. No tcp. $IPTABLES -A INPUT -i $EXT_IFACE -p udp -s $NAMESERVER_1 --sport 53 -m state --state ESTABLISHED -j ACCEPT $IPTABLES -A INPUT -i $EXT_IFACE -p udp -s $NAMESERVER_2 --sport 53 -m state --state ESTABLISHED -j ACCEPT # Allow UDP packets to DNS servers from client. $IPTABLES -A OUTPUT -o $EXT_IFACE -p udp -d $NAMESERVER_1 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT $IPTABLES -A OUTPUT -o $EXT_IFACE -p udp -d $NAMESERVER_2 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT ## SSH #echo SSH # Allow ssh outbound all interfaces. $IPTABLES -A INPUT -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT $IPTABLES -A OUTPUT -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT ##ag Allow connections from internal lan (and log while testing) #$IPTABLES -A INPUT -i $INT_IFACE -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j LOG --log-prefix "ACCEPT ssh from internal --state NEW,E,R: " $IPTABLES -A INPUT -i $INT_IFACE -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT #$IPTABLES -A OUTPUT -o $INT_IFACE -p tcp --sport 22 -m state --state ESTABLISHED -j LOG --log-prefix "ACCEPT ssh from internal --state E,R: " $IPTABLES -A OUTPUT -o $INT_IFACE -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT ## WWW ##ag I'll include this when I get my squid proxy up #echo WWW # Allow www outbound to 80. #$IPTABLES -A INPUT -i $EXT_IFACE -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT #$IPTABLES -A OUTPUT -o $EXT_IFACE -p tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT # Allow www outbound to 443. #$IPTABLES -A INPUT -i $EXT_IFACE -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT #$IPTABLES -A OUTPUT -o $EXT_IFACE -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT ## FTP ##ag For future ftp proxy #echo FTP # Allow ftp outbound. #$IPTABLES -A INPUT -i $EXT_IFACE -p tcp --sport 21 -m state --state ESTABLISHED -j ACCEPT #$IPTABLES -A OUTPUT -o $EXT_IFACE -p tcp --dport 21 -m state --state NEW,ESTABLISHED -j ACCEPT # 1) Active ftp. #$IPTABLES -A OUTPUT -o $EXT_IFACE -p tcp --dport 20 -m state --state ESTABLISHED -j ACCEPT # 2) Passive ftp. #$IPTABLES -A INPUT -i $EXT_IFACE -p tcp --sport $UP_PORTS --dport $UP_PORTS -m state --state ESTABLISHED -j ACCEPT #$IPTABLES -A OUTPUT -o $EXT_IFACE -p tcp --sport $UP_PORTS --dport $UP_PORTS -m state --state ESTABLISHED,RELATED -j ACCEPT ## SMTP #echo SMTP ##ag Allow smtp outbound to internal lan only. $IPTABLES -A INPUT -i $INT_IFACE -p tcp --sport 25 -m state --state ESTABLISHED -j ACCEPT $IPTABLES -A OUTPUT -o $INT_IFACE -p tcp --dport 25 -m state --state NEW,ESTABLISHED -j ACCEPT ## TRACEROUTE #echo TRACEROUTE # Outgoing traceroute to internet. $IPTABLES -A OUTPUT -o $EXT_IFACE -p udp --sport $TR_SRC_PORTS --dport $TR_DEST_PORTS -m state --state NEW -j ACCEPT ## ICMP #echo ICMP ##ag This is where netfilter really shines. It is sooo much easier! ##ag rose can ping either interface and accepts pings from internal $IPTABLES -A INPUT -i $EXT_IFACE -p icmp -m state --state ESTABLISHED,RELATED -j ACCEPT $IPTABLES -A INPUT -i $INT_IFACE -p icmp -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT $IPTABLES -A OUTPUT -o $EXT_IFACE -p icmp -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT $IPTABLES -A OUTPUT -o $INT_IFACE -p icmp -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT ## LOGGING #echo LOGGING ##ag Rate limit the logging # Any udp not already allowed is logged and then dropped. $IPTABLES -A INPUT -i $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -p udp -j LOG --log-prefix "DROP UDP-IN: " $IPTABLES -A INPUT -i $EXT_IFACE -p udp -j DROP $IPTABLES -A OUTPUT -o $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -p udp -j LOG --log-prefix "DROP UDP-OUT: " $IPTABLES -A OUTPUT -o $EXT_IFACE -p udp -j DROP # Any icmp not already allowed is logged and then dropped. $IPTABLES -A INPUT -i $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -p icmp -j LOG --log-prefix "DROP ICMP-IN: " $IPTABLES -A INPUT -i $EXT_IFACE -p icmp -j DROP $IPTABLES -A OUTPUT -o $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -p icmp -j LOG --log-prefix "DROP ICMP-OUT: " $IPTABLES -A OUTPUT -o $EXT_IFACE -p icmp -j DROP # Any tcp not already allowed is logged and then dropped. $IPTABLES -A INPUT -i $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -p tcp -j LOG --log-prefix "DROP TCP-IN: " $IPTABLES -A INPUT -i $EXT_IFACE -p tcp -j DROP $IPTABLES -A OUTPUT -o $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -p tcp -j LOG --log-prefix "DROP TCP-OUT: " $IPTABLES -A OUTPUT -o $EXT_IFACE -p tcp -j DROP # Anything else not already allowed is logged and then dropped. $IPTABLES -A INPUT -i $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -j LOG --log-prefix "DROP PROTOCOL-X-IN: " $IPTABLES -A INPUT -i $EXT_IFACE -j DROP $IPTABLES -A OUTPUT -o $EXT_IFACE -m limit --limit 6/h --limit-burst 5 -j LOG --log-prefix "DROP PROTOCOL-X-OUT: " $IPTABLES -A OUTPUT -o $EXT_IFACE -j DROP # THE END # ================================================================== -- -ashley One of these days I'm going to completely organize my life.

1 0

Re: [suse-security] How to prevent home-phoning ?
by christian.burri＠synecta.ch 03 May '01

03 May '01

I suggest that you use iptables and snort on the SuSE box and then, additionally go and install something like norton personal firewall or something alike on the internal computers (if they 're win32 as I suppose). The SuSE box divides your LAN from the internet, whereas the (host based) personal firewalls allow you to see which process uses what sockets and connects to where, plus you can allow/disallow individual applications. A drawback however is, that the win32 personal firewalls wont most likely not log to a centralized syslog, plus you will have to configure (and eventually maintain) them all manually. A different approach is presented by NFR (www.nfr.com) They do offer a complete solution for intrusion detection that works with agents, which, once deployed on each host within the LAN, log to the central NFR log repository (afaik). But this is like, costly ;-( hope that helps & cheers Chris Burri jun. Systems- & Network Engineer Synecta Informatik AG 9000 St. Gallen Switzerland .-. /v\ L I N U X // \\ >Phear the Penguin< /( )\ ^^-^^ |--------+-----------------------> | | Andreas | | | Fiesser | | | <fiesser(a)gmx.| | | net> | | | | | | 03.05.01 | | | 18:49 | | | | |--------+-----------------------> >---------------------------------------------------------------------------------------------------------------------------------------------| | | | To: Security SuSE <suse-security(a)suse.com> | | cc: | | Subject: [suse-security] How to prevent home-phoning ? | >---------------------------------------------------------------------------------------------------------------------------------------------| I've got a SuSE 7.0 box sitting between my home LAN and my DSL ISP. Among other services this host acts as a firewall for the LAN. The clients connect by masquerading or JunkBuster (running on the router) to the internet. Theoretically the FW should keep all the bad boys/girls out by stealthing my ports. How can I make sure that only those apps get out where I say it's OK ? I figure that this is no trivial task but maybe there are solutions to do this. Primarily I use Netscape to browse the Net and do my e-mails. Then I need a few programs to ftp outside. I guess it's a bit tricky to know if any other software tries to establish connections ? Sorry, if this sounds a bit naive but I'm wondering if my firewall thingy is actually any good in the days of spyware thrown at us users "to improve the knowledge about the needs of dear customers". --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

How to prevent home-phoning ?
by Andreas Fiesser 03 May '01

03 May '01

I've got a SuSE 7.0 box sitting between my home LAN and my DSL ISP. Among other services this host acts as a firewall for the LAN. The clients connect by masquerading or JunkBuster (running on the router) to the internet. Theoretically the FW should keep all the bad boys/girls out by stealthing my ports. How can I make sure that only those apps get out where I say it's OK ? I figure that this is no trivial task but maybe there are solutions to do this. Primarily I use Netscape to browse the Net and do my e-mails. Then I need a few programs to ftp outside. I guess it's a bit tricky to know if any other software tries to establish connections ? Sorry, if this sounds a bit naive but I'm wondering if my firewall thingy is actually any good in the days of spyware thrown at us users "to improve the knowledge about the needs of dear customers".

2 1

kernel 2.4.2 and (new) IP MasQ configuration
by Harold ! 03 May '01

03 May '01

Has anyone setup Connection sharing with kernel 2.4.2-4suse ?? I use a dialup connection and share it currently with IP Masq. Looking forward to migrating to netfilter's con sharing... I am currently running ManDrake 7.2 on my "server" box, and and to replace it with SuSE (running the updated kernel. I know that IP Masq has been replaced with netfilter. My questions are as follows: 1. Is the neccessary utils bundled with SuSE 7.1 Pro (updated)? 2. Does the SuSEFirewall utility set this up? 3. If not Where can I find Idiot instructions? Thank you for your time. Ambrosius1972(a)hotmail.com _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

3 2