October 2004 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement: libtiff (SUSE-SA:2004:038)
by Marcus Meissner 22 Oct '04

22 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: libtiff Announcement-ID: SUSE-SA:2004:038 Date: Friday, Oct 22nd 2004 18:00 MEST Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Enterprise Server 8, 9 SUSE Linux Desktop 1.0 Vulnerability Type: code execution Severity (1-10): 9 SUSE default package: yes Cross References: CAN-2004-0803 CAN-2004-0804 CAN-2004-0886 CAN-2004-0929 Content of this advisory: 1) security vulnerability resolved: - several buffer overflows and related problems in libtiff were fixed. problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - security problems in PDF viewers - freeradius denial of service problems - mpg123 buffer overflow 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion libtiff is used by image viewers and web browser to view "TIFF" images. These usually open and display those images without querying the user, making a normal system by default vulnerable to exploits of image library bugs. Chris Evans found several security related problems during an audit of the image handling library libtiff, some related to buffer overflows, some related to integer overflows and similar. This issue is being tracked by the CVE ID CAN-2004-0803. Matthias Claasen found a division by zero in libtiff. This is tracked by the CVE ID CAN-2004-0804. Further auditing by Dmitry Levin exposed several additional integer overflows. These are tracked by the CVE ID CAN-2004-0886. Additionally, iDEFENSE Security located a buffer overflow in the OJPEG (old JPEG) handling in the SUSE libtiff package. This was fixed by disabling the old JPEG support and is tracked by the CVE ID CAN-2004-0929. SUSE wishes to thank all the reporters, auditors, and programmers for helping to fix these problems. 2) solution/workaround There is no workaround. Update the libtiff packages. 3) special instructions and notes Make sure that you restart your web browser after updating. 4) package location and checksums 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. You can also use the YaST Online Update tool to install the security updates. Our maintenance customers are being notified individually. The packages are being offered for installation from the maintenance web. x86 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libtiff-3.6.1-38.12.i5… cd373c181599ebbf3be0f021b811c7da patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libtiff-3.6.1-38.12.i5… a45416ea1ac9628b9e4e7e6f09653cb5 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/tiff-3.6.1-38.12.src.rpm 2387abe21eebb97f319b6ddf1a982314 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libtiff-3.5.7-376.i586… db8b4d23eb887b3c391f5262f766ff86 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libtiff-3.5.7-376.i586… 58112fc9e5c6395bc316f3b46ffeb0ca source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/tiff-3.5.7-376.src.rpm 0810ea6ffe77b7a450698386a6238e61 SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libtiff-3.5.7-376.i586… 339e0ce21cceadb883d2022ec01c1219 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libtiff-3.5.7-376.i586… 608c1b39e6d67c9da02e02d2176b7a97 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/tiff-3.5.7-376.src.rpm 8891d3c8ff0dd0f283f63d4b3021b894 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libtiff-3.5.7-376.i586… ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - security problems in pdf viewers Chris Evans, Dmitry Levin and others found several buffer and integer overflow problems in xpdf and xpdf clones. These are being tracked under the CVE Ids CAN-2004-0888 and CAN-2004-0889. New packages will be available soon. - freeradius Several bugs that can be abused to remotely crash freeradius have been discovered (CAN-2004-0938, CAN-2004-0960, CAN-2004-0961). New packages will be available soon. - mpg123 A buffer overflow in mpg123 has been discovered. New packages will be available soon. ______________________________________________________________________________ 6) 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 recommend against subscribing to security lists that cause the e-mail 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 file name 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 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.2.4 (GNU/Linux) iQEVAwUBQXkgNXey5gA9JdPZAQH0LAf9GkmMXVs4mBrwyGqvJTHP6+fglyixuDKm tTdR9JIsgdSZu8O6LKxuQtqmBhgnEjZTue0LhcmVevWuD/TJiMeVqs6eJ4dFrseW iSOgstBxxg4OGxyTxxRtxrAQvQsS5AzvA+FyKQ482cAaV1xm/1jdTQzjZQ3sI0/k prpHD/2MzS0Y6miQcEYePcfZdB2nSgVDWWkElhUIzLNAF3H7MJxpHW5ZNPaA8Mwa BzOO6hVDObuN7QN35cNB2foUvfV/N+/wieWjFO0n1htx0x1pkwRMrn2Bg/DCKr1D 0mhXoytvF6uahD64UUDlY8eInVgbmNb6Q2PEN6PpplPav5NdrLGbwQ== =Lhl9 -----END PGP SIGNATURE-----

