May 2001 - openSUSE Security - openSUSE Mailing Lists

OT(?): Apache segfaults after update to 7.1
by Pini Remo 21 May '01

21 May '01

After the long due update from 6.4 to 7.1, apache (child-procs only) segfaults upon page requests. booting: Starting httpd [ SSL PHP4 mod_perl contrib ] done log (after page request): # more httpd.error.log [Mon May 21 18:33:59 2001] [notice] Apache/1.3.14 (Unix) (SuSE/Linux) mod_fastcgi/2.2.2 mod_perl/1.24 PHP/4.0.4pl1 mod_ssl/2.7.1 OpenSSL/0.9.6 configured -- resuming normal operations [Mon May 21 18:33:59 2001] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Mon May 21 18:35:35 2001] [notice] child pid 14729 exit signal Segmentation fault (11) ... kernel: 2.2.18-SMP apache: Server version: Apache/1.3.14 (Unix) (SuSE/Linux) / Jan 19 2001 14:00:47 any hints? greets, remo pini ps: index page is default suse index page pps: if you think this message is inapropriate for this forum, ignore it or tell me privately, this list has already seen it's fair share of bull/flame/educative remarks.

2 1

Re: AW: [suse-security] ipchains masq + active ftp
by Sp0oKeR 21 May '01

21 May '01

Try modprobe ip_masq_ftp I think that you forgot this only ... Regards ... Sp0oKeR > > ---------- Início da mensagem original ----------- > De: Christian Uhde <mail(a)christian-uhde.de> > Para: suse-security(a)suse.com > Cc: > Data: Mon, 21 May 2001 23:17:50 +0200 > Assunto: Re: AW: [suse-security] ipchains masq + active ftp > Hi! > I think you need the module ip_masq_ftp.o to masquarade active ftp with > ipchains, aren't you? So it works fine for me. Perhaps take a look at > http://www.linux-firewall-tools.com/linux/. > > Hope thats you are looking for! > > Christian > > > Am Montag, 21. Mai 2001 10:09 schrieben Sie: > > Hi! > > > > >> I want to use active-ftp with some clients behind my gateway-pc > > >> (ipchains-masquerading)... (passive ftp works) > > >> How do I configure my ipchains-firewall to allow this? > > >> > > >> I hope someone can help me... > > > > PS> Deconfigure all passive ftp components and open your firewall for > > PS> tcp/20,21,1024: > > > > That didn't work for me... > > I have "allow-all-rules" for input, ouput and forward and I didn't > > deny tcp/20,21,1024... > > > > I have just deny-rules for some ports and one forwarding rule: > > ipchains -A forward -s 0.0.0.0/0.0.0.0 -d ! 192.168.0.0/255.255.0.0 -j MASQ > > > > With this I can do passive ftp - but active ftp sucks... :-( > > > > Bye. > > > > > > ----------------------------------------------------- ---------------- > > To unsubscribe, e-mail: suse-security- unsubscribe(a)suse.com > > For additional commands, e-mail: suse-security- help(a)suse.com > > ------------------------------------------------------- -------------- > To unsubscribe, e-mail: suse-security- unsubscribe(a)suse.com > For additional commands, e-mail: suse-security- help(a)suse.com > > Sp0oKeR - NsC spooker(a)bol.com.br Powered By Linux - SuSe & Slackware __________________________________________________________________________ Acesso pelo menor preço do mercado! R$ 14,90 nos 3 primeiros meses! ASSINE AGORA! http://www.bol.com.br/acessobol/

1 0

Suse 7.1 knfsd
by Selcuk Ozturk 21 May '01

21 May '01

Hi, I just installed 7.1 on a new machine and became aware of the fact that in this version the kernel nfs daemon has not been compiled with the netgroup support unlike 7.0. Is there any particular reason to this? I am using the stock 2.2.18 kernel that came on the CD. Is the updated 2.2.19 different? Is there a simple way to fix it? Thanks, Selcuk

3 3

what is the better solution?!
by Daniel Quappe 21 May '01

21 May '01

hi list, what is the more secure opportunity to "redirect" e.g. web-requests on the firewall to a dmz-webserver: - FW_FORWARD_TCP or - using the ipmasqadm-package i read about the FW_FORWARD_TCP-param in my home-7.0-firewall-suse-config. don't know the SuSEfirewall-version... are there any problems with that command?! the comment above this directive was a little bit nervous about using this...;-) many thanks in advance, bye, daniel -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

2 1

2.4.2 kernel problems
by Marko Kaening 21 May '01

21 May '01

Hi, I tried to upgrade my 2.2.17 kernel to 2.4.2. Unfortunately now the system couldn't find any module. I did a 'depmod -a', but for some reason it didn't work... Can it be that the 2.4.* kernel is not working with old (2.2.*) depmod? I noticed that the 2.4.* has a different directory structure in the /lib/modules and when I copied those modules by hand in directories like in 2.2.* I got depmod working properly. I would like to run a 2.4.* kernel because of security issues and also because I would be able to use the PROMISE IDE controller in UltraDMA mode. But it looks like compiling the kernel is not enough this time... Did anyone get into such a problem? Marko P.S.: I am sorry if this is not 100% security related! -- O _ O 0 0 ------------------m-\o/-m------------------------------------------ Dr. Marko K"aning Tel/Fax: +49-3834 554 442 / -3834 554 301 INP Greifswald email : kaening(a)inp-greifswald.de

5 5

kernel2.2.19 cannot find modules.dep
by Iain Gray 21 May '01

21 May '01

I recently ran the prescribed upgrade (i am running suse 7.0 with SMP), and although the machine ( a webserver) rebooted, it did not load the ethernet drivers (eepro100), complaining of being unable to find modules.dep. I fixed this by running depmod -a, but should I have needed to do this, or did i do stg wrong to cause this problem. I'm keen to avoid this happening again, as i'm about to move it to a colocation facility 2 hours drive away ;) ! If this needs to be done again, should i run depmod-a before reboot, just to be sure? Any ideas? thanks, Iain Gray

2 1

Ftp Problem with Suse Firewall
by Andreas M�ller 20 May '01

20 May '01

