December 2004 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] Where to Deploy Trend Micro viruswall?
by Invalid Addr3ss 05 Dec '04

05 Dec '04

I'm not really familiar with a DMZ setup. My (SOHO) network is mainly straight forwarded. > > > > Internet | > > | | > > | | > > Cable Modem | > > | | > > | | > > Firewall/Router | | | | | Viruswall v I'll look into it. Thanks for a response Daniel Invalid Addr3ss

1 0

SUSE Security Announcement: various kernel problems (SUSE-SA:2004:042)
by Marcus Meissner 05 Dec '04

05 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2004:042 Date: Wednesday, Dec 1st 2004 15:00 MEST Affected products: 8.1, 8.2, 9.0, 9.1, 9.2 SUSE Linux Enterprise Server 8, 9 SUSE LINUX Desktop 1.0 Novell Linux Desktop 9 Vulnerability Type: local and remote denial of service Severity (1-10): 7 SUSE default package: yes Cross References: CAN-2004-0883 CAN-2004-0949 CAN-2004-1070 CAN-2004-1071 CAN-2004-1072 CAN-2004-1073 CAN-2004-1074 Content of this advisory: 1) security vulnerability resolved: - kernel remote and local denial of service problems problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - see SUSE Security Summary Report 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion The Linux kernel is the base of the SUSE Linux system. Several security problems have been found and addressed by the SUSE Security Team. The following issues are present in all SUSE Linux based products. - Several remote denial of service conditions have been found in the smbfs file system, reported by Stefan Esser. The vulnerability could be used by a hostile SMB server (or an attacker injecting packets into the network) to crash the clients kernel. These issues have been assigned the Mitre CVE IDs CAN-2004-0883 and CAN-2004-0949. We thank Stefan Esser for reporting this issue and providing patches. - Paul Starzetz of isec.pl found several missing boundary checks in the ELF loader routines of the Linux kernel which could potentially lead a local attacker to gain root privileges by using handmade ELF binaries. These issues have been assigned the Mitre CVE IDs CAN-2004-1070,CAN-2004-1071,CAN-2004-1072, and CAN-2004-1073. We thank Paul for reporting this issue and Chris Wright for providing a patch to fix the issue. - Handcrafted a.out binaries could be used to trigger a local denial of service condition in both 2.4 and 2.6 Linux kernels, allowing a local attacker to render the system unusable. Fixes for this problem were done by Chris Wright. This issue has been assigned the Mitre CVE ID CAN-2004-1074. We wish to thank Chris for providing patches. - SUSE Linux 9.1 and SUSE Linux Enterprise Server 9 now contain stricter checks what commands you can send to read-only opened CD devices. This way local attackers only having read access to the device will not be able to destroy the firmware of SCSI related devices. This update will break the k3b and the dvd+rw-tools packages. We have released fixed versions of those packages. - The SUSE Linux 8.1, 8.2, and 9.0 and the SUSE Linux Desktop 1.0 kernel were missing the kNFSD remote denial of service fix. The respective fixes are now in the released kernels. Also, the following critical bugs were fixed by this update: - A very small race condition on SMP systems with more than 4GB of memory that could expose foreign memory pages was found and fixed by Andrea Arcangeli of SUSE. - On SUSE Linux Enterprise Server 9 a memory corruption in the NFS readdirplus command could lead to kernel crashes and potentially corruption of data on disk. This problem was fixed. - On SUSE Linux 9.2 the "dazuko" kernel module of the "antivir" RPM package caused problems with programs using Linux capabilities. The module was fixed. - A security fix for buffer overflows in the decnet protocol driver was incorrect and caused kernel crashes. 2) solution/workaround There is no workaround, please install the fixed kernels. 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) k_deflt # default kernel, good for most systems. k_i386 # kernel for older processors and chip sets 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) k_smp4G # kernel for SMP systems which supports a maximum of 4G of RAM 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/. 8.1/rpm/i586 8.2/rpm/i586 9.0/rpm/i586 9.1/rpm/i586 9.2/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. If you run SUSE LINUX 8.1 and haven't applied the kernel update (SUSE-SA:2003:034), AND you are using 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 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. <pkg_sum output> ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: Please see our weekly summary report. ______________________________________________________________________________ 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.7 (GNU/Linux) mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBiEYEExECAAYFAkGJG+YACgkQGsiRhDTRlzm8CQCg14Wz vg6j45e/r1oyt9EaHhleSacAnA+2dArk1I3xt49Z5rdnhqheF//9mQGiBDnu9IER BACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff4JctBsgs47tj miI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0dM+HFrruCgBlW t6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcOQliHu8jwRQHx lRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifr ZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBED3+D2t1V/f8l 0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1 krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoEmyW/xC1sBbDk DUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25p bmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkDwmcABAsKAwQD FQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6dNfnwI2PAsgCg jH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzO AKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUD BRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4 fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklL snr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMn snT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/ xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmp U661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0EExECAB0FAjxq qTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1fAJ9dR7saz2KP NwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0EOe70khAIAISR 0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/HZnh3TwhBIw1 FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44ht5h+6HMBzoFC MAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPTtGzcAi2jVl9h l3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM523AMgpPQtsK m9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q2Y+GqZ+yAvNW jRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8QnSs0wwPg3xE ullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWawJxRLKH6Zjo/F aKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ1sj2xYdB1xO0 ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCHORrNjq9pYWlr xsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1wwylxadmmJaJ HzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQYEQIADAUCOe70 kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol0JdGwACeKTtt geVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAKCRCoTtronIAK yofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3coSPihn1+OBNw= =Fv2n - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQa3U5Hey5gA9JdPZAQHRogf/aLEnzor/MQjqt25dph3NrD/sx8urYcVO It5IT8z5a/k5WKNyp5TO/s6fc32J1aUbYBaNFEA0h1WFkCZ7kFrL0IXBD4pPrm0i Hy/BXnXbppGYRcHlGs4IKEUZ1BWEX8KjTLRTTc2YJ7B/jP+/EZVLFuRSWvS2P9wx 4urGsMC+1gidqtqgBOr5tWeq9vekDfytM/7sGs2guE9T169L63X7IK5DZxpTdAOB q/slCF6HrpHRT+lh5VKZWaZGpEXlZboe6q+hOxbL0VrkmdACHjhj1xNSJBhNih9v DqDzSnMEfh4kFnbW9fq2if5QaLNVG9BBdd1tTqZPxaIQbeR/OW2DmQ== =96+c -----END PGP SIGNATURE-----

