September 2001 - openSUSE Security - openSUSE Mailing Lists

scp/sftp and chroot (OpenSSH)
by Ulf Stegemann 05 Sep '01

05 Sep '01

The following message is a courtesy copy of an article that has been posted to comp.security.unix,comp.os.linux.security as well. On our servers there exist serveral chroot accounts where users can log in and find themselves caged in their home directory. This works for telnet, ftp and ssh (OpenSSH 2.5.1). However, scp and sftp can't be used with these accounts, they simply hang after authentication. Searching the net I found that that's a known problem and that it could be solved using ssh3 (which is not an option for me) or a chroot-patch for OpenSSH together with statically compiled ssh binaries. The latter one didn't work for me and I'm wondering if anybody has another solution for the problem that a) works with OpenSSH and b) does not require to change /etc/passwd. Ulf -- not a real signature

1 0

SuSE Security Announcement: screen (SuSE-SA:2001:030)
by Roman Drahtmueller 05 Sep '01

05 Sep '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: screen Announcement-ID: SuSE-SA:2001:030 Date: Wednesday, September 5 2001 18:00 MEST Affected SuSE versions: (6.0, 6.1, 6.2) 6.3, 6.4, 7.0, 7.1, 7.2 Vulnerability Type: local root compromise Severity (1-10): 5 SuSE default package: yes Other affected systems: some systems with the screen program installed setuid root Content of this advisory: 1) security vulnerability resolved: screen 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 screen is a terminal multiplexer program that allows reattaching to a detached session as well as multi-attached (shared) sessions. The screen package allows a local attacker to obtain root privileges if the /usr/bin/screen command is installed setuid root and if a directory below /tmp/screens/ exists. The screen program needs root permissions from the setuid-root bit for two reasons: multi-attached sessions are only possible with root privileges, and writing terminal allocation information to /var/run/utmp (the who(1) and finger(1) commands). If the screen command is not running with special privileges, all functionality except these two features will continue to work, but the local root compromise will not be possible. In order to provide the features mentioned, the screen package used to be installed setuid-root in SuSE Linux distributions. The update packages that we provide for the supported distributions 6.3, 6.4, 7.0, 7.1 and 7.2 eliminate the error in the source code. In addition to that, the rpm package does not contain the setuid-bit on the screen program any more. If there is any more security-related bug in the screen package or libraries that it is linked against to be found in the future, these errors will not open local security holes any more. Users of the screen package who need the multi-attach feature must enable it again by adding the setuid-bit to the /usr/bin/screen file. Please note that you should reflect the changes to permissions in the files /etc/permissions*. If unsure, use the setting "secure local" for the variable PERMISSION_SECURITY in /etc/rc.config and execute "SuSEconfig" as root. Alternatively, change the settings for the screen program in /etc/permissions* and run "chkstat -set <file>" for each file that you need. Use the command "rpm -qlv screen | grep /usr/bin" to find out which files to add to the permissions file (/usr/bin/screen is a symlink). The authors of screen have released the new version screen-3.9.10 that fixes the multi-attach-error, and some other uncritical bug. Our update packages contain the necessary patches applied to the version as shipped with the original distribution. We thank Christian Hürgemann <Bzrker(a)t-online.de> for reporting this error on Monday, 3 Sep 2001. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Uhv file.rpm" to apply the update. i386 Intel Platform: SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap1/screen-3.9.8-115.i386.rpm e85453f50170ecdabe97dd2b33b51e4a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/screen-3.9.8-115.src.rpm 74ac0119ec42f7c5ad4405a7f1c00f6a SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/ap1/screen-3.9.8-115.i386.rpm fb0a3ba99db246c1f08e3814557858ae source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/screen-3.9.8-115.src.rpm 5edb0caa388be9f1ddc2cd4d0a4f3a54 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/ap1/screen-3.9.8-115.i386.rpm b7bfa891b49db29093f6ab1830d84838 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/screen-3.9.8-115.src.rpm fb1e3bf070adec10296a59f2d1231c8c SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/ap1/screen-3.9.8-115.i386.rpm a889c9090b0a64eb57a407ee00444491 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/screen-3.9.8-115.src.rpm 29b6e24378153a4f9d2445414253759c SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/ap1/screen-3.9.8-115.i386.rpm 5a47bdc2407890d9a940c710d4806383 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/screen-3.9.8-115.src.rpm f3bace3114cfcb9b1b6e798ea8b93b34 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/ap1/screen-3.9.8-61.sparc.rpm 3bfe4ac28d54ff2cab6582b2d09f3b75 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/screen-3.9.8-61.src.rpm 17da9f63ec2b0d48b3593dacfe341a7b SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/ap1/screen-3.9.8-62.sparc.rpm 13037ae193ebd81b92ce1d94d2409421 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/screen-3.9.8-62.src.rpm c542f1c51a701ad5dd06d9f9f3701cfb AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/ap1/screen-3.9.8-71.alpha.rpm c5239b5ca727a4f7d54589399b62a5c5 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/screen-3.9.8-71.src.rpm 4c389bca8641e3c081e992e82bc5065d SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/ap1/screen-3.9.8-71.alpha.rpm 9f84734233284fc9f7be494c37a4f857 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/screen-3.9.8-71.src.rpm 31920bb58b696739100e75ce363ade6d SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/ap1/screen-3.9.8-71.alpha.rpm a7f64468ecc5be193795ea3a530d3ead source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/screen-3.9.8-71.src.rpm dae933854ae9a7efd3e80e09641b9963 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/ap1/screen-3.9.8-71.alpha.rpm f66d9c18a27cd7915d5134528b47c342 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/screen-3.9.8-71.src.rpm 13157d46457be72fd7684ca0cbe6c49b PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/ap1/screen-3.9.8-52.ppc.rpm 090e4781fb4949697fb08f755a0ae12d source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/screen-3.9.8-52.src.rpm ce19f08412c6517798690fa7d99ed690 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/ap1/screen-3.9.8-52.ppc.rpm e37b478c4ce85febc13785b4a48c68c0 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/screen-3.9.8-52.src.rpm 0594837833e05e430c52421745f1abfa SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/ap1/screen-3.9.8-52.ppc.rpm 53cb3d0fdf964a4013b6aed326d77c9e source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/screen-3.9.8-52.src.rpm 89300f304c709a10975f5906bedd1529 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - sendmail SuSE Security announcement SuSE-SA:2001:028 (sendmail) offers a sendmail update package for the 7.0-i386 distribution that has a lower version number than the package in the tree for ftp installation on ftp.suse.com. If your update rpm command fails with a complaint that the version installed is newer than the one you wish to be installed, then please use the "--oldpackage" commandline option to rpm: "rpm --oldpackage -Uhv sendmail-*.rpm". We are correcting the problem as soon as possible. The new package will be named sendmail-8.11.0-10.i386.rpm and should appear on the ftp server within the next 11 hours. The *-10 package is technically identical to the *-5 package that is currently available on our ftp server. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de) the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an 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. =================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the cleartext signature shows proof of the authenticity of the text. 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.6 (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 iQEVAwUBO5ZTFHey5gA9JdPZAQHosAf/drLZSUCL8y3JyAd9EfzXg4OctE245mjb HrAn+jgXNDHvL8SzQYFpIzt5hLiJ9WLXc0+Edu3ovKkhzCJOtWIXTu2dvOiRhF99 MO3iaqWF3J+HhGMOEr2sQWsiqVKF5Mdw13SPgiwTX3le9ropXAD8gvZCoG7WjCpb nqIbbVlY2zrxdCuoDVeLrH3FJS1TksUcga/+pdJqaPG1YgdV+UFMFbTnpEITXyNT s9vB553vw9paFf9a4LGwoht3BpwtvnPRTjQlfgApJPvMbFjTGers824cT5xOjpPz pafJ3QG9ZbiD+49yY4wXMsmBNdohGM4CFsmV5Sc8aOXFenA26Kbg4Q== =tYiI -----END PGP SIGNATURE-----