1 0

RE: [suse-security] IPTables Firewall script Generator
by Michael Sim 22 Oct '04

22 Oct '04

Agreed again, I'm no geek, though I need to know what happens "behind the scenes" of a computer & Linux forces you to learn that. Even the Linux geeks in my working environment, my mentors & teachers, state how complicated playing with IPTables is. IP tables for dummies is just my level. I need a firewall sure 'nuff but it shouldn't take a month of sundays to build one. Regards Michael Sim SLI - MIS Central Team Phone: (32 0) 16 800 369 Fax: (32 0) 16 800 398 The information contained in this email is private and is solely for the use of the intended recipient(s). If you are not the intended recipient you have no entitlement to use the contents of this email. Views expressed in this email do not necessarily reflect SLi policies, does not guarantee that any attachments are free from viruses or other defects and accepts no liability for any losses resulting from infected email transmissions. Further information on SLi, services and products can be found at www.sylvania-lighting.com -----"Mike Tierney" <miket(a)marketview.co.nz> wrote: ----- To: "'Roland Kuhn'" <rkuhn(a)e18.physik.tu-muenchen.de>, "'Michael Sim'" <michael.sim(a)sylvania-lighting.com> From: "Mike Tierney" <miket(a)marketview.co.nz> Date: 22/10/2004 3:05 cc: <suse-security(a)suse.com> Subject: RE: [suse-security] IPTables Firewall script Generator Hi Roland There's nothing wrong with manually making iptables scripts. I'm just a big fan of pretty graphical interfaces! :) I'd hate to have to build big complicated rulesets for firewalls with 4 or 5 interfaces by hand, but some people are happy doing that and may even enjoy it! Cheers -----Original Message----- From: Roland Kuhn [mailto:rkuhn@e18.physik.tu-muenchen.de] Sent: Thursday, 21 October 2004 10:24 p.m. To: Michael Sim Cc: Mike Tierney; suse-security(a)suse.com Subject: Re: [suse-security] IPTables Firewall script Generator Hi Michael! On Oct 21, 2004, at 9:54 AM, Michael Sim wrote: > > Agreed Fwbuilder eases the pain of working with iptables > There seems to be some consensus about this here, which I would like to understand. I'm quite happy dealing with iptables like it is, and I wouldn't want to be unable to read the actual configuration in any case. So what's the point in learning yet another tool? Ciao, Roland -- TU Muenchen, Physik-Department E18, James-Franck-Str. 85747 Garching Telefon 089/289-12592; Telefax 089/289-12570 -- A mouse is a device used to point at the xterm you want to type in. Kim Alm on a.s.r. -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

1 0

RE: [suse-security] IPTables Firewall script Generator
by Mike Tierney 22 Oct '04

22 Oct '04

Hi Roland There's nothing wrong with manually making iptables scripts. I'm just a big fan of pretty graphical interfaces! :) I'd hate to have to build big complicated rulesets for firewalls with 4 or 5 interfaces by hand, but some people are happy doing that and may even enjoy it! Cheers -----Original Message----- From: Roland Kuhn [mailto:rkuhn@e18.physik.tu-muenchen.de] Sent: Thursday, 21 October 2004 10:24 p.m. To: Michael Sim Cc: Mike Tierney; suse-security(a)suse.com Subject: Re: [suse-security] IPTables Firewall script Generator Hi Michael! On Oct 21, 2004, at 9:54 AM, Michael Sim wrote: > > Agreed Fwbuilder eases the pain of working with iptables > There seems to be some consensus about this here, which I would like to understand. I'm quite happy dealing with iptables like it is, and I wouldn't want to be unable to read the actual configuration in any case. So what's the point in learning yet another tool? Ciao, Roland -- TU Muenchen, Physik-Department E18, James-Franck-Str. 85747 Garching Telefon 089/289-12592; Telefax 089/289-12570 -- A mouse is a device used to point at the xterm you want to type in. Kim Alm on a.s.r.

1 0

Portscan with a reason given ... ???
by Philippe Vogel 21 Oct '04

21 Oct '04