4 6

Re: [suse-security] Boot failure after Kernel update
by m3047＠inwa.net 05 Dec '04

05 Dec '04

I don't don't know if this is, properly speaking, security-related... At 9:36 PM 12/4/04, Stefan Proels wrote: >On Saturday 04 December 2004 17:51, Günther J. Niederwimmer wrote: >> Hello, >> >> > The working 9.0 machine is basically identically configured as the >> > failing one but[...] >> >> have you run lilo ?? > >No, I'm using grub. > I had a situation a month or two ago where two SuSE 9.0 Pro boxes, virtually identical hardware, far different configurations, had kernel updates applied and one of them failed to boot. The one which failed to boot had a manually selected and extremely minimal (minimal enough to get X running with some basic filesystem and network management apps running, but other than that, minimal) install. I found that either the (grub) menu.lst file had been edited, or else that the unneeded initrd file (present on the other system) had been deleted. I booted from an emergency CD ROM and deleted the reference to the now-missing file, and all is good. There was a message from grub which should have been more of a tipoff than it was in the heat of the moment; I don't recall what it was off the top of my head and I am nowhere near the particular machines in question at the moment. I sent feedback to SuSE about it, but never received a response. -- Fred Morris fredm3047(a)inwa.net (I-ACK on subject line to reply)

2 1

Re: [suse-security] Boot failure after Kernel update
by Bill.Light＠kp.org 05 Dec '04

05 Dec '04