1 0

Re: [suse-security] firewall2 and SPOOFIN
by James Bliss 05 Sep '01

05 Sep '01

I believe the problem is in your FW_MASQ_NETS setting. Ping is an ICMP protocol. Why don't you try to open this up completely (internalnet/8-16-or24 - whichever appropriately applies. then test to seen what happens. then you can start restricting this more and more to tighten the controls as needed. Jim 09/05/01 10:57:34 AM, "Anthony Hogbin" <anthony.hogbin(a)btinternet.com> wrote: >Hello > >I am running repeatedly into a brick wall here over SuSEfirewall2 > >Three NIC's - a real IP DMZ, a masqueraded LAN on 192, and a DSL router >which is my DFG and name server. > >I can do most stuff I hoped it would do when I sat down and figured out what >I needed - like web, mail, imap, ssh, MSN IM blah blah. BUT I CANNOT PING. > >No where on the network can ping at all. > >Masqueraded clients can resolve but then nothing. > >This is what I get in the /var/log/firewall (where 14 is the router - and >the 192 address is the test client): > >Sep 5 15:40:40 prometheus kernel: SuSE-FW-DROP-ANTI-SPOOFIN=eth0 OUT= >MAC=00:01:02:24:8b:9a:00:20:6f:09:7c:b5:08:00 SRC=217.34.212.14 >DST=217.34.212.2 LEN=315 TOS=0x00 PREC=0x00 TTL=60 ID=42849 PROTO=UDP SPT=53 >DPT=1027 LEN=295 > >....this is just one example of many SPOOF issues - but the one that I think >points the strongest towards my current issues. > >With a bit of luck the act of asking for help will bring some >enlightenment?! > >---- > >For your entertainment (take it easy on me!) is the setup > ># 2.) >FW_DEV_EXT="eth0" > ># 3.) >FW_DEV_INT="eth2" > ># 4.) >FW_DEV_DMZ="eth1" > ># 5.) >FW_ROUTE="yes" > ># 6.) >FW_MASQUERADE="yes" >FW_MASQ_DEV="$FW_DEV_EXT" >FW_MASQ_NETS="$INT_LAN_RANGE,0/0,tcp,20 $INT_LAN_RANGE,0/0,tcp,21 >$INT_LAN_RANGE,0/0,tcp,22 $INT_LAN_RANGE,0/0,tcp,23 >$INT_LAN_RANGE,0/0,tcp,25 $INT_LAN_RANGE,0/0,tcp,37 >$INT_LAN_RANGE,0/0,udp,37 $INT_LAN_RANGE,0/0,udp,43 >$INT_LAN_RANGE,0/0,udp,53 $INT_LAN_RANGE,0/0,tcp,53 >$INT_LAN_RANGE,0/0,tcp,80 $INT_LAN_RANGE,0/0,tcp,110 >$INT_LAN_RANGE,0/0,tcp,113 $INT_LAN_RANGE,0/0,tcp,123 >$INT_LAN_RANGE,0/0,udp,123 $INT_LAN_RANGE,0/0,tcp,143 >$INT_LAN_RANGE,0/0,tcp,443 $INT_LAN_RANGE,0/0,tcp,554 >$INT_LAN_RANGE,0/0,tcp,993 $INT_LAN_RANGE,0/0,tcp,1863 >$INT_LAN_RANGE,0/0,tcp,2401 $INT_LAN_RANGE,0/0,tcp,5800 >$INT_LAN_RANGE,0/0,tcp,5900 $INT_LAN_RANGE,0/0,tcp,6800:6900 >$INT_LAN_RANGE,0/0,udp,6800:6900 $INT_LAN_RANGE,0/0,tcp,6901 >$INT_LAN_RANGE,0/0,udp,6901 $INT_LAN_RANGE,0/0,tcp,6970:7170 >$INT_LAN_RANGE,0/0,tcp,7070" > ># 7.) >FW_PROTECT_FROM_INTERNAL="yes" > ># 8.) >FW_AUTOPROTECT_SERVICES="yes" > ># 9.) >FW_SERVICES_EXT_TCP="" >FW_SERVICES_EXT_UDP="" # Common: domain >FW_SERVICES_EXT_IP="" >FW_SERVICES_DMZ_TCP="53 3128" >FW_SERVICES_DMZ_UDP="53" >FW_SERVICES_DMZ_IP="" >FW_SERVICES_INT_TCP="23 53 3128" >FW_SERVICES_INT_UDP="53" >FW_SERVICES_INT_IP="" > ># 10.) >FW_TRUSTED_NETS="$EXT_ZFT_GATE,tcp,22" > ># 11.) >FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" >FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" > ># 12.) >FW_SERVICE_AUTODETECT="yes" # Autodetect the services below when starting >FW_SERVICE_DNS="yes" >FW_SERVICE_DHCLIENT="no" >FW_SERVICE_DHCPD="no" >FW_SERVICE_SQUID="yes" >FW_SERVICE_SAMBA="no" > ># 13.) >FW_FORWARD="$INT_LAN_RANGE,$DMZ_IP_RANGE 0/0,$DMZ_EXCHANGE,tcp,25 >0/0,$DMZ_EXCHANGE,tcp,80 0/0,$DMZ_EXCHANGE,tcp,135 0/0,$DMZ_EXCHANGE,tcp,443 >0/0,$DMZ_BACKUP,tcp,21 0/0,$DMZ_BACKUP,tcp,20" > ># 14.) >FW_FORWARD_MASQ="" # Beware to use this! > ># 15.) >FW_REDIRECT="" > ># 16.) >FW_LOG_DROP_CRIT="yes" >FW_LOG_DROP_ALL="yes" >FW_LOG_ACCEPT_CRIT="no" >FW_LOG_ACCEPT_ALL="no" >FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix >SuSE-FW" > ># 17.) >FW_KERNEL_SECURITY="yes" > ># 18.) >FW_STOP_KEEP_ROUTING_STATE="yes" > ># 19.) >FW_ALLOW_PING_FW="no" >FW_ALLOW_PING_DMZ="no" >FW_ALLOW_PING_EXT="yes" > > > >-- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com > >

