January 2005 - openSUSE Security - openSUSE Mailing Lists

SUSE Security Announcement: kernel local privilege escalation (SUSE-SA:2005:003)
by Marcus Meissner 16 Feb '05

16 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2005:003 Date: Friday, Jan 21st 2005 16:00 MET 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 privilege escalation Severity (1-10): 7 SUSE default package: yes Cross References: CAN-2004-1235 CAN-2005-0001 Content of this advisory: 1) security vulnerability resolved: - local privilege escalation - local denial of service attacks problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - see summary report 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Several exploitable security problems were identified and fixed in the Linux kernel, the core of every SUSE Linux product. - Due to missing locking in the sys_uselib system call a local attacker can gain root access. This was found by Paul Starzetz and is tracked by the Mitre CVE ID CAN-2004-1235. - Paul Starzetz also found a race condition in SMP page table handling which could lead to a local attacker gaining root access on SMP machines. This is tracked by the Mitre CVE ID CAN-2005-0001. - A local denial of service was found in the auditing subsystem which have lead a local attacker crashing the machine. This was reported and fixed by Redhat. - The sendmsg / cmsg fix from the previous kernel update was faulty on 64bit systems with 32bit compatibility layer and could lead to 32bit applications not working correctly on those 64bit systems. - The smbfs security fixes from a before-previous kernel update were faulty for some file write cases. - A local denial of service with Direct I/O access to NFS file systems could lead a local attacker to crash a machine with NFS mounts. - grsecurity reported a signed integer problem in the SCSI ioctl handling which had a missing boundary check. Due to C language specifics, this evaluation was not correct and there actually is no problem in this code. The signed / unsigned mismatch was fixed nevertheless. - Several more small non security problems were fixed. NOTE: Two days ago we released the Service Pack 1 for the SUSE Linux Enterprise Server 9. This kernel update contains fixes for the SUSE Linux Enterprise Server 9 GA version kernel line. A fix for the Service Pack 1 version line will be available shortly. 2) solution/workaround There is no workaround. Please install the provided update packages. 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. x86 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-source-2.6.8-24… e335f4e401034f79bce9bcef3b6c19e0 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-bigsmp-2.6.8-24… 848b85f02abd3d2877b04f10aa875689 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-smp-2.6.8-24.11… f103cd395e9d6e4418cb8cf91c09147d ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-default-2.6.8-2… 374dc207a2b3e81e04cdad2e3d6c0333 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-um-2.6.8-24.11.… 379085daf7dc1e1df0ce5c246c26caf4 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-source-2.6.8-24.… bbfdc289c2d1f1a73ac6fa759ecfaf87 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-bigsmp-2.6.8-24.… c999bd4ff601c34edc6322fc43caf1a5 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-smp-2.6.8-24.11.… 9539d6093144fbbd066681f61c9aa07d ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-default-2.6.8-24… eeeebf4ea4942f6093b56f7a3d7a7de3 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-um-2.6.8-24.11.n… 93953b908c54f19d4d30816b4eae2dc9 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-source-2.6.5-7.… b84574947de5c47a2bcca43525e1fc4d ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-bigsmp-2.6.5-7.… 5346f03accd80530ef1dd870a069dc11 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-smp-2.6.5-7.111… dba08e4e49dbf1f32988152956448ab3 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-default-2.6.5-7… 231eb3350db6a02b621731790f3b6d37 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-source-2.6.5-7.1… 8cd984fa2f4607ff75b0ff79a82090e0 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-bigsmp-2.6.5-7.1… a64279aae3382a1647f594e59ea321fe ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-smp-2.6.5-7.111.… 653925384a7e887fb59b58a432a86968 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-default-2.6.5-7.… f01bbb3541bb8197c36757c9ac554ba9 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-2… c577564f2588a0f23b2bdf6c53622c88 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-273.i58… e1826b653a6dc121bc09af292469ca60 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-273.i5… 4f6f2c3181e9ffa3665b078b56263b5f ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-273.i586.… 93d0f1ac7d07d8965fd995755ced96d8 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp4G-2.4.21-273.i58… dc55afa79f48b332802fcf8c957f4fb1 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_um-2.4.21-273.i586.r… aafbe34c9623ed1558cba1334d9cefb2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-27… 23d2ec2beb60fe87971679ffcd7aa43b ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-273.src.… d4570f75c0706913ab28ab591669a09f ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-273.src… 5c9f06dab451c493ea3805c7c25b5e0e ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-273.src.rpm 4f9d9932f848a81681d97b2121b95cfc ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp4G-2.4.21-273.src.… 595c9d12751dc3ed7911a0c839aa3798 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_um-2.4.21-273.src.rpm 3d2030e1fe01309363a62269544d4ecf SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… 5929f89029262db0f26f7839cae0144c ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-129.i58… 1287e9445cf09947056f8330fad24417 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-129.i5… 9e69c44a2d13d57388272f1991e2c549 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-129.i586.… 345fdb85a6e39f15cd37cecafc8af4c5 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-129.i586… 0964a18c464c9fd905b8c1efa2cd5ba1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.Su… 38e1780995f9b8463bb80d8337e9447a ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-129.src.… 449c13bd8b922c45233df240bb4b02ad ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-129.src… 05ab0427675e9aba88460e016dbbd601 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-129.src.rpm 86c6b0ae5616e0a72396fb19b3fbf172 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-129.src.r… eb488e7c3169936131ff6bac76862fb4 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-2… d2c2fae409431dc9380b1e230359ed56 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-273.i58… 503e57660b3b5f6c1eadf60a54e90508 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-273.i5… 2c5a8cb80db649a50fc64a6a37dd0230 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_smp-2.4.21-273.i586.… 14b2e9a7783986b9293f0561729a5216 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_psmp-2.4.21-273.i586… 36930ea9a97e420b67137143bc3fbd06 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kernel-source-2.4.21-27… 70862f0bae01c0003b3cd48c9161c137 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-273.src.… ef2e870d10237d85d3be66a12371cfe2 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-273.src… 87551521c8e569351d47d9c0e097550b ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_smp-2.4.21-273.src.rpm 5062c220dd0ebe012e9f2f71137458ea ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_psmp-2.4.21-273.src.r… f6e881395e1d069e2dee910cdb311964 x86-64 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-source-2.6.… d8d5dfd431c9b989195f94d3d3c1ea64 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-smp-2.6.8-2… 3a16e2109a1dbf177500430213e45b69 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-default-2.6… 51213878a7116455b9443688d0b39aa0 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-source-2.6.8-2… bbfdc289c2d1f1a73ac6fa759ecfaf87 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-smp-2.6.8-24.1… 9539d6093144fbbd066681f61c9aa07d ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-default-2.6.8-… eeeebf4ea4942f6093b56f7a3d7a7de3 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-source-2.6.… 44996d9e1da1df537cb1b2100553d2af ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-smp-2.6.5-7… 11ad693478569dd691d237679328bd1b ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-default-2.6… deaeb48a6815587535b1adddf68131ef source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-source-2.6.5-7… fdef7eaed76e07a85ebbba9323b64f8d ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-smp-2.6.5-7.11… 3605a6f50f0d799c73849cb382d786ac ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-default-2.6.5-… d0410d0e5c32cd44bae3da7b42cac23a SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… ed6c099957a83fc87abd74e3549e9799 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-273… 18226b51d911e09cd83657c99dd4506f ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-273.x… 0489274cc30666eeec2be0127a669530 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… 792149722a14f021aa095ec4fcc33976 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-273.sr… 9279c9a0613473a71057e76ab4b5a0e5 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-273.src.… 3bbd006852b9b8aab8a2868d922451d5 ______________________________________________________________________________ 5) pending vulnerabilities in SUSE Distributions and Workarounds: Please refer to our SUSE Security 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) iQEVAwUBQfEaXHey5gA9JdPZAQE8uAf/UDupbQayrLk1Tu6mm0u1FybBMmHmi1nx bj69KQRt5PjjYf1mkxHg65Z69oAjNLIjv+cCX8eJWc164ueiVpXgUzjqLouNgCcU dR266o+ZOlQXlTIv1HDLnU2D2yilOJz/EYk4OeGUh2wZNc+DLW7+rJ49qvPIsWBr ECZpwaOhIBOGicdS8i64b3AKW7gNV09Yru21/A/wn7QVfAAPMzQxDTn4/f2/ttxF 3E3xKURN1J9rSkGZMoX7BXK/4iLVurow8t8g2w6DMedyYvIuSLDyB3IlehLnhPmL uL2lSd1PK0rkGuVI6kTZL2lvDjfq4/CHf4MhHWGwDq88L+irqorMSQ== =xoll -----END PGP SIGNATURE-----