I don't don't know if this is, properly speaking, security-related... At 9:36 PM 12/4/04, Stefan Proels wrote: >On Saturday 04 December 2004 17:51, Günther J. Niederwimmer wrote: >> Hello, >> >> > The working 9.0 machine is basically identically configured as the >> > failing one but[...] >> >> have you run lilo ?? > >No, I'm using grub. > I had a situation a month or two ago where two SuSE 9.0 Pro boxes, virtually identical hardware, far different configurations, had kernel updates applied and one of them failed to boot. The one which failed to boot had a manually selected and extremely minimal (minimal enough to get X running with some basic filesystem and network management apps running, but other than that, minimal) install. I found that either the (grub) menu.lst file had been edited, or else that the unneeded initrd file (present on the other system) had been deleted. I booted from an emergency CD ROM and deleted the reference to the now-missing file, and all is good. There was a message from grub which should have been more of a tipoff than it was in the heat of the moment; I don't recall what it was off the top of my head and I am nowhere near the particular machines in question at the moment. I sent feedback to SuSE about it, but never received a response. -- Fred Morris fredm3047(a)inwa.net (I-ACK on subject line to reply) ============================================================================== To my knowledge - nothing has been done. you will find that if you "roll your own" kernel, you can apply the source update - but if you have an Adaptec controller, you will get a kernel panic and failure to re-boot. It was a recommended SuSE security update - so I would think that it IS security related ... you won't be able to boot your box afterward...How's that for secure. Apparently Adaptec isn't considered mainstream by SuSE any longer.

1 0

nessus scanner
by ray_carlino＠comcast.net 04 Dec '04

04 Dec '04

We just switched over to Suse and installed 9.2 on several servers but the serves get scnned with a nessis scanner be fore we can get firewall ports open. The problem is I can't find a way to match up the security alearts to patches in Suse. I have a problem with apache right now and they won't open th eport. Question is Is there a addon to nessus or a file that I can send to tell nessus that the current version has been patched so it will look at the sub version numbers. Ray

1 0

SUSE Security Announcement: cyrus-imapd (SUSE-SA:2004:043)
by Thomas Biege 03 Dec '04