Hello NG, I've installed the WU FTPD on my Suse 7.1 Box. The ftp connect to localhost is successfull. I can list directorys, create and delete them. But if I try to to connect from the Internet to my linux box, then I can login but the LIST command is not successfull, the ftp process from the client is hanging. I think it's a problem with the firewall. In the logfile there is the following entry: May 20 17:43:42 dolly kernel: Packet log: input DENY eth1 PROTO=6 111.111.111.111: 20 217.4.191.240:65415 L=60 S=0x08 I=57760 F=0x4000 T=64 SYN (#91) But I have configured FW_FORWARD_TCP="0/0,111.111.111.111,21" I think it's no problem with active and passive ftp, because have probed the ftp command in active and passive mode, everything the same. Hope that anybody could help. Best Regards Andreas Müller

3 2

SuSE 7.1 machine hanging at the line "Starting kernel based NFS server"
by Aboubacar Dramé 20 May '01

20 May '01

HI, I added the line /sbin/ipchains-restore < /etc/ipchains.rules to the /etc/init.d/boot.local script at boot, my first machine(SuSE7.1) booted ok, and the ipchains policy restored fine, but the second test machine is hanging at the line "Starting kernel based NFS server",. What can I do to fix the problem ? Thanks again, Abou. > -----Original Message----- > From: Roman Drahtmueller > Sent: Friday, May 18, 2001 7:11 PM > To: Aboubacar Dramé > Cc: 'suse-security(a)suse.com' > Subject: Re: [suse-security] ipchains-restore script > > > > > Hi > > I'd like to run a script to retore ipchains rolls saved using > ipchains-save > > There is any sample script made for SuSE 7.1, I can run at boot to > call > > the file and restore the policy in ipchains-restore ? > > In wich directory of my SuSE linux 7.1 the script will be to get ruuned > at > > boot ? > > The scripts you're looking at are > > /sbin/ipchains-restore > /sbin/ipchains-save > > they read and write to stdio, so save your rules with > > /sbin/ipchains-save > /etc/ipchains.rules > > and read the rules at startup like > > /sbin/ipchains-restore < /etc/ipchains.rules > > the script to do that would be /etc/init.d/boot.local for a 7.1. It runs > before any network interface is up and running, which ipchains doesn't > care about and which is a good idea because you will not have some packets > getting through when your machine boots. > > > Thanks > > Abou. > > Thanks, > Roman. > -- > - - > | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | > SuSE GmbH - Security Phone: // not enable user to fly." > | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | > - -

1 0

SuSE Security Announcement: kernel (SuSE-SA:2001:18)
by Roman Drahtmueller 19 May '01

19 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: kernel Announcement-ID: SuSE-SA:2001:18 Date: Thursday, May 17th, 2000 16:40 MET Affected SuSE versions: (6.1, 6.2), 6.3, 6.4, 7.0, 7.1 Vulnerability Type: local root compromise Severity (1-10): 7 SuSE default package: yes Other affected systems: All Linux systems using a v2.2 kernel Content of this advisory: 1) security vulnerability resolved: kernel Problem, Workaround, Recommended solution, Instructions, Notes, Verification 2) Acknowledgements 3) standard appendix (further information) ______________________________________________________________________________ 1) The Problem, Workaround, Recommended solution, Instructions, Notes, Verification The Problem: The SuSE Linux kernel is a standard kernel, enhanced with a set of additional drivers and other improvements, to suit the end-user's demand for a great variety of drivers for all kind of hardware. Multiple security vulnerabilities have been found in all Linux kernels of version 2.2 before version 2.2.19. Most of the found errors allow a local attacker to gain root privileges. None of the found errors in the v2.2 linux kernel make it possible for a remote attacker to gain access to the system or to elevate privileges from the outside of the system. Thanks to Alan Cox, a summary of these errors can be found at http://www.linux.org.uk/VERSION/relnotes.2219.html . One of the numerous features in the SuSE Linux kernels is support for reiserfs, a fast, stable logging filesystem. In addition to the bugs listed at www.linux.org.uk, the SuSE Linux kernel contains a fix for a race condition between mmap(2) and write(2) in reiserfs that can expose raw data from the disk to an unprivileged user (this problem affected the ufs and ext2fs drivers in FreeBSD systems, see FreeBSD-SA-01:30.ufs-ext2fs at http://www.freebsd.org/security/) Please see the acknowledgement section 2) below for credits on hunting these bugs and fixing them. Workarounds: In order to solve the security problems, it is recommended to update the kernel to version 2.2.19. Some problems (ptrace race) can be circumvented by removing all suid and sgid bits from all binaries in the system. Since this does not help against the other errors, there is no appropriate temporary workaround against all of the known problems except for locking out users with shell access. Advanced Linux users may decide to compile and install the 2.2.19 kernel themselves by hand. This requires some experience on behalf of the administrator and may not be all satisfying because the standard 2.2.19 kernel does not contain some of the drivers that are included in the SuSE kernel (ppp over ethernet, hardware health monitoring (SMBus), reiserfs, graphics hardware acceleration modules (DRI), ...). Recommended solution: SuSE have chosen to provide update packages for the supported distributions to the newest kernels instead of supplying patched update kernel packages of the same kernel version in order to avoid confusion about whether a vulnerable version of a kernel is installed on a system or not. In addition to the clarifying effect of a visible new kernel version that is known to have all publically known security problems fixed, SAP LinuxLab (http://www.sap.com/linux/) have certified this release of the SuSE-enhanced Linux kernel version 2.2.19 with respect to stability and performance. We expect that our usership will benefit from this achievement. Currently, only kernel update packages for the Intel i386 distributions are available. The other supported architectures will have their kernel updates in their respective update directories on our ftp server. The SuSE Linux distribution 6.0 was shipped with a kernel of version 2.0. All of the SuSE Linux distributions 6.1, 6.2, 6.3, 6.4, 7.0 and 7.1 are ready for a kernel of version 2.2.19. However, since update support for the SuSE Linux distributions 6.0, 6.1 and 6.2 has been discontinued, we strongly encourage all users of these distributions to update their systems to a newer version of the SuSE Linux distribution. Please know that the full distribution can be installed from our ftp server or one of its mirrors. Experienced Linux users may choose to update their kernels by hand to the latest version 2.2.19. Step-By-Step Installation Instructions: The kernel of a Linux/Un*x system is the most critical component with relation to stability, reliability and security. By consequence, an update of that component requires some care and full attention to succeed. The following paragraphs will guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, you decide if the paragraph is needed for you or not. Please read through all of the steps down to the end. All of the commands that need to be executed are required to be run as the superuser (root). Each step relies on the steps before to be successfully completed. **** Step 1: Determine the needed RPM package Use the command rpm -qf `awk -F= '/image/{print $2}' < /etc/lilo.conf` to find the name of the kernel RPM package that is installed on your system. Get the respective kernel RPM package from the following location: ftp://ftp.suse.com/pub/suse/i386/update/<DIST>/kernel/2.2.19/ where <DIST> is the distribution version of your system (one out of 6.3, 6.4, 7.0 or 7.1). Most installations are likely to run a k_deflt kernel. To verify the integrity of the files that you need to download, see the section "Verification" near the end of this announcement. In SuSE-6.3 distributions, the above command can produce inconclusive results. This is caused by a different kernel installation procedure in this version of the SuSE Linux distribution. To select your kernel type, choose from the following options: k_eide - should be used for "exotic" IDE chipsets, mostly found on additional IDE interface adapters to PCI or ISA bus systems. k_laptop - should be used for laptops. This kernel has APM support configured. k_i386 - a kernel that should run on most i386 processors. Use this kernel package if the k_pentiu kernel will not boot. k_smp - kernel for multiprocessor systems (SMP) k_pentiu - the standard kernel. It should run on most systems. In the case that you have a self-compiled kernel running on your system, please note that most kernels for the newer distributions have APM configured. This obsoletes the need for a particular laptop kernel. k_deflt (after SuSE-6.3) should do on most modern hardware. **** Step 2: SuSE-6.3 special If you have a SuSE-6.3 system, continue to read this paragraph, otherwise jump to Step 3. In SuSE Linux version 6.3, the kernel and the kernel modules are packaged in two different packages. Both packages must be downloaded and installed. On SMP systems, the packages kernmods (-> kernmod-SMP) and k_smp are needed. On single processor systems, get the kernmod package plus the package as determined by the description in Step 1. **** Step 3: Installation of the RPM package Install the rpm package using the command rpm -Uhv <K_FILE.RPM> where <K_FILE.RPM> is the rpm package you downloaded in Step 1 (for 6.3 also Step 2, two packages!). If the RPM command complains about conflicting files or unfulfilled dependencies, use the options "--nodeps" and "--force". In this case there is no risk for the consistency of the packages on your system. **** Step 4: aic7xxx If you use an Adaptec aic7xxx SCSI host adapter, continue to read this paragraph, otherwise jump to Step 5. The new kernel comes with two versions for the Adaptec aic7xxx driver. If you have such a card, you should see the driver listed in the output from the command lsmod or you should see the adapter in the output of the command lspci The new driver is known to work reliably. However, if you encounter any problems with CDROM drives or other removeable devices (CD-RW drives, tapes, etc) after this kernel upgrade, then you should try to use the old driver which is called aic7xxx_old instead of aic7xxx. If you decide to make this change, then the steps 6 and 7 are mandatory for the update to succeed, regardless if you get back to this paragraph after your first reboot or not. To use the old driver, please use your favourite editor to edit the file /etc/rc.config. Change aic7xxx into aic7xxx_old at the line that starts with INITRD_MODULES. You should find it near the top of the file. Do not forget to save your changes. Then go to Steps 6 and 7. If you want to use the new driver, then do not change anything. **** Step 5: LVM If you use LVM, then continue to read this paragraph, otherwise jump to Step 6. If you use LVM (Logical Volume Manager) in your installation of SuSE Linux, then you need the updated lvm package from the kernel/2.2.19/ directory for your distribution as well. The package contains the userspace utilities to manage the Logical Volume Manager driver. An update package is needed because the LVM data format/structure on disk has changed with the new version of the LVM kernel driver. Install the package as usual using the command rpm -Uhv lvm-0.9.1_beta4-12.i386.rpm Be sure you have downloaded the package for the explicit version of your SuSE Linux Installation. The package names are identical for all distribution versions. WARNING: After the first boot with the new kernel you will not be able to downgrade to older versions of LVM any more. **** Step 6: initrd Upon kernel boot (after lilo runs), the kernel needs to use the drivers for the device (disk/raid) where the root filesystem is located. If this driver is not compiled into the kernel, it is supplied as a kernel module that must be loaded _before_ the root filesystem is mounted. This is done using a ramdisk that is loaded along with the kernel by lilo (See next Step). This ramdisk, called "initrd", must be generated using the command mk_initrd The modules as configured in the variable INITRD_MODULES from /etc/rc.config (See Step 4) are being added to the initrd. Without the "mk_initrd"-call your system might not boot any more. **** Step 7: lilo lilo is responsible for loading the kernel image and the initrd ramdisk image into the system and for transferring control over the system to the kernel. Therefore, a proper installation of the bootloader (by calling the program lilo) is essential for the system to boot (!). Manually changed settings in /etc/lilo.conf require the admin to make sure that /boot/vmlinuz is listed in the first "image" line in that file. Verify that the line starting with initrd= is set to initrd=/boot/initrd Execute lilo and you should see your label in an output like Added linux * Every other output should be considered an error and requires attention. If your system managed to reboot before the upgrade, you should not see any additional output from lilo at this stage. **** Step 8: SuSE-7.0 special If you have a SuSE Linux 7.0 distribution, then continue to read this paragraph, otherwise jump to Step 9. During testing of the 2.2.19-SuSE Linux kernel, we have found an error in the glibc (shlibs) package of the SuSE Linux 7.0 distribution. The error might result in readdir(3) calls to return -EIO to the user program due to incorrect handling of the return value of getdents(2) from the kernel. This bug mostly appears on NFS-mounted filesystems when commands such as tar(1) are used. We have prepared update packages that solve this specific problem. Former security updates are included in this package, of course. Determine which packages you need: See the output of the command rpm -q shlibs libc libd nssv1 It should not be necessary to update a package that is not installed. Select the needed update packages and download them from the following list of URLs ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/shlibs-2.1.3-193.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/nssv1-2.1.3-193.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/7.0/d1/libc-2.1.3-193.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/7.0/d2/libd-2.1.3-193.i386.rpm !!! !!! WARNING: !!! !!! After download and before installation of the glibc packages, the system should be brought to single user mode ("init 1"). If this is not suitable for operational reasons, then please keep the system as calm as at all possible during the update of the shlibs and nssv1 packages. In particular, do not run any shell scripts or any other processes that execute other binaries. Stop the cron and at services, and shut down your MTA. Suspend the execution of active processes by killing them with the -STOP signal and let them resume their work after the installation of the shlibs and nssv1 packages with a -CONT signal. After verifying that the right conditions are in place, install the packages using the command rpm -Fhv nssv*.rpm shlibs*.rpm rpm -Fhv <rest> Afterwards, execute the command ldconfig to update the cache for the dynamic linker. NOTE: updating shared libraries in the running system requires enough space on the root and /usr filesystem to keep both versions of the shared libraries on the disk. The old libraries will be deleted, but the files continue to use diskspace until they are not used by any processes any more. (See Step 9). Similar considerations apply for the the memory consumption of the system. **** Step 9: reboot Reboot your machine for the new kernel to boot and therefore become active. Make sure that all of the above steps have completed successfully. Shutdown and reboot using the command shutdown -r now or init 6 Notes: a) After the upgrade, you might notice kernel messages upon execution of an NFS mount command: silence kernel: nfs warning: mount version older than kernel These messages are complaints that the mount(8) command needs to be upgraded. The mount(8) command is contained in the package "util" ("util-linux" for SuSE-7.1) - we will provide update packages for the "util" ("util-linux" for SuSE-7.1) package. The change is mostly a cosmetic nature and does not have any impact on the security or the stability of the system. b) The kernel sources are contained in the RPM kernel/2.2.19/lx_sus22-2.2.19.SuSE-25.i386.rpm in each distribution update tree. The kernel documentation is in the package kernel/2.2.19/lx_doc22-2.2.19.SuSE-25.i386.rpm and installs to the base path /usr/share/doc/kernel/. c) The directory kernel/misc/ in each distribution tree contains the .config files, the spec and changes file as well as the compilation output for the respective kernel, each in a directory where it belongs to. In addition, the sources for the lvm package can be found in the lvm directory as appropriate. Known problems: * The kernel modules for the cipe and the freeswan packages are not contained in the kernel RPM packages. If you use these packages, then you should wait with the kernel update until the kernel modules for these packages are available, or you could recompile the kernel modules yourself (See section Notes b). Please read the section 2) of the upcoming SuSE security announcements for the location of the cipecb.o and ipsec.o kernel modules. Verification: All RPM packages are gpg-signed using the build(a)suse.de SuSE packaging key that can be found in the toplevel directory of the first CD on SuSE-7.1 and younger, as well as at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de (this key is signed by security(a)suse.de) All files that are needed or referred to in this announcement have their md5 sums listed in the file ftp://ftp.suse.com/pub/suse/i386/update/<dist>/kernel/MD5SUMS . These files are signed by security(a)suse.de in the file MD5SUMS.sig. Since there are 150 files, we do not send the md5sums with the mail this time. ______________________________________________________________________________ 2) Acknowledgements SuSE Security wishes to express their gratitude for the following people who have invested their time for the bugs that are subject of this announcement: Chris Evans Solar Designer Alan Cox David Miller for spotting and fixing the problems as listed in the 2.2.19 release notes Chris Mason for fixing the reiserfs mmap/write race condition Sven Berkvens and Marc Olzheim for spotting the mmap/write race condition in FreeBSD drivers that affects reiserfs in Linux ______________________________________________________________________________ 3) standard appendix: 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 annoucements 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>. =============================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOwPjCney5gA9JdPZAQHnowf/Z4oGIAWzSdnXcxhoUot4UABzH8X2rUfD 9caheLboumIR+gJ8XwuJzxkgl06wfZ6+4SF+WyKovEzJNYN2NjrZOtVYVukc/h9l txnJ5MQ0vtllge45eBGI5r+MZnfk5l107U/Az5/7hZuw7bUTZP991HCPHfnlUDAd YErqQ1KkSg2waTd5dqUjjSXGNjHP8dXG4RAwzqEXQ7PyQmVfwh6YQ0JpJLqXSKM/ Fx9sRaQXVX+Ujx7GI4TA/nPt7SIrLJhBKloV/En2tjHYcq6HiPiyO0a3jwD70wBf 9J3FYdPyWrarwKRqETBDfy+d7mWxgYmisPcZTeGgmK4ekakUSZfcEg== =uQx9 -----END PGP SIGNATURE-----

