January 2004 - openSUSE Security - openSUSE Mailing Lists

SUSE Security Announcement: gaim (SuSE-SA:2004:004)
by thomas＠suse.de 29 Jan '04

29 Jan '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: gaim Announcement-ID: SuSE-SA:2004:004 Date: Thrusday, Jan 29th 2004 10:30 MET Affected products: 8.0, 8.1, 8.2, 9.0 SuSE Linux Desktop 1.0 Vulnerability Type: remote system compromise Severity (1-10): 5 SUSE default package: no Cross References: Content of this advisory: 1) security vulnerability resolved: - two buffer overflows problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - kernel binaries for SLES8 AMD64 - mc - mod_gzip - tripwire - XDM (XFree86, xf86) - 3ddiag - mod_auth_shadow - cvsup - nmap - netpbm - zebra - quagga - tcpdump - mod_python 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Gaim is a multi-protocol instant-messaging client. Stefan Esser found 12 vulnerabilities in gaim that can lead to a remote system compromise with the privileges of the user running GAIM. The GAIM package that SUSE LINUX ships is affected by just two of these bug: - Yahoo Packet Parser Overflow - HTTP Proxy Connect Overflow The first vulnerability is easy to exploit and results in a classic stack overflow which can be used to execute arbitrary code. The latter vulnerability requires the gaim client use a HTTP proxy under the control of the attacker. The exploitation of this bug results in arbitrary code execution too. There is no known workaround. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, to apply the update use the command "rpm -Fhv file.rpm". Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/gaim-0.67-65.i586.rpm 09f8d12dd52e246cf32dca8ad3374f39 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/gaim-0.67-65.i586.patc… 3a633e341b9e56facdbe0250b55dd33a source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/gaim-0.67-65.src.rpm 5ee6a86077c0297a64815532782f7a54 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/gaim-0.59.8-60.i586.rpm 7a269744304f72bf951c7bd6974560f2 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/gaim-0.59.8-60.i586.pa… e7b18f0da02c1c4392dc1b03e835a827 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/gaim-0.59.8-60.src.rpm ae7d7b1c9735696244547a0d6a5ee92e SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/gaim-0.59-158.i586.rpm 22b1d4be5737906f8ff0975918279034 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/gaim-0.59-158.i586.pat… 7644020869e92cc980b881efebf9d617 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/gaim-0.59-158.src.rpm cd1532f71a79ed32d016d456a844ff4b SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/gnm3/gaim-0.50-187.i386.rpm 7dcb581b78bf8ab61e82bf0836a4357e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/gnm3/gaim-0.50-187.i386.patch.r… 5a6f596538edc56e0b3a70a23200c21e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/gaim-0.50-187.src.rpm d38c8da629941eecef7f75d6a5ea9e80 ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - kernel binaries for SLES8 AMD64 Due to a human failure the kernel binaries of SuSE Linux Enterprise Server 8 for AMD64 lack the fix described in SuSE-SA:2004:003. The kernel-source packages and the packages for IA64 are *not* affected. New packages are available at our maintenance-web. - mc By using a special combination of links in archive files it is possible to execute arbitrary commands while mc tries to open it in its VFS. New packages are available on our FTP servers. - mod_gzip (apache-contrib) The apache module mod_gzip is vulnerable to remote code execution while running in debug-mode. We do not ship this module in debug-mode but future versions will include the fix. Additionally the mod_gzip code was audited to fix more possibly security related bugs. After more testing a new apache-contrib RPM package will be released. - tripwire Tripwire is a file integrity checker. The version of tripwire included with SuSE Linux 9.0 crashs when a requested file does not exists. New packages are available on our FTP servers. - XDM (XFree86, xf86) A missing check for failure conditions in the PAM code of XDM can lead to local root access in conjunction with Kerberos or other authentication methods. New packages are available on our FTP servers. - 3ddiag Some 3ddiag scripts handle temporary files in an insecure manner. Thanks to Stefan Nordhausen <nordhaus at informatik.hu-berlin.de> for reporting some of these issues. New packages are available on our FTP servers. - mod_auth_shadow (apache-contrib) This apache module ignores account expiration dates. The update will be released together with mod_gzip. - cvsup cvsup uses a library path which is world-writeable. This behavior can lead to local privilege escalation. Thanks to Matthias Andree for notifying us. Upcoming SuSE Linux versions have an automatic check enabled to detect these types of bugs. New packages are available on our FTP servers. - nmap Due to a bad interaction between kernel and user-space for pre- calculated IP checksums nmap did not work on SUSE LINUX 9.0. New packages are available on our FTP servers. - netpbm Some tools in the netpbm suite create files in an insecure manner that can lead to local privilege escalation. New packages will be available soon. - zebra Local users can send malicious netlink messages that cause denial-of-service conditions in zebra. New packages will be available soon. - quagga Local users can send malicious netlink messages that cause denial-of-service conditions in the routing-daemon quagga. New packages are available on our FTP servers. - tcpdump The code for handling ISAKMP and RADIUS messages contained bugs which allowed remote attackers to crash tcpdump or to execute arbitrary code. New packages are available on our FTP servers. - mod_python A remote denial-of-service attack can be triggered against the Apache web server by sending a specific query string that is processed by mod_python. New packages will be available 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: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBQBj9FXey5gA9JdPZAQEzpwf+NgFmU++b3VxVKAFbGEax/N5iTUCLqvzh L7pnVkGflFDsjhscQJOz0cr1fBpo51MuSK8KCmw2JZv9eeJsUs7MGfV5CICmdJk6 1MOaC8OMhHEk8JNYS9dViWBJUJUiHEwLFjLI81Ad3KIrOe982mhzZ/1RSCZJW+Yd ipfs8Z1l9e0bOIjH3Uod2/sm11KfxUaUv8kPSQlVzS1yClZ9j1dpI8wRtdUZzlWo /ZJzM1rduLWGEFNDvC+g+IkBTPytFkYOrUgiYE7DOovdwGYzWCwotT6x5DokDdyU P+zerCPGxJUe1H/u9Y0gv4VOxQD+rE6Ur6ChDJ4JSjw6uicjnWRYVA== =iAfN -----END PGP SIGNATURE-----