03 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: cyrus-imapd Announcement-ID: SUSE-SA:2004:043 Date: Friday, Dec 3rd 2004 13:00 MEST Affected products: 8.1, 8.2, 9.0, 9.1, 9.2 SUSE Linux Enterprise Server 8, 9 SuSE-Linux-Standard-Server 8 SuSE Linux Openexchange Server 4 Vulnerability Type: remote command execution Severity (1-10): 5 SUSE default package: No Cross References: CAN-2004-1011 CAN-2004-1012 CAN-2004-1013 Content of this advisory: 1) security vulnerability resolved: - buffer overflow and out of bounds access in cyrus imapd problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - suidperl - putty 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Stefan Esser reported various bugs within the Cyrus IMAP Server. These include buffer overflows and out-of-bounds memory access which could allow remote attackers to execute arbitrary commands as root. The bugs occur in the pre-authentication phase, therefore an update is strongly recommended. 2) solution/workaround There is no temporary workaround except shutting down the IMAP server. 3) special instructions and notes After successfully updating the cyrus-imapd package you have to issue the following command as root: /sbin/rccyrus restart 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. Our maintenance customers are being notified individually. The packages are being offered for installation from the maintenance web. x86 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/cyrus-imapd-2.2.8-6.3.… 563c7c359df3e4572c27bccd1c4962eb patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/cyrus-imapd-2.2.8-6.3.… ceee2a62831855a563c56a0d7be12a6d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/cyrus-imapd-2.2.8-6.3.s… c24904edebe628e9dab9b805af56359a SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/cyrus-imapd-2.2.3-83.1… 53af4c594493abca71bd2789c6599019 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/cyrus-imapd-2.2.3-83.1… 2c596ce65de5d13c0ca14459e0462bd9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/cyrus-imapd-2.2.3-83.19… 015268204791fc27c128705b1a22ca37 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/cyrus-imapd-2.1.15-89.… ed3c4bc9178eea7ad5a8a406d53a230d patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/cyrus-imapd-2.1.15-89.… b1ddc189663da719ec5d55ea186b795b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/cyrus-imapd-2.1.15-89.s… 6692959f014ed63d0c83ca02632e456b SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cyrus-imapd-2.1.12-75.… 09223533665db543be3e85b53b89b50a patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cyrus-imapd-2.1.12-75.… c4606d6b48577af54486c40fb35a31b9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/cyrus-imapd-2.1.12-75.s… beb341ef93888c1f1e3f6e6532109b0d SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cyrus-imapd-2.1.16-56.… 2d5c5cc7de173ff8153544166a19533c patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cyrus-imapd-2.1.16-56.… 8d1cc9bea8f323c15b982dfc43df7b6c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/cyrus-imapd-2.1.16-56.s… bd1e20bd42974bbe9f8e3aee826a4444 x86-64 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/cyrus-imapd-2.2.8-… 57bd598694d82f7f52af34659773d890 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/cyrus-imapd-2.2.8-… 9702a0541440af888aead910120085af source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/cyrus-imapd-2.2.8-6.3… c24904edebe628e9dab9b805af56359a SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/cyrus-imapd-2.2.3-… d279dd8620493482cba6b4706ea6124d patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/cyrus-imapd-2.2.3-… 33184f8fb2dfeb4f27fe506ee204ee82 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/cyrus-imapd-2.2.3-83.… 742352f41f57c4b3221e0672e31f865f SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/cyrus-imapd-2.1.15… d9e387c4161fdeef2680508d17df159a patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/cyrus-imapd-2.1.15… 4411a55662c6567ba48055c72d9ebd1d source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/cyrus-imapd-2.1.15-89… 42cc2346b342320e77be923ee12c5678 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - suidperl SUSE LINUX 9.2 follows the new upstream policy to install /usr/bin/suidperl as hardlink to /usr/bin/perl. In previous perl versions it used to be a hardlink to /usr/bin/sperl*. Therefore one must not set a setuid bit on /usr/bin/suidperl as suggested in the RPM package description of perl. Set the bit on /usr/bin/sperl5.8.5 instead if you really need the suid feature. Also check your /etc/permissions.local file for references of /usr/bin/suidperl if you where upgrading from previous SUSE LINUX releases. SUSE Linux is not affected by this problem in the default installation, only if the administrator added the s-bit to suidperl. - putty The SUSE LINUX distribution comes with putty a Windows-based SSH and Telnet client. This client is vulnerable to a buffer overflow that can be exploited by a malicious SSH server to execute arbitrary code remotely. Putty is just included on the CDs/DVDs and is not installed on the Linux system. Upcoming distributions will have this vulnerability fixed. ______________________________________________________________________________ 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.7 (GNU/Linux) mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBiEYEExECAAYFAkGJG+YACgkQGsiRhDTRlzm8CQCg14Wz vg6j45e/r1oyt9EaHhleSacAnA+2dArk1I3xt49Z5rdnhqheF//9mQGiBDnu9IER BACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff4JctBsgs47tj miI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0dM+HFrruCgBlW t6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcOQliHu8jwRQHx lRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifr ZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBED3+D2t1V/f8l 0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1 krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoEmyW/xC1sBbDk DUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25p bmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkDwmcABAsKAwQD FQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6dNfnwI2PAsgCg jH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzO AKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUD BRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4 fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklL snr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMn snT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/ xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmp U661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0EExECAB0FAjxq qTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1fAJ9dR7saz2KP NwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0EOe70khAIAISR 0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/HZnh3TwhBIw1 FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44ht5h+6HMBzoFC MAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPTtGzcAi2jVl9h l3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM523AMgpPQtsK m9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q2Y+GqZ+yAvNW jRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8QnSs0wwPg3xE ullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWawJxRLKH6Zjo/F aKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ1sj2xYdB1xO0 ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCHORrNjq9pYWlr xsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1wwylxadmmJaJ HzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQYEQIADAUCOe70 kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol0JdGwACeKTtt geVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAKCRCoTtronIAK yofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3coSPihn1+OBNw= =Fv2n - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iQEVAwUBQbBrN3ey5gA9JdPZAQFECQf/VVvQEDyF52vdsYfu17Aj5Ymbpj5rs/lj g5tt6UTTeVFYpoCoEPMQbYbGNgci8FHjybQszgEN/EertnlY2LHD8wptyDsAW0o8 X8ThSsl154763rayxyBFOcip3SW+RcvyfeZ81I3a3/nHks5lz8qlgiZYRi07Thya LsJGzy1X8WP5ZdE2wDM1SJZjPAgm7jJnXj4Gz5DYdvX0cV/LK+2SAITKOC2FsoCT uU9/zhH3dietmmVGqkvNVCZKyTgDWDlOmMUUdyrocIZT12sSzYqG5MKN60bA3fTk i/nBLKw4BbsottzXIzvpyh8Twe3QZ2jlUHN/vOKxdvvchOflucMePQ== =nB+R -----END PGP SIGNATURE-----

1 0

