May 2000 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] harden_suse documentation
by rhoerbe＠netpromote.co.at 22 May '00

22 May '00

I learned to take care of two things with harden_suse: 1. run it before you start the usual configuration stuff, as it would overwrite many options 2. take care of the reduced password-expiration time in /etc/login-defs. When you set a system in production, you have to learn after a month, that no user can login anymore - this does not make sense for ftp or mail only users. Even for administrative accounts, if you visit the system infrequently. //Rainer Ragnar Beer <rbeer(a)uni-goettingen.de> Sent by: suse-security-return-1788-rhoerbe=netpromote.co.at(a)suse.com 22.05.00 11:38 To: suse-security(a)suse.com cc: marc(a)suse.de Subject: [suse-security] harden_suse documentation During the weekend I had some time to look at the harden_suse script. What it does looks very reasonable to me but I wish there was some more documentation or references respectively. Here is my wishlist: - Although I can guess what the users xok and trusted ar needed for it would be great to get _some_ more information about it. - It would be great to get a little background information about what's going on in the 10 steps to hardening. I'm not talking about writing a book or something but it would be great to have a book-reference or a link where to go and look for each of the 10 steps. The first thing I did (of course;) was to look at the manual but it could have been more helpful. --Ragnar --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

RE: [suse-security] harden_suse documentation
by Matthias Pigulla 22 May '00

22 May '00

Hi Ragnar, I haven't yet looked at that script, maybe I should :-). > -----Original Message----- > - Although I can guess what the users xok and trusted ar needed for > it would be great to get _some_ more information about it. I found that the trusted group is used in the permissions file /etc/permissions.paranoid. Some commands (e. g. like su) are chgrp'd to this group, so that only users belongig to this group may execute them. Probably all X binaries are chgrp'd to xok? :-) Sorry I can't help any more. Matthias -- w e b f a c t o r y G m b H Matthias Pigulla <mp(a)webfactory.de> - Geschaeftsfuehrer Lessingstr. 60 - D-53113 Bonn - Germany - www.webfactory.de Fon +49(0)228-9114455 - Fax +49(0)228-9114499 - ICQ 49185492

1 0

harden_suse documentation
by Ragnar Beer 22 May '00

22 May '00

During the weekend I had some time to look at the harden_suse script. What it does looks very reasonable to me but I wish there was some more documentation or references respectively. Here is my wishlist: - Although I can guess what the users xok and trusted ar needed for it would be great to get _some_ more information about it. - It would be great to get a little background information about what's going on in the 10 steps to hardening. I'm not talking about writing a book or something but it would be great to have a book-reference or a link where to go and look for each of the 10 steps. The first thing I did (of course;) was to look at the manual but it could have been more helpful. --Ragnar

1 0

Antwort: Re: [suse-security] Invisible X?
by Holger-Schmidt＠arcor.net 20 May '00

20 May '00

>X -nolisten tcp works fine. Does anyone know which files I have to >change so that X always goes up with this option when switching to >runlevel 3 or using startx? I just couldn't find it :( >--Ragnar on SuSE-system put in /usr/X11R6/lib/X11/xdm/Xservers Bye Holger

2 1

Invisible X?
by Ragnar Beer 19 May '00

19 May '00

Howdy! I like to have as many as possible ports closed. Is it possible to configure X in a way that it's only "visible" for localhost/127.0.0.1 ? --Ragnar

3 3

kernel exploit update?
by Markus Faber 19 May '00

19 May '00

