SuSE Security Announcement: libz/zlib (SuSE-SA:2002:010) (tandem-announcement, first part)
-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: libz/zlib Announcement-ID: SuSE-SA:2002:010 Date: Monday, Mar 11th 2002 20:45 MET Affected products: 6.4, 7.0, 7.1, 7.2, 7.3 SuSE Linux Database Server SuSE eMail Server III SuSE Firewall SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 Vulnerability Type: remote command execution Severity (1-10): 8 SuSE default package: yes Other affected systems: systems with recent versions of the compression library Content of this advisory: 1) security vulnerability resolved: libz/zlib problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The zlib compression library is being used by many applications to provide data compression/decompression routines. An error in a decompression routine can corrupt the internal data structures of malloc by a double call to the free() function. If the data processed by the compression library is provided from an untrusted source, it may be possible for an attacker to interfere with the process using the zlib routines. The attack scenario includes a denial of service attack and memory/data disclosure, but it may also be possible to insert arbitrary code into the running program and to execute this code. This update fixes the known problems in the libz/zlib as a permanent fix. There exists no temporary workaround that can efficiently remedy the problem. It is expected that a large range of software is affected. The systems affected are by no means limited to Linux systems or other open-source based operating systems. Note: The libz compression library is being used by several hundred packages in all SuSE products. While the update of the libz package as itself is not problematic, it must be noted that many packages bring their own compression library in their source code. If these packages link against their own version of the libz compression library, their source needs to be fixed as well. Considering the length of a combined Security Announcement, SuSE Security publish a tandem-announcement, consisting of two seperate Security Announcements released in quick succession: SuSE-SA:2002:010 libz/zlib SuSE-SA:2002:011 packages containing libz/zlib Acknowledgements: We thank Owen Taylor who tracked down the bug in the compression library, and to Matthias Clasen for reporting the problem that seemed to be located in the libpng at first. We also thank Mark Adler and Jean-loup Gailly, the authors of the zlib package, for their quick response in the double-free() matter. SPECIAL INSTALL INSTRUCTIONS: =============================== * Installation of the update package: The installation of shared libraries on an actively running system should be done with special care. During the update of the libz package, runtime-linking the shared libraries is likely to fail for processes that execute a new binary with the execve(2) system call. If at all applicable, a system receiving the update should be kept as quiet as possible during the time that the RPM command runs. In doubt, please perform the update in Single User Mode ("init S"). The RPM command must not be interrupted during its operation. After performing the update, the processes that still use the old version of the package must be restarted for the libz upgrade to become effective. If you have performed the update in Single User Mode, this has been done already, and you can safely return to your default runlevel. If in doubt, reboot your system to make sure that the changes are becoming effective. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/a1/libz-1.1.3-597.i386.rpm 799491ca29f9bf95e3e38a73f25abea8 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/libz-1.1.3-597.src.rpm a4071506da6ab39dca5495530028d291 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/a1/libz-1.1.3-573.i386.rpm 2197aff65b09fb05b8969ace64d7a4a6 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/libz-1.1.3-573.src.rpm 1694ed149ca946e7ea1cc2da3f14c181 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/libz-1.1.3-570.i386.rpm c309b104231c596bb81008c38a4e473c source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/libz-1.1.3-570.src.rpm 950c86970cd7c3fc0a30cfab176769ac SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/libz-1.1.3-571.i386.rpm 8bde6b53a78e5f920080bfa3b6a236a6 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/libz-1.1.3-571.src.rpm 718c36c91cd0f97466cbb2303967d51c SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/libz-1.1.3-575.i386.rpm 270fc89c1be6854288925a9326f9ca6e source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/libz-1.1.3-575.src.rpm 625ed87653f820f7f65a4a8e045f6cc2 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/a1/libz-1.1.3-419.sparc.rpm f890b6d04e9164fc2afa05241c0e94c9 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/libz-1.1.3-419.src.rpm 818d39946dc6c73f425620fba546935c SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/libz-1.1.3-406.sparc.rpm ff4ea0da2c5126311f654b2896a70dd9 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/libz-1.1.3-406.src.rpm c3a49ea61f2642d53e29c8a81e07bfd9 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/libz-1.1.3-406.sparc.rpm b9e22f0ff9785ca1d226bd2c5e135909 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/libz-1.1.3-406.src.rpm 25c2b7cd4e20da69b7d806551966bae8 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/a1/libz-1.1.3-434.alpha.rpm e8cd8561a1434c36afcccd856d79a483 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/libz-1.1.3-434.src.rpm f7c21774f76fb240205291c4e91ad83c SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/libz-1.1.3-434.alpha.rpm 15510fc7563e669145d28a69e0e77d8e source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/libz-1.1.3-434.src.rpm 008bc8f743e64e26dccd89baf882b214 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/libz-1.1.3-435.alpha.rpm 7d29b7d929e4b36dd6268058bf3c7538 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/libz-1.1.3-435.src.rpm 67a4bd496c7625aaa3049417930e97f8 PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/a1/libz-1.1.3-432.ppc.rpm b06097a1496ca5fd7b3492c2ab4f7337 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/libz-1.1.3-432.src.rpm 45127ca06e4b019b2e700a0c87c2edb6 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/libz-1.1.3-417.ppc.rpm 783a39b17295e169d344a5f7f1ad7e86 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/libz-1.1.3-417.src.rpm 2ac1e404e8a6723b1eb101b7c7d118e8 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/libz-1.1.3-417.ppc.rpm 24901e0c7ccb6bf5bf17b2af60596d96 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/libz-1.1.3-417.src.rpm f9e6cda577a5007baa84fb9940ec718d SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/libz-1.1.3-416.ppc.rpm b3580d5e1b3702c330957bde4422486c source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/libz-1.1.3-416.src.rpm 32cbca2dbc911da128b5bd1d19789792 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - Please see the following SuSE Security Announcement SuSE-SA:2002:011 (packages containing libz) for upgrade information regarding packages that bring their own compression library in their source. ______________________________________________________________________________ 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@suse.de), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build@suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security@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@suse.com>. suse-security-announce@suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe@suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info@suse.com> or <suse-security-faq@suse.com> respectively. ===================================================================== SuSE's security contact is <security@suse.com> or <security@suse.de>. The <security@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 cleartext signature shows proof of the authenticity of the text. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@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----- Roman Drahtmüller, SuSE Security. - -- - - | Roman Drahtmüller <draht@suse.de> // "You don't need eyes to see, | SuSE GmbH - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPI0L+ney5gA9JdPZAQHxZgf/bORLAqA2QUZ9udAPixhnIhfhMCRTHnvF GXHbJ5kKFthOat011HFUIYAjzx501919EFdAY7Bs3RJfLicXtIB9LNpYKsVw4OU9 xfngF4jZ4sPYDtf1/5vG/JWlWVeae1hy5/zlfal+9ior3cZtO+z4ClI1eHr/25lU ehwgDC3nLAd7wL2ZKRHPCTylQR95hrGQFn5rf+A+2/ll8uwPkLRuQSE5FwyaGhis XsQHBVmJNj/4sw8Fz00ULxQTHPpk44cBYutbn6pJY0NqygJIXzDd/r8pPJ8g3I2o E5XFPbicGhY+H03gOvZF44yZxcS+N5+u6beXnCSiLRiqqywNQfJFzg== =rQ8h -----END PGP SIGNATURE-----
Roman Drahtmueller wrote:
The libz compression library is being used by several hundred packages in all SuSE products.
We have many hundred systems running various SuSE versions, some now not supported by SuSE anymore. There was a discussion on Slashdot where someone mentioned the possibility of setting the MALLOC_CHECK_ variable (possible values 0,1,2) with a slight performance penalty. Is this an option for (older remote) systems where no update packages will be supplied? Kevin -- _ | Kevin Ivory | Tel: +49-551-37000041 |_ |\ | | Service Network GmbH | Fax: +49-551-3700009 ._|ER | \|ET | Bahnhofsallee 1b | mailto:Ivory@SerNet.de Service Network | 37081 Goettingen | http://www.SerNet.de/
Hello, One of the SuSE update RPMs seems to have gone missing. The page http://www.suse.de/en/support/download/updates/72_i386.html refers to ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/apache-contrib.rpm and this file no longer exists (it did until a day or two ago). Is it in the process of being updated or has something gone wrong? Thanks, Bob ============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691
On Tue, Mar 12, 2002 at 01:46:50PM +0000, Bob Vickers wrote:
Hello,
One of the SuSE update RPMs seems to have gone missing. The page http://www.suse.de/en/support/download/updates/72_i386.html refers to ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/apache-contrib.rpm and this file no longer exists (it did until a day or two ago).
I can see this file on ftp.suse.com, with a time stamp of Sep 8 2001. Peter -- VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
Peter, Sorry, I should have been more explicit. apache-contrib.rpm exists, but it is a link to a non-existent file: ftp> dir apache-contrib*.rpm 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. lrwxrwxrwx 1 suse suse 32 Sep 8 2001 apache-contrib.rpm -> apache-contrib-1.0.9-94.i386.rpm 226 Transfer complete. Bob On Wed, 13 Mar 2002, Peter Poeml wrote:
On Tue, Mar 12, 2002 at 01:46:50PM +0000, Bob Vickers wrote:
Hello,
One of the SuSE update RPMs seems to have gone missing. The page http://www.suse.de/en/support/download/updates/72_i386.html refers to ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/apache-contrib.rpm and this file no longer exists (it did until a day or two ago).
I can see this file on ftp.suse.com, with a time stamp of Sep 8 2001.
Peter
-- VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691
On Wed, Mar 13, 2002 at 10:42:45AM +0000, Bob Vickers wrote:
Peter,
Sorry, I should have been more explicit. apache-contrib.rpm exists, but it is a link to a non-existent file:
ftp> dir apache-contrib*.rpm 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. lrwxrwxrwx 1 suse suse 32 Sep 8 2001 apache-contrib.rpm -> apache-contrib-1.0.9-94.i386.rpm 226 Transfer complete.
Also sorry... I didn't notice that the link is broken resp. that the rpm is missing. Thanks for the notice... I'll try to find out what's wrong. Peter -- VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
Hi As long as libz is linked dynamically you can download zlib-1.1.4 from http://www.gzip.org/zlib/, compile and use instead of bugged one. Cheers Marcin You an try to download the newest At 14:26 12-03-2002 +0100, Kevin Ivory wrote:
Roman Drahtmueller wrote:
The libz compression library is being used by several hundred packages in all SuSE products.
We have many hundred systems running various SuSE versions, some now not supported by SuSE anymore.
There was a discussion on Slashdot where someone mentioned the possibility of setting the MALLOC_CHECK_ variable (possible values 0,1,2) with a slight performance penalty. Is this an option for (older remote) systems where no update packages will be supplied?
Kevin -- _ | Kevin Ivory | Tel: +49-551-37000041 |_ |\ | | Service Network GmbH | Fax: +49-551-3700009 ._|ER | \|ET | Bahnhofsallee 1b | mailto:Ivory@SerNet.de Service Network | 37081 Goettingen | http://www.SerNet.de/
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
Marcin Gryszczuk wrote:
As long as libz is linked dynamically you can download zlib-1.1.4 from
Sure, I figured so from the announcement. But even in a SuSE system quite a few statically linked binaries remain. That is why I would like information from someone knowledgeable if the MALLOC_CHECK_ variable can be used as an emergency aid for unsupported systems. Kevin -- _ | Kevin Ivory | Tel: +49-551-37000041 |_ |\ | | Service Network GmbH | Fax: +49-551-3700009 ._|ER | \|ET | Bahnhofsallee 1b | mailto:Ivory@SerNet.de Service Network | 37081 Goettingen | http://www.SerNet.de/
As long as libz is linked dynamically you can download zlib-1.1.4 from
Sure, I figured so from the announcement. But even in a SuSE system quite a few statically linked binaries remain. That is why I would like information from someone knowledgeable if the MALLOC_CHECK_ variable can be used as an emergency aid for unsupported systems.
We can't make sure that this workaround does indeed work, which is why I didn't mention it. I personally don't trust such a workaround. Basically, it's easiest to rpm --rebuild the 6.4 rpm on an older system. The binary rpm should work seamlessly.
Kevin
Thanks, Roman. -- - - | Roman Drahtmüller <draht@suse.de> // "You don't need eyes to see, | SuSE GmbH - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - -
Hello All - On Tuesday 12 March 2002 09:47, Roman Drahtmueller wrote:
Basically, it's easiest to rpm --rebuild the 6.4 rpm on an older system. The binary rpm should work seamlessly.
Roman: could you expand on this idea a bit? I have a server still running 6.2, and have been concerned lately about not being able to keep it up to date with current patches. I took care of the recent SSH problems by compiling current SSH and SSL from source, and simply disabled PHP to deal with that vulnerability. Are you saying there is an easy procedure for using 6.4 RPMs on "end of life'ed" distributions? If so, I'd be very happy to hear about it. Or should I make plans to move the domains to other, more current machines? Thanks.
* naurgrim (naurgrim@karn.org) [020312 16:17]:
On Tuesday 12 March 2002 09:47, Roman Drahtmueller wrote:
Basically, it's easiest to rpm --rebuild the 6.4 rpm on an older system. The binary rpm should work seamlessly.
Roman: could you expand on this idea a bit? I have a server still running 6.2, and have been concerned lately about not being able to keep it up to date with current patches.
Hopefully Roman is asleep by now but.... If you take the 6.4 source rpm for zlib (ftp.suse.com//pub/suse/i386/update/6.4/zq1/libz.spm) do: rpm -ivh libz.spm cd /usr/src/packages/SPECS rpm -bb libz.spec If you are lucky, you have a new rpm in /usr/src/packages/RPMS/<arch> in a few minutes. You may need to edit the spec file to work around changes that occured between 6.1 and 6.4 but I doubt there are any with something like libz. Of course, this assumes you have a working gcc, autoconf, etc.
I took care of the recent SSH problems by compiling current SSH and SSL from source, and simply disabled PHP to deal with that vulnerability.
You could do the same with these two without much work probably. -- -ckm
Hello All - On Tuesday 12 March 2002 19:32, Christopher Mahmood wrote:
If you take the 6.4 source rpm for zlib (ftp.suse.com//pub/suse/i386/update/6.4/zq1/libz.spm) do: rpm -ivh libz.spm cd /usr/src/packages/SPECS rpm -bb libz.spec
On Tuesday 12 March 2002 19:43, Jeremy Buchmann wrote:
Yes, there is an easy way to do it. Download the 6.4 SOURCE RPM (ends in .src.rpm)
type rpm --rebuild libz-1.1.3-575.src.rpm
This will compile libz and build a regular put the resulting RPM in /usr/src/packages/RPMS/i386/ (or whatever your arch is).
My thanks to both of you for your responses - I'll give these a shot, and hopefully squeeze some more life out of a machine that has served faithfully. If all goes well, you have saved me a headache. Many thanks.
On Tuesday 12 March 2002 09:47, Roman Drahtmueller wrote:
Basically, it's easiest to rpm --rebuild the 6.4 rpm on an older system. The binary rpm should work seamlessly.
Roman: could you expand on this idea a bit? I have a server still running 6.2, and have been concerned lately about not being able to keep it up to date with current patches.
I took care of the recent SSH problems by compiling current SSH and SSL from source, and simply disabled PHP to deal with that vulnerability.
Are you saying there is an easy procedure for using 6.4 RPMs on "end of life'ed" distributions? If so, I'd be very happy to hear about it. Or should I make plans to move the domains to other, more current machines?
Yes, there is an easy way to do it. Download the 6.4 SOURCE RPM (ends in .src.rpm) type rpm --rebuild libz-1.1.3-575.src.rpm This will compile libz and build a regular put the resulting RPM in /usr/src/packages/RPMS/i386/ (or whatever your arch is). then, just upgrade like you would with any other package: rpm -Uhv libz-1.1.3-575.i386.rpm I just did this on a 6.3 system the other day and it worked perfectly. libz is pretty simple, though. Not all packages will work as cleanly. --Jeremy
participants (8)
-
Bob Vickers
-
Christopher Mahmood
-
Jeremy Buchmann
-
Kevin Ivory
-
Marcin Gryszczuk
-
naurgrim
-
Peter Poeml
-
Roman Drahtmueller