January 2000 - openSUSE Security - openSUSE Mailing Lists

SSH Authentication
by Joao Reis 18 Nov '02

18 Nov '02

Hi! I implemented a ssh conection from the outside to my intranet. This ssh requires a username and a password. In terms of security what is more secure: require authentication (username and password) or having the public key of each user that connects to our intranet in the authorized public key lists (in this case there is no need for username and password)? In the second case there is no need of authentication and only the users wich have the public keys in the list are allowed to enter in my intranet. This second solution is a good solution or that brings other security problems ? Thanks. -- Farewell. "Keep your friends close, but your enemies closer." "Do or do not. There is no try" - Yoda João Reis -------------------------------------------------------

2 1

multi-services server securing
by Gediminas Grigas 16 Aug '00

16 Aug '00

Hello there, I feel erroneusly (?) secure after .host.denyed in.telnetd and in.sshd from everywhere except one pc, which is denying all exept keyboard. I belive that if i can keep hosts.deny and hosts.allow files safe, and from time to time patch most actual security holes i`ll be conditionaly safe. Em i wrong? Probably I do. I just cant imaginate how system can be cracked in lower stage, so that is my problem. I heard that inetd is very insecure, and some peoples using tcpd (or soundlike). I run harden_suse, but was forced to answer 8/10 to no, as my server should provide a lot of public services, and have world writible directories as well. And thats right - this script was developed not for systems like mine one. However i`ll run SuSE-firewall-3.0 script, to make my system even stronger. But thats all. I dont know what can i do else. I should keep folowing services open: httpd; smptd; pop3d; ftpd; snmpd; named; inetd; sshd; nscd. So if you know how to keep them at minimal risk, or know some holes at those, i would be very gratefull for any info and/or tips. I dont ask to do work for me - link to good manual would be nice too. By the way i have SuSE 6.3 (2.2.13). Thanks in advice. Sincerely Yours, Gediminas Grigas mailto:gedas@kryptis.lt

5 5

AW: [suse-security] POP3 with Outlook SSL
by F. Spitzer, GEOSYSTEMS 04 Feb '00

04 Feb '00

Thanks for your help. I am using SSLWRAP now. It's working fine and it's also very easy to configure (read README.SuSE in /usr/doc/packages). Bye Fritz -----Ursprüngliche Nachricht----- Von: Holger Woehle [mailto:Holger.Woehle@ITELLIUM.com] Gesendet am: Montag, 31. Januar 2000 12:37 An: f.spitzer(a)geosystems.de Betreff: AW: [suse-security] POP3 with Outlook SSL -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hallo Fritz, you can use SSLWRAP. It comes to you with SUSE-Linux since 6.1. It belongs to the sec (security) Packages. After installing it, you have to create a key/certificate pair and modify your /etc/inetd.conf & /etc/services (see below) and kill -HUP inetd ... Pretty simple, isn't it ? btw. Don't be confused about my inetd.conf. I am using qmail & qmail-pop3d. You only have to insert the pop3s line. cu Holgi inetd.conf : pop3 stream tcp nowait root /var/qmail/bin/qmail-popup qmail-popup itmail.itellium.nvag.de /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir pop3s stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -cert /usr/ssl/certs/annina.pem -port 110 services : # # Secure Ports: smtps 465/tcp # smtp protocol over TLS/SSL nntps 563/tcp # nntp protocol over TLS/SSL imaps 993/tcp # imap4 protocol over TLS/SSL pop3s 995/tcp # POP3 protocol over TLS/SSL ftps-data 989/tcp # ftp protocol (data) over TLS/SSL ftps 990/tcp # ftp protocol (control) over TLS/SSL - -----Ursprüngliche Nachricht----- Von: F. Spitzer, GEOSYSTEMS [mailto:f.spitzer@geosystems.de] Gesendet: Montag, 31. Januar 2000 10:19 An: suse-security(a)suse.com Betreff: [suse-security] POP3 with Outlook SSL Hi, I am wondering if anyone has an idea how to implement a POP3-concention over SSL from Microsoft (Outlook 98, Outlook-Express) on a Linux mailserver -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.5.3i for non-commercial use <http://www.pgpi.com> iQA/AwUBOJVlyKwDHGNKekZYEQINgQCgpMCsb7+TMBi7ufPM1USF2Yt/5pQAoKRg nYIghUiA6cEv4f26q/z0lJ8q =OUkg -----END PGP SIGNATURE-----

7 11

RE: [suse-security] language barriers
by Paxton, Michael 02 Feb '00