1 0

Re: [suse-security] Kernel
by Hendrik Brandenburger 05 Sep '01

05 Sep '01

Am Mit, 05 Sep 2001 schrieb Eduard Meiler: > > Hallo , can anybody tell me what all of this mean ?? > > > > Sep 5 00:06:35 wall kernel: eth0: Transmit error, Tx status register 82. >Hi, >just one question. Do you have a ethernetcard with the Realtek9029-Chip in ^^ Sorry, I mean 8029. Greetings Hendrik --

1 0

SuSE Firewall 2 - Masq , IRC
by Michael Brandejsky 05 Sep '01

05 Sep '01

Dear List, i have Suse 7.2 Pro and the SuSE Firewall2 , ftp, www masquerade works fine but i have a problem to tranfer DCC Files in IRC , time ago there are some IRC Masq Modules, but they are not compatible to the 2.4.x Kernel. So , what should I do to use DCC Sends. I don't want to install an old kernel. greetings

2 1

Kernel
by Eduard Meiler 05 Sep '01

05 Sep '01

Hallo , can anybody tell me what all of this mean ?? Sep 5 00:06:35 wall kernel: eth0: Transmit error, Tx status register 82. Sep 5 00:06:35 wall kernel: Flags; bus-master 1, dirty 17668(4) current 17668(4) Sep 5 00:06:35 wall kernel: Transmit list 00000000 vs. c74f2300. Sep 5 00:06:35 wall kernel: 0: @c74f2200 length 80000586 status 00010586 Sep 5 00:06:35 wall kernel: 1: @c74f2240 length 80000586 status 00010586 Sep 5 00:06:35 wall kernel: 2: @c74f2280 length 80000586 status 00010586 Sep 5 00:06:35 wall kernel: 3: @c74f22c0 length 80000586 status 80010586 Sep 5 00:06:35 wall kernel: 4: @c74f2300 length 80000056 status 00010056 Sep 5 00:06:35 wall kernel: 5: @c74f2340 length 80000056 status 00010056 Sep 5 00:06:35 wall kernel: 6: @c74f2380 length 8000002a status 0001002a Sep 5 00:06:35 wall kernel: 7: @c74f23c0 length 8000003e status 0001003e Sep 5 00:06:35 wall kernel: 8: @c74f2400 length 8000004a status 0001004a Sep 5 00:06:35 wall kernel: 9: @c74f2440 length 80000055 status 00010055 Sep 5 00:06:35 wall kernel: 10: @c74f2480 length 80000063 status 00010063 Sep 5 00:06:35 wall kernel: 11: @c74f24c0 length 80000036 status 00010036 Sep 5 00:06:35 wall kernel: 12: @c74f2500 length 80000057 status 00010057 Sep 5 00:06:35 wall kernel: 13: @c74f2540 length 80000071 status 00010071 Sep 5 00:06:35 wall kernel: 14: @c74f2580 length 80000042 status 00010042 Sep 5 00:06:35 wall kernel: 15: @c74f25c0 length 80000047 status 00010047 Sep 5 00:15:17 wall su: (to nobody) root on none Sep 5 00:15:17 wall PAM-unix2[4185]: session started for user nobody, service su Sep 5 00:17:04 wall PAM-unix2[4185]: session finished for user nobody, service su Mit freundlichen Grüßen Eduard Meiler ___________________________