1 0

using susefirewall2 for NAT
by Arie Reynaldi Zanahar 29 Jan '04

29 Jan '04

Hi all, I just joint suse-security, I have using suse 82. for several months. Right now I have problem using susefirewall2 for my firewall / router. I'd like to change my network topology from this Internet | | ---------- Web Server 200.200.200.1 | ---------- Mail Server (qmail) 200.200.200.2 | ---------- SSH server 200.200.200.3 SuseFirewall2 | | LAN To This : Internet | | | SuseFirewall (200....1 for web and SSH, 200...2 for mail ) | |----------- Web Server 192.127.0.2 |----------- SSH server 192.127.0.3 LAN With this case, if someone go to 200.200.200.1 port 80, will forwarded to my internal webserver 192.127.0.2, and if they use SSH to that IP, it will go to my SSH server. Right now I use astaro secure linux 4 as my firewall and I use NAT for this purpose. With SuSEFirewall2, how can I use it ? I've read EXAMPELS, FAQ and search the web but I still got no clue. If someone can point me examples or documentation to do that, I'd be more greatful.. :) regards, -- Arie Reynaldi Zanahar reyman(a)reynaldi.com

6 8

SuSEfirewall2 as bridging firewall
by Christian Richter 29 Jan '04

29 Jan '04