4 3

ipchains-restore script
by Aboubacar Dramé 18 May '01

18 May '01

Hi I'd like to run a script to retore ipchains rolls saved using ipchains-save There is any sample script made for SuSE 7.1, I can run at boot to call the file and restore the policy in ipchains-restore ? In wich directory of my SuSE linux 7.1 the script will be to get ruuned at boot ? Thanks Abou.

2 1

suspicious apache-log-entries?
by Daniel Quappe 18 May '01

18 May '01

hi list, got this logs in my apache-logs MANY, MANY times...;-) (>1000) "GET / HTTP/1.1Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/msword, application/vnd.ms-excel, application/vnd.ms-powerpoint, */*" any ideas about this (hack-attempt)?! greets and bye, daniel -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

3 2

ping over a masquerading firewall
by Guido 18 May '01

18 May '01

Hello List, I'm trying to build a firewall with ipchains which also should masqerade an internal net. The problem is that I can't ping from inside to the outside. I was able to ping from the inside to the firewall and from the firewall to the outside. If I use a "firewall" like ipchains -F ipchains -P input ACCEPT ipchains -P output ACCEPT ipchains -P forward ACCEPT ipchains -A forward -i $EXTERNAL_INTERFACE -s $INTERN -j MASQ I'm able to ping from inside to outside. In my "real" firewall, I tried it the same way like ssh, which works fine, but ssh has tcp as protokoll and not icmp like ping. My configuration for ssh is the following which works fine ipchains -A input -i $INTERNAL_INTERFACE -p tcp -s $INTERN $SSH_PORTS \ -d $ANYWHERE 22 -j ACCEPT ipchains -A output -i $INTERNAL_INTERFACE -p tcp ! -y -s $ANYWHERE 22 \ -d $INTERN $SSH_PORTS -j ACCEPT ipchains -A output -i $EXTERNAL_INTERFACE -p tcp -s $EXT_IPADDR $UNPRIVPORTS \ -d $ANYWHERE 22 -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p tcp ! -y -s $ANYWHERE 22 \ -d $EXT_IPADDR $UNPRIVPORTS -j ACCEPT ipchains -A forward -i $EXTERNAL_INTERFACE -p tcp -s $INTERN $SSH_PORTS \ -d $ANYWHERE 22 -j MASQ I don't want to use a general rule like ipchains -A forward -i $EXTERNAL_INTERFACE -s $INTERN -j MASQ, And converting the rule from ssh/tcp to ping/icmp doesn't work. (I think it's also because of sending ICMP 8 and receiving ICMP0) TIA Guido

