April 2003 - openSUSE Security - openSUSE Mailing Lists

ezmlm instalation
by Mirza Muhic 04 Apr '03

04 Apr '03

Hello , i trying to install ezmlm software on my linux box and i would like to ask You is it posible to use ezmlm together with sendmail or postfix or it requires qmail . And if this is case , can someone provide me informations where i can find tutorials or manuals how to install and work with ezmlm. Thanks in advance Sorry for crosspost but i dont know where else to ask for help .

2 1

Request: Link to a FAQ
by Ton Machielsen 04 Apr '03

04 Apr '03

Hi all, Can someone point me to a FAQ or HOW-TO on setting up a SuSE 8.1 box from scratch to be a fairly secure firewall with VPN? How is the standard SuSEfirewall2 compared to the commercial firewalls like CheckPoint or Cisco PIX? Complete rubbish or when it's set up properly is it good enough to protect a hosting environment? Thanks for the info, Ton.

1 0

SuSE Security Announcement: openssl (SuSE-SA:2003:024)
by Sebastian Krahmer 04 Apr '03

04 Apr '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: openssl Announcement-ID: SuSE-SA:2003:024 Date: Fri Apr 4 14:00:00 MEST 2003 Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 SuSE Linux Database Server SuSE eMail Server III, 3.1 SuSE Firewall Adminhost VPN SuSE Linux Admin-CD for Firewall SuSE Firewall on CD 2 - VPN SuSE Firewall on CD 2 SuSE Linux Live-CD for Firewall SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 SuSE Linux Enterprise Server 8 SuSE Linux Office Server UnitedLinux 1.0 Vulnerability Type: remote private-key retrieval Severity (1-10): 5 SuSE default package: Yes Cross References: http://www.openssl.org Content of this advisory: 1) security vulnerability resolved: Remote timing attack and "Klima-Pokorny-Rosa" attack. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - glibc - vnc 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Researchers from the University of Stanford have discovered certain weaknesses in OpenSSL's RSA decryption algorithm. It allows remote attackers to compute the private RSA key of a server by observing its timing behavior. This bug has been fixed by enabling "RSA blinding", by default. Additionally an extension of the "Bleichenbacher attack" has been developed by Czech researchers against OpenSSL. This weakness has also been fixed. 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 -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. i386 Intel Platform: SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-12.i586… b418a2f73ab572f99f156335f3cd4ef4 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-1… d0539c626612c5fcd9b1e81e529dc3af patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-12.i586… 3c8a296170b34838db459a5aefc3e104 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-1… 8978902dde74da69f72c4ff93a90f1eb source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-12.src.r… 6dfaa0788bcdcb99939890d4bbd62826 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-68.i586… 2ecce759f2806b5ab475877b0ccd1f6f ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-6… aa79f7f72e503393f8fa9c34290ab497 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-68.i586… 68e33f6f3f90234a599e7473262e4924 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-6… 07ee91826db414421ad2a5a1abe27191 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-68.src.r… 177ff751ecf0e5e191b36e9df28479ee SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-85.i386.rpm fabc6f1768cb113555690dbc26b26779 ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-85.i386… 788751185ecf5c3538378de8f583c900 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-85.i386.pat… dc19ef5b07fcd32d060e8c6c0f11d3e1 ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-85.i386… 0152c98bab2617456b7250431f37c41e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-85.src.rpm 66080ca41e143339ef95d7dd0c4c19fe SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssl-0.9.6b-156.i386.rpm 7da5bae86380a034312d69e745bb1bb5 ftp://ftp.suse.com/pub/suse/i386/update/7.3/d2/openssl-devel-0.9.6b-156.i38… d54d7948b2a5cce732971890f51520a3 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-156.src.rpm 13749156d3a6fd7597407a65bf2c527b SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssl-0.9.6a-82.i386.rpm 105d9266ea2117bfa9643eb66441f39b ftp://ftp.suse.com/pub/suse/i386/update/7.2/d2/openssl-devel-0.9.6a-82.i386… 5d607333a4ddae3cb1e303a8afaf2f43 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-82.src.rpm 7a06275dda66ea2e9da6c76425439369 SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/openssl-0.9.6a-81.i386.rpm 8bb8ea69f878aa08331269bf3f38afa2 ftp://ftp.suse.com/pub/suse/i386/update/7.1/d2/openssl-devel-0.9.6a-81.i386… dede7c66740ab249de577e5699e8639f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/openssl-0.9.6a-81.src.rpm 07bc8370887abba6db3ace2d523eeade Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/openssl-0.9.6b-89.sparc.r… 1391d007fdb5b99fd71aba949aeb0310 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/d2/openssl-devel-0.9.6b-89.spa… 9f0ff708c016fd62d103cadbf3f6892e source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-89.src.rpm fac800ccac7c5f2c3eb544f5a7bf0aea AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec1/openssl-0.9.6a-31.alpha.rpm c8d02c071cee8f6d70d8a9bb26b010f2 ftp://ftp.suse.com/pub/suse/axp/update/7.1/d2/openssl-devel-0.9.6a-31.alpha… 13cdfd1f3b35ee90a7d09240a2a3df40 source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/openssl-0.9.6a-31.src.rpm e64213b7b488d16de6152d94db9aaa99 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssl-0.9.6b-150.ppc.rpm cb2b6467cbad88c2ac4cecd889b2cb40 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d2/openssl-devel-0.9.6b-150.ppc.… c11a579a40184ad6a108bfaa787b2038 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-150.src.rpm 889ea0f28304224329a37d12390e370b SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/openssl-0.9.6a-31.ppc.rpm 1694ef2f2018cfcdd4a4bab97d21978b ftp://ftp.suse.com/pub/suse/ppc/update/7.1/d2/openssl-devel-0.9.6a-31.ppc.r… f1b6838c46f3775d4ee6c51714247cb1 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/openssl-0.9.6a-31.src.rpm 5a8af3aa4592efba1194518b9a50253e ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - glibc New glibc packages will be available soon which fix a RPC XDR integer overflow. The packages are currently being tested. - vnc VNC (Virtual Network Computing) uses a weak cookie generation process which can be exploited by an attacker to bypass authentication. New packages are currently being tested and will be available on our FTP servers soon. ______________________________________________________________________________ 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 un-installed 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 top-level 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 announcements 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> or <security(a)suse.de>. The <security(a)suse.de> 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 clear-text signature shows proof of the authenticity of the text. SuSE Linux AG 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 mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPo12tHey5gA9JdPZAQExTQf+OWFAmPg/bt+BWNFWdJPF4XHB37NDX5B0 ckOFGItPq19RtrKY3K80vkruNCEd6hBeVr5FuoG1+VodYOypV8G2toELtGPvPz1X /YHneSzg7qbBnzE65qsHeFv4H/ietYAvgakY9aFZX1dh5mldCYl+Ja7479V6LP9h pxryqFkMwnw6WAKHADcYSjazMRIvF3LvrzeqbKBFBDqt39itcUuM8brC/tt1HzPV 3bWZ1NRLIxguTI/xYo5SyrAb/wLoneU8Vmn6YTgqD3MRZ3JnCStWCjmKK382a8yl dfBPzDzYKKRzpP5wzGDKQapbdDJ1bBjw9iITD6LVQeSfLqkUPUmSEA== =WPBB -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0