Good Morning list, I have following problem: I have been unable to set up a working SuSEfirewall2 on a bridge running on a SuSE 9.0 system using kernel 2.6.1 (also tried the supplied 2.6.0-test-5, but didn't change anything). The bridge is working fine, the firewall loads and runs without errors, I can see logs that make quite sense. Only what doesn't work is the forwarding. No matter from where I try to forward where I receive a message like: SuSEfirewall ILLEGAL-ROUTING phsyindev=eth0 physoutdev=eth1 .... So my question: is it possible to get this setup working at all? Any comments appreciated. Thanx in advance, Christian internal net ---- bridge ---- router ---- external net

1 0

Susefirewall and port
by Frédéric Poulet 29 Jan '04

29 Jan '04

Hi, I would like to know if my susefirewall config is correct : my network schema is --------------------- INTERNET | |eth0 FIREWALL eth2----- WEB SERVER (192.168.5.20) (apache proftpd ssl webmin) |eth1 | INTERNAL NETWORK (192.168.1.x) (it can use http, https, ftp, pop, smtp to internet) my susefirewall config is -------------------------- ## Type: string # 1.) # 2.) FW_DEV_EXT="eth0" ## Type: string # 3.) FW_DEV_INT="eth1" ## Type: string # 4.) FW_DEV_DMZ="eth2" ## Type: yesno ## Default: no # 5.) FW_ROUTE="yes" ## Type: yesno ## Default: no #6 FW_MASQUERADE="yes" ## Type: string FW_MASQ_DEV="$FW_DEV_EXT" ## Type: string FW_MASQ_NETS="192.168.1.0/24,0/0,tcp,80 192.168.1.0/24,0/0,tcp,53 192.168.1.0/24,0/0,udp,53 192.168.1.0/24,0/0,tcp,25 192.168.1.0/24,0/0,tcp,110 192.168.1.0/24,0/0,tcp,21 192.168.1.0/24,0/0,tcp,113 192.168.5.0/24 192.168.1.0/24,0/0,tcp,20 192.168.1.0/24,0/0,tcp,1024:65535 192.168.1.0/24,0/0,tcp,443" ## Type: yesno ## Default: yes # 7.) FW_PROTECT_FROM_INTERNAL="yes" ## Type: yesno ## Default: yes # 8.) FW_AUTOPROTECT_SERVICES="yes" ## Type: string # 9.) FW_SERVICES_EXT_TCP="" ## Type: string FW_SERVICES_EXT_UDP="" ## Type: string FW_SERVICES_EXT_IP="" ## Type: string # FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" ## Type: string FW_SERVICES_DMZ_IP="" ## Type: string # FW_SERVICES_INT_TCP="" ## Type: string FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" ## Type: string # 10.) FW_TRUSTED_NETS="" ## Type: string # 11.) FW_ALLOW_INCOMING_HIGHPORTS_TCP="no" ## Type: string FW_ALLOW_INCOMING_HIGHPORTS_UDP="no" ## Type: yesno ## Default: yes # 12.) FW_SERVICE_AUTODETECT="no" ## Type: yesno ## Default: no FW_SERVICE_DNS="no" ## Type: yesno ## Default: no FW_SERVICE_DHCLIENT="no" ## Type: yesno ## Default: no FW_SERVICE_DHCPD="no" ## Type: yesno ## Default: no FW_SERVICE_SQUID="no" ## Type: yesno ## Default: no FW_SERVICE_SAMBA="no" ## Type: string # 13.) FW_FORWARD="192.168.1.0/24,192.168.5.20/24,tcp,1:65535" ## Type: string # 14.) FW_FORWARD_MASQ="0/0,192.168.5.20,tcp,80 0/0,192.168.5.20,tcp,21 0/0,192.168.5.20,tcp,443 0/0,192.168.5.20,tcp,25 0/0,192.168.5.20,tcp,100" ## Type: string # 15.) FW_REDIRECT="192.168.5.0/24,192.168.1.0/24,tcp,113,113" ## Type: yesno ## Default: yes # 16.) FW_LOG_DROP_CRIT="no" ## Type: yesno ## Default: no FW_LOG_DROP_ALL="no" ## Type: yesno ## Default: yes FW_LOG_ACCEPT_CRIT="no" ## Type: yesno ## Default: no FW_LOG_ACCEPT_ALL="no" ## Type: string FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" ## Type: yesno ## Default: yes # 17.) FW_KERNEL_SECURITY="yes" ## Type: yesno ## Default: no # 18.) FW_STOP_KEEP_ROUTING_STATE="no" ## Type: yesno ## Default: yes # 19.) FW_ALLOW_PING_FW="no" ## Type: yesno ## Default: no FW_ALLOW_PING_DMZ="no" ## Type: yesno ## Default: no FW_ALLOW_PING_EXT="no" ## # END of rc.firewall ## # # #-------------------------------------------------------------------------# # # # EXPERT OPTIONS - all others please don't change these! # # # #-------------------------------------------------------------------------# # # # # 20.) # Allow (or don't) ICMP time-to-live-exceeded to be send from your firewall. # This is used for traceroutes to your firewall (or traceroute like tools). # # Please note that the unix traceroute only works if you say "yes" to # FW_ALLOW_INCOMING_HIGHPORTS_UDP, and windows traceroutes only if you say # additionally "yes" to FW_ALLOW_PING_FW # # Choice: "yes" or "no", defaults to "no" if not set. # FW_ALLOW_FW_TRACEROUTE="yes" ## Type: yesno ## Default: yes # # 21.) # Allow ICMP sourcequench from your ISP? # # If set to yes, the firewall will notice when connection is choking, however # this opens yourself to a denial of service attack. Choose your poison. # # Choice: "yes" or "no", defaults to "yes" # FW_ALLOW_FW_SOURCEQUENCH="yes" ## Type: yesno ## Default: no # # 22.) # Allow/Ignore IP Broadcasts? # # If set to yes, the firewall will not filter broadcasts by default. # This is needed e.g. for Netbios/Samba, RIP, OSPF where the broadcast # option is used. # If you do not want to allow them however ignore the annoying log entries, # set FW_IGNORE_FW_BROADCAST to yes. # # Choice: "yes" or "no", defaults to "no" if not set. # FW_ALLOW_FW_BROADCAST="no" ## Type: yesno ## Default: yes # FW_IGNORE_FW_BROADCAST="yes" ## Type: yesno ## Default: no # # 23.) # Allow same class routing per default? # REQUIRES: FW_ROUTE # # Do you want to allow routing between interfaces of the same class # (e.g. between all internet interfaces, or all internal network interfaces) # be default (so without the need setting up FW_FORWARD definitions)? # # Choice: "yes" or "no", defaults to "no" # FW_ALLOW_CLASS_ROUTING="no" # Copyright (c) 2000-2002 SuSE GmbH Nuernberg, Germany. All rights reserved. # # Author: Marc Heuse <marc(a)suse.de>, 2002 # Please contact me directly if you find bugs. # # If you have problems getting this tool configures, please read this file # carefuly and take also a look into # -> /usr/share/doc/packages/SuSEfirewall2/EXAMPLES ! # -> /usr/share/doc/packages/SuSEfirewall2/FAQ ! # -> /usr/share/doc/packages/SuSEfirewall2/SuSEfirewall2.conf.EXAMPLE ! # # /etc/sysconfig/SuSEfirewall2 # # for use with /sbin/SuSEfirewall2 version 3.1 which is for 2.4 kernels! # # ------------------------------------------------------------------------ # # PLEASE NOTE THE FOLLOWING: # # Just by configuring these settings and using the SuSEfirewall2 you are # not secure per se! There is *not* such a thing you install and hence you # are safed from all (security) hazards. # # To ensure your security, you need also: # # * Secure all services you are offering to untrusted networks (internet) # You can do this by using software which has been designed with # security in mind (like postfix, apop3d, ssh), setting these up without # misconfiguration and praying, that they have got really no holes. # SuSEcompartment can help in most circumstances to reduce the risk. # * Do not run untrusted software. (philosophical question, can you trust # SuSE or any other software distributor?) # * Harden your server(s) with the harden_suse package/script # * Recompile your kernel with the openwall-linux kernel patch # (former secure-linux patch, from Solar Designer) www.openwall.com # * Check the security of your server(s) regulary # * If you are using this server as a firewall/bastion host to the internet # for an internal network, try to run proxy services for everything and # disable routing on this machine. # * If you run DNS on the firewall: disable untrusted zone transfers and # either don't allow access to it from the internet or run it split-brained. # # Good luck! # # Yours, # SuSE Security Team # # ------------------------------------------------------------------------ # # Configuration HELP: # # If you have got any problems configuring this file, take a look at # /usr/share/doc/packages/SuSEfirewall2/EXAMPLES for an example. # # # All types have to set enable SuSEfirewall2 in the runlevel editor # # If you are a end-user who is NOT connected to two networks (read: you have # got a single user system and are using a dialup to the internet) you just # have to configure (all other settings are OK): 2) and maybe 9). # # If this server is a firewall, which should act like a proxy (no direct # routing between both networks), or you are an end-user connected to the # internet and to an internal network, you have to setup your proxys and # reconfigure (all other settings are OK): 2), 3), 9) and maybe 7), 11), 14) # # If this server is a firewall, and should do routing/masquerading between # the untrusted and the trusted network, you have to reconfigure (all other # settings are OK): 2), 3), 5), 6), 9), and maybe 7), 10), 11), 12), 13), # 14), 20) # # If you want to run a DMZ in either of the above three standard setups, you # just have to configure *additionally* 4), 9), 12), 13), 17), 19). # # If you know what you are doing, you may also change 8), 11), 15), 16) # and the expert options 19), 20), 21), 22) and 23) at the far end, but you # should NOT. # # If you use diald or ISDN autodialing, you might want to set 17). # # To get programs like traceroutes to your firewall to work is a bit tricky, # you have to set the following options to "yes" : 11 (UDP only), 18 and 19. # # Please note that if you use service names, that they exist in /etc/services. # There is no service "dns", it's called "domain"; email is called "smtp" etc. # # *Any* routing between interfaces except masquerading requires to set FW_ROUTE # to "yes" and use FW_FORWARD or FW_ALLOW_CLASS_ROUTING ! # # If you just want to do masquerading without filtering, ignore this script # and run this line (exchange "ippp0" "ppp0" if you use a modem, not isdn): # iptables -A POSTROUTING -t nat -j MASQUERADE -o ippp0 # echo 1 > /proc/sys/net/ipv4/ip_forward # and additionally the following lines to get at least a minimum of security: # iptables -A INPUT -j DROP -m state --state NEW,INVALID -i ippp0 # iptables -A FORWARD -j DROP -m state --state NEW,INVALID -i ippp0 # ------------------------------------------------------------------------ ## Path: Network/Firewall/SuSEfirewall2 ## Description: SuSEfirewall2 configuration ## Type: yesno ## Default: no # # 1.) # Should the Firewall run in quickmode? # # "Quickmode" means that only the interfaces pointing to external networks # are secured, and no other. all interfaces not in the list of FW_DEV_EXT # are allowed full network access! Additionally, masquerading is # automatically activated for FW_MASQ_DEV devices. and last but not least: # all incoming connection via external interfaces are REJECTED. # You will only need to configure 2.) and FW_MASQ_DEV in 6.) # Optionally, you may add entries to section 9a.) # # Choice: "yes" or "no", if not set defaults to "no" # FW_QUICKMODE="no" ## Type: string # 9a.) # External services in QUICKMODE. # This is only used for QUICKMODE (see 1.)! # (The settings here are similar to section 9.) # Which services ON THE FIREWALL should be accessible from either the # internet (or other untrusted networks), i.e. the external interface(s) # $FW_DEV_EXT # # Enter all ports or known portnames below, seperated by a space. # TCP services (e.g. SMTP, WWW) must be set in FW_SERVICES_QUICK_TCP, and # UDP services (e.g. syslog) must be set in FW_SERVICES_QUICK_UDP. # e.g. if a secure shell daemon on the firewall should be accessible from # the internet: # FW_SERVICES_QUICK_TCP="ssh" # e.g. if the firewall should receive isakmp (IPsec) internet: # FW_SERVICES_QUICK_UDP="isakmp" # For IP protocols (like IPsec) you need to set # FW_SERVICES_QUICK_IP="50" # # Choice: leave empty or any number of ports, known portnames (from # /etc/services) and port ranges seperated by a space. Port ranges are # written like this: allow port 1 to 10 -> "1:10" # e.g. "", "smtp", "123 514", "3200:3299", "ftp 22 telnet 512:514" # For FW_SERVICES_*_IP enter the protocol name (like "igmp") or number ("2") # # QUICKMODE: TCP services open to external networks (InterNet) # (Common: ssh smtp) FW_SERVICES_QUICK_TCP="" ## Type: string # QUICKMODE: UDP services open to external networks (InterNet) # (Common: isakmp) FW_SERVICES_QUICK_UDP="" ## Type: string # QUICKMODE: IP protocols unconditionally open to external networks (InterNet) # (For VPN firewall that is VPN gateway: 50) FW_SERVICES_QUICK_IP="" ## Type: string # # 25.) # Do you want to load customary rules from a file? # # This is really an expert option. NO HELP WILL BE GIVEN FOR THIS! # READ THE EXAMPLE CUSTOMARY FILE AT /etc/sysconfig/scripts/SuSEfirewall2-custom # #FW_CUSTOMRULES="/etc/sysconfig/scripts/SuSEfirewall2-custom" FW_CUSTOMRULES="" ## Type: yesno ## Default: no # # 26.) # Do you want to REJECT packets instead of DROPing? # # DROPing (which is the default) will make portscans and attacks much # slower, as no replies to the packets will be sent. REJECTing means, that # for every illegal packet, a connection reject packet is sent to the # sender. # # Choice: "yes" or "no", if not set defaults to "no" # FW_REJECT="no" ## Type: string # # 27.) # Tuning your upstream a little bit via HTB (Hierarchical Token Bucket) # for more information about HTB see http://www.lartc.org # # If your download collapses while you have a parallel upload, # this parameter might be an option for you. It manages your # upload stream and reserves bandwidth for special packets like # TCP ACK packets or interactive SSH. # It's a list of devices and maximum bandwidth in kbit. # For example, the german TDSL account, provides 128kbit/s upstream # and 768kbit/s downstream. We can only tune the upstream. # # Example: # If you want to tune a 128kbit/s upstream DSL device like german TDSL set # the following values: # FW_HTB_TUNE_DEV="ppp0,125" # where ppp0 is your pppoe device and 125 stands for 125kbit/s upstream # # you might wonder why 125kbit/s and not 128kbit/s. Well practically you'll # get a better performance if you keep the value a few percent under your # real maximum upload bandwidth, to prevent the DSL modem from queuing traffic in # it's own buffers because queing is done by us now. # So for a 256kbit upstream # FW_HTB_TUNE_DEV="ppp0,250" # might be a better value than "ppp0,256". There is no perfect value for a # special kind of modem. The perfect value depends on what kind of traffic you # have on your line but 5% under your maximum upstream might be a good start. # Everthing else is special fine tuning. # If you want to know more about the technical background, # http://tldp.org/HOWTO/ADSL-Bandwidth-Management-HOWTO/ # is a good start # FW_HTB_TUNE_DEV="" Yahoo! Mail: votre e-mail personnel et gratuit qui vous suit partout ! Créez votre adresse à http://mail.yahoo.fr

1 0

Replace susefirewall2 with fwbuilder
by Arie Reynaldi Zanahar 29 Jan '04

29 Jan '04

What if I want to replace susefirewall with fwbuilder ? How can I start the service ? -- Arie Reynaldi Zanahar reyman(a)reynaldi.com

1 0

nmap
by Michael Galloway 29 Jan '04

29 Jan '04

looks like there is an nmap release that resolves the issue of root not being able to run scans: maple:~ # rpm -qa | grep nmap nmap-3.30-70 thanks guys for getting this out. -- michael

2 1

Fw: Fw: [suse-security] sftp with no ssh login
by Manuel Balderrábano 28 Jan '04

28 Jan '04

Ups! You are absolutely right! I did not want to change my instalation, but it looks not only the best solution but the only one. Regards. > Yes ... user can still remove it, because he owns his home directory and > has therefore delete rights. You COULD set the permissions like in /tmp > (1755), but I ask myself, why you don't use scponly or rssh as shell, as I > suggested? They are designed for your purpose. No clumsy scripts and > permissions necessary! > > Markus > -- > __________________ /"\ > Markus Gaugusch \ / ASCII Ribbon Campaign > markus(at)gaugusch.at X Against HTML Mail > / \

2 1

Amavis + Sendmail + Suse9.0
by Tall0n 28 Jan '04

28 Jan '04

Is there anywhere that there is documentation on how to get amavis and sendmail up and running on a fresh Suse 9.0 machine. In the Readme.Suse in /usr/share/doc/packages/amavis-new/ it just says do 2 things. I did those and it's not checking for virii. TIA, Tall0n

1 0

vsftpd & epsv4 mode
by Nikolisin, Harald 28 Jan '04

28 Jan '04

hi list yesterday I set up a vsftpd server - sucessfully ;-) all common connections (from the beloved redmond tools) make no problems. curiously the lukeftp command line tool has problems connecting the server. in standard mode all command which active the passive mode fails: 229 Entering Extended Passive Mode (|||46597|) ...here is dead end. after googeling I discover the epsv4 toggle mode. after disabling the extended passive commands, following server message appear: 227 Entering Passive Mode (XXX,XXX,XX,XX,23,72) that works quite good. curiously I can establish a connection to this ftp-server via VPN (and the private IP-Number). within my enterprise network the 229 - Extended Passive Mode works! therefore it is definitely not the fault of vsftpd. here comes my questions. 1) I assume the number "46579" is the port number given from the FTP server in the case of epsv. the ",23-72" is the range of data port given by FTP in case of pasv mode. is that correct? therefore one firewall seems blocking the high-port 46579 in the case of internet-connection (at VPN connection all traffice goes through..)?? 2) if I establish with lukeftp a connection to "ftp.suse.com" I am immediately in the pasv mode (instead epsv). I assume SuSE also running vsftpd - therefore a setting must exist which forces ftp-clients to use classical pasv mode. unfortunately I could not find this option. regards harald -- Mit freundlichen Grüßen / With kind regards Dipl.-Ing. Harald Nikolisin SOFiSTiK AG (Entwicklung)

8 9

Tripwire Segmentation Fault error...
by Stefano Bertotti 27 Jan '04

27 Jan '04

Dear Sir, we are near to SuSE 9.1 without official solutions for this problem in SuSE 9.0 ... You have never explained the real nature of the problem. Are You supporting the porting solutions from 8.2 proposed in this list ? If the answer is "yes" can You publish the official patch on the onlineupdate servers, otherwise can You explain this incredible support delay...? Regards

6 9