August 2004 - openSUSE Security - openSUSE Mailing Lists

SUSE loop_fish2 keylength ?
by szh＠dgap.mipt.ru 06 Aug '04

06 Aug '04

Hello I am wondering what keylength does SUSE loop_fish2 use ? Suse losetup setups 20+20=40 bytes of loopinfo.lo_encrypt_key data, sets keylength = 20 and passes to kernel loop_fish2 it seems work only with 128, 192, 256 bits keys. Can somebody please clarify : Which length loop_fish2 uses ? and How is it derived from lo_encrypt_key ?

1 0

Kernel vulnerability?
by Frank Steiner 06 Aug '04

06 Aug '04

Hi, are the SuSE kernels affected by this? http://isec.pl/vulnerabilities/isec-0016-procleaks.txt It seems that this issue (if it is one) is more or less ignored on the LKML. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049

3 2

pam_unix2 ldap limiting host access
by rian bogle 05 Aug '04

05 Aug '04

How can one go about limiting access to hosts by ldap users with suse pam_ldap and nss_ldap. It appears as though pam_unix2 actually uses nss_ldap and thus ignores the traditional pam_check_host_attr for pam_ldap in ldap.conf. In my network, we have multiple suse workstations and servers who authenticate to an ldap server and mount a remote home dir. I would like to limit access of users to certain and specific hosts by using the host dn in my ldap db. Thanks, Rian -- ******************************************************** * Rian Bogle * * Computer Programmer / IT Specialist * * Flagstaff Field Center * * US Geological Survey * * (928) 556 7212 * * * * "Unix is user friendly, * * its just particular about who its friends are...." * * * ********************************************************

1 0

administrativa: unsubscribed amazon addresses
by Roman Drahtmueller 05 Aug '04

05 Aug '04

FYI: ---------- Forwarded message ---------- From: Roman Drahtmueller <suse-security-owner(a)suse.com> To: all amazon subscribers <suse-security-owner(a)suse.com> Cc: abuse(a)amazon.com Date: Thu, 5 Aug 2004 13:01:18 +0200 (MEST) Subject: your subscription Dear subscriber on suse-security(a)suse.com, due to some complaints of other list members, all subscribers using amazon domains in their subscription email address are being removed from the list, effective immediately. The complaints refer to unsolicited email sent to addresses that appear actively on the list, and that stem from amazon.co.uk or amazon.com domains. We consider this reason enough to unsubscribe you from the list. If you feel that your unsubscription from suse-security(a)suse.com happened in error, then please let us know, and feel free to re-subscribe to the list. If you are the reason why we are unsubscribing all amazon email addresses from our list, then please stay off the list. Thank you, Roman Drahtmüller, SUSE Security. -- - - | Roman Drahtmüller <draht(a)suse.de> // The mistakes you regret the most in | Novell - SUSE Linux AG - Security // your life are the ones you didn't | Nürnberg, Germany // commit when you had the chance. (HR) | - -

3 2

SuSE 8.0 patch update : problem with mod_ssl-2.8.7-120.i386.patch .rpm
by Theytaz Antoine 05 Aug '04

05 Aug '04

hello all, I have exactly this problem. Armin, did you get any answer ? Thanks, Antoine ---------------------------------------------------------------------------- ----------------- Date: Tue, 27 Jul 2004 08:11:28 +0000 (GMT) From: Armin Schoech <schoech(a)iap-kborn.de> Message-ID: <Pine.LNX.4.58.0407270808170.3318(a)pcramnan.iap-kborn.de> Subject: [suse-security] Problem with mod_ssl-2.8.7-120.i386.patch.rpm Hi ! I have a problem with the newest mod_ssl Patches on my SuSE 8.0 boxes. The error messsage ist: error: failed dependencies: apache = 1.3.23-152 is needed by mod_ssl-2.8.7-120 But there is no apache-1.3.23-152.i386.rpm on the SuSE FTP server. The latest patch for apache is apache-1.3.23-150.i386.rpm. There is only a apache-1.3.23-152.src.rpm but no pre-compiled rpm. Is anyone having the same problem ? Can I just force the update with "--nodeps" option ? Armin