Hi! I got this [...] <quote> The reason for the scan on the IP address that "doesn't exist" was as a result of the following spam being reported. Received: from donjacobo.es (lsanca1-ar62-4-8-246-254.lsanca1.dsl-verizon.net [4.8.246.254]) by cmx0.sol.net (8.12.11/8.12.11/SNNS-1.04) with SMTP id i953lEXr053775 for <steven.payeur(a)wyof.com>; Mon, 4 Oct 2004 22:47:28 -0500 (CDT) Received: from <FROM_MY_IP_RANGE> by smtp.sanet.com.br; Tue, 05 Oct 2004 03:45:23 +0000 Message-ID: <8c1001c4aa8d$e692821b$59f01b90(a)donjacobo.es> From: "Josie Wooten" <josiewooten_eq(a)sanet.com.br> To: <> Subject: <> Date: Mon, 04 Oct 2004 21:45:16 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit If you would like to be whitelisted from any further testing then please notify us so that we can add your imaginary IP addresses for exemption from further testing [sensible answers only please] </quote> [...] after I wrote that [...] <quote> If you don't scan other servers except proxies, why does my ids show you as portscanner and my scanlogs as well? Oct 5 05:52:00 fb7-fg6 scanlogd: 82.195.234.3 to x.x.x.x ports 23, 1181, 81,889, 1027, 1028, 1029, 1066, ..., fSrpauxy, TOS 00, TTL 50 @05:52:00 Oct 5 05:52:06 fb7-fg6 scanlogd: 82.195.234.3 to x.x.x.x ports 23, 1181, 81,889, 1027, 1028, 1029, 1066, ..., fSrpauxy, TOS 00, TTL 50 @05:52:06 Oct 5 05:52:09 fb7-fg6 scanlogd: 82.195.234.3 to x.x.x.x ports 23, 1181, 81,889, 1027, 1028, 1029, 1066, ..., fSrpauxy, TOS 00, TTL 50 @05:52:09 Oct 5 05:52:13 fb7-fg6 scanlogd: 82.195.234.3 to x.x.x.x ports 23, 1181, 81,889, 1027, 1028, 1029, 1066, ..., fSrpauxy, TOS 00, TTL 50 @05:52:13 Oct 5 05:52:16 fb7-fg6 scanlogd: 82.195.234.3 to x.x.x.x ports 23, 1181, 81,889, 1027, 1028, 1029, 1066, ..., fSrpauxy, TOS 00, TTL 50 @05:52:16 Oct 5 05:52:22 fb7-fg6 scanlogd: More possible port scans follow afaik nor this ip does not exist in our network neither it was somewhere listed. </quote> 82.195.234.3 = open-proxy-testing-visit-web-server-on-this-host.nubian.blitzed.org Or visit http://open-proxy-testing-visit-web-server-on-this-host.nubian.blitzed.org/ [...]. Somehow they seem for me incompetetnt, because they don't tell me, what they test. If I would test this for myself I would test if ip exists or answers to any sort of test (e.g. a portscan or a nmap ping ...). I would not test that much like they did. It is not the reason because I saw a portscan, it is the reason, that the portscanner does as if he was probing kind'a' open proxies and whatever as his reason for doing portscans but not showing or telling what he exactly does. Am I right or am I whining? Philippe

1 0

Re: [suse-security] yay. the bots have the list again.
by Carlos E. R. 21 Oct '04

21 Oct '04

El 2004-10-21 a las 13:02 -0000, Keith Roberts escribió: (You forgot to email to the list) > Hi there - I use pine and postfix. > > I think pine sets the from address in the email according to > the user and domain. > > You could try setting up a new user account for mailing > lists only, and see if that does the trick. That's what I'm doing, using roles. > > Or, the other thing is to open another mailing list account > with suse-security list, using the email address of your > choice. Then when you send out any mail to the list, use > that email in the from: header. Of course, I have an account dedicated to the list. You can read a more detailed explanation of what I would like to do in another email on this same thread. It is a diferent trick, not possible with Pine alone. -- Saludos Carlos Robinson

1 0

RE: [suse-security] IPTables Firewall script Generator
by Michael Sim 21 Oct '04

21 Oct '04