6 5

RE: [SLE] SuSEfirewall2 questions ?
by Eric Romang 05 Sep '01

05 Sep '01

Hello, Thanxs for your answer. I have uninstall SuSEfirewall1 and personnal suse firewall in the method you give. Thxs ;) I wan't to know how to make an upgrade of SuSEFirewall2 there is a new version on http://www.suse.de/~marc Yes I use SSH to log remotely ;) For DHCPD, my ps -aux give me this : root 611 0.0 0.2 1364 636 ? S 13:13 0:00 /sbin/syslogd -a /var/lib/dhcp/var/run/dhcpd.pid Why DHCPD has an process with syslog ?? I don't have lunch DHCPD on startup... I don't wan't dhcpd... In my rc.concfig START_DHCPD is set to no... but they are some pid ... But I don't understand why my server freeze whitout reason... Regards > -----Original Message----- > From: Jaakko Tamminen [mailto:jtamminen@satabaana.net] > Sent: 05 September 2001 12:58 > To: Eric Romang > Subject: Re: [SLE] SuSEfirewall2 questions ? > > > Hi > > Disable personal-firewall, that blocks all outside connection attempts, > and that seems to be the case for You. > > To remove the "old" susefirewall, do it with yast->install/remove > packages, or you can try someting like "rpm -e SuSEfirewall". The name > must be correct, but I believe it might be that one. > > Actually there is no need to remove the "old" firewall, just don't > enable it. In my server I have both installed the same time, and the > only annoying thing is that there is both entrys in configuration file, > but it does not really matter. > > I hope You are using ssh to log remotely...? > > About dhcp.. I did not really understand Your question.. Do you need > DHCP-client to get Your IP for the server? If so, You need to enable > that (start dhcp), and also in firewall configuration section you need > to set "dhcp client" to YES. > > Hope this helps > > Jaska. > > > > > > > Hello, > > > > I have install SuSEfirewall2 on my serveur with two ethernet card. > > One for the private network, the other to the internet. > > > > I have some crash from the server I can't explain. > > The server freeze and i don't have the hand on it... no more root > > login possible > > and the tty are froozen... > > > > I have no error messages in my message log file, and also in my > > firewall message. > > > > But I have this line in my message log and warm message. > > > > My message log messages : > > > > Sep 6 12:04:36 lithium SuSEfirewall2: Firewall rules successfully > > set from /etc/rc.config.d/firewall2.rc.config > > Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: > > SuSEpersonal-firewall: Loading of module ipchains was not successful. > > Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: Aborting. No > > action taken. > > > > My warm log messages : > > > > Sep 6 12:04:35 lithium kernel: ip_tables: (c)2000 Netfilter core > > team Sep 6 12:04:35 lithium kernel: ip_conntrack (2047 buckets, > > 16376 max) Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: > > SuSEpersonal-firewall: Loading of module ipchains was not successful. > > Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: Aborting. No > > action taken. > > > > I have also, my sylogd how run dhcp, but i don't have start the dhcpd > > on startup... > > I can see a line in process... > > > > Somebody can explain me why my server freeze ?? > > > > And another question, I wan't to upgrade my SuSEfirewall2. > > What are the step to remove the old one ? > > > > Thanxs. > > Regards > > > > Eric Romang - System Administrator > > eric.romang(a)synapse.lu > > --------------------------------------------------------------------- > >------- --------- > > Site : http://www.synapse.lu > > Synapse Internet Services > > 49, Bd. G-D. Charlotte, L-1331 Luxembourg > > Tel : +352 / 44 79 44 77 > > Fax : +352 / 44 79 44 79 > > GSM : +352 / 021 7000 35 > > --------------------------------------------------------------------- > >------- --------- > > ---------------------------------------- > Content-Type: text/html; charset="iso-8859-1"; name="Liite: 1" > Content-Transfer-Encoding: quoted-printable > Content-Description: > ---------------------------------------- >