Question about new Samba packages
by BoneMachine 04 Apr '03

04 Apr '03

Hi, Are the new samba-packages for all of the SuSE Linux versions an update of the problem reported by Bob Vickers or is this yet another security issue in the smb-packages? (I refer to the samba-2.2.5-171 package for 8.1 that is published on the site. Last known good version ought to be samba-2.2.5-160, according to the security advisory) greetings Bone Machine --- "I was all dressed in black, she was all dressed in black" - The Pixies ---

2 1

RE: [suse-security] SuSE Firewall2
by M. Edwin 04 Apr '03

04 Apr '03

Hi lars, Thanks for your reply. I think it means the same. I just wonder, even it works also in our site but if I ping to a machine in internet from internal machine it's not reply 100%, RTO always come (I'm sure that the machine allow the icmp request). It never happen before I installed the firewall2. Is there anyone here facing the same problem? What do you mean by your basic policy? greetings M. Edwin -----Original Message----- From: lars [mailto:lars@brainlift.de] Sent: Friday, April 04, 2003 2:49 PM To: Moh Edwin Subject: Re: [suse-security] SuSE Firewall2 Hi, i´m not sure about the syntax / spelling; this may be correct: iptables -A INPUT -i eth1 -s 192.168.117.0/24 -d 0/0 -p icmp --icmp-type echo-request -j ACCEPT works at my box (though I still got a problem with my default olicy, ;-) but basically my firewall works well). greetings warzenpower > Hi all, > > I just installed SuSE firewall2 on 7.3 and already setup the config > file according to our need. I allow access from internal to outside on > ftp, ssh, www, smtp and pop. From the outside only ssh and web are > accessible. I check with nmap and everything is OK. I also set the > internal net to ping the outside, but I thing something wrong because > it cannot work. > > I put : > > FW_ALLOW_PING_FW="yes" > FW_ALLOW_PING_EXT="yes" > > and also add on firewall2-custom.config > > iptables -A input -i eth1 -s 192.168.117.0/24 -d 0/0 -j ACCEPT -p icmp > --icmp-type echo-request > > Is this wrong? > > I also got an email from someone that when he's trying to send me an > email, the message is connection timeout to my email server, which is > reside on separate machine (with public IP and always connect to > internet with leased channel) and also running firewall2 on 7.3 with > main function is to protect smtp and pop3. This is not happen before I > installed firewall2. Is there a "delay effect" after firewall2 > installation? > > TIA > M. Edwin > > > -- http://www.ruebenschweine.de Try also: http://www.warzenpower.de +++ http://www.lars-und-sandra.de +++ http://www.r100rt.de Diese email wurde automatisch generiert, Sie können deshalb nicht darauf antworten; webmaster(a)warzenpower.de

