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

AvMailGate does not find Eicar
by Jochen Kaechelin 03 Dec '01

03 Dec '01

I installes Antivir and AntivirMailGate from SuSEs original 7.3prof. antivir is working find and it detects the test-file from eicar: checking drive/path (cwd): /home/jochen /home/jochen/fff Date: 2.12.2001 Time: 10:10:59 Size: 68 VIRUS: file contains code of the virus 'Eicar-Test-Signatur' /home/jochen/eicarcom2.zip Date: 2.12.2001 Time: 23:58:43 Size: 308 VIRUS: file contains a signature of the virus 'Eicar-Test-Signatur' My /etc/avmailgate.conf looks this way: user uucp group uucp SpoolDir /var/spool/vscan/avmailgate Postmaster jochen PidFile_avgated /var/run/avmailgate/avmailgate_d.pid ListenAddress 192.168.0.1 port 25 SmtpTimeout 300 MaxIncomingConnections 0 MaxMessageSize 0 #MaxRecipientsPerMessage100 #MinFreeBlocks 100 RefuseEmptyMailFrom NO PidFile_avgatefwd /var/run/avmailgate/avmailgate_fwd.pid MaxForwarders 3 BlockSuspiciousMime FALSE ExposeAlerts FALSE ForwardTo SMTP: localhost port smtp-backdoor my /etc/sendmail.cf contains the following: O DaemonPortOptions=Name=MTA,Port=smtp-backdoor my /etc/services contains the following: smtp-backdoor 825/tcp # AntiVir MailGate When I send the attached eicar-test-file AntiVirMailGate shows no reaction. When starting with "rcavgate start" /var/log/mail shows the following: Dec 3 06:58:15 jochen avgated[19907]: ready to accept connections on port 25 Dec 3 06:58:16 jochen avmgatefwd[19906]: running in full featured mode When sending a mail with kmail /var/log/mail shows the following: Dec 3 07:05:38 jochen sendmail[19982]: fB365c419982: from=jochen, size=442, class=0, nrcpts=1, msgid=<200112030605.fB365c419982(a)jochen.wa-p.netz>, relay=localhost [[UNIX: localhost]] Dec 3 07:05:39 jochen sendmail[19984]: fB365c419982: to=jk(a)wa-p.de, ctladdr=jochen (500/100), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=120442, relay=smtp.wa-p.de [62.67.200.3], dsn=2.0.0, stat=Sent (ok 1007359540 qp 28590) Can anyone please help me - it's very urgent for me. Thanx. -- WA-P: Programmierung - Beratung - Hosting Stuttgarter Strasse 3 - D-73033 Goeppingen Tel. 07161 - 92 95 94 Fax 07161 - 1 36 01 http://internet.wa-p.de - jk(a)wa-p.de

2 2

SuSE Firewall on CD and SQUID
by Alexander Reach 03 Dec '01

03 Dec '01

Hello Group, just a little question about this nice product. Is it possible to change the squid error pages (html-format) ? I tried to put them on the floppy (in the right subdir, of course), but it seems, that these files won't be copied to the ram-disk. Is the script, responsible for the copy-process, on the CD, or is it on the floppy, so that I can edit it? Thanks in advance, Alexander

1 0

error in amavis?
by Stadt.Waren-Mueritz＠t-online.de 03 Dec '01

03 Dec '01

Hi, in /usr/sbin/amavis (original 25.10.2001 / perl-11) is an "error" in line 1147 [...] 1146 /^gzip compresssed/io && ..... 1147 /^compress'd/io && ..... < is this correct?? 1148 /^bzip2 compressed/io && ..... [...] Kind regards --- Matthias Bitterlich Tel: 03991-177151 Fax: 03991-177112 Stadt Waren (Müritz) Hauptamt - EDV www.stadt-waren.de Zum Amtsbrink 1 17192 Waren (Müritz) Germany

2 1

Zeroing chain (ipchains )
by Erwin Zierler - stubainet.at 03 Dec '01