5 9

Pam issue, Winbind - sudo combination
by Ciro Iriarte 10 Feb '05

10 Feb '05

Well, i'll repost my question, because my first mail wasn't clear (i was in a hurry while writing it ). Have a Suse 9.2 Pro box authenticating against an NT Domain, i could join the domain, the users login, the homes get created automagically, all seems perfect, BUT, i'm having a little problem with sudo, any time an nt-domain-user runs it, sudo prompts for password (as it should), but it never accepts it!!. The original /etc/pam.d/sudo file looked like this: ------------------------------------------------------- #%PAM-1.0 auth required pam_unix2.so ------------------------------------------------------- Didn't find a Suse specific solution, tried a debian based one (the only one i've found), but it doesn't work, it looks like this: ------------------------------------------------------- #%PAM-1.0 auth sufficient pam_winbind.so auth required pam_unix2.so use_first_pass ------------------------------------------------------ Thanks in advanced. Ciro

3 5

Security patches for Suse's 2.6 kernel
by nordi 08 Feb '05

08 Feb '05

Hi list! I've ported the hardlink/symlink protection of the grsecurity patch to Suse's 2.6 kernels. My patch makes it considerable harder (and sometimes impossible) to exploit insecure handling of files in /tmp. Additionally it prevents some other annoying things that an attacker could do with hard/symlinks. The patch, more details and install instructions can be found on my website (http://private.addcom.de/nordi/). Feedback is welcome! The patch is very small and non-intrusive. The slightly changed handling of links should(!) not break existing software. At least I've been using this patch myself on a Suse 9.1 and a 9.2 machine for a couple of weeks now and haven't seen anything break that wasn't broken before ;) Regards nordi SHA1 checksums for the patches: Suse 9.2: d8138ce3da839aefa77a236ac0bd6436318ffc52 Suse 9.1: c7210821fa8c2ca87f2a4e2cb13646bdec36f72c

2 3

Help getting DMZ+reverse-proxy working
by Rainer Duffner 31 Jan '05

31 Jan '05

Hi, I have the following setup: LAN: 192.168.0.0/24 DMZ: 10.0.0.0/24 Internet: some DSL-connection, real IP. looks like this internal (192.168.0.0/24) ^ | | <----Internet----|FW|-->DMZ----10.0.0.0/24 I want to be able to access the webserver in the DMZ via port 443 (which works) and then reverse-proxy these requests to some internal IP on 192.168.0.0/24. That doesn't work. Here's what I have so far: FW_QUICKMODE="no" FW_DEV_EXT="eth-id-00:01:03:4c:cd:c0" FW_DEV_INT="eth-id-00:a0:24:a8:fb:a4" FW_DEV_DMZ="eth-id-00:04:76:13:6d:e5" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="0/0" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="ssh" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_EXT_RPC="" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_DMZ_RPC="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_SERVICES_INT_RPC="" FW_SERVICES_QUICK_TCP="" FW_SERVICES_QUICK_UDP="" FW_SERVICES_QUICK_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="no" FW_ALLOW_INCOMING_HIGHPORTS_UDP="DNS" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SAMBA="no" FW_FORWARD="" FW_FORWARD_MASQ="0/0,10.0.0.x,tcp,443 10.0.0.x,192.168.0.y,tcp,80" FW_REDIRECT="" Any ideas how to do that ? Or do I need a real IP also in the DMZ ? cheers, Rainer -- =================================================== ~ Rainer Duffner - rainer(a)ultra-secure.de ~ ~ Freising - Munich - Germany ~ ~ Unix - Linux - BSD - OpenSource - Security ~ ~ http://www.ultra-secure.de/~rainer/pubkey.pgp ~ ===================================================

2 4

Basics needed: receive mail but mail header contains no 'for'
by Preusse, Mathias 31 Jan '05

31 Jan '05

Hi list, i need probably some basics. The mail header, so i can see it with outlook, seems to be broken. Example: Microsoft Mail Internet Headers Version 2.0 Received: from our.mailgateway.de ([a.b.c.d]) by internal.mailserver.de with Microsoft SMTPSVC(5.0.2195.5329); Mon, 31 Jan 2005 01:38:49 +0100 Received: from egan.earth9.com ([207.254.32.6]) by citation.freezemail.com (InterMail vK.4.04.00.00 781-3[3 This mail goes direktly to a user, not to a postbox for unknown user. It contains no 'for' or message id. I know, that any Mail header could be manipulated, but i thougt, there must be at last a target user (for) to sort it in a available postbox. Any hints or urls? best regards, Mathias Preusse

3 2

SuSE firewall and Elster
by Juergen.Mell＠t-online.de 31 Jan '05

31 Jan '05

Hi List, I have a problem with our current firewall setup and the German ELSTER tax program: I use SuSE 9.2 on our internet gateway. Right now, any direct traffic from the internal network to the internet is blocked by SuSE firewall and I have squid and postfix running on the gateway to allow web and e-mail traffic. As the elster program uses a propriatary protocol which cannot be fed through a proxy I now have to open the ports 8000 to 8006 which are used by this program for connections from the internal network to the internet. From what I found, this can be done with the iptables commands iptables -A FORWARD -i $INT -o $EXT -p TCP --dport 8000:8006 \ -j ACCEPT and iptables -A FORWARD -i $EXT -o $INT -m state \ --state ESTABLISHED,RELATED -p TCP --sport 8000 -j ACCEPT ($INT and $EXT are the internal resp. external interfaces) So far - so good. But what I am missing now is the masquerading of the IP address of the computer on the internal network (it gets a dynamic IP from the private address range 192.168.x.y). In the firewall script I have disabled masquerading (FW_MASQUERADE="no") to prevent any packets going out without using the squid proxy. Is there any way to open direct connections from the internal network _only_ for destination ports 8000 to 8006 without opening everything else (file-sharing networks etc.)? What iptables commands do I need for this purpose? Is there any better way to get this wounderful piece of software to work? Thank you for your help! Jürgen

4 5

Re: [suse-security] SuSE firewall and Elster
by Juergen.Mell＠t-online.de 30 Jan '05

30 Jan '05

On Sunday 30 January 2005 11:17, Jure Koren wrote: > On Sunday 30 January 2005 11:06, Jürgen Mell wrote: > > > iptables -t nat -A POSTROUTING -o $EXT -p tcp \ > > > --dport 8000:8006 -j SNAT --to-source <your static IP address> > > > > This does not work here. I always get > > iptables: No chain/target/match by that name > > iptables -t nat -n -L > > shows: > > Chain PREROUTING (policy ACCEPT) > > target prot opt source destination > > > > Chain POSTROUTING (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > > > Do you have any idea what is wrong here? > > Can you paste the exact iptables command you entered into the email? > > This usually happens when iptables is unable to load the target module > into the kernel, but SNAT and DNAT targets are part of the ip_conntrack > module, anyway, but MASQUERADE target is in a separate module, > ipt_MASQUERADE. Yes, that is the problem. The ipt_MASQUERADE module was not loaded and the computer was not booted after the last automatic kernel update from SuSE. Sorry, this is my fault. But now everything seems to work fine. > Another thing I noted is that your 8000-8006 range is for a specific > application that probably only connects to one server (or one remote > network). It would be wise to limit the destination of these connections > in the forward table to prevent users to use these ports to connect to > other servers on the internet. You can do this by adding "-d <your > elster server ip network>" to the outgoing FORWARD table entry. Yes, that's a good idea. Only problem here: there are 5 different servers on 5 IP addresses (on different networks) - and who knows when they will change these addresses. They do not even use host names but have the IPs hard-coded in the software. Sigh. Jürgen

2 1

LDAP and Kerberos
by info.bogenrieder＠sytech.de 28 Jan '05

28 Jan '05

Hi, I'm working on better security for my Server ( SuSE Pro 9.2) and decided to implement Kerberos(0.6.2-8, original heimdal rpm from SuSE 9.2) and LDAP (openldap2-2.2.15-5). I found this excellent howto: http://www.opentechnet.com/auth-howto/ar01s06.html. Now I have one Problem. I started to write my kerberos-information into the LDAP-Directory under the tree ou=kerberos,cn=exaple,cn=com just described on 6.2.1 to 6.2.7 when I change now the kerberos settings in my krb5.conf to [kdc] database = { realm = HIBYTE.DE dbname = ldap:dc=example,dc=com mkey_file = /var/heimdal/m-key } and make now a 'kadmin -l list *' the retrun is empty. In the syslog-fiel I see following entry: Jan 28 17:27:44 linux slapd[17048]: conn=44 fd=13 ACCEPT from PATH=/var/run/slapd/ldapi (PATH=/var/run/slapd/ldapi) Jan 28 17:27:44 linux slapd[17048]: conn=44 op=0 BIND dn="" method=163 Jan 28 17:27:44 linux slapd[17048]: conn=44 op=0 BIND authcid="uidnumber=0+gidnumber=0,cn=peercred,cn=external,cn=auth(a)EXAPLE.COM" Jan 28 17:27:44 linux slapd[17048]: conn=44 op=0 BIND dn="uidnumber=0+gidnumber=0,cn=peercred,cn=external,cn=auth" mech=EXTERNAL ssf=0 Jan 28 17:27:44 linux slapd[17048]: conn=44 op=1 SRCH base="dc=exaple.com,dc=de" scope=1 deref=0 filter="(objectClass=krb5KDCEntry)" Jan 28 17:27:44 linux slapd[17048]: conn=44 op=1 SRCH attr=krb5PrincipalName cn krb5PrincipalRealm krb5KeyVersionNumber krb5Key krb5ValidStart krb5ValidEnd krb5PasswordEnd krb5MaxLife krb5MaxRenew krb5KDCFlags krb5EncryptionType modifiersName modifyTimestamp creatorsName createTimestamp Jan 28 17:27:44 linux slapd[17048]: conn=44 op=1 SEARCH RESULT tag=101 err=0 nentries=0 text= Jan 28 17:27:44 linux slapd[17048]: conn=44 op=2 UNBIND Jan 28 17:27:44 linux slapd[17048]: conn=44 fd=13 closed If I change krb5.conf to [kdc] database = { realm = HIBYTE.DE dbname = ldap:ou=kerberos,dc=example,dc=com mkey_file = /var/heimdal/m-key } and then make a 'kadmin -l list *' I see all userer. I think the Problem is the searchscope of kerberos. In the logfile the scope is 1, is there a possibility to change this behavior to scope=2? Jörg

1 0

Re: [suse-security] SuSE-firewall with webserver and samba
by Birgit Kellner 28 Jan '05

28 Jan '05

Thanks to all who've helped so far. Here are a few further details. Christian Eisendle wrote: > In case of a slow network, the DNS-Server could be the reason for this > >problem, but after a refresh of the site (or maybe restart of the >browser) the website should be opened. >Are there any virtual hosts on the webserver? If not, users having >this problem could try to enter the IP-Adress of your webserver >instead of the DNS-Name, to determine if the name-resolving makes the >problems. > > > Indeed, some users who couldn't use the name can now access the server with the IP-Adress. From this I conclude that the problem must definitely be with the DNS-Server, or with network speed. The web server is registered with the central university administration, and they've told me it is entered correctly in their DNS server. I can't readily compare nslookup output from outside the university and inside because I'm inside the university network even if I connect from home, but I'll try to get someone to do that for me. As for the samba problem: >What's the exact problem? Is it a connection or an authenticating >problem? At first try to connect with the ip-adress instead of the >netbios name (\\222.222.222.x\share) >Does a telnet to samba server on port 139 work? >Does it work, when SuSEfirewall2 is stopped? > > > > 1) Connection with IP-Address works. 2) telnet is disabled on the server. an ssh connection on that port doesn't work. 3) the connection works without the firewall, even with the server name, and not only with the ip address. with the firewall, it only works with the ip address. The firewall configuration file now looks like this: FW_QUICKMODE="no" FW_DEV_EXT="eth0" FW_DEV_INT="" FW_MASQUERADE="no" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="22 80 ssh www" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="131.130.180.0/25,tcp,137 131.130.180.0/25,tcp,138 131.130.180.0/25,tcp,139 131.130.180.0/25,tcp,445 131.130.180.0/25,udp,137 131.130.180.0/25,udp,138 131.130.180.0/25,udp,139 131.130.180.0/25,udp,445" FW_ALLOW_INCOMING_HIGHPORTS_TCP="dns" FW_ALLOW_INCOMING_HIGHPORTS_UDP="dns" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_SAMBA="yes" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="yes" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_KERNEL_SECURITY="yes" FW_ALLOW_PING_FW="no" FW_ALLOW_PING_EXT="no" FW_IPSEC_TRUST="no" FW_DEV_DMZ="" FW_SERVICES_DMZ_IP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_TCP="" FW_MASQ_NETS="" FW_ROUTE="no" FW_ALLOW_FW_TRACEROUTE="yes" This is my smb.conf: [global] workgroup = ISTB netbios name = ISTB server server string = ISTB fileserver on %h encrypt passwords = yes invalid users = root hosts allow = 222.222.222.0/25 localhost load printers = no passdb backend = smbpasswd:/etc/samba/smbpasswd [data] comment = ISTB Kollektivverzeichnis volume = ISTB-Kollektiv path = /istb_userdata browseable = yes writeable = yes guest ok = no valid users = istb_user read list = istb_user write list = istb_user Thanks again, Birgit

2 1

Re: AW: [suse-security] SuSE-firewall with webserver and samba
by Birgit Kellner 27 Jan '05

27 Jan '05

Christian Eisendle - asut computer wrote: >Hi Birgit! > >What does the logfile say? > >Try to install "iptraf" (also included in the suse distribution - maybe >it is already installed :) > >Stop the firewall, start iptraf, choose "IP traffic monitor" and select >your network interface. >Now try to connect to the samba server with the server-name and look at >the output of iptraf - it shows you any IP-connections. >Have a look at the tcp and udp ports, which are used and include them in >your firewall configuration. > >HTH > >Christian > > > Hi Christian, thanks! iptraf shows tcp traffic on ports 139 and 445. both are already open to the trusted net in the firewall. I've now tried to enter one specific IP address in FW_TRUSTED_NETS, rather than a block in the notation 222.222.222.0/25. With this changed setting, access works. So it seems that my FW_TRUSTED_NETS syntax was wrong after all. But what would be the right way to enter a whole block? Confused greetings, Birgit

2 1

Howto force an account to change its password at next logon?
by Daniel Wirth 27 Jan '05

27 Jan '05

Dear list, we try to implement an operator proof solution to force a user to change his password at the next logon. The only way we found is: - manually alter the password creation date in /etc/shadow to a date in the past - set an coresponding password expiration period (so that the password has already expired) Do you know any nice GUI-tools to set the password creation date in /etc/shadow? Or is there any easier way to implement this? Thanks in advance Daniel

2 1

RE: [suse-security] Howto force an account to change its password at next logon?
by Ness, Todd 27 Jan '05

27 Jan '05

# passwd --help Usage: passwd [-f|-g|-s|-k[-q]] [name] passwd [-n min] [-x max] [-w warn] [-i inact] user passwd {-l|-u|-d|-S[-a]|-e|-h} user passwd - change password information -f Change the finger (gecos) information -h Change the home directory -s Change the login shell -g Change the group password -k Change the password only if expired -q Try to be quiet -S Show the password attributes -a Only with -S, show for all accounts -d Delete the password for the named account -l Locks the password entry for "user" -u Try to unlock the password entry for "user" -e Force the user to change password at next login -n min Set minimum field for "user" -x max Set maximum field for "user" -w warn Set warn field for "user" -r service Use nameservice 'service' --help Give this help list --usage Give a short usage message --version Print program version Valid services for -r are: files, nis, nisplus, ldap I believe that "passwd -e " would be the best way to do this. Although not a GUI solution, how much more simple can it get. -----Original Message----- From: Daniel Wirth [mailto:dw@wirthuell.de] Sent: Thursday, January 27, 2005 9:34 AM To: suse-security(a)suse.com Subject: [suse-security] Howto force an account to change its password at next logon? Dear list, we try to implement an operator proof solution to force a user to change his password at the next logon. The only way we found is: - manually alter the password creation date in /etc/shadow to a date in the past - set an coresponding password expiration period (so that the password has already expired) Do you know any nice GUI-tools to set the password creation date in /etc/shadow? Or is there any easier way to implement this? Thanks in advance Daniel -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

2 1

SuSE-firewall with webserver and samba
by Birgit Kellner 27 Jan '05

27 Jan '05

Hello, I'm trying to configure a webserver (SuSE 9.1), with a SUSE firewall, and perhaps also with samba fileshares, though I'm not sure there's a reasonably secure way of doing this. ssh should also be accessible. There is no internal (private) network. The server, and the machines accessing the fileshares, are part of a university network. All machines access the internet through that network; nothing from them (or to them) goes through the firewall, which should only protect the machine running the webserver and the samba shares. The server host and the samba clients belong to the same DNS subdomain, and have an IP address block like 222.222.222.2 - 222.222.222.126. The clients all run Windows NT 4.0, Windows 2000, or Windows XP. As I've currently configured the system, I have two problems: (1) some users from outside report that the webserver is not accessible; connection attempts throw up DNS errors. I have no rejected packets for port 80 in the firewall log, and am therefore inclined to think that the problem is not with the server or firewall configuration. From within the university network, I have no problems connecting to the server on port 80. Could it be that it just takes some time until the DNS information for the server spreads around, or does this entail that there's something wrong with the DNS entry for the server? (2) the samba fileshares can't be accessed. Actually, there's only one fileshare. Only one particular username is accepted as valid, and the samba clients must belong to the IP block 222.222.222.xxx/25. The firewall configuration file currently looks as follows: FW_QUICKMODE="no" FW_DEV_EXT="eth0" FW_DEV_INT="" FW_MASQUERADE="no" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="www ssh 139 137 138 445" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="222.222.222.0/25,tcp,137 222.222.222.0/25,tcp,138 222.222.222.0/25,tcp,139 222.222.222.0/25,tcp,445 222.222.222.0/25,udp,137 222.222.222.0/25,udp,138 222.222.222.0/25,udp,139" FW_ALLOW_INCOMING_HIGHPORTS_TCP="dns" FW_ALLOW_INCOMING_HIGHPORTS_UDP="dns" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_SAMBA="yes" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="yes" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_KERNEL_SECURITY="yes" FW_ALLOW_PING_FW="no" FW_ALLOW_PING_EXT="no" My idea was to define the ip block of the samba clients as a "trusted net", and to only open the required tcp/udp ports, which are (I believe) 137-139 and 445. I'm not sure whether my syntax for FW_TRUSTED_NETS is correct. But would the general approach be ok? And are there any other non-sensical or counterproductive settings? Thanks a lot; I'm very new at this (as one might perhaps have gathered from the configuration ...), best regards, Birgit Kellner

2 1

SELinux Support in SuSE 9.2
by Tedi Heriyanto 27 Jan '05

27 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am currently learning about SELinux. Do I just need to do the following to enable SELinux in SuSE 9.2 : - - change the entry in kernel option in grub/lilo config to "selinux=1" - - install libselinux Thank you very much - -- Tedi Heriyanto URL : www.tedi-h.com GPG fingerprint = C02C 7797 0EF0 5D25 798A 0A25 1DD3 6924 57C7 5D78 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB928WHdNpJFfHXXgRAmYUAKCKhNEJQWutpE1Hvveympo+4wcqXACgjctJ dDSpHpaifPDpO5/ygc6GkRY= =DcAn -----END PGP SIGNATURE-----

2 3

WLan ->(Intranet) ->Internet Howto?
by Andreas Paulick 25 Jan '05

25 Jan '05

Hello there, I have read the last days the Inet about security stuff (VPN-Howto, VPN-Masq-Howto) and got more and more confused. I want share my inet-dialup-connection with my neighbour across the street. He has a Win98SE-PC with a WLan-network-card and here will stay a standard access point. Because Win98, there are some difficults to establish a WPA-Connection. If I test with another client, the Wlan-speed with WPA enabled is awfull slow (as expected from this cheap AP here) But thats not the way we're want to go. We want a solution to keep the kiddys and normal crackers out. (I think a real Hacker doesnt give up if he sees a VPN). So I want to secure this connection with a VPN-connection. But where to start? There are no win98-clients for IPsec out there, but there is an L2TP-client. There are Firewall / Masquerade problems with VPN.... For the right way to split up the secure zones I will set the router like this: !--------------------! clients---Intranet-----!eth1 ROUTER eth0!---DSL/ISP---> via Cat5 Hub ! with FW, ! ! VPN-server ! client-----WLAN-AP-----!eth2 ! with Wlan !--------------------! +VPN-client Is this overkilled (additional Network-Card) or easier to configure? Im afraid, there are much concerns to care about, if I plug the WLAN-AP direct to the Intranet-Hub. What Server/client would you suggest to use for VPN (keep in mind the client-soft have to run on Win98SE)? Have I care about firewall concerns at eth2? As is see, there should only one piece of software listen on this network interface: the VPN-server. Because I decrypt the traffic on my router, have I worry about masqueradeing the traffic to/ from the public Inet? How could I prevent the VPN-Users from any services in the Intranet exept for the forwaring to the public Inet? Could you point me either to a howto or a software path ("Take client XXyyzz from MicroLinux, take server freegoose from SuseSoft and glue them together" or some raw main points to look for? thanks in advantage Andy

3 2

Re: [suse-security] errata page
by Niki Rahimi 25 Jan '05

25 Jan '05

Marcus wrote: >On Tue, Jan 25, 2005 at 02:42:46PM -0600, Niki Rahimi wrote: >> Hi All, >> Would anyone know of an errata page with security vulnerabilities >> and other issues listed that one >> could look up within the suse.com or .de pages? I'm also open to non SuSE >> pages but would prefer one >> directly from the company. >Just go to www.suse.de (which links to Novell) and click on SUSE Linux >Security. >Ciao, Marcus Terrific! I was looking on suse.com before. This is great info. Thanks much!! Niki A. Rahimi IBM Premium Services Advanced Support narahimi(a)us.ibm.com

1 0

errata page
by Niki Rahimi 25 Jan '05

25 Jan '05

Hi All, Would anyone know of an errata page with security vulnerabilities and other issues listed that one could look up within the suse.com or .de pages? I'm also open to non SuSE pages but would prefer one directly from the company. Thanks, Niki Niki A. Rahimi IBM Premium Services Advanced Support narahimi(a)us.ibm.com

2 1

product lifecycle for SuSE 8.2
by Bob Vickers 25 Jan '05

25 Jan '05

Hello, I'm trying to do some forward planning and I've scoured the SuSE website trying to find out when we will stop getting security updates for SuSE 8.2. I know it's quite soon because 8.2 came out roughly in spring 2003 and there is a 2-year lifecycle: does anyone have a more accurate date? Thanks, Bob ============================================================== Bob Vickers R.Vickers(a)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

2 1

SUSE Security Announcement: Realplayer 8 (SUSE-SA:2005:004)
by Marcus Meissner 24 Jan '05

24 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: realplayer 8 Announcement-ID: SUSE-SA:2005:004 Date: Monday, Jan 24th 2005 16:00 MET Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Desktop 1.0 Vulnerability Type: remote code execution Severity (1-10): 8 SUSE default package: yes Cross References: none Content of this advisory: 1) security vulnerability discussed: - integer overflow problem description 2) solution/workaround 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion RealPlayer is a combined audio and video player for RealMedia formatted streaming data. These formats are very common throughout the Internet. eEye Security in October 2004 discovered a flaw in the .rm RealMovie stream handling routines which allows a remote attacker to exploit an integer overflow vulnerability using a special .rm file. This might allow a remote attacker to execute code as the user running RealPlayer. Reference URLs for this problems are the Real security advisory: http://service.real.com/help/faq/security/040928_player/EN/ and the eEye security advisory: http://www.eeye.com/html/research/advisories/AD20041001.html SUSE Linux includes RealPlayer as both standalone player and as a plugin for web browsers like Mozilla and Konqueror. This might allow the attacker to just provide a web page or E-Mail linking to the special exploit .rm file. We cannot fully evaluate the impact of this problem due to lack of information and lack of source code to review. SUSE Linux versions up to 9.1 and the SUSE Linux Desktop 1.0 include RealPlayer version 8 and are affected by this problem. SUSE Linux 9.2 and the Novell Linux Desktop 9 include RealPlayer version 10 and are NOT affected by this problem. Real does not offer a fixed version 8 RealPlayer, but suggests upgrading RealPlayer to version 10. However, upgrading Realplayer is not possible for older SUSE Linux products since Realplayer 10 requires newer dynamic library versions than the ones to be found in those products. Also some old Real content is not compatible with the RealPlayer version 10. For these reasons we cannot offer fixed packages for older SUSE Linux based products. 2) solution/workaround We suggest one of the following workarounds: a) De-install RealPlayer Either use YaST to deinstall RealPlayer, or as root do: # rpm -e RealPlayer You will lose the ability to view Real content. b) Remove the RealPlayer plug in As root, execute the following commands: # rm /usr/lib/browser-plugins/raclass.zip # rm /usr/lib/browser-plugins/rpnp.so Content can still be viewed by starting "realplay" and opening URLs, but automatic exploits via web pages or E-Mails are no longer possible. ______________________________________________________________________________ 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 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.4 (GNU/Linux) iQEVAwUBQfULuXey5gA9JdPZAQFlBQf/TBBqYIAXgwKUKxq9qOpXOLQQ1L+CkTy+ Ck0FIKtH/YrqmfxIudDPQzzvBBQqM530SohAyQT90kz/9L6nxc3n2RgKdu03pUlt mgmE5sOm9ImEM3ror7j+ZzyWcGCFPyC/4SWtHwzTZi1cgcRZwpuxEhBps2C3LO2k QJdUWHlPTcYJVVnqGvxk2ZGokpiVlvMTzLMXJe+Cq0cZIwMS9lB3x+GHdkYDBRES 1m8mgleJN8jpyJRNRMLyKcqTYHOAllDFuC2rte2AajUcxdX87Uxl6X0sBBWwTtNK c+AeKyMzFm4U/mxbjdfS1UOcGnIRAt1nJ2OqYZ9i8AO30y4ooEwTmw== =j1Cu -----END PGP SIGNATURE-----

1 0

Multiple YOU patches with _seemingly_ outdated versions...
by pelibali 21 Jan '05

21 Jan '05

Hi List! I made a short PERL script, for doing some statistics-analysis on all of the new and obsolete patches available via YOU. But there are several packages, where I can't find out, what is behind, and why I see sometimes seemingly outdated packages. One example xine-ui and xine-lib, where actually both of them were build from xine-lib-xxx.nosrc.rpm, but as the vulnerability was discovered, from TWO different versions: Buildtime: 2004-04-26 16:18:03 Package: xine-ui-0.99.rc3a-106.3.i586.rpm Source: (xine-lib-0.99.rc3a-106.3.nosrc.rpm) Buildtime: 2004-11-16 13:55:32 Package: xine-lib-0.99.rc3a-106.15.i586.rpm Source: (xine-lib-0.99.rc3a-106.15.nosrc.rpm) My question would be (even, that I realized, that there is nothing wrong!), that how is this possible, that after the second patch got available via YOU, the xine-ui-0.99.rc3a-106.15.i586.rpm was not build again from the updated source? Another, more theoretical question would be, that in case one decides to build e.g. the first package from the _newer_ source, would one get the same as the prior variant xine-ui, only with a tiny change exclusively in the version-numbers? (While checking the output of my program, in the case of some arts, dhcp, kdelibs3, subversion, and XFree86 packages the situation is very similar: few updated rpms coming from updated sources, but their 'sisters' got no update...) I'm not so familiar with deeper rpm-related themes, so I would be really hapy to get a correct explanation, more or less on the user-level:) Thanks a lot, Pelibali

3 3

idle timeout
by Miguel Albuquerque 21 Jan '05

21 Jan '05

Is there a way to auto logoff inactive local open sessions ? Thanks :-) -- ______________________________________________________________ «¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»«¤»¥«¤»§«¤»¥«¤» ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ CODALIS SA www.codalis.ch 17, rue de la Fontenette, CAROUGE TEL : +41 22 827 30 30 FAX : +41 22 827 30 33 ______________________________________________________________ «¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»«¤»¥«¤»§«¤»¥«¤» ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