1 0

SuseFirewall2 and icq-phone
by Alexander Meier 04 Apr '03

04 Apr '03

hi all, I've got a PPC (PowerMac 7300 with G4 card) set up as firewall for our student-home-network. Now one of my friends uses icq-phone to talk to his girlfriend abroad.... and since I'm a nice guy, I'd like to allow him that ;-) now here's the config and the problem: suse 7.3, kernel 2.4.12, installation method: suse predefined server config the mac is our dhcp, dns, masquerading server and also our firewall. icq-phone uses udp port's 6701 for icq-phone (sniffed with ettercap and ethereal) a connection between my friend and his girl can be established, but they cannot communicate... I don't know why! for testing purposes I set the firewall to minimal security, allowing all ports above 1024 to come in and out. has anyone got an idea how I could solve this problem? My only guess is that I have to to enable a port forwarding from the server to the friend's client on the port 6701? could that solve our problems? thanks for any help!! cheers alex Content Security by MailMarshal

1 0

SuSE Firewall2
by M. Edwin 04 Apr '03

04 Apr '03

Hi all, I just installed SuSE firewall2 on 7.3 and already setup the config file according to our need. I allow access from internal to outside on ftp, ssh, www, smtp and pop. From the outside only ssh and web are accessible. I check with nmap and everything is OK. I also set the internal net to ping the outside, but I thing something wrong because it cannot work. I put : FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_EXT="yes" and also add on firewall2-custom.config iptables -A input -i eth1 -s 192.168.117.0/24 -d 0/0 -j ACCEPT -p icmp --icmp-type echo-request Is this wrong? I also got an email from someone that when he's trying to send me an email, the message is connection timeout to my email server, which is reside on separate machine (with public IP and always connect to internet with leased channel) and also running firewall2 on 7.3 with main function is to protect smtp and pop3. This is not happen before I installed firewall2. Is there a "delay effect" after firewall2 installation? TIA M. Edwin

