December 2001 - openSUSE Security - openSUSE Mailing Lists

Permission problem with Apache
by Jasmine Davis 04 Dec '01

04 Dec '01

Hi I am setting up apache 1.3.19 on our Suse 7.1 server & I am have a problem with mapping ~user to public_html. After creating the public_html directory in the user directory & placing an index page in it. I then try typing in the url http://my.server/~user I get a 403 error, "Forbidden You don't have permission to access /~user on this server". I have a had a lot of experience with IIS but this is the first time I have started to work with Apache. So I know this is something stupid, I just can't put my finger on it. Regards, Jasmine -- Jasmine Davis - Photo Girl www.photo-girl.com -------------------------->> Welcome to Suse Linux 7.1 i686 - Kernel 2.4.2-4 hotgirls login: 9:29am up 3 days, 21:02, 1 user, load average: 0.09, 0.33, 0.40

8 9

SuSE Security Announcement: OpenSSH
by Sebastian Krahmer 04 Dec '01

04 Dec '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: openssh Announcement-ID: SuSE-SA:2001:044 Date: Mon Dec 3 14:01:19 CET 2001 Affected SuSE versions: 6.4, 7.0, 7.1, 7.2, 7.3 Vulnerability Type: various bugs Severity (1-10): 4 SuSE default package: yes Other affected systems: All systems shipping OpenSSH <= 2.9.9 Content of this advisory: 1) security vulnerability resolved: Various problems in OpenSSH. 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 OpenSSH daemon shipped with SuSE distributions contains various minor bugs which allows bypassing of IP-access control in some circumstances or the deletion of files named "cookies" if X11 forwarding is enabled. It has also been verified that the recent remotely exploitable crc32 bug as well as the logging-bug has been fixed in our latest ssh packages. We strongly recommend to update to OpenSSH version 2.9.9p2. Please download and update the packages as described in section 3. Then invoke /etc/rc.d/sshd restart to restart the OpenSSH daemon. If you are logged on via sshd, then it is adviseable to perform the update in an atjob to make sure that it can be completed if your secure shell daemon gets killed: rpm -Uhv openssh-*.rpm echo "rcsshd restart" | at now Please note that OpenSSH 2.9.9p2 is *not* vulnerable to the crc32/deattack exploit. Some people made wrong statements about that recently and claimed they have found exploits for this version "in the wild" which exploits the crc32 hole against this version. This is wrong and you can safely ignore these discussions. If you installed the ssh-1.2.27 package instead of the openssh package no updates should be necessary as long as you recognized the SuSE Security Announcement SuSE-SA:2001:04 which recommends to update to the latest ssh-1.2.27 packages. Due to legal constraints, the packages for the 7.0 and older distributions containing cryptographic code can be found on ftp.suse.de, not ftp.suse.com. The distribution 7.1 and newer have all of their update packages on ftp.suse.com. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssh-2.9.9p2-38.i386.rpm 6ba603f1115b0125abf0b62f28ba6666 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssh-2.9.9p2-38.src.rpm 644d74829ecaa12c6a28cc9564bb0a1c SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssh-2.9.9p2-25.i386.rpm 0b0406a63181bf23c683add3f6f9abc3 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssh-2.9.9p2-25.src.rpm 5914018a06e77f7477058afa8617ab10 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/openssh-2.9.9p2-26.i386.rpm 0d69dce8f61317c84efde55f6cc95f10 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/openssh-2.9.9p2-26.src.rpm 3aeba61d45d243773db8d1b7eedf6924 SuSE-7.0 ftp://ftp.suse.de/pub/suse/i386/update/7.0/sec1/openssh-2.9.9p2-27.i386.rpm 2defc4cf8182b1e5eb4b204224007dd6 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/7.0/zq1/openssh-2.9.9p2-27.src.rpm 1999c7c42507c1c4d831daf170e88c6e SuSE-6.4 ftp://ftp.suse.de/pub/suse/i386/update/6.4/sec1/openssh-2.9.9p2-27.i386.rpm 5fe6fdee55502e81b383b5b11047cee9 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/6.4/zq1/openssh-2.9.9p2-27.src.rpm cfee6bebb8086dc2d861aeb5fff6dc17 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/sec1/openssh-2.9.9p2-8.sparc.r… 8dcf46c82f11c35e8812d477caacd3b2 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/openssh-2.9.9p2-8.src.rpm 27ed16f77bcabd34919681fa07fcbd1c SuSE-7.0 ftp://ftp.suse.de/pub/suse/sparc/update/7.0/sec1/openssh-2.9.9p2-8.sparc.rpm a23db0e0516a935cfce8a199a48ce036 source rpm: ftp://ftp.suse.de/pub/suse/sparc/update/7.0/zq1/openssh-2.9.9p2-8.src.rpm e4c6c636fe7dd5e234d89dd28564611b AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec1/openssh-2.9.9p2-5.alpha.rpm b0e29b53f247c7a8ba6d17297867730e source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/openssh-2.9.9p2-5.src.rpm 73a832a3b10876d751203aca7fd37607 SuSE-7.0 ftp://ftp.suse.de/pub/suse/axp/update/7.0/sec1/openssh-2.9.9p2-6.alpha.rpm 5e07df7ce670e3918f0948495d74e23c source rpm: ftp://ftp.suse.de/pub/suse/axp/update/7.0/zq1/openssh-2.9.9p2-6.src.rpm 3a26418017f5af49ba707e51fa28d954 SuSE-6.4 ftp://ftp.suse.de/pub/suse/axp/update/6.4/sec1/openssh-2.9.9p2-6.alpha.rpm c2e7364a00aef31a9d121302d316ce4f source rpm: ftp://ftp.suse.de/pub/suse/axp/update/6.4/zq1/openssh-2.9.9p2-6.src.rpm d3a9299f748395912644c375e24302f7 Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssh-2.9.9p2-23.ppc.rpm bdab314f57128accaa4855a8aedf23df source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssh-2.9.9p2-23.src.rpm 840bde44f9b372e637a7bdcf3b11a87e SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/openssh-2.9.9p2-25.ppc.rpm d3b5f2b85ce6cf9e30a0826127f5b6e4 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/openssh-2.9.9p2-25.src.rpm 888e553f06f96ddd7395ad4c241e0b69 SuSE-7.0 ftp://ftp.suse.de/pub/suse/ppc/update/7.0/sec1/openssh-2.9.9p2-18.ppc.rpm 34eee0c543d2cf266d084d7262475573 source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/7.0/zq1/openssh-2.9.9p2-18.src.rpm c33d2e38303853e9363ee0beb9889b43 SuSE-6.4 ftp://ftp.suse.de/pub/suse/ppc/update/6.4/sec1/openssh-2.9.9p2-17.ppc.rpm 4d00f9e0a85631c3e2dd721ca0784f27 source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/6.4/zq1/openssh-2.9.9p2-17.src.rpm 685e7c8f85117384ea1205b683593b47 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: No additional information in this announcement. ______________________________________________________________________________ 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 L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GZkBogQ57vSBEQQAk/GN+ftr 7+DBlSoixDDpfRnUk+jApGEt8hCnrnjVnPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45 t4E0fKyLVzDerCRFB1swz/mNDxT26DLysdBV5fwNHTPhxa67goAZVrehQPqJEckk IpYriOaYcKpF3n5fQIZMEfMaHEElQhcXML8AoJVXDkJYh7vI8EUB8ZURNLZMEECN A/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6TepRdLZhaylwVF/iu7uIn62ZUL4//NTOC DY7V63qg4iba/fUbOsWtEnGaiE7mQuAlsSWvRspwRA9/g9rdVf3/JdLJrLmKBThe yG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQnJn2euqylHRubEQP/aL53NZK0kBdvrKgf f6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiY I2lTRYT4uMdHuwVC3b4DqAKmoy375FERwHkrMVyKBJslv8QtbAWw5A1CAUseaHo+ 91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1U0UgUGFja2FnZSBTaWduaW5nIEtleSA8 YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUCOe70gQUJA8JnAAQLCgMEAxUDAgMWAgEC F4AACgkQqE7a6JyACspfLACffAYA+NM8NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0 xY7WbKoXs1+72b2AiEYEEBECAAYFAjpwXlIACgkQnkDjEAAKq6TczgCgi+ddhWb7 +FWcfeE6WwPZccqAHowAnjjtRyGwHLQHr5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey 5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk/xGJJREt7V12iSafaRzGuH8xWvIz1bb+ VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6iJXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq 2pudfwljp52lYVM53jgPYEz0q/v3091nlZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU +lDQT2EC6VKaxeWK8pNt6UFDwICRDQxKnlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKN bWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc 9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelxufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr 6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7UVCiSfb9CV38dmeHdPCEEjDUWquFYEnvj 3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qTJzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBE VE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/ 9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiUXpRoFCdglMznbcAyCk9C2wqb2j/D1Z2B eSBaGCSFkR6pRLebnE17LWcu72Iy+r0z+JecbPiyDpDZj4apn7IC81aNFGi7fNIT sHODbwwjiwADBgf/YPvVdzkc8OC7ztacEWCanwylKvxCdKzTDA+DfES6WUYShyiV JvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/pdGy1aKtJZrAnFEsofpmOj8VoqyyFgp/y AGQBp12+mXek7SCZRhuqalDfEMRiWEJ6J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxx QqNQXL6Z3NSxS61p+5n6BseiDUI39xxkKTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwb sklszZt6xbU+R0SjFqTvjPWx6eHfqbmNC9WMDdTjGrXDDKXFp2aYlokfN6It9vsb VlGNlOwHt/JjGoPMxW6Xqj0FLA7/VewgCdXW64hMBBgRAgAMBQI57vSSBQkDwmcA AAoJEKhO2uicgArKSyIAmwUHf/vtKQfcmVg4asR7U6XQl0bAAJ4pO22B5U8UH6IY l2LBCXFqw5+5fA== =Jnnf - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPAuIOXey5gA9JdPZAQGvqwf/VccDrlkw/x8n8HQ31D83Rj1P6BLP8SGO feN3PDYK3og7ES9LhNxca1yJDnhAUQskCK5p32zMlEF2j1+2VTTn2MNq0yunoO86 s399Onk0+7x9O9WBXP5h7CPE4OfgPrlKlJm5BpQ3dT601TuetMT0JANJHX/xofGk Zbd9IpAyKH8r71RYKQws9C9CAGUm2RlPTe4TEB3i+Z3e/rpG8gGKsTNtzqM4YOln iMXu+EfFv1HQQAXIQzGz4M+FnCTf7zTsHWRN2yMBCAjC6RKG09F54/1+I0yvG2GN ENVrmacVqiZ1gU+71aTVEWbsTJYRfScE44fkW3FgC2YqCUUqRiMAsA== =tD4R -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