Problem with ipsec routing, kernel 2.6 and susefirewall
by ONAY, Gabriel 03 Dec '04

03 Dec '04

Dear all I have a problem with my ipsec-connection. It works only in a direction Configuration: GW-Left: Suse 9.2 (kernel 2.6.8-24.3-default)) Openswan 2.2.0 Susefirewall 3.2 GW-Right: Suse 7.3 (kernel 2.4-18) freeswan 1.98b Susefirewall PC-Left/Right Windows XP SP1 |PC-Left|---|GW-Left|--<Router>---|GW-Right|---|PC-Right| 10.0.0.116 83.0.0.51 83.0.0.52 10.0.0.231 The ipsec tunnel established and key-exchange seems to work, but a ping from PC-Left to PC-Right don't works. A ping from PC-Right to PC-Left works fine. The Ping from PC-Left to PC-Right shows following messages in /var/log/message: Dec 2 17:35:52 FWTest kernel: SFW2-FWDint-ACC-PING IN=eth1 OUT=eth0 SRC=10.0.0.116 DST=10.0.0.231 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=2517 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=36864 Dec 2 17:35:57 FWTest kernel: SFW2-FWDint-ACC-PING IN=eth1 OUT=eth0 SRC=10.0.0.116 DST=10.0.0.231 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=2519 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=37120 Dec 2 17:36:03 FWTest kernel: SFW2-FWDint-ACC-PING IN=eth1 OUT=eth0 SRC=10.0.0.116 DST=10.0.0.231 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=2521 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=37376 There i can see, the ping packets arrive the firewall not encrypted. The Ping from PC-Right to PC-Left shows following: Dec 2 17:45:53 FWTest kernel: SFW2-INext-ACC-IP IN=eth0 OUT= MAC=00:04:75:97:79:19:00:50:04:31:22:cf:08:00 SRC=83.0.0.52 DST=83.0.0.51 LEN=112 TOS=0x00 PREC=0x00 TTL=64 ID=32706 PROTO=ESP SPI=0x6ffc8a25 Dec 2 17:45:53 FWTest kernel: SFW2-FWDext-ACC-FORW IN=eth0 OUT=eth1 SRC=10.0.0.231 DST=10.0.0.116 LEN=60 TOS=0x00 PREC=0x00 TTL=126 ID=5381 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=35585 Dec 2 17:45:53 FWTest kernel: SFW2-FWDint-FWD-RELA IN=eth1 OUT=eth0 SRC=10.0.0.116 DST=10.0.0.231 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=2734 PROTO=ICMP TYPE=0 CODE=0 ID=512 SEQ=35585 Dec 2 17:45:54 FWTest kernel: SFW2-INext-ACC-IP IN=eth0 OUT= MAC=00:04:75:97:79:19:00:50:04:31:22:cf:08:00 SRC=83.0.0.52 DST=83.0.0.51 LEN=112 TOS=0x00 PREC=0x00 TTL=64 ID=32707 PROTO=ESP SPI=0x6ffc8a25 Dec 2 17:45:54 FWTest kernel: SFW2-FWDext-ACC-FORW IN=eth0 OUT=eth1 SRC=10.0.0.231 DST=10.0.0.116 LEN=60 TOS=0x00 PREC=0x00 TTL=126 ID=5383 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=35841 There i see, ipsec data is encrypted. My ipsec.conf of GW-Left plutodebug=none # Certificate Revocation List handling #crlcheckinterval=600 #strictcrlpolicy=yes # Change rp_filter setting, default = 0 (switch off) rp_filter=%unchanged # Switch on NAT-Traversal (if patch is installed) nat_traversal=yes interfaces=%defaultroute #forwardcontrol=yes # default settings for connections conn %default # Default: %forever (try forever) #keyingtries=3 # Sig keys (default: %dnsondemand) #leftrsasigkey=%cert #rightrsasigkey=%cert # Lifetimes, defaults are 1h/8hrs #ikelifetime=20m #keylife=1h #rekeymargin=8m left=%defaultroute compress=no # Add connections here # sample VPN connection conn kbs-test type=tunnel auth=esp # Left security gateway, subnet behind it, next hop toward right. left=83.0.0.51 leftsubnet=10.0.0.64/26 leftnexthop=83.0.0.49 # Right security gateway, subnet behind it, next hop toward left. right=83.0.0.52 rightsubnet=10.0.0.192/26 rightnexthop=83.0.0.49 # To authorize this connection, but not actually start it, at startup, # uncomment this. auto=start authby=secret #Disable Opportunistic Encryption include /etc/ipsec.d/examples/no_oe.conf Any ideas about that? Greetings, Gabriel