2 2

Firewall-SUSE 7.0
by Juergen Foag 05 Sep '01

05 Sep '01

Hello, on SUSE-LINUX 7.0, kernel 2.2.16, I've installed the firewall in the sense of a packet-filter (no proxies, no DMZ, no masquerading). From an firewall-external host (192.168.0.3), I tried to establish a connection (ssh, ping or http with our internal webserver (xx.yy.zz.15)) but have failures. The network topology is: external firewall firewall internal argos eth1 eth0 webserver 192.168.0.3 192.168.0.2 xx.yy.zz.42 xx.yy.zz.15 In the case of trying to connect from the external web client our Webserver http://xx.yy.zz.15, the var/log/firewall-file on the firewall host notices: kernel: Packet log: forward ACCEPT eth0 PROTO=6 192.168.0.3:36341 xx.yy.zz.15:80 With ethereal, I've logged on the internal interface (eth0) of the dual-homed firewall-host the message: Source Destination Protocol Info argosxx.yy.zz.42 xx.yy.zz.15 TCP Source Port 36345 > Dest. Port http (80) So I conclude, that my web request toward my webserver is handled correctly. But with ethereal on the webserver interface, I cannot receive the request message (going to port 80 http). After the web client request was timed out, the message on the web client host (argos) sends "unable to connect to server". The firewall.rc.config file looks like: # 2.) FW_DEV_WORLD="eth1" FW_DEV_WORLD_eth1="192.168.0.2 255.255.255.0" # 3.) FW_DEV_INT="eth0" FW_DEV_INT_eth0="xx.yy.zz.42 255.255.255.0" # 4.) FW_DEV_DMZ="" # 5.) FW_ROUTE="yes" # 6.) FW_MASQUERADE="no" FW_MASQ_NETS="" FW_MASQ_DEV="$FW_DEV_WORLD" # e.g. "ippp0" or "$FW_DEV_WORLD" # 7.) FW_PROTECT_FROM_INTERNAL="no" # -> NIS ypbind # 8.) FW_AUTOPROTECT_GLOBAL_SERVICES="no" # "yes" is a good choice # 9.) FW_SERVICES_EXTERNAL_TCP="0:65535" # for trial FW_SERVICES_EXTERNAL_UDP="0:65535" # for trial FW_SERVICES_INTERNAL_TCP="0:65535" # for trial FW_SERVICES_INTERNAL_UDP="0:65535" # for trial # 10.) FW_TRUSTED_NETS="192.168.0.0 xx.yy.zz.0/24" FW_SERVICES_TRUSTED_TCP="ssh 8 80 443" # Common: ssh FW_SERVICES_TRUSTED_UDP="8" # Common: syslog time ntp # 11.) FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" # Common: "ftp-data" (sadly!) FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" # Common: "dns" # 12.) FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SAMBA="no" # 13.) FW_FORWARD_TCP="" # Beware to use this! FW_FORWARD_TCP="192.168.0.3/24,xx.yy.zz.15,80 192.168.0.3/24,xx.yy.zz.4,22" FW_FORWARD_UDP="" # Beware to use this! # 14.) FW_FORWARD_MASQ_TCP="" # Beware to use this! FW_FORWARD_MASQ_UDP="" # Beware to use this! # 15.) FW_REDIRECT_TCP="" FW_REDIRECT_UDP="" # 16.) FW_LOG_DENY_CRIT="yes" FW_LOG_DENY_ALL="yes" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" # normally no # 17.) FW_KERNEL_SECURITY="no" # 18.) FW_STOP_KEEP_ROUTING_STATE="no" # 19.) FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="no" # 20.) FW_ALLOW_FW_TRACEROUTE="no" # 21.) FW_ALLOW_FW_SOURCEQUENCH="yes" # 22.) FW_MASQ_MODULES="autofw cuseeme ftp irc mfw portfw quake raudio user vdolive" So, if anyone has a solution to get a connection established, let me know it. Thanks Jürgen Foag -- _____________________________________________________________________ Telefon: +49 (0) 89 / 289 - 25290 Fax: +49 (0) 89 / 289 - 28323 Technische Universität München - Lehrstuhl f. Integrierte Schaltungen Arcisstrasse 21 - 80290 München - Deutschland / Germany E-Mail: Juergen.Foag(a)ei.tum.de Homepage: http://www.lis.e-technik.tu-muenchen.de/people/jf.html _____________________________________________________________________ If everything you try works, you are not trying hard enough ! (Gordon Moore) _____________________________________________________________________