5 7

Firewall on CD and T-DSL
by Alexander Reach 04 Dec '01

04 Dec '01

Hi Group, has anyone successfully established a connection with the firewall on CD and T-DSL, and can give me some tips how to enable this? I already have a normal SuSE 7.0 running with T-DSL, but now we want to use the Firewall on CD (T-DSL is only Backup, of course ;) ). Thanks, Alexander

1 0

Stuff in firewall log ...
by Ray Leach 04 Dec '01

04 Dec '01

Hi Does anyone know what this is? Dec 4 09:51:55 firefly kernel: eth2: Transmit error, Tx status register 82. Dec 4 09:51:55 firefly kernel: Flags; bus-master 1, dirty 5131692(12) current 5131692(12) Dec 4 09:51:55 firefly kernel: Transmit list 00000000 vs. cff6d500. Dec 4 09:51:55 firefly kernel: 0: @cff6d200 length 80000265 status 00010265 Dec 4 09:51:55 firefly kernel: 1: @cff6d240 length 80000036 status 00010036 Dec 4 09:51:55 firefly kernel: 2: @cff6d280 length 800000b1 status 000100b1 Dec 4 09:51:55 firefly kernel: 3: @cff6d2c0 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 4: @cff6d300 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 5: @cff6d340 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 6: @cff6d380 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 7: @cff6d3c0 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 8: @cff6d400 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 9: @cff6d440 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 10: @cff6d480 length 800005ea status 000105ea Dec 4 09:51:55 firefly kernel: 11: @cff6d4c0 length 800005ea status 800105ea Dec 4 09:51:55 firefly kernel: 12: @cff6d500 length 800000ff status 000100ff Dec 4 09:51:55 firefly kernel: 13: @cff6d540 length 80000036 status 00010036 Dec 4 09:51:55 firefly kernel: 14: @cff6d580 length 800000ff status 000100ff Dec 4 09:51:55 firefly kernel: 15: @cff6d5c0 length 80000036 status 00010036 I have several of these in my firewall log. Started a few days ago. Also notice that there are transmit errors on the interfaces. Is this normal? Ray