1 0

copy of passwd ...
by Thorsten Marquardt 18 May '01

18 May '01

Hi, what from etc do I have to copy to a second machine to get all the user-accounts accessable without doing further changes? Thanx Thom -- ------------------------------------------------------------------- bye bye (c) by Thom | Thorsten Marquardt | EMail: THOM(a)kaupp.chemie.uni-oldenburg.de | Member of the pzt project. | http://kaupp.chemie.uni-oldenburg.de/pzt -------------------------------------------------------------------

5 5

mod_ssl Update for S.u.S.E. Linux 7.0 available?
by Michael Ströder 18 May '01

18 May '01

HI! I'm using S.u.S.E. Linux 7.0. I've downloaded updated RPMs of Apache 1.3.19 and several modules but I can't find a mod_ssl RPM which fits that version of Apache. Am I missing something? Ciao, Michael.

2 4

problems with DoS part II
by Gediminas Grigas [home] 18 May '01

18 May '01

Hello, Thanks to all for responses. That kiddie still abuses my server like 10 queries/sec. It seems like its not proxy`ing - Hes somehow fakes his IP`s, becouse its endless list, and some of those IP`s (~8-10%) basicly does not exists (or does not respond to ping/traceroute; I hardly can belive that somebody closed ICMP and left open proxy or even worse...) So, i made my script to recognize his calls, and exit fast, so damage is now kind of minimal (like 5% of CPU and full logs of trash). However its sad to think that there is not much i can do, except wait when this guy gets bored. Is there ANY chances fight against spoofed IP`s? Its surely one way call, however, server is very vulnerable to this. What if such guy gets on leased line - not on dial-up. He could make 100 calls/second with almost no chance to trace. Is there any tool to block/recognize/delay/check for spoofed IP`s? Maybe those spoofed packets could be logged on he`s ISP`s gw router? (I think i know which ISP`s service he`s using) Still i cant understand why that router routes such packets becouse none of them belongs to that network. I`m not a big expert in routing, but its seems weird to me. Original story was: ----------------------------------------------------------------- Hello, I`m recently under heavy attack from an l33t hax0r kiddie. Hes using lots of proxies to access my banner exchange (i mean real lots - hundrets and hundrets) - he was able to add new hosts faster than i was able to lock them out wit ipchains (like 10 hosts/min or so). So its ended by that i changed input policy to DENY and set ACCEPT only for lithuanian ISP`s (about 40 major subnets). But thats not solution, becouse system is now locked from outside Lithuania. However that kiddie started abusing my exchange from his real IP (an biggest ISP dial-up service). I cannot lock-out this ISP becouse i would lock 10.000 users as well. So i`m forced to monitor whats happening everytime and lock him once in a while, or server load will jump from 0.4 to 10.00 on my P-III 1Ghz host. I connot do anything in legal way - becouse we dont have anything in our law system against "l33t hax0rs", besides that isp has terrible support and monopoly, so it will probably even dont bother to respond to my requests. My question would be - is there an tool which could run with apache to automaticly lock host for some time if it tryies access system more that 10 times per minute or so? Could anybody pass me an idea how to fight against such attacks? On other hand - i remember someone once said that he has an "legal request to ISP against hackers" or so... some nice warning text to send to ISP on detection of intrusion or DoS. Could you please refer me to it? Sorry for my broken english. Hope you got the matter. P.S. Host running SuSE 7.1 with 2.2.x kernel Thanks ---------------------------------------------------------------------- -- Best regards, Gediminas mailto:gedas@kryptis.lt

3 2

WAY OFFTOPIC! Job Opportunity for Matrix 2 & 3!
by Nix 18 May '01

18 May '01

This has nothing to do with SuSE Security, but this is a post that went to the Sydney Linux Users Group mailing list a few minutes ago. The money is ok but not brilliant, but if there is anyone who wants something VERY cool for their resume, this looks like a load of fun. For reference, Fox Studios is about 5-10 min from central Sydney.... Cheers -Nix >Delivered-To: slug(a)slug.org.au >From: "Steve Cronan" <steve(a)webdev.net.au> >To: <slug(a)slug.org.au> >X-Mailer: Microsoft Outlook Express 5.50.4133.2400 >Subject: [SLUG] Job Opportunity for Matrix 2 & 3! >Sender: slug-admin(a)slug.org.au >X-BeenThere: slug(a)slug.org.au >X-Mailman-Version: 2.0.4 >List-Help: <mailto:slug-request@slug.org.au?subject=help> >List-Post: <mailto:slug@slug.org.au> >List-Subscribe: <http://lists.slug.org.au/listinfo/slug>, > <mailto:slug-request@slug.org.au?subject=subscribe> >List-Id: General Discussions <slug.slug.org.au> >List-Unsubscribe: <http://lists.slug.org.au/listinfo/slug>, > <mailto:slug-request@slug.org.au?subject=unsubscribe> >List-Archive: <http://lists.slug.org.au/archives/slug/> >X-Original-Date: Fri, 18 May 2001 17:16:45 +1000 >Date: Fri, 18 May 2001 17:16:45 +1000 > >Hi Everyone >Been on the list a long time, but never posted! > >I'm currently working at fox studios on the next 2 matrix movies >and I'm looking for someone to assist me. > >It will involve support of a network containing Pc's, Mac's & a couple >Linux servers (Redhat & FreeBSD). >The opportunity to program in php and mysql as well as leaning every >aspect of the movie industry. > >I'm looking for someone with network support, programming and database >experience as well as having the right personality. > >It will be a contract for a year, working 8am-6:30pm at fox studios for >$50-$60K depending on experience. >Its a small IT department so you will have to be very organised! > >Please email me your CV's asap because I'm look to start someone in about >a week. > >Thanks >Steve Cronan > >Digital Assets Manager >Matrix 2 Productions Viel Spaß Nix - nix(a)susesecurity.com http://www.susesecurity.com

1 0

firewall2
by Alexander Grujic 18 May '01

18 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi List :-) I have a problem with firwall2 for iptables. When I run the final Susefirewall2_final start script i get the following error messages : Starting Firewall Initialization: (phase 3 of 3) iptables v1.1.2: Unknown arg `--syn' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--sport' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--syn' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--sport' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--syn' Try `iptables -h' or 'iptables --help' for more information. iptables v1.1.2: Unknown arg `--sport' Try `iptables -h' or 'iptables --help' for more information. the manpage says --sport is an alias for --source-port and --syn should be ok too. My firewall2.rc.config is attached to this mail ... it is still under construction but i have no idea what causes the above error messages :-( Help would be appreciated, Ciao, Alex. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7A9G6X1OUiCutGtcRApjuAJ4gc+NhcaOXMh8te7a1201J4nhJAACcDf/p Z/Spv0xcLJOyUDLirkozZ28= =d304 -----END PGP SIGNATURE-----

2 1

RE: [suse-security] problems with DoS part II
by Reckhard, Tobias 18 May '01

18 May '01

