August 2000 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] Problems with YaST+sendmail
by Simon 04 Aug '00

04 Aug '00

--- Christian Mudra <c_mudra(a)informatik.uni-kl.de> wrote: > It's annoying to re-install a working sendmail.cf > each time I use YaST, > especially as there a several linux machines in our > workgroup running. > > Any ideas to prevent/fix these behaviours? Try "Do not install /etc/sendmail.cf" option, in sendmail configuration under Yast. Or just change SENDMAIL_TYPE to "no" in /etc/rc.config.d/sendmail.rc.config. Greetings, Simon. =============== Dr. Simone Grabstein listuser(a)egontek.net ===============

1 0

/proc
by mgribov＠kplab.com 04 Aug '00

04 Aug '00

Hi, as one of security meausures, I learned that it is a good idea to do chmod 550 /proc/sys and chmod 550 /proc/net. First question I have, is this true? It seems right, because ordinary users cannot view network or system information, which is not a bad thing. Second question is, I implemented the above, but after a reboot permisions were back to standard ( I believe 555). How come? Thanks Max

3 4

Antwort: [suse-security] Problems with YaST+sendmail
by andreas.baetz＠herma.de 04 Aug '00

04 Aug '00

Christian Mudra wrote: > I experienced problems with YaST and sendmail. Every time I use YaST > to change the installation (Choose/Install packages), change something > and leave this submenu back to the main menu, a new sendmail.cf > is written. When I change something else with YaST, e.g. System > administration, a warning is written, that sendmail.cf was edited by hand, > and _my_ sendmail.cf is not overwritten. Did you check that SENDMAIL_TYPE="no" is set in /etc/rc.config.d/sendmail.rc.config ? Then it shouldn`t touch your sendmail configuration. Keep in mind that you have to have this file though, since it is read in /sbin/init.d/sendmail (you need at least the SENDMAIL_ARGS). Andreas ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been scanned for the presence of computer viruses. **********************************************************************

1 0

Problems with YaST+sendmail
by Christian Mudra 04 Aug '00

04 Aug '00

Hi, I experienced problems with YaST and sendmail. Every time I use YaST to change the installation (Choose/Install packages), change something and leave this submenu back to the main menu, a new sendmail.cf is written. When I change something else with YaST, e.g. System administration, a warning is written, that sendmail.cf was edited by hand, and _my_ sendmail.cf is not overwritten. Here in our installation it is needed not to use the MX-record for smtp, for which I don't see a way to make that known to YaST. Also another behaviour: Using an adapted /etc/mail/linux.mc for creating a sendmail.cf file I added a define(`SMTP_MAILER_FLAGS', `0') to /etc/mail/linux.mc. Compiling with m4, this line is not taken care of, I get exactly the same result with and without that define. Both with Solaris 2.5/2.7 it works and adds the 0 to the mailer flags. (e.g. Msmtp, P=[IPC], F=mDFMuX0, S=11/31, R=21, E=\r\n, L=990, ..) ^ It's annoying to re-install a working sendmail.cf each time I use YaST, especially as there a several linux machines in our workgroup running. Any ideas to prevent/fix these behaviours? Greetings, Christian. PS: I'm using YaST 1.05.2 on SuSE 6.4. ---------------------------------------------------------------------------- Christian Mudra Just remember what your mother always told you: mudra(a)informatik.uni-kl.de "When you open windows you let in bugs". AG Wiehagen, Universität Kaiserslautern

1 0

Problems with /var/log/messages
by Geert-Jan.Laat-de＠dsm-group.com 04 Aug '00

04 Aug '00

I'm having the following problem: Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered. The only solution I found sofar is rebooting the machine, there has to be a simpler solution ! Best regards, Geert-Jan de Laat

6 6

SuSE Security: miscellaneous
by Roman Drahtmueller 03 Aug '00

03 Aug '00