03 Dec '01

Hi list, I'm using ipchains on some SuSE 6.4 box with kernel 2.2.19. Recently I implemented a few rules to log and count traffic from portscans (coming from know IP addresses). I use ipchains on this box mainly for accounting really and now I'd like to reset (i.e. set to zero) a few chains. According to the manpage on my system it would go like this: ipchains -Z chain_name (i.e. ipchains --zero chain_name) But nothing happens! Am I missing something or should I be worried? TIA for any input on this. Erwin PS.: ipchains -V says ipchains 1.3.9, 17-Mar-1999 -- Erwin Zierler | web- / host- / postmaster - stubainet.at | erwin.zierler(a)stubainet.at / webmaster(a)stubainet.at | Tel.: 0 5225 - 64325 Fax 99 Mobil: 0664 - 130 67 91

2 2

port 445
by spiekey 03 Dec '01

03 Dec '01

Hello! I am using logcheck and portsentry. I read that port 445 is something from smb and not really a reason to worry about, but well, its a external ip which wanted to "do" something. Something to worry about? Active System Attack Alerts =-=-=-=-=-=-=-=-=-=-=-=-=-= Dec 3 01:43:47 suse portsentry[5576]: attackalert: TCP SYN/Normal scan from host: pD951A6F2.dip.t-dialin.net/217.81.166.242 to TCP port: 445 Dec 3 01:43:47 suse portsentry[5576]: attackalert: Host 217.81.166.242 has been blocked via wrappers with string: "ALL: 217.81.166.242" Thanks! Spiekey

3 2

RE: [suse-security] Connecting firewall directly to router ...
by Reckhard, Tobias 03 Dec '01

03 Dec '01

> > Well, it need not be accomplished by proxy-arp, for one. > Then, who's saying > > the IP address that's being DNATed is in a local subnet of > the firewall at > > all? I.e. the firewall could have two networks attached, > 1/8 and 2/8. It > > could still be instructed to DNAT traffic to 2.1.1.1 to 3.1.1.1. No > > proxy-arp involved. > > > I read the man page for arp. It says that the kernel does > automagic arp if a > route exists between the subnets. And...? > > I'd ask for a /30 subnet to put the Cisco and the firewall (external > > interface) into, additionally to the /28 subnet for the DMZ > and have the > > Cisco sysadmin configure the firewall as the gateway to > that /28. The /30 > > subnet needn't have official addresses, BTW, in case that's > a problem, > > because noone should need to send traffic to the firewall directly. > > > What about setting the cisco's default gateway for the > 66.8.45.160/28 network > to the firewall interface? Number one, there is only one default gateway, also called the gateway of last resort. There is no subnet-specific *default* gateway. I don't think the Cisco would let you configure it's interface as 66.8.45.161/255.255.255.240 and then issue a route to that very subnet pointing at a gateway, since it knows that that subnet is directly attached. You can, however, split that subnet into smaller blocks and apply routes to those. More specific routes, i.e. ones with a larger number of bits in the subnet mask, take precedence over less specific routes. The easiest way to do this in your situation, where you don't have many hosts, is to issue host routes. Under no circumstances give the Cisco a different subnet mask than the Linux box. They won't be able to see each other if you do, as network and broadcast addresses don't correspond anymore. Cheers Tobias

1 0

DHCLIENT, masquarding and firewall
by Ryan Allen 03 Dec '01

03 Dec '01