> Is there ANY chances fight against spoofed IP`s? > Not really on your side, unfortunately. You can exclude large portions of the possible IPv4 address space as they are reserved -- there's a list on the same FTP site as the definitive assigned port listings, but I'm not sure how accurate it actually is.. -- but the attacker can still pick valid IP addresses at will that you don't want to simply deny access to your server. The only real way to stop spoofing is for everyone to perform egress filtering to stop spoofed packets from leaving one's network. If I've got 1.2.3.4/24 assigned to me, then only packets with a source address of 1.2.3.0 through 1.2.3.255 should be allowed to leave my network (actually those two probably shouldn't, but anything between them should). This is something ISPs should do as well and that's where you could perhaps succeed. > Its surely one way > call, however, server is very vulnerable to this. > What if such guy gets on leased line - not on dial-up. He could make > 100 calls/second with almost no chance to trace. > What if he uses a DDoS with many well-connected zombies? You are right, you are experiencing a real problem. But unfortunately, you can't solve it on your end, you need the cooperation of his ISP, I'm afraid. > Is there any tool to block/recognize/delay/check for spoofed IP`s? > Well, if they're not actually assigned or are unused at the time, they won't respond to the SYN/ACK packet your server sends back to it and the connection will time out after a while. However, this causes resource consumption on your server, as the half-open connection is kept in the TCP state table until the timeout expires. Perhaps that timeout can be reduced. However I'm not sure if that is your problem or if the packets are saturating your link to your ISP. In the latter case, there's nothing you can do. The packets would need to be dropped before they reach your suspectedly small pipe, i.e. at his ISP or at your's. Of these two, only his ISP can effectively (and easily, for the matter) identify the spoofed packets, so that's the natural point where the operation should take place. > Maybe those spoofed packets could be logged on he`s ISP`s gw router? (I > think i know which ISP`s service he`s using) > If his ISP is using Cisco routers, then a simple ACL (access control list) such as: access-list 1 permit 10.20.30.0 0.255.255.255 interface BRI0 ip access-group 1 in would allow the subnet 10.20.30.0/24, which I assume him to have, into the router and the implicit deny rule would drop anything else. > Still i cant understand why that router routes such packets becouse > none of them belongs to that network. > I`m not a big expert in routing, but its seems weird to me. > It's very unfortunate from a security point of view and the only argument against the egress filtering on their border routers (or those that border their 'peering transit zones') is the hit in performance associated with access lists. However, people like your friend can happily abuse the absence of filtering and create illegal packets that cause load on the ISP's equipment as well... Good luck Tobias

1 0

Re: [suse-security] SuSE Security Announcement: kernel (SuSE-SA:2001:18) (fwd)
by Roman Drahtmueller 17 May '01

17 May '01

---------- Forwarded message ---------- From: Roman Drahtmueller <draht(a)suse.de> To: Jacobo González Simón <jacobo(a)tyc.es> Date: Thu, 17 May 2001 22:21:41 +0200 (MEST) Subject: Re: [suse-security] SuSE Security Announcement: kernel (SuSE-SA:2001:18) > > Where is lvm-0.9.1_beta4-12.i386.rpm ?. I have suse 7.0 and i can´t find > it. I only can find lvm-0.8-0.i386.rpm at > ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1. It's in the same directory as the kernel RPMs. ftp://ftp.suse.com/pub/suse/i386/update/7.0/kernel/2.2.19 > > Thanks > You're welcome. Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> "Caution: Cape does not | SuSE GmbH - Security enable user to fly." | Nürnberg, Germany (Batman Costume warning label) | - -

1 0

[suse-security] Open Port
by Markus Kohli 16 May '01

16 May '01

Hi List! I just ran a "nmap -sS localhost", and what I got was the following: Starting nmap V. 2.53 by fyodor(a)insecure.org ( www.insecure.org/nmap/ ) Interesting ports on localhost (127.0.0.1): (The 1519 ports scanned but not shown below are in state: closed) Port State Service 22/tcp open ssh 80/tcp open http 631/tcp open unknown 6000/tcp open X11 Nmap run completed -- 1 IP address (1 host up) scanned in 0 seconds Now my question: what is that port 631 -> unknown. What could this be? Is it something I should take care of, or is it "normal"? Thanks in advance! Markus P.S: Have a look @ www.handybutler.ch __________________________________________________________________________ I believe the technical term is "Oops!"

4 3

somebody subscribed in the list has list in spam filter
by Michael Rauter 16 May '01

16 May '01

Hello after my last posting, I received this mail. Maybe this person (olaf.kionka(a)trianet.de) should be removed from list, because list postings will be rejected... Regards M. Rauter -----Ursprüngliche Nachricht----- Von: FETCHMAIL-DAEMON(a)localhost.trianet.de [mailto:FETCHMAIL-DAEMON@localhost.trianet.de] Gesendet: Mittwoch, 16. Mai 2001 10:44 Our spam filter rejected this transaction.

3 3

SuSE Security Announcement: cron (SuSE-SA:2001:17) (resent)
by Roman Drahtmueller 16 May '01

16 May '01

-----BEGIN PGP SIGNED MESSAGE----- As a result of a package rebuild, the package for the SuSE-7.1 Intel i386 distribution is not available under the URL as listed below. The listed package was named "cron-3.0.1-297.i386.rpm". This package also fixed the mentioned problems with the package. We are resending this announcement with the correct pathnames and md5sums. Thank you for your understanding, Roman Drahtmüller. ______________________________________________________________________________ SuSE Security Announcement Package: cron-3.0.1-296 Announcement-ID: SuSE-SA:2001:17 (resent) Date: Tuesday, May 15th, 2001 15:30:00 CEST Affected SuSE versions: 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 7 SuSE default package: yes Other affected systems: All UN*X systems using this package Content of this advisory: 1) security vulnerability resolved: crontab problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The crontab program is running setuser-id root and invokes the editor specified in the EDITOR environment variable, usually vi. If crontab discovers that the format of the edited file is incorrect, it executes the editor again but fails to drop its root privileges before. Therefore it is possible to execute arbitrary commands as root. It has been fixed by properly dropping the privileges before executing the editor. This bug was found by Sebastian Krahmer. A possible temporary workaround is to remove the suid bit of the /usr/bin/crontab program: chmod -s /usr/bin/crontab. If you change the mode, you should also do so in the files /etc/permissions*. A permanent solution for the problem is to update the cron package from our ftp server. Download the update package from locations desribed below and install the package with the command `rpm -Uhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig file.rpm', independently from the md5 signatures below. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/cron-3.0.1-335.i386.rpm 606d2c5d67a851ce4e1907146a184cd4 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/cron-3.0.1-335.src.rpm 57805850a0f4fcf8afa99326d3071fd0 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/cron-3.0.1-316.sparc.rpm 4db292d0276badc0ae58fd6aeaab64c0 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/cron-3.0.1-316.src.rpm 16facdbbce03d43fa05d540b810d8636 AXP Alpha Platform: The SuSE-7.1 AXP-Alpha Edition does not suffer from this problem. PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/cron-3.0.1-295.ppc.rpm 589e8575bbbee29a07319f5c5ada9bcc source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/cron-3.0.1-295.src.rpm ff747e2aee85a53e3a30827b33383a7d ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - The man program running setuser-id 'man' suffers from format string and bufferoverflow bugs. Updates are available on the ftp server at the usual location, the announcement will follow shortly. ______________________________________________________________________________ 3) standard appendix: 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 annoucements 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>. =============================================== Regards, Sebastian Krahmer ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOwEziXey5gA9JdPZAQFgmQf/cQz+X/6/iNYOSs7DxN5jK+j5Z2nc83LY 1knhQlpNvgMxeG8m8G1mi8b1B8cKaZStr9dPd9M4EnOzB9KAzdf2Xeajn9+CcLhW LhhVc3lcZfhhBE0L/ZPlu2Cz78vCP3jDu9XaD4e4f2h/rcL9Efs/ezAePP2x5tFP luyXP6BEd4xwMyaLUAesVUxyjPlBH1PhMDj04mX1T+M/3gV2F4GHDzqjPYtlAmE3 qYAFJxg/5g9X0D8ehBiwnBC6ccPLzQqvnM31GyDzwomWnTRp0rQoNVq5uT63Q4Jc rRHQQeTk8Al7TEcufUFblkTo1WGplgPsJGX8yUTfh5pHuFGcCdVqaA== =PTuO -----END PGP SIGNATURE-----

4 6

kernel source for k_deflt-2.2.19
by jan meyer 16 May '01

16 May '01

hi, does somebody know if/when the kernel source for the recently updated k_deflt-2.2.19 SuSE-Kernel is available/will be released ? I've searched the ftp-servers with no result. thanx jan meyer

5 4

scanlogd messages
by Togan Muftuoglu 16 May '01

16 May '01