1 0

How does SuSEfirewall2 handle privileged ports
by malte_gell＠t-online.de 04 Apr '03

04 Apr '03

Hi, I'm using the SuSEfirewall2 script V2.1 on a machine which is running e.g. leafnode on port 119, no connection from the internet on port 119 should be allowed. A normal home user's machine so to say. Leafnode is protected with the tcpd wrapper, nevertheless, I'm curious why SuSEfirewall2 seems to accept packages on port 119, although it shouldn't. FW_SERVICES_[EXT,DMZ,INT]_[TCP,UDP] are set to "" FW_AUTOPROTECT_SERVICES="yes" When I telnet the machine, packages go through SuSEfirewall2 and tcpd refuses the connect, but I expected SuSEfirewall to block any traffic on port 119, why doesn't this happen ? I expected so see something like "SuSE-FW-DROP Default IN=ppp0 ... SRC=... DST=... SPT=... DPT=119" that doesn't happen. Now, how does SuSEfirewall2 handle ports < 1024 which are not mentioned in the preferences, traffic on port 119 seem to be accepted, though nowhere allowed. I don't want the tcpd to be the "last line of defense", I'd like to get this traffic blocked by the SuSEfirewall2. The same applies e.g. to the IPP protocol (CUPS printer system) on port 631, if I telnet it, okay the connection is refused, but theres no "SuSE-FW-DROP Default IN=ppp0 ... SRC=... DST=... SPT=... DPT=631" appearing which I expected to see, with port 80 this works ! Any connection attempt causes a "SuSE-FW-DROP Default IN=ppp0..." message. SuSEfirewall2 V 2.1 from www.suse.de/~marc/SuSE.html on a SuSE 7.3, Kernel 2.4.19, iptables v1.2.2 Thanx Malte

1 0

RES: [suse-security] IPSec NAT traversal and kernel >= 2.5.45
by Valter Rehn 03 Apr '03

03 Apr '03

If upgrading your OS to 8.1 is an option, I would recommend it. (may not solve the problem, but one of my systems looks like this and works :) ---------------- --------------- | Win2k VPN | | Corp. Net |--| & Firewall |--- Internet ------------------| --------------- | & NAT | | ---------------- I N E --------------- ---------------- ----------------- T | Other Net |--| SuSe 8.1 VPN |--| Bridge Router |--- ADSL ---| --------------- | & Firewall | ----------------- | & NAT & PPTP | ---------------- you did not specify where in the draw did your VPN resided, if LEFT or RIGHT of the NATing router.... if it is LEFT, you will need the patch indeed. if it is RIGHT, not. regards, Valter Rehn OCP DBA - Support Analyst Phone: +55 (51) 3218-9139 www.panvel.com.br

1 0

IPSec NAT traversal and kernel >= 2.5.45
by GentooRulez 03 Apr '03

03 Apr '03

Hi list, I does not found anything reliable while googling and so I'll ask you. Assuming you've IPSec-VPN gateways that are behind NATing routers (which are not yours) you'll need a NAT Traversal patch for free/SWan IPSec to tunnel the VPN traffic, cause the NAT modifies the packets and unpatched free/SWan won't work than properly. --------------- ----------------- | VPN Gateway |--| NATing Router |--- Internet ---| --------------- ----------------- I N E --------------- ----------------- T | VPN Gateway |--| NATing Router |--- Internet ---| --------------- ----------------- ASC-II art - is'nt it :O? Does the new implementation of IPSec in kernel >=2.5.45 include such mechanism or do i have to patch thoose kernels too? Thx in advance Michael

2 1