02 Feb '00

Would it be feasible to have a formal "header" that would be part of all original posts that should include succinct information (along the lines of Kernel version, Product version, brief vulnerability type(s) (eg Buffer Overflow, root compromise ) etc) to keep some key information as unambiguous as possible and a policy that all translations should be identified as either automatically or manually produced and should ALWAYS have the original message attached - hopefully you can limit the chance of a translation error to discussion or debate sections of messages making it more likely an error will be embarassing rather than fatal and including original text means a poster is less likely to feel misrepresented. I submit my entry as the longest sentence of 2000 .. any challengers? Michael Paxton Australian Institute of Health & Welfare > -----Original Message----- > From: John F. Eldredge [SMTP:eldredge@poboxes.com] > Sent: Monday, January 31, 2000 3:14 PM > To: 'Steffen Dettmer' > Cc: SuSE Security MailList (E-mail) > Subject: RE: [suse-security] language barriers > > > -----Original Message----- > > From: Steffen Dettmer [mailto:steffen@dett.de] > > Sent: Saturday, January 29, 2000 9:17 PM > > To: suse-security(a)suse.com > > Subject: Re: [suse-security] language barriers > > > > * cogNiTioN wrote on Sun, Jan 30, 2000 at 00:38 +0000: > > > On 30 Jan 2000 brian-suse(a)stech.cx wrote: > > > > > > > I've had enough of this "talk in english or be flamed" > > stuff. We need to > > > > have a system of translation set up. > > > > Well, of course, since this it's an english list, german (or > > other) language is off-topic. Flames are off-topic too. So far. > > Do you think it's a big problem to have native languages in a > > security list? Most of the stuff we have to read is english > > anyway, most postings concerning security issues are written in > > english, and need to be very actual, so translations are a little > > bit late usually... > > Someone suggested running non-English posts through the Babelfish > automatic-translation site. While this is better than no translation > at > all, I hope that someone familiar with both languages would > double-check > such a message before it was posted to the mailing list. Given the > current > state of the art for computer-aided translation, I wouldn't want to > reconfigure my computer solely on the basis of a computer-translated > document. Subtle translation errors can have major consequences. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com

2 1

language barriers
by brian-suse＠stech.cx 02 Feb '00

02 Feb '00

4 3

Marc Heuse's firewall package and SAMBA
by Arjen Runsink 31 Jan '00

31 Jan '00

At the moment I am running version 1.8 of Marc Heuse's firewall configuration scripts. I use this at home on a superduperdoitallwithoneoldcomputer box that does DNS, SAMBA, DHCP and a lot of other stuff that I think it needs to do. The problem is in the SMB and NMB services it runs. It deny's packetes that were broadcasted from itself from these ports (137:138) and IP 192.168.0.1 an coming back to 192.168.0.255 Now I do not have a problem with the denying, but the problem is they get logged. Since this system will run on 24h/24h basis this does fillup my logs and the box does not go into a powersave modus. Tonight I will install version 1.9 of the script and I am wondering if I can make a small change somewhere to relieve myself of this logging. BTW. I know that a box is less secure the more it has running but I just want my own "onedoesitall" BB, Arjen -- Sell what you use, use what you sell.

2 1

Re: [suse-security] SuSE firewall script + UDP ports
by Jan Niemann 31 Jan '00

31 Jan '00

Hi Juergen, "Jürgen Mell" wrote: > > Hi folks, > > I would like to set up a firewall using the firewals 1.4-6 > packet on a 2.2.14 kernel. > My problem is, that I want to use nameserver services from > the (insecure) internet and time server services. For the > time servers, I have to have an open UDP port 1026 for > incoming UDP connections. > If I set FW_UDP_ALLOW_INCOMING_HIGHPPORTS = "dns 1026" I > get error messages, which are caused by a special handling > of the string 'dns' in the script. Up to now, the only > solution I have found is to set that variable to 'yes', but > that opens all my high UDP ports, and would really prefer > to have only those ports open, which I really need. > Is there a better solution available? have a look at /etc/services port 53 is named 'domain', not 'dns' using domain instead of dns should do the job. !! dns also makes use of tcp connections !! see http://www.rustcorp.com/linux/ipchains/HOWTO-5.html (a very good howto) regards Jan Niemann

1 0

Re: [suse-security] ftpd
by Security Webmaster OKDesign oHG 31 Jan '00

31 Jan '00