Hi SuSE Security, I'm new to this list. Due to changed to Excite at home shutting down, I had to make some changes to my firewall config. I used to have a static IP and everything worked great, but now I have a dynamic IP assigned via DHCP. Behind my SuSE 7.1 machine, I'm running a LAN that uses masquerading through the SuSE machine. I'm getting my DHCP offer just fine, and have hull access to the Internet from my SuSE machine, but I cannot access the Internet from any machine behind the SuSE machine. I've tweaked everything I can in /etc/rc.config.d/firewall.rc.config and restarted my firewall many times. Any ideas? I'm running kernel 2.4.2, if it makes a difference?? thanks in advanced! -- Ryan here is my firewall config: FW_DEV_WORLD="eth1" FW_DEV_INT="eth0" FW_DEV_DMZ="" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_NETS="10.10.55.0/24" FW_MASQ_DEV="$FW_DEV_WORLD" # e.g. "ippp0" or "$FW_DEV_WORLD" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_GLOBAL_SERVICES="yes" # "yes" is a good choice FW_SERVICES_EXTERNAL_TCP="20 21 22 80 8080 6346" # Common: smtp domain FW_SERVICES_EXTERNAL_UDP="20 21 " # Common: domain FW_SERVICES_EXTERNAL_IP="" # For VPN/Routing which END at the firewall!! # FW_SERVICES_DMZ_TCP="" # Common: smtp domain FW_SERVICES_DMZ_UDP="" # Common: domain syslog FW_SERVICES_DMZ_IP="" # For VPN/Routing which END at the firewall!! # FW_SERVICES_INTERNAL_TCP="" # Common: ssh smtp domain FW_SERVICES_INTERNAL_UDP="" # Common: domain syslog FW_SERVICES_INTERNAL_IP="" # For VPN/Routing which END at the firewall!! FW_TRUSTED_NETS="" FW_SERVICES_TRUSTED_TCP="" # Common: ssh FW_SERVICES_TRUSTED_UDP="" # Common: syslog time ntp FW_SERVICES_TRUSTED_IP="" # For VPN/Routing which END at the firewall!! FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" # Common: "ftp-data" (sadly!) FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" # Common: "DNS" or "domain ntp" FW_SERVICE_DNS="no" # if yes, FW_SERVICES_*_TCP needs to have port 53 # (or "domain") set to allow incoming queries. # also FW_ALLOW_INCOMING_HIGHPORTS_UDP needs to be "yes" FW_SERVICE_DHCLIENT="yes" # if you use dhclient to get an ip address # you have to set this to "yes" ! FW_SERVICE_DHCPD="no" # set to "yes" if this server is a DHCP server FW_SERVICE_SAMBA="no" # set to "yes" if this server uses samba as client # or server. As a server, you still have to set # FW_SERVICES_{WORLD,DMZ,INT}_TCP="139" # Everyone may send you udp 137/138 packets if set # to yes! (samba on the firewall is not a good idea!) FW_FORWARD_TCP="" # Beware to use this! FW_FORWARD_UDP="" # Beware to use this! FW_FORWARD_IP="" # Beware to use this! FW_FORWARD_MASQ_TCP="" # Beware to use this! FW_FORWARD_MASQ_UDP="" # Beware to use this! FW_REDIRECT_TCP="" FW_REDIRECT_UDP="" FW_LOG_DENY_CRIT="yes" FW_LOG_DENY_ALL="no" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_KERNEL_SECURITY="yes" FW_STOP_KEEP_ROUTING_STATE="no" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="no" ## # END of rc.firewall ## #-------------------------------------------------------------------------# # # # EXPERT OPTIONS - all others please don't change these! # # # #-------------------------------------------------------------------------# # # FW_ALLOW_FW_TRACEROUTE="no" FW_ALLOW_FW_SOURCEQUENCH="yes" FW_MASQ_MODULES="autofw cuseeme ftp irc mfw portfw quake raudio user vdolive" #FW_CUSTOMRULES="/etc/rc.config.d/firewall-custom.rc.config"

2 2

RE: [suse-security] Connecting firewall directly to router ...
by Reckhard, Tobias 03 Dec '01

03 Dec '01