2 2

How can sshd be turned off and on via a browser on a suse distro?
by phil 03 Dec '01

03 Dec '01

I have been trying to figure out how to get sshd to start and stop via a browser. If I call rcsshd stop or rcsshd start from a cgi script it won't find the keys. In general I have the cgi script call sshd like so: if variable = variable then system rcsshd start else system rcsshd stop there's a little more to it than that (obviously), and I know it can work, I just can't get suse to cooperate. I've tried calling sshd from /etc/ssh, from /usr/sbin etc none of these methods will seem to work The reasons I wish to do this: 1. crackers won't see a port open when they scan. 2. the html page for controling sshd can be obscured. eg. http://somewhere/lkjsfkjsfljsdfh/123987kjghkjhdfgkh/lkjsdflkjsldfkjlskdjf.c… 3. an .htaccess can be used to protect the page which the cracker would need to know the name and password for. 4. even if said cracker could find obscured page, and hack name and pass, they still would need to find the correct name and password to actually logon the sshd. 5. sshd seems to be starting the same trend as "wu_ftp" and such. Future idea: Doing the same for ftpd. Need to somehow write a fresh inet.d and HUP it somehow... ? Thanks phil

3 2

Re[2]: [suse-security] UDP 4665
by Ralf Koch 03 Dec '01