6 7

passwordless user account warning
by Alex Angerhofer 21 Jan '05

21 Jan '05

Hi list, I checked one of my boxes (SuSE 9.2 Pro with the latest patches) today with the latest version of rkhunter and got the following warning: Checking for passwordless user accounts... Warning! Found passwordless user account. See logfile for more information The logfile reveals this: [21:26:27] Warning! Found passwordless account (+) [21:26:27] Check this account and give it a password. A look at /etc/shadow shows as the last line: +::0:0:0:::: I am kind of worried about this, especially about the password-less user +. This is apparently not an account that one could log on to, but still I haven't seen this at all in the past. My home box running the 64bit version of SuSE 9.2 doesn't show this user at all. I'd be really grateful to anybody that could help me shed light on this or at least point me in the right direction. Best regards, Alex. P.S.: There doesn't seem to be anything particularly worrying in the log. A couple of vanilla log on attempts on the sshd that people seem to have reported about from time to time: Jan 9 11:57:36 falco sshd[32471]: Illegal user jordan from ::ffff:220.228.116.140 Jan 9 11:57:36 falco sshd[32471]: reverse mapping checking getaddrinfo for adsl-220-228-116-140.nh.sparqnet.net failed - POSSIBLE BREAKIN ATTEMPT! Jan 9 11:57:36 falco sshd[32471]: error: Could not get shadow information for NOUSER Jan 9 11:57:36 falco sshd[32471]: Failed password for illegal user jordan from ::ffff:220.228.116.140 port 4205 ssh2 Jan 9 11:57:36 falco kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0c:6e:63:0d:50:00:03:fe:a0:e4:0a:08:00 SRC=220.228.116.140 DST=128.227.89.85 LEN=60 TOS=0x00 PREC=0x00 TTL=48 ID=30681 DF PROTO=TCP SPT=4239 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A0152624E0000000001030300) and repeats of these with different login names ad nauseam. There was also an attempt at brute-forcing my root password (fat chance): Jan 11 04:48:05 falco sshd[9001]: Failed password for root from ::ffff:67.19.157.18 port 58602 ssh2 Jan 11 04:48:06 falco sshd[9003]: reverse mapping checking getaddrinfo for 18.67-19-157.reverse.theplanet.com failed - POSSIBLE BREAKIN ATTEMPT! Jan 11 04:48:06 falco sshd[9003]: Failed password for root from ::ffff:67.19.157.18 port 58628 ssh2 Jan 11 04:48:06 falco sshd[9005]: reverse mapping checking getaddrinfo for 18.67-19-157.reverse.theplanet.com failed - POSSIBLE BREAKIN ATTEMPT!