> On Monday 03 December 2001 07:37, Reckhard, Tobias wrote: > > Try: > > 1. man arp (see the options -D and -s) > > 2. http://www.linuxdoc.org/HOWTO/mini/Proxy-ARP-Subnet/ > > > If I'm using IPTABLES and I'm using the DNAT rules, why does > the kernel not > do the proxy-arp automatically? Surely what DNAT is trying to > accomplish > requires this, i.e. listening on a public IP and redirecting > to a private IP. Well, it need not be accomplished by proxy-arp, for one. Then, who's saying the IP address that's being DNATed is in a local subnet of the firewall at all? I.e. the firewall could have two networks attached, 1/8 and 2/8. It could still be instructed to DNAT traffic to 2.1.1.1 to 3.1.1.1. No proxy-arp involved. Use different tools for different tasks. > > PS: I dislike either of these setups. If you've got > separate subnets, you > > should have separate subnet addresses, IMHO. But the above > should work > > nonetheless. > So you would have 66.8.45.161/28 on the router LAN interface > and something > else on the internet interface on the firewall? Does this > mean that the > internet interface on the firewall requires a public IP? No, you can't have the Linux firewall's external interface and the router's 'internal' interface on different subnets (well, in Linux with PtP interfaces you can and Cisco allows for 'ip unnumbered', so this is actually not entirely true, but..). I'd ask for a /30 subnet to put the Cisco and the firewall (external interface) into, additionally to the /28 subnet for the DMZ and have the Cisco sysadmin configure the firewall as the gateway to that /28. The /30 subnet needn't have official addresses, BTW, in case that's a problem, because noone should need to send traffic to the firewall directly. Cheers Tobias

2 1

RE: [suse-security] Connecting firewall directly to router ...
by Reckhard, Tobias 03 Dec '01

03 Dec '01

> Sorry ... made a mistake there ... 130 should be 166 OK. > > You can do either of two things to remedy the situation: > > 1. Configure the firewall to perform proxy-arp on behalf of > the public > > servers. You do this on the firewall. > This sounds like what I'm looking for, any idea on how I can do this? Try: 1. man arp (see the options -D and -s) 2. http://www.linuxdoc.org/HOWTO/mini/Proxy-ARP-Subnet/ > > 2. Configure the firewall to be the router for the official > subnet of the > > public servers. This is performed on the router. This would work like this (on the Cisco): # conf t (config)# ip route <IP of server1> 255.255.255.255 <IP of Linux-GW> (config)# ip route <IP of server2> 255.255.255.255 <IP of Linux-GW> ... (config)# end # copy run start HTH Tobias PS: I dislike either of these setups. If you've got separate subnets, you should have separate subnet addresses, IMHO. But the above should work nonetheless.

2 1

Have I been hacked?
by Hans Körber 03 Dec '01

03 Dec '01

Hallo, I found user "nobody" performing a "find" on my linux box few days ago. In the /home section of the filesystem I found a subdirectory "httpd" which I did not create. The "httpd" directory itself contained a subfolder, "bin-cgi". I didn't find any other changes. The linux machine runs IPTABLES with open ports for SSH, HTTP and HTTPs. Connection is via pppd. I'm still a "newbie" to security. I would appreciate any key words and explanations to find out if I've been hacked, how this has been achieved and how it can be avoided in the future. Thank you very much in advance. Regards, Hans Körber

5 4

RE: [suse-security] SuSE Security Announcement: wuftpd (SuSE-SA:2001:043)
by carlos＠keysoft.pt 02 Dec '01

02 Dec '01