1 0

SUSE Security Announcement: libpng (SUSE-SA:2004:023)
by Thomas Biege 05 Aug '04

05 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: libpng Announcement-ID: SUSE-SA:2004:023 Date: Wednesday, Aug 4th 2004 16:00 MEST Affected products: 8.0, 8.1, 8.2, 9.0, 9.1 SUSE Linux Database Server, SUSE eMail Server III, 3.1 SUSE Linux Enterprise Server 7, 8, 9 SUSE Linux Firewall on CD/Admin host SUSE Linux Connectivity Server SUSE Linux Office Server Vulnerability Type: remote system compromise Severity (1-10): 9 SUSE default package: yes Cross References: VU#388984 VU#236656 VU#160448 VU#477512 VU#817368 VU#286464 CAN-2004-0597 CAN-2004-0598 CAN-2004-0599 Content of this advisory: 1) security vulnerability resolved: - stack based buffer overflows - NULL pointer dereference - integer overflows problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - mod_ssl - lha - gfxboot - liby2util - pure-ftpd - neon - pavuk - sox - gaim - kernel 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Several different security vulnerabilities were found in the PNG library which is used by applications to support the PNG image format. A remote attacker is able to execute arbitrary code by triggering a buffer overflow due to the incorrect handling of the length of transparency chunk data and in other pathes of image processing. (VU#388984, VU#817368, CAN-2004-0597) A special PNG image can be used to cause an application crashing due to NULL pointer dereference in the function png_handle_iCPP() (and other locations). (VU#236656, CAN-2004-0598) Integer overflows were found in png_handle_sPLT(), png_read_png() functions and other locations. These bugs may at least crash an application. (VU#160448, VU#477512, VU#286464, CAN-2004-0599) Many thanks to Chris Evans who reported issues to us and other vendors. 3) special instructions and notes Various applications use libpng either dynamically linked, statically linked, or by linking a copy of libpng included in the application's source distribution. In the first case you have to restart the affected application. In the other cases we will release updates for these packages if the vulnerable libpng code is called with input from an untrusted source. 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/libpng-1.2.5-182.7.i58… 0e89a04a0a50a49f756795bbd319e1dd patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libpng-1.2.5-182.7.i58… dc7270f4c0c728c3ba7252d0a551e437 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/libpng-1.2.5-182.7.src.… bb8d8000a010d92747dda1b0908d41aa SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libpng-1.2.5-191.i586.… 5b34c70a715cd34bb0e5879063dcf63b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libpng-1.2.5-191.i586.… 6c192934eae546bc1f2c9b7980c848f0 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/libpng-1.2.5-191.src.rpm c740a8c8c6188470512c91ec8e9e70a9 SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libpng-1.2.5-191.i586.… 64d76d67104123317c4a66a0721072e8 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libpng-1.2.5-191.i586.… 372b2eae57ff3ff90ad1250e8a2d3a91 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/libpng-1.2.5-191.src.rpm 16dde1bf26f8c9c006ccad4779d138d7 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libpng-1.2.4-115.i586.… 88dc17c0edccfcd65fea3539379de370 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libpng-1.2.4-115.i586.… 24d8632e5454e46ce4623c5a672a3d5d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/libpng-1.2.4-115.src.rpm e3086525ee914ddc5dc0c7da7ab96a25 SUSE Linux 8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/gra1/libpng-2.1.0.12-169.i386.r… 09b22a2fab61b1018ce73e2965777123 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/gra1/libpng-2.1.0.12-169.i386.p… 097de7e1c11106390128b6996041fe3c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/libpng-2.1.0.12-169.src.rpm 9e1da14f139fc4dcf481cdf836397da7 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libpng-1.2.5-182.7… c6c0f425059cf94803952530f0e9ba02 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libpng-1.2.5-182.7… 01814d5c445560c6bcca0f1d9221e5be source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/libpng-1.2.5-182.7.sr… 27c4236b2ca11a760b3028c5058db7cf SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libpng-1.2.5-191.x… 5e8c7dcfe20c386150c4129bb549569f patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libpng-1.2.5-191.x… 4fc9a5a29f5c813b32b9dee230250b17 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/libpng-1.2.5-191.src.… 526c0048344f1aa467903b1a8bce3506 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - mod_ssl A remotely exploitable format string bug has been found in the logging function of mod_ssl. New packages are available at our FTP servers. - lha A source code review of lha was conducted by the SuSE Security-Team to fix all possible buffer overflows. New packages are available at our FTP servers. - gfxboot/bootsplash-theme-SuSE/bootsplash-theme-SuSE-Home A bug in gfxboot on SUSE LINUX 9.1 caused the lilo boot password to be shown in cleartext while typing. The standard boot loader is grub. New packages are available at our FTP servers. - liby2util File names of patch files are no longer passed to gpg via the system() call. Since those file names are not protected by a digital signature, an attacker could previously manage to implant shell code. New packages are available at our FTP servers. - pure-ftpd This update fixes a possible DoS attack because of a bug in the accept_client function handling the setup of new connections. New packages are available at our FTP servers. - neon This update adds a missing filter for control characters. New packages are available at our FTP servers. - pavuk This update fixes several buffer overflows in pavuk's digest authentication support. Thanks to Matthew Murphy for reporting this issue to us. New packages are available at our FTP servers. - sox Several buffer overflows in the 'sox' and 'play' have been fixed that can be exploited by playing specially crafted .wav files. (CAN-2004-0557) New packages are available at our FTP servers. - gaim The SuSE Security Team discovers various remotely exploitable buffer overflows in the MSN-protocol parsing functions of gaim. The only affected product is SUSE LINUX 9.1. New packages will be available soon. (CAN-2004-0500) - kernel Paul Starzetz from iSEC informed us about a race condition in the 64bit file offset handling code of the kernel. New kernels for SUSE LINUX Enterprise Server 9 are available from the maintenance-web. The updates for the SUSE LINUX 9.1 kernels are available from our FTP servers. Kernel update packages for older SUSE LINUX distributions will be available in the next few days and will be announced with a dedicated advisory. ______________________________________________________________________________ 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.2 (GNU/Linux) iQEVAwUBQRD6oHey5gA9JdPZAQH0sQf/Y8TYYttWr44JA29vuduY6dZg4HkCujEh tMjOLSxJ2MfvLkbY5dGdjpwx5ih4it57jt0IeWfcjQ3CeQOA/3z6xRYwlQ0QgzXD YOaGdq1W30FDBfphZUvBvBrWbzJpETFEcb36PEMSncedpx4a7Hmz3GbDiAPoMMke /ykL9NG5ooSvmf09LreXPl5xD+mbT9qxX0Mw0nSixmyMKTJBnqub+Sa03lnmq0Ud c+R5UaG9ncB3MZfLK4YlZVygpIPn6+ezoEQ4KUvI91ESNdvoqozHNhf//37TzRLL noVNSAouV1R1aEeFGxjtHVatnlWdv/NTekxW5rcs2ENQ1bDT/TPVQw== =ossK -----END PGP SIGNATURE-----