I am receiving scanlogd messages from ftp.gwdg.de there is a wget ftp download scrip there is running yet this is the first time I am getting messages like this the downloading machine is masquared should the inner ip be as my real ip. Can someone give a guidance what to check for TIA -- Togan Muftuoglu Unusual System Events =-=-=-=-=-=-=-=-=-=-= May 16 15:41:34 gardiyan scanlogd: 134.76.11.100:20 to 192.168.1.3 ports 2549, 2550, 2551, 2552, 2553, 2554, 2555, ..., ??r??uxy, TOS 08, TTL 41 @15:40:50 May 16 15:52:11 gardiyan scanlogd: 134.76.11.100:20 to 192.168.1.3 ports 2715, 2716, 2717, 2718, 2719, 2720, 2721, ..., ??r??uxy, TOS 08, TTL 41 @15:51:26 May 16 15:53:12 gardiyan scanlogd: 134.76.11.100:20 to 192.168.1.3 ports 2744, 2745, 2746, 2747, 2748, 2749, 2750, ..., ??r??uxy, TOS 08, TTL 41 @15:52:28 May 16 15:59:00 gardiyan /USR/SBIN/CRON[10460]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) ----- End forwarded message ----- -- Togan Muftuoglu

2 2

mail-messup
by Roman Drahtmueller 16 May '01

16 May '01

Sorry for the mess with the mails that went to the list. Sebastian and I were discussing the accident that happened with the cron announcement. Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -

1 0

problems with TLD ...
by patric illi 16 May '01

16 May '01

Cheers Linux freaks I have a general question about TLD and ccTLD ( top level domains ), I am sorry for this post but I found no other resource to ask ! We have a two DNS Servers ( ns1.intersoft-networks.ch and ns2.intersoft-networks.ch ). Till now we only registered ".ch" domains. That was working fine. Some days ago I unsuccessfully tried to register a ".net" domain. The output always shows me an Error. My question now; is it possible that a TLD can't point to a ccTLD Nameserver ? So would it work if I register a TLD and configure it as master server ? thx in advance ! patric illi

1 0

SuSE Firewall
by Faessen Jean-Paul 16 May '01

16 May '01

Hi; Finally started (had to find out how first) my SuSE Firewall in SuSE 7.0. Of course,want to configure. So tried to run/open config in Vim and in text console. /etc/rc.conf.d/firewall.rc.config in text console: access debnied. So I run chmod u+x /etc/rc.conf.d/firewall.rc.config nothing happens. Went to Vim doesn't know /etc/ So,how to configure my freshstarted Firewall? Can I use kfirewall to do this? thank's..; Jean-Paul

4 5

do I need util-linux-2.11b-15.i386.rpm?
by omar castillo 16 May '01

16 May '01

i'm upgrading to the new 2.2.19 kernel due to security reasons. do I need util-linux-2.11b-15.i386.rpm?

3 2

Unwanted guest is trying to relay
by Togan Muftuoglu 16 May '01

16 May '01

I had this in my logs isguzar sendmail[5670]: f4FKqSd05670: ruleset=check_rcpt, arg1=<telu(a)telus.net>, relay=user115.mdi.ca [207.230.250.115], reject=550 5.7.1 <telu(a)telus.net>... Relaying denied Ok AFAIU he couldnot get the relay and from=<j6hd6hegh34(a)yahoo.com>, size=0, class=0, nrcpts=0, proto=SMTP, daemon=MTA, relay=user115.mdi.ca [207.230.250.115] but this one I did not get did he managed to use me as his relay or not. If he did what steps can I take to make life harder to outsiders I am using the sednmail 8.11.2-4 that comes with 7.1 -- Togan Muftuoglu

2 2

RE: [suse-security] somebody subscribed in the list has list in s pam filter
by Franziskus Scharpff 16 May '01

16 May '01

Hello Michael, maybe your Provider uses an open Relay for Maildelivery. I had this also a year ago, when Isend some mails via Strato to an account wich checks for open relay for Spam-Preventing. Franziskus > -----Original Message----- > From: Michael Rauter [mailto:rauter@ctos.de] > Sent: Mittwoch, 16. Mai 2001 10:59 > To: suse-security(a)suse.com > Subject: [suse-security] somebody subscribed in the list has list in > spam filter > > > Hello > > after my last posting, I received this mail. Maybe this > person (olaf.kionka(a)trianet.de) should be removed from list, > because list postings will be rejected... > > Regards > M. Rauter > > -----Ursprüngliche Nachricht----- > Von: FETCHMAIL-DAEMON(a)localhost.trianet.de > [mailto:FETCHMAIL-DAEMON@localhost.trianet.de] > Gesendet: Mittwoch, 16. Mai 2001 10:44 > > > Our spam filter rejected this transaction. > >

1 0

Re: [suse-security] Unwanted guest is trying to relay
by Togan Muftuoglu 16 May '01

16 May '01