1 0

Routing IPSec through SuSEFirewall2
by Oliver Stettner 02 Dec '04

02 Dec '04

Hello, I have the following configuration: Internet-Connection | | eth0 (official IP) Linux-Server eth1 (private IP) | | Home LAN with private IPs On the Linux-Server the SuSEFirewall2 is activated. It does Masquerading and protects my Linux-Server and my internal LAN. Now I want to connect a Notebook with a IPSec VPN-Client to my Home LAN, since I have to connect to an Office LAN's VPN-Server over the Internet. I don't need IPSec on the Linux-Server itself, I just want to route the IPSec Traffic through the Linux-Server. I was told, the IPSec-Client on the Notebook works with Masquerading. Is there anything special I have to configure in /etc/sysconfig/SuSEFirewall2? My first tests dind't succeed. If necessary I can post my /etc/sysconfig/SuSEFirewall2 here. Thank You and Regards, Oliver.

2 2

RE: [suse-security] lpd kills xdm and other useful processes + network failure on boot
by Theytaz Antoine 02 Dec '04

02 Dec '04

yes reboot is not necessary, only for kernel had once a strange problems like processes dying (oracle/xdm/...) and I could never explain why... I was patching my system for one year or more without ever rebooting (suse 8.0 pro security updates). Don't know if it is related and now I don't have any problem. Antoine -----Message d'origine----- De : Mike Rose [mailto:mr349@cam.ac.uk] Envoyé : jeudi 2 décembre 2004 15:41 À : Theytaz Antoine Cc : suse-security(a)suse.com Objet : RE: [suse-security] lpd kills xdm and other useful processes + network failure on boot Nope. There was a kernel patch within the last month so computers had to be rebooted for that. I've just applied the latest kernel patch so another round of reboots should be due. curious: why do you ask, as Linux should not require a reboot for sofware changes to take effect unless they are somewhat kernel related, no? Mike Rose On Thu, 2 Dec 2004, Theytaz Antoine wrote: > just curious : did you update SuSE packages with patch rpm's for a long time without rebooting these workstations ? > > -----Message d'origine----- > De : Mike Rose [mailto:mr349@cam.ac.uk] Envoyé : jeudi 2 décembre 2004 > 14:51 À : suse-security(a)suse.com Objet : [suse-security] lpd kills xdm > and other useful processes + network failure on boot > > Hi, > > I know both of these things are slighly off topic, but I have heard nothing from Suse about the network failure on boot, and I am wondering if anyone else has hit the lpd problem: > > > We just replaced /etc/printcap (trivial change) on a bunch of Suse9.1 workstations, restarted lpd (we are using the Suse provided lprng) and about half of the workstations were left in a bizarre state where printing via lpd left all the print jobs on the local computer and did not send them on, so to speak. > > Hmm, OK let's try and restart lpd on a computer that has this lpd problem: > /etc/init.d/lpd restart > results in xdm being killed along with a few other rather critical processes. This action logs me off the computer (as root) and the person who "was" using the console. Only a reboot will suffice. > > Most of the computers seem to have been fixable using: > killall -KILL lpd; /etc/init.d/lpd start > > http://www.lprng.com/ > thinks that: > (For LPRng-3.8.28) > is the latest version, whereas > lprng-3.8.25-37 > is what Suse provide in 9.1 > > between 3.8.25 and 3.8.28 there is a fix for a memory leak..... > > Also our process accouting logs seem to show lpd getting into a state where it is creating a new process every 10 seconds. > > > > > Approximately 1 out of 30 boots of Suse 9.1 result the network service not starting during boot. After the boot it is always possible to start it ( /etc/init.d.network start) successfully, but not much use with other services relying upon it. Another boot of the same computer and everything is always fine, so no repeatiblity to speak of - yuk. > > Anyone else seen this? > > > > > Mike Rose > > -- > 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] lpd kills xdm and other useful processes + network failure on boot
by Theytaz Antoine 02 Dec '04

02 Dec '04