Agreed Fwbuilder eases the pain of working with iptables Regards Michael Sim SLI - MIS Central Team Phone: (32 0) 16 800 369 Fax: (32 0) 16 800 398 The information contained in this email is private and is solely for the use of the intended recipient(s). If you are not the intended recipient you have no entitlement to use the contents of this email. Views expressed in this email do not necessarily reflect SLi policies, does not guarantee that any attachments are free from viruses or other defects and accepts no liability for any losses resulting from infected email transmissions. Further information on SLi, services and products can be found at www.sylvania-lighting.com -----"Mike Tierney" <miket(a)marketview.co.nz> wrote: ----- To: <suse-security(a)suse.com> From: "Mike Tierney" <miket(a)marketview.co.nz> Date: 20/10/2004 23:36 Subject: RE: [suse-security] IPTables Firewall script Generator I've just started using Fwbuilder. It has a VERY nice graphical interface and can generate rules for a variety of platforms (including iptables). It stores the rules and objects in a platform independent fashion which unfortunitely means you can't just read in your old ruleset but once you've built your new one you could easily change your firewall platform (i.e. from Linux to some form of BSD) and just re-compile the rules for whichever system you need! The Linux/etc versions are free to use. The Windows version isn't free. Check out http://www.fwbuilder.org/ I've just built rules for our new firewall with 5 network interfaces with no trouble. Cheers -----Original Message----- From: suse(a)karsites.net [mailto:suse@karsites.net] Sent: Monday, 11 October 2004 11:02 p.m. To: suse-security(a)suse.com Subject: [suse-security] IPTables Firewall script Generator Hi all. Just found this in freshmeat daily news. http://www.links2world.org/doc/links2world-Firewall-HOWTO/index.html Still in development. Taken from the homepage: links2world Firewall is a very simple tool writen in C, that helps you generate iptables rules for Linux 2.4.x and newer kernels. Released under GNU General Public License, it is very easy to configure and designed to run on hosts with one or more network interfaces. Most of the existing iptables script generators are shell scripts. You have to dig in and to look through entire script in order to customize and configure it for your needs. Furthermore, they are able to generate iptables rules for one or maximum two network interfaces. On the other hand, links2world Firewall uses a very human readable configuration file that is very easy to understand and write. Still more, it does not matter if you have one, two, three or twenty network interfaces, links2world Firewall is able to generate statefull iptables rulesets able to control the packet flows between all the networks your machine is connected to. May be of interest to anyone managing alot several NIC IF's. HTH - Keith Roberts -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

2 1

SuSE Security Announcement: kernel (SUSE-SA:2004:037)
by Marcus Meissner 21 Oct '04