* Paul Miles <paul.miles(a)padlondon.com> [010516 01:14]: > Throw away sendmail and install Exim. (http://www.exim.org) > > Exim is so much easier to setup, hence more likely to configure a secure > setup/ Many thanks for the informative answer to my question After checking my logs and reading the sendmail op.txt that was located in the docs directory I do not now think the person was able to do send a mail since SuSE sendmail is compiled with no relay option the unwanted guest could not achieved what he dreamed. -- Togan Muftuoglu

1 0

vanished user accounts?
by Night Watcher 15 May '01

15 May '01

Hi all, i have the following problem on my three suse 7.0 and one 7.1 box, after a while when i wanted to log in under my test account, the message was, cannot switch to homedir (no access or something) i relogged in under my root account and then i wanted to correct this problem, i used midnight commander to look where the directory and user permissions of the /home/test account were, these stuff were correctly displayed: i found out that all the permissions still belonged to user test, this was very strange in my opinion, i thought well that is not right but reinstall might help, so i did that, and then my other three boxes suddenly displayed the same problem, all after 2 to 3 weeks, i am pretty sure that i didn't change the userpermissions on the machines ( i can make an mistake but not on 4 machines :)*) so i am guessing that it's an bug, removing the users and readding them does NOT work, so anyone, can u help me? or someone of the SuSE team : is this correcT? met vriendelijke groeten, with kind regards, Remko JC @ irc.super-chat.nl (tech-Admin) NightWatcher @ irc.grunn.org / irc2.grunn.org (IRCoperator) [DrL] Member [Grunn] Coders [Zyber] /* hope the day after you die is an nice one */ niets uit deze mail mag worden gecopieerd of aan derden gelezen laten worden zonder toestemming van de auteur. al deze emails vallen onder briefgeheim. wetboek van strafrecht. Nothing from this mail may be duplicated of may be read by others then the target name. you need authorization from the owner to duplicate it. these mails are secure and restricted confirming the dutch book of law _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

4 5

pop3 endcodes mail with netscape and suse7.x
by ingo＠cimdata.de 15 May '01

15 May '01

hi list, heare in my brillant english, a question: Wher coud I find some infos over: how I encodes the pop3 protocol (ssh?) so that I coud use encode mail with netscape? I coud'nt find something over it at www.obenssh.org, isint it the right cryptosoftwaere? -- []___¸ ######-\ O_-_-_O-\

3 2

ip_masq_h323
by Togan Muftuoglu 15 May '01

15 May '01

Hi, Suse kernel's do not have the ip_masq_h323 module, although someother distribution do have it. Is there any security reasons that the others have not noticed yet or is it just a preference by SuSE. If I compile it byself will I create headaches for myself if the answer to the first part is by preference. TIA -- Togan Muftuoglu

2 3

ipchains problem ?
by stephane parenton 15 May '01

15 May '01

hi, I have a SuSE 7.0 linux box that runs as DNS, filter and gateway. The filter is quite simple. and I 'experiencing troubles... The public ip adress is 62.161.161.253, and the internal lan is nat'ed and use the 192.168.0.x adresses. The computers from the lan can see almost all the internet except the sites that have ip's beginning with 62.*... What can be the trouble ?.... here's the filter i use. #!/bin/sh echo 1 > /proc/sys/net/ipv4/ip_forward /sbin/ipchains -F forward /sbin/ipchains -P forward DENY route add -net 62.161.161.192 netmask 255.255.255.224 gw 62.161.161.222 tr0:0 route add 192.168.0.3 gw 62.161.161.253 route add default gw 62.161.161.254 /sbin/ipchains -A forward -s 0.0.0.0/0.0.0.0 -d 62.161.161.194/255.255.255.255 -j ACCEPT /sbin/ipchains -A forward -s 0.0.0.0/0.0.0.0 -d 62.161.161.195/255.255.255.255 -j ACCEPT /sbin/ipchains -A forward -s 62.161.161.194/255.255.255.255 -d 0.0.0.0/0.0.0.0 -j ACCEPT /sbin/ipchains -A forward -s 62.161.161.195/255.255.255.255 -d 0.0.0.0/0.0.0.0 -j ACCEPT /sbin/ipchains -A forward -s 192.168.0.0/255.255.0.0 -d 0.0.0.0/0.0.0.0 -j MASQ TIA Stephane Parenton

3 2

Re: [suse-security-announce] SuSE Security Announcement: cron
by Nix 15 May '01

15 May '01

At 10:48 PM 15/05/2001, you wrote: > Sebastian Krahmer has found the bug. It has been fixed by properly > dropping > the privileges before executing the editor. Nice work Sebastian. I've been waiting for the SuSE announcement since I saw your name on bugtraq. Good to see that SuSE's extra auditing pays off. Viel Spaß Nix - nix(a)susesecurity.com http://www.susesecurity.com

1 0

SuSE Security Announcement: cron
by Sebastian Krahmer 15 May '01

15 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: cron-3.0.1-296 Announcement-ID: SuSE-SA:2001:17 Date: Tuesday, May 15th, 2001 14:30:00 CEST Affected SuSE versions: 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 7 SuSE default package: yes Other affected systems: All UN*X systems using this package Content of this advisory: 1) security vulnerability resolved: crontab problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The crontab program is running setuser-id root and invokes the editor specified in the EDITOR environment variable, usually vi. If crontab discovers that the format of the edited file is incorrect, it executes the editor again but fails to drop its root privileges before. Therefore it is possible to execute arbitrary commands as root. Sebastian Krahmer has found the bug. It has been fixed by properly dropping the privileges before executing the editor. A possible temporary workaround is to remove the suid bit of the /usr/bin/crontab program: chmod -s /usr/bin/crontab. If you change the mode, you should also do so in the files /etc/permissions*. A permanent solution for the problem is to update the cron package from our ftp server. Download the update package from locations desribed below and install the package with the command `rpm -Uhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig --nogpg file.rpm', independently from the md5 signatures below. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/cron-3.0.1-297.i386.rpm b51f3331fff5dac8474a51a1e7d22454 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/cron-3.0.1-297.src.rpm 495f7f5df30d28a0c6b078a9773fc799 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/cron-3.0.1-316.sparc.rpm 4db292d0276badc0ae58fd6aeaab64c0 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/cron-3.0.1-316.src.rpm 16facdbbce03d43fa05d540b810d8636 AXP Alpha Platform: The SuSE-7.1 AXP-Alpha Edition does not suffer from this problem. PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/cron-3.0.1-295.ppc.rpm 589e8575bbbee29a07319f5c5ada9bcc source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/cron-3.0.1-295.src.rpm ff747e2aee85a53e3a30827b33383a7d ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - The man program running setuser-id 'man' suffers from format string and bufferoverflow bugs. Updates are currently being built. ______________________________________________________________________________ 3) standard appendix: 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 annoucements 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>. =============================================== Regards, Sebastian Krahmer ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOwElIney5gA9JdPZAQHJ+Qf/Z6Q8ofh8j807uLChfv42lCkWmvOCfJLb S4Vg32n3P5oyFcb1J2qHUt+Dv1NlLuGGqsiUlCTNa6xqlt7pWBWQPtyRGnBUGDNh t+VjFBDzILMdIA5A1U25+JtChPXUXYJsvl/KCefoxfXpbiae3J5xqT9lPwe/Djez ZLBdsowmUV7s5lJKUyxrmHhTapLT4ksnunJ5bCmo/z86NMFFGvefeclcEFZ9/q7n rFX48x3vh4psCTJqRVFJoSFAYVfHuXDNuMj59p17JbK3TlVV63rFlk/+zSB+HlnU ddnacjnYfsQhdOhY/QJ68byk/GsusJTbDSHDFobFNgbEVyUmUFC3QQ== =OH6U -----END PGP SIGNATURE-----

3 4

Antwort: Re: [suse-security] Kernel security
by Alexander Schwartz 15 May '01

15 May '01

I think SuSE has the problem that is uses a patched (enhanced) kernel with IPSEC etc. enabled that make it more complicated than necessary. There are distributions like debian who keep things simple and that came up with a recent kernel a long time ago. Using debian, you can update your system with two command (apt-get update / apt-get upgrade) -- never seen that working on a SuSE-machine. Makes administration easy and reduces TOC. Mit freundlichen Grüßen Alexander Schwartz

2 1

Re: [suse-security] Driver Licence
by Alexander Schwartz 15 May '01

15 May '01

Hmm... a driver licencse covers use of cars on normal roads and in cities. But when you "drive" your "box" on the internet, its more like driving in the sahara and rainforest at the same time. A.

1 0

problems with DoS
by Gediminas Grigas [home] 15 May '01

15 May '01

Hello, I`m recently under heavy attack from an l33t hax0r kiddie. Hes using lots of proxies to access my banner exchange (i mean real lots - hundrets and hundrets) - he was able to add new hosts faster than i was able to lock them out wit ipchains (like 10 hosts/min or so). So its ended by that i changed input policy to DENY and set ACCEPT only for lithuanian ISP`s (about 40 major subnets). But thats not solution, becouse system is now locked from outside Lithuania. However that kiddie started abusing my exchange from his real IP (an biggest ISP dial-up service). I cannot lock-out this ISP becouse i would lock 10.000 users as well. So i`m forced to monitor whats happening everytime and lock him once in a while, or server load will jump from 0.4 to 10.00 on my P-III 1Ghz host. I connot do anything in legal way - becouse we dont have anything in our law system against "l33t hax0rs", besides that isp has terrible support and monopoly, so it will probably even dont bother to respond to my requests. My question would be - is there an tool which could run with apache to automaticly lock host for some time if it tryies access system more that 10 times per minute or so? Could anybody pass me an idea how to fight against such attacks? On other hand - i remember someone once said that he has an "legal request to ISP against hackers" or so... some nice warning text to send to ISP on detection of intrusion or DoS. Could you please refer me to it? Sorry for my broken english. Hope you got the matter. P.S. Host running SuSE 7.1 with 2.2.x kernel Thanks -- Best regards, Gediminas Grigas Tel.: (2)226036; (86) 55362 Techninis direktorius Fax.: (2)627986 UAB "Dizaino kryptis" A.Jaksto 9-233, Vilnius, Lietuva 2001 mailto:gedas@kryptis.lt

5 4

man segfault
by Togan Muftuoglu 15 May '01

15 May '01

Hi I have read this on the securityfocus >Heap Based Overflow of man via -S option gives GID man. > Due to a slight error in a length check, the -S option to > man can cause a buffer overflow on the heap, allowing redirection of > execution into user supplied code. > man -S `perl -e 'print ":" x 100'` >redhat 7.0 with man-1.5h1-10 (default > package) and earlier. but running it on suse with man-2.3.10d69s-190 I also get the same thing $ man -S `perl -e 'print ":" x 100'` sometext Segmentation fault -- Togan Muftuoglu

1 0

Using SuSEfirewall for the internal lan
by Togan Muftuoglu 15 May '01

15 May '01

Hi I am getting 1 of probes to port 80 since yesterday to my home network which consists of SuSE 7.1 firewall/router serving 3 1 which are also running SuSE 7.1 and 1 Windows 98 laptop. Although firewall/router has ipchains blocking for all ports except forwarding port 25 can using ipchains firewall in the masquareded 5 increase my security and if so how will it affect the performance. I am planning to use Marc's SuSEfirewall-4.6 but I could not figure out what is my dev_world if I just say eth0 then it will get the address of the NIC but that is not how the packets are coming to the 0 lan since it is masquared. Any guidance is 0 TIA -- Togan Muftuoglu

1 0

Obtuse smtp
by Togan Muftuoglu 14 May '01

14 May '01

Hi I have enabled fort portwarding for port 25 on the firewall. I have the sendmail running on the masquareded machine 192.168.1.3. I have edited the inetd.conf as it says in the INSTALL smtp stream nowait root /usr/sbin/smtpd smtpd I have restarted inetd started smtpfwdd and this is what I am receiving in the messages smtp/tcp(2) bind:adress already in use ???? 1)I have chagned the sendmail option to -q10m in sendmail.rc.config 2) I could not find an init script for smtpfwdd 3) In order to use the anitspam rules it says smtpd should be compiled with CHECK_ADDRESS=1 is this the case for Suse TIA -- Togan Muftuoglu