-----Ursprüngliche Nachricht----- Von: Sebastian Seitz <sebastian.seitz(a)berlin.snafu.de> An: Security Webmaster OKDesign oHG <security(a)okdesign.de> Cc: SuSE-Security-List <suse-security(a)suse.com> Datum: Sonntag, 30. Januar 2000 04:41 Betreff: Re: [suse-security] ftpd >first of all, chroot is crap. every idiots exploids breaks it. second >thing: you remembered about ls and its libaries... ? :P Hi, chroot'ing anonymous logins is standard behaviour of wu.ftpd distributed with SuSE (at least AFAIK), so "ls and its libraries" and all the other necessary commands are working fine. and about the security-level of chroot: well, maybe there are enough folks around being able to break it. But at least its a little bit of security stopping the not-so-experienced users. And even the experienced ones would need a little of time to break it. I won't have anything really valuable on the server, so why should anyone make afforts to break it ? BTW, what has this to do with my question ? --- Stephan

6 7

VPN zwischen 2 PC im Internet
by Torsten Behne 31 Jan '00

31 Jan '00

Hi ich versuche seit einiger Zeit eine sichere Verbindung zwischen 2 PCs die permanent am Internet hängen zu erzeugen. Mit ssh 2.x.x habe ich auch schon einige Erfolge gehabt. Allerdings gibt es da ein paar Nachteile. Bei ssh habe ich auch immer eine Shell auf, das brauche ich nicht und halte es für gefählich. Ferner muss für jeden Port den ich brauche ein ssh-client laufen, ist zuviel. Ich möchte VPN nutzen. Nun zu meinem Problem : Ich finde nur Informationen wie ich eine VPN verbindung per pppd (o.Änhliches) erzeugen kann. Nun sind allerdings beide Rechner pemanent am Internet, bei verschiedenen Providern, und da gibt es keine Einwahl. Jemand einen Tip wie das mit SUSE 6.2 o. SUSE 6.3 geht ? mfg Torsten -- mailto:behne@tdance.de http://www.tdance.de Nickname : Lucky[tm]

6 6

SuSE Security Announcement - lprold-update
by marc＠suse.de 31 Jan '00

31 Jan '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement (update) Package: lprold < 3.0.48 Date: Tue, 21 Jan 2000 12:06:11 GMT Affected SuSE versions: all including 6.3 Vulnerability Type: local and remote vulnerabilities SuSE default package: yes Other affected systems: all unix systems using lpr(-old) ______________________________________________________________________________ UPDATE INFORMATION: We apologize for the wrong md5 checksums in our original advisory. You can find the correct checksums below. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (For SuSE 6.0, please use the 6.1 updates) ea107e004f8c101421a8b3951e7237fe ftp://ftp.suse.com/pub/suse/axp/update/6.1/n1/lprold-3.0.48-0.alpha.rpm 8a175ed07a65ef4ea9c88a408aef1e4b ftp://ftp.suse.com/pub/suse/axp/update/6.3/n1/lprold-3.0.48-0.alpha.rpm a40c4313756d5b3870fd4bd90e74bc32 ftp://ftp.suse.com/pub/suse/i386/update/6.1/n1/lprold-3.0.48-0.i386.rpm 13fbf962761751a5a8eec000da26202f ftp://ftp.suse.com/pub/suse/i386/update/6.2/n1/lprold-3.0.48-0.i386.rpm 52b8bc00d744995f13b4f35da2c6cb5d ftp://ftp.suse.com/pub/suse/i386/update/6.3/n1/lprold-3.0.48-0.i386.rpm ______________________________________________________________________________ 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 send 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 iQEVAwUBOInUWHey5gA9JdPZAQH8AQgAkFLtyAs9lVe+MqSKE5mPK45D+H9dTOd1 dvkYnP1xpvSZQZ+P7IKnahxjvdHQlVNOhg92SoWJAgfasvJiz/DitQjgyYHWazdx m49KJfOHKrYVKVYjIlg3b0+5nliEpOYwMWM9yOfyRw008xDmUknn0A5RG0cy4Atv PxhycX9tsEXmycfn9pxdrKBWzt5h7PMBLFtiGdENnIa6kTXIe4Z6e/M9TfCcTP5B 4IDpVWNpJr75gDI7ZbR7n3YjNqBxqdKDfa2B/FqLefZSUx6m6OKgAyDKgIesYRf1 DoQ0x+m0re0TBQgnKiHhjoyJqDVxnoDV0MoQDcULHS8Us1C/dWEyFw== =pGuv -----END PGP SIGNATURE-----

4 3