Hi List! This is maybe a silly question, but after the latest mail from suse about the new security hole in kernel < 2.2.15 I downloaded the file k_laptop.rpm (which isn't mentioned in the mail and there is no md5sum either but I wanted to use apm..) and tried to update via yast - install packages -> failure. Then I tried to update using rpm (rpm -U k_laptop.rpm) -> failure. Now I suspect I have to recompile my kernel with the provided file, is this correct? (using patch) I'm using suse 6.3, kernel 2.2.13 thanx in advance Markus Faber

2 1

manpath again
by Ragnar Beer 18 May '00

18 May '00

Manpaths are becoming an internal DoS for me. I can kill them when I see them running but I still haven't found where they get started. Could anybody help, please? --Ragnar

7 12

Re: [suse-security] httpd run as root
by Eilert Brinkmann 18 May '00

18 May '00

kei <csec(a)m-net.arbornet.org> wrote: > In spite of the fact that I have apache set to chown to wwwrun, ps -aux > still reports an httpd as owned by root. Actually, there are two httpd > running and one is owned by root and the other is owned by httpd. In > httpd.conf I have StartServers = 1. Why are there two deamons running? In order to bind to a priviledged Port (80 < 1024) httpd must run as root. To be able to do this again (e.g., after loading a new configuration at runtime) the initial httpd process remains with root priviledges. This process forks one (as in your case) or more server processes which will handle incoming HTTP requests and change their user ID to that one specified in the configuration file. Eilert -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Eilert Brinkmann -- Universitaet Bremen -- FB 3, Informatik eilert(a)informatik.uni-bremen.de - eilert(a)tzi.org - eilert(a)linuxfreak.com http://www.informatik.uni-bremen.de/~eilert/

1 0

httpd run as root
by kei 17 May '00

17 May '00

In spite of the fact that I have apache set to chown to wwwrun, ps -aux still reports an httpd as owned by root. Actually, there are two httpd running and one is owned by root and the other is owned by httpd. In httpd.conf I have StartServers = 1. Why are there two deamons running? Am I overreacting due to extreme newbieness? I'm running SuSE 6.3

1 0

SuSE Security Announcement - kernel
by marc＠suse.de 17 May '00

17 May '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: kernel < 2.2.15 Date: Wed, 17 May 2000 18:24:50 GMT Affected SuSE versions: 6.1 - 6.4 Vulnerability Type: bypass ipchains filter rules denial of service SuSE default package: yes Other affected systems: all linux versions using kernel 2.2.x and several stateful firewall packages ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description The masquerading feature in the Linux kernel has got a vulnerability in the udp and ftp masquerading code which allows arbitary backward connections to be opened. Some denial of service were found. 2. Impact Remote users may bypass ipchains filter rules protecting the internal network. Users can crash the machine. 3. Solution Update the package from our FTP server. Please note that we provide a patched 2.2.14 kernel to ensure stability and not the 2.2.15 kernel. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (NOTE: the 6.4 updates fit 6.1 to 6.3 as well) 765e268875a7716f681c14389a1c9b9b ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/k_deflt.rpm be6ee213f0cafd4dac5c51a2a8d100f0 ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/k_eide.rpm b900eb9f47c94df5cc15721e5f96a58e ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel/k_i386.rpm 37deca6ee856c3242a13c2a24f32fc7f ftp://ftp.suse.com/pub/suse/i386/update/6.4/d1/lx_suse-2.2.14.SuSE-24.i386.… ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are sent to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. 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 iQEVAwUBOSLptXey5gA9JdPZAQFAswf+L1yoW+eVDCmBDeBHbVqZMb+/X52dh391 jcQ4XAT5gnkuWpqyy7XhvFUqnh555SqNssdgtoqpGYdCoH9tmG4QOY/aK0oRcMee ttZfmqD/+SWJdS970sdr75t61/m/iqvVmLemtRnYgXjDOI2e1RgTTHK7eEvDgMlA F9eB1BPa4YsbtAtsh5HOPRRfgDUjbp5Cfss2mMNRwL1NEX3RkVug8dePM3zvQNVy S1+hCsMkuvHtzwGegsOh0Ix8DVDDDSMh1ZV7i6ECAaH1/10Vw7Osp0swEP1VkZ6/ nL1tZKA2kDtHpCtPi3Z4oQNbMdDuKAaFD/eLx7UvMdCjjnf8GbUNkA== =BFxK -----END PGP SIGNATURE-----

1 0