just curious : did you update SuSE packages with patch rpm's for a long time without rebooting these workstations ? -----Message d'origine----- De : Mike Rose [mailto:mr349@cam.ac.uk] Envoyé : jeudi 2 décembre 2004 14:51 À : suse-security(a)suse.com Objet : [suse-security] lpd kills xdm and other useful processes + network failure on boot Hi, I know both of these things are slighly off topic, but I have heard nothing from Suse about the network failure on boot, and I am wondering if anyone else has hit the lpd problem: We just replaced /etc/printcap (trivial change) on a bunch of Suse9.1 workstations, restarted lpd (we are using the Suse provided lprng) and about half of the workstations were left in a bizarre state where printing via lpd left all the print jobs on the local computer and did not send them on, so to speak. Hmm, OK let's try and restart lpd on a computer that has this lpd problem: /etc/init.d/lpd restart results in xdm being killed along with a few other rather critical processes. This action logs me off the computer (as root) and the person who "was" using the console. Only a reboot will suffice. Most of the computers seem to have been fixable using: killall -KILL lpd; /etc/init.d/lpd start http://www.lprng.com/ thinks that: (For LPRng-3.8.28) is the latest version, whereas lprng-3.8.25-37 is what Suse provide in 9.1 between 3.8.25 and 3.8.28 there is a fix for a memory leak..... Also our process accouting logs seem to show lpd getting into a state where it is creating a new process every 10 seconds. Approximately 1 out of 30 boots of Suse 9.1 result the network service not starting during boot. After the boot it is always possible to start it ( /etc/init.d.network start) successfully, but not much use with other services relying upon it. Another boot of the same computer and everything is always fine, so no repeatiblity to speak of - yuk. Anyone else seen this? Mike Rose -- 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

lpd kills xdm and other useful processes + network failure on boot
by Mike Rose 02 Dec '04

02 Dec '04

Hi, I know both of these things are slighly off topic, but I have heard nothing from Suse about the network failure on boot, and I am wondering if anyone else has hit the lpd problem: We just replaced /etc/printcap (trivial change) on a bunch of Suse9.1 workstations, restarted lpd (we are using the Suse provided lprng) and about half of the workstations were left in a bizarre state where printing via lpd left all the print jobs on the local computer and did not send them on, so to speak. Hmm, OK let's try and restart lpd on a computer that has this lpd problem: /etc/init.d/lpd restart results in xdm being killed along with a few other rather critical processes. This action logs me off the computer (as root) and the person who "was" using the console. Only a reboot will suffice. Most of the computers seem to have been fixable using: killall -KILL lpd; /etc/init.d/lpd start http://www.lprng.com/ thinks that: (For LPRng-3.8.28) is the latest version, whereas lprng-3.8.25-37 is what Suse provide in 9.1 between 3.8.25 and 3.8.28 there is a fix for a memory leak..... Also our process accouting logs seem to show lpd getting into a state where it is creating a new process every 10 seconds. Approximately 1 out of 30 boots of Suse 9.1 result the network service not starting during boot. After the boot it is always possible to start it ( /etc/init.d.network start) successfully, but not much use with other services relying upon it. Another boot of the same computer and everything is always fine, so no repeatiblity to speak of - yuk. Anyone else seen this? Mike Rose

1 0

ssh-Attack?
by Kai Pfeiffer 02 Dec '04

02 Dec '04