21 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2004:037 Date: Wednesday, Oct 20th 2004 18:00 MEST Affected products: 9.1 SUSE Linux Enterprise Server 9 Vulnerability Type: remote denial of service Severity (1-10): 9 SUSE default package: yes Cross References: CAN-2004-0816 CAN-2004-0887 Content of this advisory: 1) security vulnerability resolved: - remote system crash with enabled firewall - local root exploit on the S/390 platform - minor /proc information leaks problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - libtiff - cyrus-sasl - php4 - zinf ______________________________________________________________________________ 1) problem description, brief discussion An integer underflow problem in the iptables firewall logging rules can allow a remote attacker to crash the machine by using a handcrafted IP packet. This attack is only possible with firewalling enabled. We would like to thank Richard Hart for reporting the problem. This problem has already been fixed in the 2.6.8 upstream Linux kernel, this update contains a backport of the fix. Products running a 2.4 kernel are not affected. Mitre has assigned the CVE ID CAN-2004-0816 for this problem. Additionaly Martin Schwidefsky of IBM found an incorrectly handled privileged instruction which can lead to a local user gaining root user privileges. This only affects the SUSE Linux Enterprise Server 9 on the S/390 platform and has been assigned CVE ID CAN-2004-0887. Additionaly the following non-security bugs were fixed: - Two CD burning problems. - USB 2.0 stability problems under high load on SMP systems. - Several SUSE Linux Enterprise Server issues. (see the Maintenance Information Mail for more informations). 2) solution/workaround If you are not using an iptables based firewall (like SUSEfirewall2) on your system, you are not affected. If you are using a firewall, a workaround is to disable firewall logging of IP and TCP options. We recommend to update the kernel. 3) special instructions and notes SPECIAL INSTALL INSTRUCTIONS: ============================== The following paragraphs will guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, the steps outlined in a particular paragraph may or may not be applicable to your situation. Therefore, please make sure to read through all of the steps below before attempting any of these procedures. All of the commands that need to be executed are required to be run as the superuser (root). Each step relies on the steps before it to complete successfully. **** Step 1: Determine the needed kernel type Please use the following command to find the kernel type that is installed on your system: rpm -qf /boot/vmlinuz Following are the possible kernel types (disregard the version and build number following the name separated by the "-" character) kernel-64k-pagesize kernel-bigsmp kernel-default kernel-smp **** Step 2: Download the package for your system Please download the kernel RPM package for your distribution with the name as indicated by Step 1. The list of all kernel rpm packages is appended below. Note: The kernel-source package does not contain a binary kernel in bootable form. Instead, it contains the sources that the binary kernel rpm packages are created from. It can be used by administrators who have decided to build their own kernel. Since the kernel-source.rpm is an installable (compiled) package that contains sources for the linux kernel, it is not the source RPM for the kernel RPM binary packages. The kernel RPM binary packages for the distributions can be found at the locations below ftp://ftp.suse.com/pub/suse/i386/update/. 9.1/rpm/i586 After downloading the kernel RPM package for your system, you should verify the authenticity of the kernel rpm package using the methods as listed in section 3) of each SUSE Security Announcement. **** Step 3: Installing your kernel rpm package Install the rpm package that you have downloaded in Steps 3 or 4 with the command rpm -Uhv --nodeps --force <K_FILE.RPM> where <K_FILE.RPM> is the name of the rpm package that you downloaded. Warning: After performing this step, your system will likely not be able to boot if the following steps have not been fully followed. **** Step 4: configuring and creating the initrd The initrd is a ramdisk that is loaded into the memory of your system together with the kernel boot image by the bootloader. The kernel uses the content of this ramdisk to execute commands that must be run before the kernel can mount its actual root filesystem. It is usually used to initialize SCSI drivers or NIC drivers for diskless operation. The variable INITRD_MODULES in /etc/sysconfig/kernel determines which kernel modules will be loaded in the initrd before the kernel has mounted its actual root filesystem. The variable should contain your SCSI adapter (if any) or filesystem driver modules. With the installation of the new kernel, the initrd has to be re-packed with the update kernel modules. Please run the command mk_initrd as root to create a new init ramdisk (initrd) for your system. On SuSE Linux 8.1 and later, this is done automatically when the RPM is installed. **** Step 5: bootloader If you run a SUSE LINUX 8.x, SLES8, or SUSE LINUX 9.x system, there are two options: Depending on your software configuration, you have either the lilo bootloader or the grub bootloader installed and initialized on your system. The grub bootloader does not require any further actions to be performed after the new kernel images have been moved in place by the rpm Update command. If you have a lilo bootloader installed and initialized, then the lilo program must be run as root. Use the command grep LOADER_TYPE /etc/sysconfig/bootloader to find out which boot loader is configured. If it is lilo, then you must run the lilo command as root. If grub is listed, then your system does not require any bootloader initialization. Warning: An improperly installed bootloader may render your system unbootable. **** Step 6: reboot If all of the steps above have been successfully completed on your system, then the new kernel including the kernel modules and the initrd should be ready to boot. The system needs to be rebooted for the changes to become active. Please make sure that all steps have completed, then reboot using the command shutdown -r now or init 6 Your system should now shut down and reboot with the new kernel. 4) package location and checksums 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. x86 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-default-2.6.5-7… 735f99730442772d0caeb1043576da0e ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-smp-2.6.5-7.111… 8e38495a90203fdeef0167126e9699fd ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-bigsmp-2.6.5-7.… 54474a313ff90c5a5ded8cd3590016ee source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-default-2.6.5-7.… 60a46f48bbae6989a50d2b3c735cd176 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-smp-2.6.5-7.111.… 5bc77692dc82521b83378c97d39acd72 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-bigsmp-2.6.5-7.1… 348c5d63b8c26c548d8b5bfcc894b805 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-default-2.6… 53ec1285f8933f79b6e53f2cb4d2094a ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-smp-2.6.5-7… de3bf18c94d26a2b3477cf11cf723380 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-default-2.6.5-… 3e6123bd50f2802cf6a96ccfa2af674f ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-smp-2.6.5-7.11… 365354d9e91032e53436f949da6ae8f6 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: libtiff - Several buffer and integer overflows have been found in the image handling library libtiff by Chris Evans and Dmitry Levin, recorded under CVE Ids: CAN-2004-0803,CAN-2004-0804,CAN-2004-0886. We are working on updates and will release them within the next days. cyrus-sasl - The SASL_PATH environment variable was also used to load plugins even with setuid privileges set, which can lead to a local root privilege escalation. The default SUSE installation was not found to be affected by this problem, neithertheless we are in the process of releasing updates. The CVE ID for this issue is: CAN-2004-0884 php4 - File overwrite problems were identified in php4. We have released updates for this issue. However, due to problems with php4-recode in combination with php4-mysql we had to withdraw the update from YaST2 Online Update for some SUSE Linux versions. New packages will be available soon. zinf - A tempfile race condition in zinf / freeamp was fixed, packages are available. phpMyAdmin - A bug in phpMyAdmin that would allow users to execute arbitrary commands has been discovered. New packages will be available soon. mysql - Several bugs in mysql have been discovered. New packages will be available soon. libpng - The issues with libpng described in CAN-2004-0954 and CAN-2004-0955 where already fixed in the last libpng update. Fixed packages are therefore already available on our ftp server. ______________________________________________________________________________ 6) 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.2.4 (GNU/Linux) iQEVAwUBQXdo13ey5gA9JdPZAQE6Hwf7Bw82jWwK890uLPv8ByWeb3V8+M4kHiUc 1b33YLWPv/Q9OL1/Shyu6axownxUtSP/xgypv81Z5qKG4ETwV1EqB/v8eAQGQjCO ptkA5rID9EhZYxXxPb4v4jFiqBMxRM3Sp8n0q0eRMNnOgHY5edS6tfkbwR2SsWEc i8uGPVYaXOOnkLEB83Ra9o7UsMpXXy1W711EN7G20Tu6XT8HhNwOZZu69/KzKbso /OVY48usd6EkExrFxLSJBtWI4OU2Qn/zerd2bRmmEN+gMH+/c7pceGC+SEDGn+Bq p/mnwsDz3e4Z3LfkMgNY3qGXc7h6fOYF4GJtLB9tkH8/gIXwSqiDuQ== =SsBR -----END PGP SIGNATURE-----