Jus't to say that I also didn't see the suse-security announce. I'm subscribed to both lists and always archive the announcements from suse-security (shorter subject) - I'm (I was:) still waiting for the suse-security announcement so that it could be archived. Carlos > -----Original Message----- > From: cwe(a)bph.ruhr-uni-bochum.de [mailto:cwe@bph.ruhr-uni-bochum.de] > Sent: sexta-feira, 30 de Novembro de 2001 18:12 > To: abien(a)gmx.net; draht(a)suse.de > Cc: suse-security(a)suse.com > Subject: Re: RE: [suse-security] SuSE Security Announcement: wuftpd > (SuSE-SA:2001:043) > > > 30.11.2001 19:00:16, Roman Drahtmueller <draht(a)suse.de> wrote: > > >Actually no... I've seen it running through. It was sent to > >suse-security-announce at Wed, 28 Nov 2001 23:55:25 +0100 (MET), to > >suse-security at Wed, 28 Nov 2001 23:58:18 +0100 (MET), and > to bugtraq at > >Wed, 28 Nov 2001 23:59:42 +0100 (MET). We usually wait until > we see our > >own posting from -announce until we send it off to > suse-security, later > >other addresses, including bugtraq. > > > >Roman. > > > Hi, > well I didn't get it and I can't find it on the list archive > > http://lists2.suse.com/archive/suse-security/2001-Nov/ > > but maybe I am too stupid... > > Christoph > -- > .-. Ruhr-Universitaet Bochum > /v\ L I N U X Lehrstuhl fuer Biophysik > // \\ >Penguin Computing< c/o Christoph Wegener > /( )\ Gebaeude ND 04/Nord > ^^-^^ D-44780 Bochum, GERMANY > > Tel: +49 (234) 32-25754 Fax: +49 (234) 32-14626 > mailto:cwe@bph.ruhr-uni-bochum.de http://www.bph.ruhr-uni-bochum.de > > > > > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com > >

4 4

Re: [suse-security] firewall log entries
by Robert Rottscholl 02 Dec '01

02 Dec '01