2 2

Re: [suse-security] Kernel RPMs
by Roman Drahtmueller 14 May '01

14 May '01

> > Hi together, > > ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/RPMs/ > > 7. To avoid complaints from the kernel about an old mount, update the > > util-linux (util for 7.0 and older), too, using rpm -Uhv <packname>. > > is the util-package "util-2.11b-0.i386.rpm" correctly packaged? > I'm missing 'setserial' after update. Right. This needs to be changed. Thanks for the note. > > Peter Wiersig > Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> "Caution: Cape does not | SuSE GmbH - Security enable user to fly." | Nürnberg, Germany (Batman Costume warning label) | - -

3 3

RE: [suse-security] vanished user accounts?
by Marco van Beek 14 May '01

14 May '01

You may also find that the system is saving the username/group as a number, and simply recreating the user doesn't mean they inherit the old permissions. I have noticed that when using YaST it often deletes and re-adds when you edit a username or group. Marco van Beek. -----Original Message----- From: Peer-Christoph Mettelem [SMTP:Peer-Christoph.Mettelem@bezreg-muenster.nrw.de] Sent: Monday, May 14, 2001 11:53 AM To: suse-security Subject: RE: [suse-security] vanished user accounts? never use test as username, dirname or something. It's a command and may cause problems. -----Original Message----- From: Night Watcher [mailto:theeagle84@hotmail.com] Sent: Monday, May 14, 2001 12:43 PM To: suse-security(a)suse.com Subject: [suse-security] vanished user accounts? Hi all, i have the following problem on my three suse 7.0 and one 7.1 box, after a while when i wanted to log in under my test account, the message was, cannot switch to homedir (no access or something) i relogged in under my root account and then i wanted to correct this problem, i used midnight commander to look where the directory and user permissions of the /home/test account were, these stuff were correctly displayed: i found out that all the permissions still belonged to user test, this was very strange in my opinion, i thought well that is not right but reinstall might help, so i did that, and then my other three boxes suddenly displayed the same problem, all after 2 to 3 weeks, i am pretty sure that i didn't change the userpermissions on the machines ( i can make an mistake but not on 4 machines :)*) so i am guessing that it's an bug, removing the users and readding them does NOT work, so anyone, can u help me? or someone of the SuSE team : is this correcT? met vriendelijke groeten, with kind regards, Remko JC @ irc.super-chat.nl (tech-Admin) NightWatcher @ irc.grunn.org / irc2.grunn.org (IRCoperator) [DrL] Member [Grunn] Coders [Zyber] /* hope the day after you die is an nice one */ niets uit deze mail mag worden gecopieerd of aan derden gelezen laten worden zonder toestemming van de auteur. al deze emails vallen onder briefgeheim. wetboek van strafrecht. Nothing from this mail may be duplicated of may be read by others then the target name. you need authorization from the owner to duplicate it. these mails are secure and restricted confirming the dutch book of law _________________________________________________________________ ________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. ----------------------------------------------------------------- ---- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

The curiose Mysql Problems
by Thomas Nowak 14 May '01

14 May '01

Hi list, May its a little bit OT but I don't understand the follow facts: First of all I usinig SuSE 6.4 and mysql. A nice feature of SuSE is the cleaning script which deletes file from the /tmp directory if they are not owned by root. The first Problem is, that mysql has in the standard installation his socket file in this location which is owned by the mysql user so this file is removed after one week. ( I havend found this error in the SuSE Support DB ! ) So I have put the socket file to /var/run ( In my opinion it should the perfect place ) :-) With "/sbin/init.d/mysql start" all is OK, but after each restart mysql will not automatic start. I had found that this is becaus the /var/run directory ist owned by root.uucp and has 775 pemissions, so mysql can't create the socket file as user mysql! But what is the great difference betwwen the start of the script /sbin/init.d/mysql from init and by "hand" as root In both cases I should be root or not? Bye Thomas

1 0

Kernel RPMs
by Roman Drahtmueller 14 May '01

14 May '01

Hi together, As some of you may have seen, I've just put the kernel RPMs for the Intel i386 distributions 6.3, 6.4, 7.0 and 7.1 in place. You can find them at ftp://ftp.suse.com/pub/suse/i386/update/6.3/kernel/RPMs/ ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/RPMs/ ftp://ftp.suse.com/pub/suse/i386/update/7.0/kernel/RPMs/ ftp://ftp.suse.com/pub/suse/i386/update/7.1/kernel/RPMs/ for download. The announcement is waiting to be published, but you get the preliminary version. A kernel update is not rocket science, but it is more sensitive than exchanging a package that you have never heard of for a stupid tempfile race. You should carefully follow each step before you reboot your machine for the freshly installed kernel to become active. We decided to update the kernel packages on all supported distributions to the most recent version 2.2.19 instead of fixing the known security bugs with patches. Tons of other problems have been fixed with the release of the 2.2.19 kernel, and we believe that this is the most stable kernel in the 2.2 release row. To find out which package to download use the command rpm -qf `awk '/^image =/ { print $3 }' < /etc/lilo.conf` Additional stuff can be found in the respective misc/ directory under ftp://ftp.suse.com/pub/suse/i386/update/<distvers>/kernel/misc, such as the .config used for kernel configuration, the output of the compile run and the specfile for the RPM packages. To install the kernel, proceed as follows: 1. Download the kernel rpm for your installation. 2. Install the kernel using the command rpm -Uhv k_deflt.rpm or whatever the command necessary for your installation (see above). It may be necessary to either deinstall the old kernel package and modules package or to use the "--force --nodeps" commandline options for rpm in addition to -Uhv. 3. If you use an Adaptec aic7xxx scsi host adapter, please change "aic7xxx" in INITRD_MODULES on top of /etc/rc.config to read "aic7xxx_old". 4. Execute mk_initrd An error indicates that the initrd is not written to disk. It is possible that your machine will not boot if you have a scsi system. 5. Execute lilo If you did not change the line starting with "initrd" in /etc/lilo.conf, then the freshly created init-Ramdisk will be loaded together with the kernel by lilo upon system boot. This initrd contains the drivers that are necessary for the kernel to mount the root filesystem of the system. On scsi systems, you can't boot without the modules contained in the initrd. 6. If you use lvm, update the lvm package as well. It is contained in the same directory as the kernel rpms. 7. To avoid complaints from the kernel about an old mount, update the util-linux (util for 7.0 and older), too, using rpm -Uhv <packname>. 8. The 7.0 distribution contained a bug in the glibc that is triggered by 2.2.19. The bug may result in mounted nfs filesystems to report -EIO when listing directories in some rare cases. Get the update package for shlibs (the other sub-packages are not needed) from i386/update/7.0/a1/shlibs.rpm, and install it, again, using "rpm -Uhv <packname>". Keep your machine in a quiet state during this upgrade; if at all possible, bring the machine into single user mode, using the command "init 1" Execute "ldconfig" after completion of the rpm command. 9. Execute init 6 or shutdown -r now # which is the same without warning ...and if it fails, drop me a mail, please. Thanks, Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -

7 15

https
by Dietmar Strasdat 14 May '01

14 May '01

Hello suse-security-list, i have installed a suse 7.0 with squid 2.3 stable 3 and Marcs firewall script 4.5. For ftp is proxy suite installed and so long it works fine. But i can t connect to a https url. in firewall.rc.config: FW_SERVICES_INTERNAL_TCP="22 25 53 80 110 119 443 3128" Any hints? -- Best regards, Dietmar mailto:earthmate@gmx.net

1 0

Re: [suse-security] shadow doesn't work anymore with kernel 2.2.19
by Togan Muftuoglu <toganm 13 May '01

13 May '01

* Thomas Schweikle <tschweikle(a)fiducia.de> [010514 02:30]: > In this case someting must have gone wrong updating KDE, Kernel, and X. Any > hint, where I might look? I do not know the answer and its better to hit reply all so the list gets the mail as well incerasing your chance to get answer -- Togan Muftuoglu

1 0

shadow doesn't work anymore with kernel 2.2.19
by Thomas Schweikle 13 May '01

13 May '01

Hi! I've noticed shadow not working anymore since I've installed kernel 2.2.19. Passwords changed will be entered into /etc/passwd directly, even if the shadow-package is installed. Anyone else noticed this? -- Thomas

2 1