1 0

IPTables Firewall script Generator
by suse＠karsites.net 20 Oct '04

20 Oct '04

Hi all. Just found this in freshmeat daily news. http://www.links2world.org/doc/links2world-Firewall-HOWTO/index.html Still in development. Taken from the homepage: links2world Firewall is a very simple tool writen in C, that helps you generate iptables rules for Linux 2.4.x and newer kernels. Released under GNU General Public License, it is very easy to configure and designed to run on hosts with one or more network interfaces. Most of the existing iptables script generators are shell scripts. You have to dig in and to look through entire script in order to customize and configure it for your needs. Furthermore, they are able to generate iptables rules for one or maximum two network interfaces. On the other hand, links2world Firewall uses a very human readable configuration file that is very easy to understand and write. Still more, it does not matter if you have one, two, three or twenty network interfaces, links2world Firewall is able to generate statefull iptables rulesets able to control the packet flows between all the networks your machine is connected to. May be of interest to anyone managing alot several NIC IF's. HTH - Keith Roberts

2 1

Configuring SuSE 9.1 as software router
by scshepard＠comcast.net 20 Oct '04

20 Oct '04

hi all, I'm trying to configure my 9.1 Professional server to act as a software router. In the future I want it to be a firewall/net/proxy server also, but I'm already stumped. Two network cards (eth0, eth1) hiding behind a cable modem (ie: 192.168.1.0/24, 196.168.2.0/24, original, no?). What is the basic "dummy" setup? And what commands for checking the configuration and errors? thanks in advance. /steve

1 0

Tripwie Segmentation Fault on Suse 8.2
by Milind Nanal 20 Oct '04

20 Oct '04

I am in the process of migrating my service from RedHat to Suse. I was sing tripwire to carry out file level audit on RedHat. I am facing problem in setting up the same on Suse 8.2. It is giving Segmentation Fault. Need your help on this. Also any alternative file integrity tool for suse may be suggested. Regards, Milind

4 3