-----BEGIN PGP SIGNED MESSAGE----- August 3rd, 2000 This notice addresses the latest security advisories from various Linux Vendors as well as private contributors. The list of packages: netscape knfsd system user account nobody pam_console gpm openldap mailman cvsweb.cgi kon2 There will be SuSE Security Announcements for the packages where work is in progress as indicated in the respective section below. * jpeg buffer overflows in netscape: The latest version of netscape is currently being tested. SuSE netscape rpms contain efficient workarounds against some "morbid" properties of netscape - it is necessary to provide stable packages. These additions are being reworked right now. _________________________________________________________________________ * rpc.kstatd The SuSE package containing rpc.kstatd (other vendors named it rpc.statd) is called knfsd.rpm. An updated package is currently being tested. _________________________________________________________________________ * user `nobody's HOME directory set to / and misconfigured webservers: SuSE Linux used to have user nobody's HOME directory set to /tmp for years. Starting with SuSE-7.0, it will be set to /var/lib/nobody . Apache, as distributed with SuSE, is configured `UserDir public_html' and is therefore not vulnerable for the http://machine/~nobody/-problem. However, we encourage admins to change this user's home using the commands mkdir -p /var/lib/nobody chown nobody.nogroup /var/lib/nobody usermod -d /var/lib/nobody Make sure that you move files belonging to user nobody from the former location to the new home and that you don't rely on the old absolute path in your scripts. _________________________________________________________________________ * problems around pam_console: SuSE Linux does not contain the said pam-module because it isn't included in the official pam release. The idea of it is intriguing, but we have decided not to include the module into the distribution as a consequence of the problems that accompany its use. See Linux-Mandrake Security Update Advisory ID MDKSA-2000:029. _________________________________________________________________________ * gpm DoS, setgid() return value: We ship a slightly older version of gpm because of some grief with the latest versions. The vulnerabilities in gpm have been addressed to the fully necessary extent back in April 5. As mentioned above, there is no pam_console module that could change the ownerships of the gpm control socket /dev/gpmctl. By consequence, a local denial of service attack against gpm is possible. However, we believe that the most effective measure against this is userdel(8), since hogging disk space/performance, CPU, bandwidth etc is still possible in the wild even with appropriate permissions on the gpm socket. _________________________________________________________________________ * modes of openldap package files: The files are installed 755 or 644. There is no problem with this package in SuSE-Linux. _________________________________________________________________________ * mailman problem cvsweb.cgi (TurboLinux Advisory ID#: TLSA2000016-1): kon2 (Linux-Mandrake Security Update Advisory ID: MDKSA-2000:028) SuSE-Linux either does not contain these packages or the files therein causing the publically announced security vulnerabilities. _________________________________________________________________________ Regards, Roman Drahtmüller. - -- - - | 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) | - - 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 iQEVAwUBOYnpPney5gA9JdPZAQEUOQf8DKKIHhn7oUvTW5Ol7gww2/aIwXmG2e5c 4iKyQgGoU94YZURlGxRRI5Zf1Yydfj8JrKiUvnwxRCcQF2WWWCWkGNqQkJzt+c00 BiEyU16fklxMV17JeI6zmb9rTrne0JftjAycAPubzYeDpheVDbmPtGvotanRwVUn j2zaE3uLIBjie2025q8nZnYeTylXua4ulnTW0+PFDZnWgyxCMXvvu/1Lsf715vi6 1M6L78IlYkng5OV4OTeBVY5gm7sdy3eg/CQ/FiEHmIDgI33ywRVGQhXqhpp3QOrX OA7UoIl6xAhNHBEX9lSPwNpfFaTsQrEAWVbihnzFYSLlBz3kxd1jdQ== =5DM/ -----END PGP SIGNATURE-----

1 0

Re: [suse-security] Problems with YaST / Usermanagement
by Simone Grabstein 03 Aug '00

03 Aug '00

--- Stefan Suurmeijer <stefan(a)symbolica.nl> wrote: > Have you checked the daemon startup script > (/etc/rc.d/nscd)? Mine looks > ok, but maybe in your distribution there is a typo > which causes it to not > check for a START_NSCD=yes. > Just a thought. Good point, but here's what I found in /sbin/init.d/nscd [...] # Force execution if not called by a runlevel directory. test $link = $base && START_NSCD=yes test "$START_NSCD" = yes || exit 0 test -x /usr/sbin/nscd || exit 0 [...] Greetings, Simone ===== ===================== Dr. Simone Grabstein gsimon(a)rocketmail.com ===================== __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/

2 1

Re: [suse-security] SuSE security reputation, etc..
by Simone Grabstein 03 Aug '00

03 Aug '00

--- rhoerbe(a)netpromote.co.at wrote: > A very common setup for a system with remote > maintenance is to use SSH for > shell access. However, this is insecure, if you keep > using ftp and pop for > the same account with the same password. My setup > is, to use separate > accounts for different services. Quite inconvenient, > unless you configure > different password-dbs for ftp/pop/samba. Actually, while remote telnet should probably be disabled completely, I find that in most cases it is not so inconvenient to have separate accounts for those users who need ftp (GUEST/chroot'd accounts, of course!). Besides, one might also use scp. A partial solution to the pop database problem is switching to APOP: the only real inconvenience i found is having users adopt a client which supports this authentication method (for Windows, I know Eudora - but NOT Outlook...). As for Samba, well, this is easy: it already has a separate password database (/etc/smbpasswd). One should only remember to enable encrypted password support and add users with "smbpasswd -a". Greetings, Simon. ===== ===================== Dr. Simone Grabstein gsimon(a)rocketmail.com ===================== __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/

1 0

Re: [suse-security] Problems with YaST / Usermanagement
by Simone Grabstein 03 Aug '00

03 Aug '00

> The problem that you encounter is most likely caused > by incoherent caching > of the nscd. You could change some settings in > /etc/nscd.conf, or you > disable it completely (since you don't use NIS(+) or > alike) in > /etc/rc.config. What about NSCD starting up AUTONOMOUSLY?! I have it explicitly disabled in the /etc/rc.config of a 24/7 server of mine, and after a while I find 7 (SEVEN) instances of /usr/sbin/nscd up and happily running! I've no idea about who or what invokes it. :-( ===== ===================== Dr. Simone Grabstein gsimon(a)rocketmail.com ===================== __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/

4 3

Fwd: Re: [suse-security] Problems with YaST / Usermanagement
by Matthias Krawen 03 Aug '00

03 Aug '00

Moin, > > A cd '~test' or cd '~test2' ends with following error-message: > > x:/webroots # cd ~test2 > > bash: cd: ~test2: No such file or directory >The problem that you encounter is most likely caused by incoherent caching Isn't it just the wrong path ? Try ~ or ~/test2 sorry, but three times misstyped... ? MfG Matthias Compositiv EDV- und Kommunikationslösungen, PC-Service Matthias Krawen Peiffersweg 9 22307 Hamburg Tel: 040 / 611 673 - 40 EMail: info(a)compositiv.de Fax: 040 / 611 673 - 41 http://www.compositiv.de

1 0