2 2

Fwd: [suse-security] reiserfs strange behavior
by melissad＠speakeasy.net 03 Aug '04

03 Aug '04

Per the source for Reiser or to get an answer, go to the Reiser Site at http://namesys.com or reiser(a)namesys.com I quit using Reiser as my successive SuSE release updates would not recognize the volumes and could not mount them. I would have to go to the Reiser Site, obtain the version that SuSE was using, then load and compile, then rebuild the file system. I just went to Ext3 --- not as criticism of Reiser. neither Reiser nor I could fathom why SuSE's installation would not provide a bridge for allowing for updating the Reiser file system with an upgrade. The folks at namesys.com, the owners of Reiser, are great and helpful. melissa > -----Original Message----- > From: Guido Tschakert [mailto:guido.tschakert@src-gmbh.de] > Sent: Tuesday, August 3, 2004 01:53 PM > To: suse-security(a)suse.com > Subject: Re: [suse-security] reiserfs strange behavior > > Hello, > > > > You may even try the following pairs > > bb3001/am3001 > > gb3001/fm3001 > > mb4001/lm4001 > > mb4002/lm4002 > > ma4001/ll4001 > > td3001/so3001 > > ma4001/ll4001 > > > > I found these files becaus this is my system for user accounts. Among my > > 1300 usernames I found about 10 pairs with this kind of clash! > > > I also can confirm the problem (didn't test the hole bunch written above :-) > Is anybody here knowing the sourcecode of reiserfs (At the moment I > don't have installed the source nor I have the time to look through). I > wonder if this names are reserved in some way by reiserfs, so you can't > use'm. > I also tried to find a correaltion between the pairs mentioned above, > but I didn't see anything :-( > > But will this be the only ones? > > > I fear there are more of this kind. Why should it be only 7 pairs, you > found by chance. > > Somebody here who can test it on another Kernel < 2.6.5 > In Kernel 2.4.x (no I did not test all of them :-) I didn't found the > problem. I could imagine that it is a problem of kernel 2.6.x + reiserfs. > > guido > > Best > > Uwe > > > > > > > > > > > > > > > -- > 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] suse-security
by Carlos E. R. 03 Aug '04