03 Dec '01

Hi, myabe that I got something wrong here - but why do you reply to 3 mails of this thread without adding anything? And - by the way - please answer to the list. If there's anything interesting in the answer, it might be of interest for others too. Cheers, Ralf >Hallo Ralf, > >Am Thursday, November 29, 2001, 10:09:22 PM, schriebst du: > >> Hi list, > >> quick question: > >> In the last days, my firewall logs filling up with messages like the >> following: > >> Nov 29 22:02:57 acme kernel: Packet log: input DENY ppp0 PROTO=17 >> 217.216.153.114:3058 217.0.156.224:4665 L=34 S=0x00 I=29563 F=0x0000 >> T=113 (#48) > >> 15 - 50 hits per second. Does anybody know what they try to connect to? >> A quick scan gave me something like eDonkey, but I don't think eDonkey >is >> widely spread to give my firewall so many hits. > >> Any guesses? > >> Thanks > >> Ralf >> * >> * Ralf 'coko' Koch >> * mailto:info@formel4.de >> * >> --- >> Hiroshima 45, Tchernobyl 86, Windows 2000 > > >> -- >> To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >> For additional commands, e-mail: suse-security-help(a)suse.com > >

2 1

Connect to Port 0
by secadmin＠gmse.de 03 Dec '01

03 Dec '01