3 2

[ vpn masquerade problem]
by Gudmundur Arnljotsson 21 Jan '05

21 Jan '05

Hi all I’m using Standard Server 8 as mail server, samba, domain, proxy and firewall. (SuSE standard installation + pptpd as vpn all is up to date) My setup is: XP clients on Local LAN1<->Server<->Local LAN2<->DSL router<->internet<->XP road warriors and MS vpn server with official IP Multiple road warriors can vpn connect to Server without problems (even at the same time) and see LAN1. The problem is vpn from LAN 1 to MS vpn server (never fails from LAN2) Can only connect occasionally, if I get connection I can repeat it but then others can not connect. If I move the PC that could connect within LAN1 I can’t connect again. The only way to reconnect is to give the command SuSEfirewall2, even using SuSEfirewall2 test doesn’t work. Firewall doesn’t block any vpn traffic according to logs Any ideas? LAN1 192.168.50.0 eth0 on server LAN2 192.168.100.0 eth1 on server DSL router does NAT and forwards traffic to server, has official fixed IP on outside but inside is LAN2 FW_DEV_EXT="eth1 ppp+" FW_DEV_INT="eth0" FW_DEV_DMZ="" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="192.168.50.0/24,MS vpn server IP/24" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="1723 smtp" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="gre" FW_SERVICES_INT_TCP="1723" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="gre" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_AUTODETECT="no" FW_SERVICE_DNS="yes" FW_SERVICE_DHCLIENT="auto" FW_SERVICE_DHCPD="yes" FW_SERVICE_SQUID="yes" FW_SERVICE_SAMBA="yes" FW_FORWARD="" FW_FORWARD_MASQ="" FW_REDIRECT="192.168.50.0/255.255.255.0,0/0,tcp,80,8080 \ 192.168.50.0/255.255.255.0,0/0,tcp,21,2121" FW_KERNEL_SECURITY="yes" FW_STOP_KEEP_ROUTING_STATE="no" -- regards Gudmundur Arnljotsson B.Sc Independent Scales Ltd 100a Hayton Road P.O. Box 8098 Christchurch Tel Office 03-341 1324 Mobile 021 475 581

1 0

telnet doesnt work
by Riaz Ur Rahaman 20 Jan '05

20 Jan '05

Hi, I am not able to telnet to my system...I didnt have this problem when I was running 9.1.... >telnet 215.176.125.70 Trying 215.176.125.70... telnet: connect to address 215.176.125.70: Connection refused What configuration changes are required to be done in this case? If the firewall is on, can i disable it completely or is there any way of allowing my telnet session to happen? -- Riaz Ur Rahaman <riazrahaman(a)hp.com>

18 28

sles 9 unable to use bind with rev.lookup
by Mrvka Andreas 20 Jan '05

20 Jan '05

hi list, i have to add a reverse lookup entry in bind. i use sles 9 with yast to edit bind. but there i am not able to make a reverse lookup! (PTR) please can anybody help me? cheers andrew

5 6