Hello list, in my logs I found the appended entries. My question is, what is the intention of this guy. I don't understand, why he uses a few loginnames many times and others only one time. There is no account on my box which matches to one of the tested loginnames. Another thing. I get this userlist (exactly the same names in the same order) from many different IPs. Any hints? regards Kai Pfeiffer Dec 1 11:02:54 mybox sshd[14251]: Illegal user patrick from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:55 mybox sshd[14253]: Illegal user patrick from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:55 mybox sshd[14265]: Illegal user rolo from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:56 mybox sshd[14267]: Illegal user iceuser from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:56 mybox sshd[14269]: Illegal user horde from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:56 mybox sshd[14271]: Illegal user cyrus from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:56 mybox sshd[14273]: Illegal user www from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:56 mybox sshd[14277]: Illegal user matt from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14279]: Illegal user test from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14281]: Illegal user test from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14283]: Illegal user test from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14285]: Illegal user test from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14287]: Illegal user www-data from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14291]: Illegal user operator from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:57 mybox sshd[14293]: Illegal user adm from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:58 mybox sshd[14295]: Illegal user apache from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:58 mybox sshd[14297]: Illegal user irc from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:58 mybox sshd[14299]: Illegal user irc from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:58 mybox sshd[14301]: Illegal user adm from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:58 mybox sshd[14309]: Illegal user jane from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:58 mybox sshd[14311]: Illegal user pamela from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:02:59 mybox sshd[14323]: Illegal user cosmin from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:04 mybox sshd[14397]: Illegal user cip52 from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:04 mybox sshd[14399]: Illegal user cip51 from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:05 mybox sshd[14403]: Illegal user noc from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:05 mybox sshd[14413]: Illegal user webmaster from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:05 mybox sshd[14415]: Illegal user data from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14417]: Illegal user user from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14419]: Illegal user user from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14421]: Illegal user user from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14423]: Illegal user web from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14425]: Illegal user web from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14427]: Illegal user oracle from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14429]: Illegal user sybase from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:06 mybox sshd[14431]: Illegal user master from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:07 mybox sshd[14433]: Illegal user account from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:07 mybox sshd[14435]: Illegal user backup from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:07 mybox sshd[14437]: Illegal user server from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:07 mybox sshd[14439]: Illegal user adam from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:07 mybox sshd[14441]: Illegal user alan from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:07 mybox sshd[14443]: Illegal user frank from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:08 mybox sshd[14445]: Illegal user george from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:08 mybox sshd[14447]: Illegal user henry from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:08 mybox sshd[14449]: Illegal user john from ::ffff:xxx.xxx.xxx.xxx Dec 1 11:03:09 mybox sshd[14461]: Illegal user test from ::ffff:xxx.xxx.xxx.xxx

5 4

intruder in home system 8.2 prof
by Martin 02 Dec '04

02 Dec '04

Recently I notice a large increase in spam related to recent transactions I've made. I ordered pharmaceuticals on line and now get increased spam from thos type of business. I inquired about credit card fraud and get spam. Could this mean there is some kind of binary running in my system which sends information about my activities. I've heard about something called spyware. I believe my system has some kind of suse 8.2 supplied software firewall but don't know where or how to configure it. How would I find and remove any such unwanted intruder?

6 6

Problem with ipsec routing
by ONAY, Gabriel 01 Dec '04

01 Dec '04

Dear all I have a vpn connection that only works in a direction. Configuration: GW-Left: Suse 9.2 (kernel 2.6.8-24.3-default)) Openswan 2.2.0 Susefirewall 3.2 GW-Right: Suse 7.3 (kernel 2.4-18) freeswan 1.98b Susefirewall PC-Left/Right Windows XP SP1 | PC-Left |------------| GW-Left |--------------<Router>-------------| GW-Right |------------| PC-Right | ISAKMP SA is established, also key-exchange seems to work. A ping from PC-Right to PC-Left works fine, put a ping from PC-Left to PC-Right works not. ipsec.conf plutodebug=none # Certificate Revocation List handling #crlcheckinterval=600 #strictcrlpolicy=yes # Change rp_filter setting, default = 0 (switch off) rp_filter=%unchanged # Switch on NAT-Traversal (if patch is installed) nat_traversal=yes interfaces=%defaultroute #forwardcontrol=yes # default settings for connections conn %default # Default: %forever (try forever) #keyingtries=3 # Sig keys (default: %dnsondemand) #leftrsasigkey=%cert #rightrsasigkey=%cert # Lifetimes, defaults are 1h/8hrs #ikelifetime=20m #keylife=1h #rekeymargin=8m left=%defaultroute compress=no # Add connections here # sample VPN connection conn kbs-test type=tunnel auth=esp # Left security gateway, subnet behind it, next hop toward right. left=83.0.0.51 leftsubnet=10.0.0.64/26 leftnexthop=83.0.0.49 # Right security gateway, subnet behind it, next hop toward left. right=83.0.0.52 rightsubnet=10.0.0.192/26 rightnexthop=83.0.0.49 # To authorize this connection, but not actually start it, at startup, # uncomment this. auto=start authby=secret #Disable Opportunistic Encryption include /etc/ipsec.d/examples/no_oe.conf Any ideas about that? Greetings, Gabriel

1 0