Hi, as far as I know Ports 8 and 0 are unassigned. What does the following = entry in /var/log/firewall mean? Dec 1 11:02:12 inet kernel: Packet log: input ACCEPT eth1 PROTO=3D1 = 131.246.137.5:8 a.b.c.d:0 L=3D1500 S=3D0x00 I=3D19222 F=3D0x4000 T=3D242 = (#15) The firewall should block this connect. We are using Suse 7.1 with = standard firewall configuration. Access is allowed only on smtp, www and https. Thanks Georg

2 1

OpenSSH update requires shlibs5 also ?
by Togan Muftuoglu 03 Dec '01

03 Dec '01

* Sebastian Krahmer; <krahmer(a)suse.de> on 03 Dec, 2001 wrote: > distributions containing cryptographic code can be found on ftp.suse.de, > not ftp.suse.com. The distribution 7.1 and newer have all of their > update packages on ftp.suse.com. > Unless I misread the required packages upgrade of openssh for SuSE 7.1 fails because shlibs5.rpm is not installed. Well I did not installed it a) I do not have space on my firewall machine b) on the previous update it was not complaining about the missing files libICE.so.6 libSM.so.6 libXt.so.6 c) I do not want to install shlibs as I do not have space so here I go ask the dumb question anything else I can do about this before I go and issue the --force option ? Sorry for the silly question but I already had a bad day and I do not want to ruin it any further -- Togan Muftuoglu

2 2

Re: [suse-security-announce] SuSE Security Announcement: OpenSSH
by Simon Oliver 03 Dec '01

03 Dec '01

I installed this package last week. Is this a repeat Announcement?] -- Simon Oliver Sebastian Krahmer wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > ______________________________________________________________________________ > > SuSE Security Announcement > > Package: openssh > Announcement-ID: SuSE-SA:2001:044 > Date: Mon Dec 3 14:01:19 CET 2001 > Affected SuSE versions: 6.4, 7.0, 7.1, 7.2, 7.3 > Vulnerability Type: various bugs > Severity (1-10): 4 > SuSE default package: yes > Other affected systems: All systems shipping OpenSSH <= 2.9.9 > > Content of this advisory: > 1) security vulnerability resolved: Various problems in OpenSSH. > problem description, discussion, solution and upgrade information > 2) pending vulnerabilities, solutions, workarounds > 3) standard appendix (further information) > > ______________________________________________________________________________

3 2

Re: [suse-security] Iptables, netfiltering? I need only...
by mario libraro 03 Dec '01

03 Dec '01

BLeonhardt(a)analytek.de wrote: > > Hi, > so I'd try : > If you want only from internal network ( ie eth0 ) and the external is eth1 > iptables -I INPUT -i eth1 -p tcp - -dport 22 -m state - -state > NEW,ESTABLISHED,RELATED -j DROP > iptables -I INPUT -i eth0 -p tcp - -dport 22 -j ACCEPT > Maybe something like this could work ... much luck ! I installed SuSEFirewall2.. and recompiled the kernel to include: - Network packet filtering (CONFIG_NETFILTER) make dep make bzlilo CTRL-ALT-DEL & win-fashion reboot ;) (my kernel is all "static" (no modules) sic!) SuSEFirewall phase 1 of 3 OK SuSEFirewall phase 2 of 3 OK SuSEFirewall phase 3 of 3 AAGGHHH! iptables v.2.1a: can't initialize iptables table 'mangle': iptables who? (do you need insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v.2.1a: can't initialize iptables table 'filter': iptables who? (do you need insmod?) Perhaps iptables or your kernel needs to be upgraded. [...repeated a thousand of times] same error if I type # iptables -L iptables v.2.1a: can't initialize iptables table 'filter': iptables who? (do you need insmod?) Perhaps iptables or your kernel needs to be upgraded. :o( can you suggest me wether I have to add some other module to kernel? -- Mario Libraro Web Applications Developer Fulltrading S.p.A. 00148 Roma - Via Di Affogalasino, 105 tel. +39 06 65 73 170 fax +39 06 65 73 529 mob. +39 347 5205 752 email: m.libraro(a)fulltrading.it m.libraro(a)tiresia.it web: www.fulltrading.it

1 0