SoulPatrol wrote: > Hallo Robert, > > Am Saturday, December 01, 2001, 6:23:38 PM, schriebst du: > > > > >>michael.ryan(a)storm.ie wrote: >> > >>>I just noticed the following entries in my firewall log: >>> >>>Nov 23 19:44:11 kore kernel: Packet log: input DENY eth0 PROTO=6 >>>192.168.1.4:22 >>>a.b.c.d:22 L=40 S=0x00 I=16126 F=0x0000 T=246 SYN (#3) >>>Nov 23 19:47:21 kore kernel: Packet log: input DENY eth0 PROTO=6 >>>192.168.1.4:22 >>>a.b.c.d:22 L=40 S=0x00 I=28824 F=0x0000 T=246 SYN (#3) >>>Nov 23 19:47:58 kore kernel: Packet log: input DENY eth0 PROTO=6 >>>192.168.1.4:22 >>>a.b.c.d:22 L=40 S=0x00 I=9754 F=0x0000 T=246 SYN (#3) >>>Nov 23 19:51:35 kore kernel: Packet log: input DENY eth0 PROTO=6 >>>192.168.1.4:22 >>>a.b.c.d:22 L=40 S=0x00 I=38173 F=0x0000 T=246 SYN (#3) >>> >>>eth0 is the external i/f ... does this indicate ssh connection attempts >>>with spoofed IP source addresses? >>>(I do have a machine on reserved IP address 192.168.1.4 but it can only >>>establish connections to the firewall via eth1) >>> >>>TIA >>>Michael >>> >>> >>> >>> >>Hi Michael, >> > > >>you should enable ROUTE VERIFICATION >>---snap---- >> > echo >> "1" /proc/sys/net/ipv4/conf/<device>/rp_filter ^ | | What's that good for? See "http://www.netcologne.de/~meberg/netfilter/Packet-Filtering-HOWTO.txt" near the end you find the description. Ciao ;-) Robert > >>--end of snap-- >> > >>Ciao ;-) >> > >>Robert Rottscholl - DE >> > >

1 0

modssl: SSLSessionCache dbm
by Lukas Feiler 02 Dec '01

02 Dec '01

I can't get my SSLSessionCache working! I am running SuSE 7.2 Pro; Apache/1.3.20 mod_ssl/2.8.4 OpenSSL/0.9.6b mod_jk PHP/4.0.6 configured shm is not supported so I am using dbm: SSLSessionCache dbm:/var/log/httpd/MAIN/ssl/ssl_cache SSLSessionCacheTimeout 300 but no cache-files get created. It tried it successfully with an other machine that I configed nearly exactly the same (I am running SuSE 7.2 Pro; Apache/1.3.20 mod_ssl/2.8.4 OpenSSL/0.9.6a mod_jk PHP/4.0.6 ; httpd.conf, ssl, DNS, ...) - OpenSSL/0.9.6a instead of OpenSSL/0.9.6b anyone an idea?? Please help me! regards Lukas

1 0

sendmail problem
by Marios amrti 02 Dec '01

02 Dec '01

Hi i know this doesnt have much to do with security but i ve been trying to figure it out for a few days now and all i get is dead ends. I have been configuring sendmail with varius ways and still im not able to send anything. when i send the mail i get this output: rewrite:map dequote not found rewrite:map mailertable not found rewrite:map mailertable not found rewrite:map mailertable not found /root/dead.letter....saved in /root/dead.letter mailerdaemon...saved message in /var/log/dead letter im using sendmail 8.11.2-34 Please help this is starting to get on my head.... Thanks

1 0

firewall log entries
by michael.ryan＠storm.ie 01 Dec '01

01 Dec '01

I just noticed the following entries in my firewall log: Nov 23 19:44:11 kore kernel: Packet log: input DENY eth0 PROTO=6 192.168.1.4:22 a.b.c.d:22 L=40 S=0x00 I=16126 F=0x0000 T=246 SYN (#3) Nov 23 19:47:21 kore kernel: Packet log: input DENY eth0 PROTO=6 192.168.1.4:22 a.b.c.d:22 L=40 S=0x00 I=28824 F=0x0000 T=246 SYN (#3) Nov 23 19:47:58 kore kernel: Packet log: input DENY eth0 PROTO=6 192.168.1.4:22 a.b.c.d:22 L=40 S=0x00 I=9754 F=0x0000 T=246 SYN (#3) Nov 23 19:51:35 kore kernel: Packet log: input DENY eth0 PROTO=6 192.168.1.4:22 a.b.c.d:22 L=40 S=0x00 I=38173 F=0x0000 T=246 SYN (#3) eth0 is the external i/f ... does this indicate ssh connection attempts with spoofed IP source addresses? (I do have a machine on reserved IP address 192.168.1.4 but it can only establish connections to the firewall via eth1) TIA Michael

2 1

Fw: tcb scheme implemented for Owl
by Peter Nixon 01 Dec '01

01 Dec '01

Is SuSE looking at using this system anytime soon? -- Viel Spaß Nix - nix(a)susesecurity.com http://www.susesecurity.com Begin forwarded message: Date: Thu, 15 Nov 2001 22:56:58 +0100 From: Rafal Wojtczuk <nergal(a)owl.openwall.com> To: announce(a)lists.openwall.com Subject: tcb scheme implemented for Owl Hello, You may have noticed that recently a new package named "tcb" has been added to Owl-current. It features the new implementation of pam_unix module and the new method of storing password hashes. The interesting point is if you invest your time in reading tcb(5) and tcb_convert(8) man pages, you will be able to configure your Owl system so that many utilities can run with low privileges. Most notably, passwd(1) does not need to be suid root. Currently, new features are disabled by default. Soon during install time one will be given a choice between the old shadowed passwords scheme and the new tcb scheme. Meanwhile, we encourage you to test new tcb features and share with owl-users(a)lists.openwall.com the experience gained. You may also be interested that on 23-25th November there will be held a Linux conference, which will feature a talk on Owl. The event is named JWGL (http://www.7bulls.com/JWGL) it is held near Warsaw, Poland. It is the fourth edition of the conference which focuses on professional Linux and GNU software appliances. The event is mostly local (the speeches are given in Polish), but if you want to meet Richard Stallman personally, this is the occasion :) The JWGL Owl talk will cover amongst others: - Owl security and design concepts - software developed for the needs of Owl - generic methods to improve software security (examples from Owl) - the tcb scheme: the "least privilege" rule in flesh

1 0