03 Aug '04

El 2004-08-02 a las 16:13 -0000, suse(a)karsites.net escribió: > have the file or directory permisisons been changed somehow? No, they are those made by the rpm - I touched nothing. I had 8.2, it worked. Upgraded to 9.1, it stopped working. Reinstall afected packages, no change. -- Saludos Carlos Robinson

1 0

network performance problems with SuSEfirewall2 and multiple interfaces
by Ralf Ronneburger 03 Aug '04

03 Aug '04

Hi everyone, I've a machine with 3 real and 15 virtual interfaces under SuSE 9.0 with SuSEfirewall2. Resulting from this I've also a lot of iptable-rules (iptables-save | wc -l gives me 1068 lines). After some weeks the machine slows down network-traffic, although everything else seems to run quite well (low CPU-load, low memory-usage), so I have to reboot it (restarting SuSEfirewall2 does not help). I wounder if anybody else has experienced something similar, if anything of that kind is known and if anybody has an idea, where the problem may lay. Greetings, Ralf

3 3

SuSEfirewall2 and added iptables rule question
by guus 03 Aug '04

03 Aug '04

Hello list users, I am using SuSE 9.1 prof. And its doing quite nice on my server. Although I have a security related question. Is there somebody who can give me a hint on how to add iptables rules to the SuSEfirwall2 setup. I haven been trying severall things before posting to this list, for example: - adding the rule directly from the prompt using the iptables -A command. - usung the webmin firewall configuration tool, added the rule and made it run at startup. - put the rule in the startup script SuSEfirewall2 using the folowing: FW_CUSTOMRULES="/etc/sysconfig/scripts/SuSEfirewall2-custom" where the called script includes: fw_custom_before_denyall() { iptables -A input_ext -m state -s 80.0.0.0/0 -d 10.0.1.253 -i eth1 --state NEW,ESTABLISHED,RELATED,INVALID -j DROP true } Nevertheless when I execute the iptables -L command the rule seems not to be added to the filtering table. Only the other rules, generated by the firewall are there. I realy like to get this running, so if yoy could help then please do. Your help will be much appreciated. Thank you in advance. Guus Bill -------------------------------------------------------

2 1