December 2003 - openSUSE Security - openSUSE Mailing Lists

An update failure
by Jim Westbrook 05 Dec '03

05 Dec '03

I just did the security updates including the kernel. However, one package (gnpan) failed with a version 0.0-0 > 0.3-15 (I think that's the number) error. I do not recall seeing this particular update discussed here. Do I need to remove the package and then d/l and install manually? JimW

2 1

RE: [suse-security] An update failure
by GarUlbricht7＠netscape.net 05 Dec '03

05 Dec '03

Jim Westbrook <jimw(a)austin.rr.com> wrote: >I just did the security updates including the kernel. However, one >package (gnpan) failed with a version 0.0-0 > 0.3-15 (I think that's the >number) error. I do not recall seeing this particular update discussed >here. Do I need to remove the package and then d/l and install >manually? > >JimW > You didn't say what version of SuSE you are using. I am guessing 9.0 ???? gnpan is a news reader for Gnome... per patch description (on my 8.1 box): file:/var/cache/fou4s/packages/ftp.suse.com/i386/update/8.1/patches/gnpan-5… #Packages: ## ## -----> gnpan <----- ## # Filename: gnpan.rpm # Label: A powerful newsreader for GNOME # Series: i586 # Size: 2779985 774560 You didn't say whether you used YOU or fou4s to download your Security fix. If it was fou4s I would just try again, if it is YOU, you can redo it, I just don't know what you need to delete, so if you used YOU i would download the rpm. If it were me, I would download the "new" rpm, and not the patch rpm, and install (as root) using .. "rpm -Uvh gnpan-*.rpm" If you elect that patch, Get the rpm from: http://www.suse.de/en/private/download/updates/index.html or your favorite mirror. Hope this helps, Gar -- In the Beginning was the Command Line ---Neal Stephenson -- __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455

1 0

SuSE Security Announcement: Kernel brk() vulnerability (SuSE-SA:2003:049)
by Olaf Kirch 05 Dec '03

05 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: Linux Kernel Announcement-ID: SuSE-SA:2003:049 Date: Thursday, December 4th 2003 15:30 MET Affected products: 7.3, 8.0, 8.1, 8.2, 9.0 SuSE Linux Enterprise Server 7, SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Firewall on CD/Admin host SuSE Linux Office Server SuSE Linux Desktop 1.0 SuSE Linux School Server Vulnerability Type: local root exploit Severity (1-10): 8 SUSE default package: yes Cross References: CAN-2003-0961 Content of this advisory: 1) security vulnerability resolved: - Linux kernel brk() integer overflow problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - KDE - mc - apache1/2 - freeradius - screen - mod_gzip - unace 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information This security update fixes a serious vulnerability in the Linux kernel. A missing bounds check in the brk() system call allowed processes to request memory beyond the maximum size allowed for tasks, causing kernel memory to be mapped into the process' address space. This allowed local attackers to obtain super user privileges. An exploit for this vulnerability is circulating in the wild, and has been used to compromise OpenSource development servers. There is no temporary workaround for this bug. This update also fixes several other security issues in the kernel - race condition with files opened via O_DIRECT which could be exploited to read disk blocks randomly. This could include blocks of previously deleted files with sensitive content. - don't allow users to send signals to kmod - when reading the RTC, don't leak kernel stack data to user space 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, you decide if the paragraph is needed for you or not. Please read through all of the steps down to the end. 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 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 The following options are possible (disregarding the version and build number following the name, separated by the "-" character): k_deflt # default kernel, good for most systems. k_i386 # kernel for older processors and chipsets k_athlon # kernel made specifically for AMD Athlon(tm) family processors k_psmp # kernel for Pentium-I dual processor systems k_smp # kernel for SMP systems (Pentium-II and above) **** Step 2: Download the package for your system Please download the kernel RPM package for your distribution with the name starting as indicated by Step 1. The list of all kernel rpm packages is appended below. Note: The kernel-source package does not contain any binary kernel in bootable form. Instead, it contains the sources that the binary kernel rpm packages are made 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 these locations below ftp://ftp.suse.com/pub/suse/i386/update/. 7.3/kernel/2.4.18-20031204 8.0/kernel/2.4.18-20031204 8.1/rpm/i586 8.2/rpm/i586 9.0/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 applied. If you run SUSE LINUX 8.1 and haven't applied the previous kernel update (SUSE-SA:2003:034), AND use the freeswan package, you also need to update the freeswan rpm as a dependency as offered by YOU (Yast Online Update). The package can be downloaded from ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/ **** Step 4: configuring and creating the initrd The initrd is a ramdisk that is being 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 (set in the files /etc/rc.config up to 7.3) or /etc/sysconfig/kernel (after and including 8.0)) 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 rmadisk (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 have a 7.x system, you must now run the command lilo as root to initialize the lilo bootloader for your system. Then proceed to the next step. If you run a SUSE LINUX 8.x or a SLES8 system, there are two options: Depending on your software configuration, you have 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 applied to 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 are complete, then reboot using the command shutdown -r now or init 6 Your system should now shut down and reboot with the new kernel. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-144.i58… d93394dc68dc342c66554d4b004e8792 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-144.i586.… d23f59681e504eece1ccd4cb582d0d56 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-144.i5… 78b33420df4405715502f9bbb97f1308 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-1… f4b477a1c368ae6dc9a9a6c579313b5e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-1… 38e64b2524825ac4011f53e06366221f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-144.src.… cfd352b5058ed763d264d7ce0b276738 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-144.src.rpm 85d7dfacb641c806c6a3e37dc8c819c7 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-144.src… a2ed9a096c4767d665660514e7e18cd9 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-14… a9b3d40dc79cb2f1179661790a2a58ce SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-101.i58… 9a6363c54735fd3def6398300b091ad1 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-101.i586.… 31d4639f77dc256310d7f9fd28412d04 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-101.i5… c0c7dd94b53400f609009344a6be76a8 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-101.i586… 163057fdee5c93159ba468903974e5b1 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… f02867306164a2069a8e4e6cd7619626 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… 1483d734943e51650f135315cb2e0259 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-101.src.… 2bf8dcedc50ddcb9ebdd78427766da16 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-101.src.rpm 6299ac0c8487037b19d272234994039e ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-101.src… c8bb2a49b6dcdc7377ef42ce5b6dc744 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-101.src.r… 89b682414ea7cd774dfa5a5f26c87cf8 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.Su… 9555f0b00bb9f178fc92ee8242743b42 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-151.i58… bd095d26abf204779048356c12d207c8 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_smp-2.4.21-151.i586.… 89346bae8dc2739ec4f03709deddb5ca ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-151.i5… 3a2054a5638f336b3642a2a2a20158b9 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_psmp-2.4.21-151.i586… a7704a31f56bb3bdeba8a41f86d37e83 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-1… e671a94c8bd50deecaaaddbadbe60c13 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-1… 76bef0adbc84af087505db768d62fc76 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-151.src.… b22f8a756935574f77f86ce3004ccb28 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_smp-2.4.21-151.src.rpm f20eb07a9450769c0f5821e76fa5b3f7 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-151.src… 473e48c3e65b7720663102fc3673c36c ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_psmp-2.4.21-151.src.r… c6fc11acdfe2de62a3000f289f2ac7d4 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kernel-source-2.4.21-15… cf82b7da893aeebc0ab5b399d2ac3788 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_deflt-2.4.18-281.i386.… 074142fcbba96e5f809853251b1db575 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_smp-2.4.18-281.i386.rpm f7729ec9c4f07e237a4cbfa152fb7361 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_psmp-2.4.18-281.i386.r… 1bd2a3b98237d9e28fbac962ad6d8963 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_i386-2.4.18-281.i386.r… f475516c5baf441e14da95032cfff8e8 ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/kernel-source-2.4.18.SuSE-28… d562aade6a5e71121a1e45a561040f8d patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/kernel-source-2.4.18.SuSE-28… 5322ae840e45d57236f966f644205c15 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_deflt-2.4.18-281.src.rpm 441cc1ea08b7a60fd9a97750a332383f ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_smp-2.4.18-281.src.rpm 7eae63f8270182f208498a7e0709e2c7 ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_psmp-2.4.18-281.src.rpm b6dc4ee7bd7bb682e87cace4efe3562a ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_i386-2.4.18-281.src.rpm e16d47d6ed67a2f2b480761b287ac83e ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/kernel-source-2.4.18.SuSE-2… 831d45effd5d0bc74089b49ab1c46fc3 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.18-20031204/k_deflt-… 074142fcbba96e5f809853251b1db575 ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.18-20031204/k_smp-2.… f7729ec9c4f07e237a4cbfa152fb7361 ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.18-20031204/k_psmp-2… 1bd2a3b98237d9e28fbac962ad6d8963 ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.18-20031204/k_i386-2… f475516c5baf441e14da95032cfff8e8 ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.18-20031204/kernel-s… d562aade6a5e71121a1e45a561040f8d Opteron x86_64 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-149… 49833239e39258eb90441d8c724250cd ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-149.x… 1fdab1fb0bd48487404ca8860eba5481 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… c179dfaa4a6d5f7955a0df918eb82ab8 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… e4b45d0fe82735f94477cfbd9dbb124d source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-149.sr… c0fe06d2767b6f55e2065ddecd4f218a ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-149.src.… b86014666e0de02b1903578d6a5bb670 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… 8e7668febd1dda675b516212e1704716 ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - KDE New KDE packages are currently being tested. These packages fixes several vulnerabilities: + remote root compromise (CAN-2003-0690) + weak cookies (CAN-2003-0692) + SSL man-in-the-middle attack + information leak through HTML-referrer (CAN-2003-0459) + wrong file permissions of config files The packages will be release as soon as testing is finished. - mc By using a special combination of links in archive-files it is possible to execute arbitrary commands while mc tries to open it in its VFS. The packages are currently tested and will be release as soon as possible. - apache1/2 The widely used HTTP server apache has several security vulnerabilities: - locally exploitable buffer overflow in the regular expression code. The attacker must be able to modify .htaccess or httpd.conf. (affects: mod_alias and mod_rewrite) - under some circumstances mod_cgid will output its data to the wrong client (affects: apache2) Update packages are available on our FTP servers. - freeradius Two vulnerabilities were found in the FreeRADIUS package. The remote denial-of-service attack bug was fixed and new packages will be released as soon as testing was successfully finished. The other bug is a remote buffer overflow in the module rlm_smb. We do not ship this module and will fix it for future releases. - screen A buffer overflow in screen was reported. Since SuSE Linux 8.0 we do not ship screen with the s-bit anymore. An update package will be released for 7.3 as soon as possible. - mod_gzip The apache module mod_gzip is vulnerable to remote code execution while running in debug-mode. We do not ship this module in debug-mode but future versions will include the fix. - unace The tool unace for handling the archive format ACE is vulnerable to a buffer overflow that can be triggered with long file-names as command line argument. This only affects unace version 2.5. Unfortunately this tool is provided closed source only from the author. Therefore we are unable to check for other bugs or look at the patch. Update packages are available from our FTP servers. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SUSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SUSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de) the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an un-installed rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SUSE in rpm packages for SUSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SUSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SUSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)suse.de> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SUSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- Bye, Thomas - -- Thomas Biege <thomas(a)suse.de>, SUSE LINUX AG, Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 - -- ... stay with me, safe and ignorant, go back to sleep... - Maynard James Keenan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBP89UoXey5gA9JdPZAQGqtQf8DxIEyeugQmIq6jDsep0zTb727Oi2j09R jElfIpAmKA4uNp/w1iWJ74riMnaS3hWubXKNroPMp5/noAlhgMonvQq0acdCmdpd eGMyPz3JyA5Ufjr/E28BhGO8AaXBgTE98ute1m8rdIf7z23B/VRpPqZ/b6FbSQ2S hXLAqbMPvDkm7VQmKXE9Dnh90ysMRkiwXI1OFIOCq0Lzt5vxIkdooXoiwwEcoYGQ mqvMyM4YjXHFreQxD2f9AkBpDsz8mcWmQ81KZwlURwZBtF6uSTmDQdFxzxGX6aml VsM8yO0cbMFj4hADuPq/hMF3eA2isp8PENWTvhRMjcJLMEsc+wXfUg== =sRc/ -----END PGP SIGNATURE-----