1 0

Re : SuSEfirewall2 questions ?
by Eric Romang 05 Sep '01

05 Sep '01

Hello, Thanxs for your answer. I have uninstall SuSEfirewall1 and personnal suse firewall in the method you give. Thxs ;) I wan't to know how to make an upgrade of SuSEFirewall2 there is a new version on http://www.suse.de/~marc Yes I use SSH to log remotely ;) For DHCPD, my ps -aux give me this : root 611 0.0 0.2 1364 636 ? S 13:13 0:00 /sbin/syslogd -a /var/lib/dhcp/var/run/dhcpd.pid Why DHCPD has an process with syslog ?? I don't have lunch DHCPD on startup... I don't wan't dhcpd... In my rc.concfig START_DHCPD is set to no... but they are some pid ... But I don't understand why my server freeze whitout reason... Regards > > > -----Original Message----- > > From: Jaakko Tamminen [mailto:jtamminen@satabaana.net] > > Sent: 05 September 2001 12:58 > > To: Eric Romang > > Subject: Re: [SLE] SuSEfirewall2 questions ? > > > > > > Hi > > > > Disable personal-firewall, that blocks all outside connection attempts, > > and that seems to be the case for You. > > > > To remove the "old" susefirewall, do it with yast->install/remove > > packages, or you can try someting like "rpm -e SuSEfirewall". The name > > must be correct, but I believe it might be that one. > > > > Actually there is no need to remove the "old" firewall, just don't > > enable it. In my server I have both installed the same time, and the > > only annoying thing is that there is both entrys in configuration file, > > but it does not really matter. > > > > I hope You are using ssh to log remotely...? > > > > About dhcp.. I did not really understand Your question.. Do you need > > DHCP-client to get Your IP for the server? If so, You need to enable > > that (start dhcp), and also in firewall configuration section you need > > to set "dhcp client" to YES. > > > > Hope this helps > > > > Jaska. > > > > > > > > > > > > > Hello, > > > > > > I have install SuSEfirewall2 on my serveur with two ethernet card. > > > One for the private network, the other to the internet. > > > > > > I have some crash from the server I can't explain. > > > The server freeze and i don't have the hand on it... no more root > > > login possible > > > and the tty are froozen... > > > > > > I have no error messages in my message log file, and also in my > > > firewall message. > > > > > > But I have this line in my message log and warm message. > > > > > > My message log messages : > > > > > > Sep 6 12:04:36 lithium SuSEfirewall2: Firewall rules successfully > > > set from /etc/rc.config.d/firewall2.rc.config > > > Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: > > > SuSEpersonal-firewall: Loading of module ipchains was not successful. > > > Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: Aborting. No > > > action taken. > > > > > > My warm log messages : > > > > > > Sep 6 12:04:35 lithium kernel: ip_tables: (c)2000 Netfilter core > > > team Sep 6 12:04:35 lithium kernel: ip_conntrack (2047 buckets, > > > 16376 max) Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: > > > SuSEpersonal-firewall: Loading of module ipchains was not successful. > > > Sep 6 12:04:36 lithium /sbin/SuSEpersonal-firewall: Aborting. No > > > action taken. > > > > > > I have also, my sylogd how run dhcp, but i don't have start the dhcpd > > > on startup... > > > I can see a line in process... > > > > > > Somebody can explain me why my server freeze ?? > > > > > > And another question, I wan't to upgrade my SuSEfirewall2. > > > What are the step to remove the old one ? > > > > > > Thanxs. > > > Regards > > > > > > Eric Romang - System Administrator > > > eric.romang(a)synapse.lu > > > --------------------------------------------------------------------- > > >------- --------- > > > Site : http://www.synapse.lu > > > Synapse Internet Services > > > 49, Bd. G-D. Charlotte, L-1331 Luxembourg > > > Tel : +352 / 44 79 44 77 > > > Fax : +352 / 44 79 44 79 > > > GSM : +352 / 021 7000 35 > > > --------------------------------------------------------------------- > > >------- --------- > > > > ---------------------------------------- > > Content-Type: text/html; charset="iso-8859-1"; name="Liite: 1" > > Content-Transfer-Encoding: quoted-printable > > Content-Description: > > ---------------------------------------- > > > > > -- > 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 >

2 1

Re: [suse-security] ssh-incompatibility ?
by Daniel Quappe 05 Sep '01

05 Sep '01

hi folks, many thanks to all hints! i decided to upgrade to openssh version 2 and that works...;-) best regards, daniel -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

1 0