6 6

Kernel Update for 7.3
by Sven 'Darkman' Michels 05 Dec '03

05 Dec '03

Hi there, just if someone runs into the same problem: i had k_deflt-2.4.18-262 running on my 7.3 which was a bit buggy about ext3 modules. I had to change the order from "jbd ext3" to "ext3 jbd" to get the kernel running. But after the update, this was fixed and so the box doesn't boot cause of unresolved symbols. I had to change it back and it worked again (also the processnames in netstat -p are back ;-) HTH Sven

1 0

Running lilo after kernel update ?
by Bill.Light＠kp.org 04 Dec '03

04 Dec '03

SuSE 9.0 Professional and YAST2 Just downloaded and installed k_deflt and a "warning" or "informational" message says to: please execute /sbin/lilo after installing the update kernel and prior to rebooting lilo doesn't exist (as I recall the new default is grub?) So what do I do with "grub" to accomplish whatever the warning was for ?? Patches downloaded -- Installed -- Linker automatically runs - Quit back to a command prompt - What next ? Per Olaf's announcement "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." I did NOT issue the "rpm update" (I'm guessing Yast2 did that). Do I have to issue the command or am I at the reboot stage ? The system is remote, so I'b being extra cautious/anal about it....

3 2

[suse-security] Running lilo after kernel update ?
by Bill.Light＠kp.org 04 Dec '03

04 Dec '03

Hi, On Thu, Dec 04, 2003 at 11:59:06AM -0800, Bill.Light(a)kp.org wrote: > please execute /sbin/lilo after installing > the update kernel and prior to rebooting Okay, that should probably have read "... if you use the LILO boot loader". > Per Olaf's announcement "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." Right. grub users don't need to worry about telling the boot loader where to find the kernel image, because grub loads it by going through the file system layer (lilo goes to the block layer directly). > I did NOT issue the "rpm update" (I'm guessing Yast2 did that). Do I > have to issue the command or am I at the reboot stage ? YOU should have installed the kernel for you. You can check with "rpm -q k_deflt" which version is currently installed. Olaf =============================================== Thanks Olaf ! If I didn't do that before I started ..... does a return of: k_deflt-2.4.20-101 tell me anything ? and...to finish the thread...I can now do a "shutdown -r now" and expect to get back in ?? - Bill

1 0

Kernel brk() vulnerability
by webmaster 04 Dec '03

04 Dec '03

Hi, The rpm -qf /boot/vmlinuz gives me the following: k_pentiu-2.2.19-0 k_deflt_22-2.2.19-162 Can the SUSE Security Announcement be applied to it? Antal

2 1

k_smp kernel: brk() patch
by Philippe Vogel 04 Dec '03

04 Dec '03

Hi! My File- & Intranet-Server: Dual PII 350 Asus P2L97-DS 512 MB RAM Promise Ultra100-TX2 256 GB LVM Raid 18 GB SCSI System volume I installed the brk() vulnerability patch via yast and the installation of the patch did not work. Any conclusion? I got several servers with the same hardware and this is my testplatform for the kernelpatch. Philippe

2 2

RE: [suse-security] Secure Backup
by Mario Ohnewald 04 Dec '03

04 Dec '03

hi, > You can use plain ssh and create an unpriviledged user to store the backup > files, > I normally do something like this with ufsdump which obviously won't work > on > suse but tar should be ok as well: > > tar -czf - / | ssh -l <user> <host> 'dd -of=backup.tar.gz' But i would still like to stick to rsync, cause it has the delete and replace feature. So i dont have to tranfser the whole archive each time. > > (check syntax first, out of head and head isn't fully patched at the > moment > + infected with a trojan that is now compromising stomach as well, hate > colleagues so trying bio warfare by working anyway) > > -- > Ronny Martin > > > > -----Original Message----- > > From: Mario Ohnewald [mailto:mario.Ohnewald@gmx.de] > > Sent: Thursday, December 04, 2003 10:32 AM > > To: suse-security(a)suse.com > > Subject: [suse-security] Secure Backup > > > > > > Hello! > > I have two boxes and want to save a backup of each others on it. > > So far i have created a ssh key for both machines so i can > > make a ssh rsync > > to each other. > > But the terrible sideeffect is that IF one of those boxed get > > compromized > > the cracker will be root on both of them!!! > > > > My Backup script: > > #--- START > > --------------------------------------------------------------------- > > #!/bin/sh > > speed=500 > > verzeichnisse="etc home root boot usr/local/bin/" > > > > for verzeichniss in $verzeichnisse > > do > > find /$verzeichniss -size +10200k | rsync -avvz > > --exclude-from=- > > --delete -e "ssh" /$verzeichniss bortal.de:/backup/sts/ > > done > > #--- END > > -------------------------------------------------------------- > > ----------- > > > > > > I need to save it on each other because both have a 100MBit Internet > > connection which makes a restoring backup easy! So a tape > > Backup is not really > > possible. :/ > > > > Any ideas/hints? > > > > -- +++ GMX - die erste Adresse für Mail, Message, More +++ Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net

5 4

Discontinued SuSE Linux Distributions
by Roman Drahtmueller 04 Dec '03

04 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Thu Dec 4 18:00:00 MET 2003 Dear suse-security-announce subscribers and SUSE LINUX users, having provided security-relevant fixes for version 7.3 of our home user product, SuSE Linux, for two years, we would like to inform you that SuSE Linux 7.3 will be discontinued for all architectures. Vulnerabilities found after December 15th 2003 will not be fixed any more for SuSE Linux 7.3. By consequence, the SuSE Linux 7.3 distribution directories on our ftp server ftp.suse.com will be moved to the /pub/suse/discontinued/ directory tree structure; the 7.3 directories in the update trees will follow later in January 2004. The discontinuation of SuSE Linux 7.3 enables us to focus on the SUSE LINUX distributions of a newer release date to ensure that our customers can continuously take advantage of the quality that they are used to with SUSE LINUX products. This announcement holds true for SuSE Linux 7.3 only. As usual, SUSE will continue to provide update packages for the following home users distributions: SuSE Linux 8.0 SuSE Linux 8.1 SuSE Linux 8.2 and SUSE LINUX 9.0 for a two-year period after the release of the respective distribution. Please note that the maintenance cycles of SUSE LINUX Enterprise Server products and products based on the SUSE LINUX Enterprise Server operating system are not affected by this announcement. To learn more about SUSE LINUX business products, please visit http://www.suse.com/us/business/products/. If you have any questions regarding this announcement, please do not hesitate to contact SUSE security at <security(a)suse.de>. Best regards, Roman Drahtmüller, SUSE Security. - -- - - | Roman Drahtmüller <draht(a)suse.de> // "You don't need eyes to see, | SUSE Linux AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBP89qSHey5gA9JdPZAQGaWgf/Rlr3xfb9CMiecN6PkaIBlec1dbzyHRGM b5D6MQy2g9GPbAcRySt24iWI0V8+wbi1Kx08N7FTIMVh7M3lchhyyql/oem/pgqx NwEMsVTGRP6Za218VtYkb3Ih8oAstxIVfYhkm29vYsLKNvdhdvhTnGuMSWEdhtCJ Fk0C7Z/yRU5VwDrbOu/cDwQXObxEkuwHa3iQn/+RWqZZyBnvVzAxzYS6PZflkB+X jNvO/8aoFN1IntQFaMRn4mabRhIyVZjpRQ6Ob6oEC0pB8ybU/psaY+yP4Gxr3f41 3SOPpwJgeZRi/5XWTjecwelPgQ3xr4DtjilKNwY0NfROw/bJsmlbDg== =tp8J -----END PGP SIGNATURE-----

1 0