June 2001 - 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

PGP keyserv
by jochen mader 18 Jul '01

18 Jul '01

Hey, I've been playing around with GPG for some time now and I'd like to install a keyserver on our server to allow people to exchange their keys easily. Which servers would you suggest to use?

2 1

RE: [suse-security] IPSec system design questions (slightly OT)
by Ed 11 Jul '01

11 Jul '01

I would appreciate comments on some IPSec design issues. A transportation manufacture recently requested proposals for a Linux based system to put Internet and email services on their vehicles. This system would let passengers plug a laptop into the on board network. A number of protocols were specified including IPSec. They also specified Linux kernel 2.4.x. It seemed to me that they intended IPSec to be used from transportation vehicle to satellite to fixed server. The VP of Technology here has recently discussed using IPSec on board vehicle from web server, email server and file server to passenger seats - typically many hundreds of passengers. The transportation manufacture specified: "The file server will not preclude a user from initiating and completing a supported VPN connection from their user device through the transportation manufacturer network using the IPSec and PPTP protocol, as a minimum. The system should allow the user to switch between IPSec VPN and non-VPN without need of rebooting the laptop. The system will only pass IP based protocols between the laptop passenger interface and the file server. Passenger laptops will be assigned default gateway address via DHCP. The default gateway should reside in the server. The system will by default, route user outbound packets to a configurable gateway." Is it feasible to support IPSec from a passenger's laptop when implementations of IPSec vary and either ESP or AH modes might be used? If feasible what performance hit would be involved? I have heard estimates of 40% when encryption is used (mileage may vary I suppose based on CPU speed and resources). I assumed that a "default gateway at the server" implied that the IPSec pipe started or ended there. Since the transportation manufacturer called out other security requirements to the passenger seat, I assumed that IPSec to the seat was not required. Examples of requested security: "Multiple passengers will not be connected to shared physical media. Laptop users will not be permitted to view packets from another user's network session. Each passenger's laptop's user interface will be isolated to its own link layer subnetwork. The passenger laptop will not be able to access unauthorized IP address. The system will be immune to DoS attacks. The server will ensure that passenger laptop's can only pass packets with that user's assigned IP address." My main question are, 1) "Does the transportation manufacturer really want IPSec extended directly to the passenger's laptop?" 2) "Would it even be feasible to automate re configuration of IPSec software running on a passenger laptop to avoid compatibility issues?" 3) "What would the performance cost be of running ESP or AH IPSec on a laptop that might also be viewing an MPEG2 movie, web browsing or playing a game?" I would appreciate any opinions you care to offer. The job you save may be my own. <s> Thanks, Ed

5 6

setting up firewall in 7.1
by twowitchesinthelight＠btinternet.com 03 Jul '01

03 Jul '01

Hi All, Another newbie question. I edited my inetd.conf and commented out ftp, telnet, shell, login, pop3, finger and swat and rebooted. Everything seems to work ok. nmap -sT -v my ip shows these 22 ssh 37 time 111 sunrpc 515 printer 1024 kdm 6000 X11 nmap -sU my ip shows these 37 time 111 sunrpc 517 talk 518 ntalk Questions are these. First, is what I commented out ok? secondly, is it safe to comment out talk, ntalk, and time in inetd.conf as well? Secondly...how about ssh,sunrpc,printer and X11? Is it safe and where do I shut them down at? If you could just give me a site that would explain this to me I would be very grateful. As I said, I am new and just don't want to make any mistakes configuring or to take an unsecured machine out on the net. Thanks in advance, Dallam

3 2

AW: [suse-security] Ipsec + firewall
by Schulz, Wolfgang 03 Jul '01

03 Jul '01

Hi! The problem with the firewall + IPsec is still not solved. To split the setup problems I have tried to configure different test environment: a) Only 2 IPsec gateways b) 2 IPsec gateways with the firewall script - no masquerading c) 2 IPsec gateways with the firewall script with maquerading Setup a) is working but with setup b) I have already problems: The tunnel is established but I still cannot ping to the net on the other side. I checked the firewall.log for denied packets but couldn't find any entry. Also another strange phenomenon: If I boot the machine with the firewall script and stop afterwards the firewall script by hand the ipsec connection doesn't work too. What could be the problem with my setup. Thanks for your help Wolfgang > -----Ursprüngliche Nachricht----- > Von: Tobias Gewinner [mailto:crt@tmt.de] > Gesendet: Dienstag, 19. Juni 2001 23:32 > An: suse-security(a)suse.com > Betreff: Re: [suse-security] Ipsec + firewall > > > On Tue, Jun 19, 2001 at 05:55:09PM +0200, Schulz, Wolfgang wrote: > > Hi list! > > > > As soon as we start the firewall script (Version 4.1) ipsec > doesn't work > > anymore. > > I remember having the same problem in the past. AFAIK the > firewalls must > accept incoming requests from the outside on port 500/UDP. Also the > firewall doesn't know the net behind his partner, so any input from > these IPs to the internal net is denied. > > I remember that I set the following ipchains rules (or something like > that) manually on both machines: > > On firewall A this (may have) looked like > > ipchains -I forward -b -s [local net B] -d [local net A] -j ACCEPT > ipchains -I input -b -s [local net B] -d [local net A] -j ACCEPT > ipchains -I output -b -s [local net B] -d [local net A] -j ACCEPT > > and on firewall B you must swap the networks, of course ;-) > > After that it worked fine for me. I think you can set these rules > in /etc/rc.config.de/firewall-custom.rc.config > > Greetings! > -- > ----------------------------------------------------------------- > Tobias Gewinner <gewinner(a)tmt.de> > Fachinformatiker i.A. TMT InterNETworks GmbH > Phone: +49921560716-0 Maxstrasse 4 > Fax: +49921560716-18 D-95444 Bayreuth > ----------------------------------------------------------------- > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com >

2 1

Re: [suse-security] iptables and squid
by Stefan_Walther＠gehag-dsk.de 01 Jul '01

01 Jul '01

DIRK WROTE: Helo Stefan, helo folks, I tried that one but it`s the same thing. Realy curious is, when the firewall script starts I get an error message with reference to "Bad argument squid" even I had declared in /etc/services. The same one, when I use the port nummer."Bad argument 3128" Any idea??? Thanks and regards Dirk Hello Dirk, hello folks, I don't know if it works but you can try this, maybe you can send me your log and the full error listed at you monitor: #SQUID internal lan iptables -A INPUT -i $IF_LAN -p tcp --dport 3128 -j ACCEPT iptables -A OUTPUT -i $IF_LAN -p tcp --sport 3128 -j ACCEPT #HTTP iptables -A INPUT -i $IF_WAN -p tcp --dport 80 -j ACCEPT iptables -A OUTPUT -i $IF_WAN -p tcp --sport 80 -j ACCEPT #DNS iptables -A INPUT -i $IF_WAN -p udp --sport 1024:65535 --dport 53 -j ACCEPT iptables -A OUTPUT -o $IF_WAN -p udp --dport 53 --sport 1024:65535 -j ACCEPT iptables -A INPUT -i $IF_WAN -p tcp --sport 1024:65535 --dport 53 -j ACCEPT iptables -A OUTPUT -o $IF_WAN -p tcp --dport 53 --sport 1024:65535 -j ACCEPT just try this (use the portnumbers not names in /etc/services). if this doesn't work, you should try to install proxy and firewall at to different machines. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: +4930/89786448 Funk: +49172/3943961

2 1

How to shut down firewall
by Steve Collins 30 Jun '01

30 Jun '01

I have a standard install running SUSE 7.1 on PC hardware. It uses a 56k modem to talk to Earthlink via ppp. I believe it has firewall running since (1) I can see a couple of messages about "personal-firewall" go by during the boot sequence and (2) if I try to telnet or ssh into the box from the internet, I see messages in /var/log/messages about the connect being rejected. I would like to temporarily disable enough of the protection to allow incoming ssh, telnet, and ftp connections. I tried modifying settings in /etc/rc.config.d/firewall.rc.config to allow the desired services, but to no apparent effect. I then tried to disable the firewall completely but found that my rc.config already had the line START_FW ="no" and yet some firewall clearly is running. Any pointers to definitive docs on the SUSE 7.1 firewall setup? I don't seem to be able to figure out what I need from the printed manuals. Haben Sie viel Spa� Steve Collins __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/

3 2

Re: [suse-security] SuSEfirewall 2.1 and NetMeeting 3.01
by michael.ryan＠storm.ie 29 Jun '01

29 Jun '01

Ok, I have added the ip_masq_h323.o module and re-started masquerading to load the module. SuSEfirewall is still in place as before. I can now use NetMeeting 3.01 on a PC to connect to a hosted meeting outside the firewall. My question now is how do I allow external NetMeeting clients connect to a NetMeeting host on our internal/private network. Any help much appreciated :) MR Torsten Mueller To: michael.ryan(a)storm.ie <torsten@arch cc: suse-security(a)suse.com esoft.de> Subject: Re: [suse-security] SuSEfirewall 2.1 and NetMeeting 3.01 06/29/2001 12:41 PM Hey, i use a setup with a netmeeting kernel module and portforwarding. Look at the masquearding howto, there's the lnk to the module. Greetings Torsten michael.ryan(a)storm.ie schrieb: > > Trying to allow external sources connect to a machine on our private > network which is acting as a NetMeeting host. > Gateway is a SuSE 6.4 box, ip masquerading up and running SuSE firewall 2.1 > Anyone done this before? any advice on how this can be done securely? > > tnx in advance, > > MR > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com

2 1

NFS problem
by Selcuk Ozturk 29 Jun '01

29 Jun '01

Hi, I just upgraded my Suse 7.0 2.2.16 kernel server to 2.2.19 kernel. Everything seems to be working fine except an NFS quirk. When I try to mount the nfs shares on this machine from my Sun Solaris 7 server with the automounter, I am getting a "Permission denied" error and fail. Looking at the log on the Sun server I see: automountd[5391]: poseidon server not responding: RPC: Pro gram/version mismatch on the Linux log: Jun 28 09:54:33 poseidon mountd[419]: export request from x.x.x.x When I use the mount command like "mount poseidon:/ /mnt/tmp" then it works. But, I see in the Linux servers log: Jun 28 09:58:14 poseidon kernel: svc: unknown program 100227 (me 100003) I am using knfsd. Anybody know any fix? TIA Selcuk

2 3

SuSE Security Announcement: xinetd
by Sebastian Krahmer 29 Jun '01

29 Jun '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: xinetd Announcement-ID: SuSE-SA:2001:022 Date: Friday, June 29th 2001, 13:26:55 CEST Affected SuSE versions: (6.0, 6.1, 6.2), 6.3, 6.4, 7.0, 7.1, 7.2 Vulnerability Type: remote code execution Severity (1-10): 7 SuSE default package: yes Other affected systems: All systems using xinetd Content of this advisory: 1) security vulnerability resolved: xinetd buffer-overflows 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 Zen-parse has reported a bug to Bugtraq which allows remote attackers to overflow a buffer in the logging routine of xinetd. During investigation we found that more problems exist within xinetd. Xinetd provides its own string-handling (snprintf()-like functions) routines and fails to handle length arguments of 0 properly. Instead of an immediate return it assumes 'no limit' for writing characters to the target-buffer. This can lead to overflows and arbitrary remote code-execution. Additionally xinetd now sets the correct umask before starting other deamons. Please update the packages immediately, kill the old deamon and start the new xinetd deamon with the /etc/rc.d/xinetd start command again if you need it running. Regardless of the bugs in xinetd, please make sure you only run as many services as needed. i386 Intel Platform: SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/xinetd-2.1.8.8p3-139.i386.rpm a8122710a857e49a356b0786c8aad9eb source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/xinetd-2.1.8.8p3-139.src.rpm 90187bd35f931f07ba72b54c16c1549c SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/xinetd-2.1.8.8p3-140.i386.rpm 346868fe76e17d17d87dadbac4c032bb source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/xinetd-2.1.8.8p3-140.src.rpm 6656be9789888da5b1b37dc1aa9c69a9 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/xinetd-2.1.8.8p3-140.i386.rpm ff001b856db620213608dac1c88ebfbe source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/xinetd-2.1.8.8p3-140.src.rpm 627d2f09d9d4607f31e1902eee4e0cb5 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/xinetd-2.1.8.8p3-139.i386.rpm ef4697d57a6ceb5e6a55bde51268b92a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/xinetd-2.1.8.8p3-139.src.rpm 1384b48ed19204324d4a8c2f75d3ea20 SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/n1/xinetd-2.1.8.8p3-141.i386.rpm 3c29917f0688aa7509f98b0a00a38eed source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/xinetd-2.1.8.8p3-141.src.rpm b7f8cc1e5a7d3c2f6c56040c327a4b20 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/xinetd-2.1.8.8p3-89.sparc.r… a78dd53e2da211b8822b4ca86359a6e0 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/xinetd-2.1.8.8p3-89.src.rpm 9b0acb0dacee2962f19057de43d9f421 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/xinetd-2.1.8.8p3-96.alpha.rpm bb2b45d56d2cf54733a20561c8a8e440 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/xinetd-2.1.8.8p3-96.src.rpm 60610276aba8c103a43a40ea0366f675 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/xinetd-2.1.8.8p3-96.alpha.rpm 1e4f0685f380db64025837685f8e79c2 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/xinetd-2.1.8.8p3-96.src.rpm addfd497500387b4de4e2c77ff226e01 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/xinetd-2.1.8.8p3-95.alpha.rpm f39287594d3297d2625f3878be6b7d98 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/xinetd-2.1.8.8p3-95.src.rpm ea727667791cd774a5df8bcb5b8b2870 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/n1/xinetd-2.1.8.8p3-95.alpha.rpm 364120a5e0ba13587efba8c082faafa0 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/xinetd-2.1.8.8p3-95.src.rpm 08c540c506809a9a5b080aa21fe97406 PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/xinetd-2.1.8.8p3-102.ppc.rpm b73446661fe3f5967acd0242e83fb815 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/xinetd-2.1.8.8p3-102.src.rpm c89cb923d3c837e50e7f2efc2c9708d2 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/xinetd-2.1.8.8p3-101.ppc.rpm 01fec52a269c456636bcda0d8401b639 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/xinetd-2.1.8.8p3-101.src.rpm f91f365e3cbedc3de52aab7667db97b2 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/xinetd-2.1.8.8p3-101.ppc.rpm ed8e343b428fe812502195a15d9c4219 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/xinetd-2.1.8.8p3-101.src.rpm a340276cec8a5dedcbcd29e199bef6a1 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - rxvt The rxvt program contains a buffer-overflow which allows an attacker to locally execute arbitrary code under a different group-id. Please update to the newest rxvt packages. - dqs The dsh-program, shipped with the dqs package contains a buffer-overflow which allows local attackers to execute arbitrary code as root. Please update to the newest packages. - pcp A /tmp - race has been found in the pcp package which allows a local attacker to escalate his priviledges. Affected versions: 7.1, 7.2. We thank Mark Goodwin and Keith Owens from SGI who quickly responded to SuSE in this issue and who released a fixed version of the SGI Performance Co-Pilot in response to the security problem. Future SuSE Linux releases will include the most recent version of the package. Workaround: chmod a-s `rpm -ql pcp` /nosuchfile update-package does the same. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security 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 <security(a)suse.com> public key is listed below. =================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the cleartext signature shows proof of the authenticity of the text. 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 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GZkBogQ57vSBEQQAk/GN+ftr 7+DBlSoixDDpfRnUk+jApGEt8hCnrnjVnPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45 t4E0fKyLVzDerCRFB1swz/mNDxT26DLysdBV5fwNHTPhxa67goAZVrehQPqJEckk IpYriOaYcKpF3n5fQIZMEfMaHEElQhcXML8AoJVXDkJYh7vI8EUB8ZURNLZMEECN A/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6TepRdLZhaylwVF/iu7uIn62ZUL4//NTOC DY7V63qg4iba/fUbOsWtEnGaiE7mQuAlsSWvRspwRA9/g9rdVf3/JdLJrLmKBThe yG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQnJn2euqylHRubEQP/aL53NZK0kBdvrKgf f6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiY I2lTRYT4uMdHuwVC3b4DqAKmoy375FERwHkrMVyKBJslv8QtbAWw5A1CAUseaHo+ 91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1U0UgUGFja2FnZSBTaWduaW5nIEtleSA8 YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUCOe70gQUJA8JnAAQLCgMEAxUDAgMWAgEC F4AACgkQqE7a6JyACspfLACffAYA+NM8NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0 xY7WbKoXs1+72b2AiEYEEBECAAYFAjpwXlIACgkQnkDjEAAKq6TczgCgi+ddhWb7 +FWcfeE6WwPZccqAHowAnjjtRyGwHLQHr5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey 5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk/xGJJREt7V12iSafaRzGuH8xWvIz1bb+ VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6iJXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq 2pudfwljp52lYVM53jgPYEz0q/v3091nlZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU +lDQT2EC6VKaxeWK8pNt6UFDwICRDQxKnlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKN bWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc 9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelxufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr 6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7UVCiSfb9CV38dmeHdPCEEjDUWquFYEnvj 3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qTJzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBE VE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/ 9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiUXpRoFCdglMznbcAyCk9C2wqb2j/D1Z2B eSBaGCSFkR6pRLebnE17LWcu72Iy+r0z+JecbPiyDpDZj4apn7IC81aNFGi7fNIT sHODbwwjiwADBgf/YPvVdzkc8OC7ztacEWCanwylKvxCdKzTDA+DfES6WUYShyiV JvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/pdGy1aKtJZrAnFEsofpmOj8VoqyyFgp/y AGQBp12+mXek7SCZRhuqalDfEMRiWEJ6J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxx QqNQXL6Z3NSxS61p+5n6BseiDUI39xxkKTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwb sklszZt6xbU+R0SjFqTvjPWx6eHfqbmNC9WMDdTjGrXDDKXFp2aYlokfN6It9vsb VlGNlOwHt/JjGoPMxW6Xqj0FLA7/VewgCdXW64hMBBgRAgAMBQI57vSSBQkDwmcA AAoJEKhO2uicgArKSyIAmwUHf/vtKQfcmVg4asR7U6XQl0bAAJ4pO22B5U8UH6IY l2LBCXFqw5+5fA== =Jnnf - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOzxlG3ey5gA9JdPZAQHe3wf/fyRLvSPGLGV1KQQed4eBqqXSxJgZBskB FVgCYtYFUTbcg0cSRjE7yRp1qBYg0jeKLf1PqNoDt+GcVR2HbsG3cvmyW/8ZZUiP tfgd/7lKqDyYBYMMmSOxf16AqUwHp8sVihmBkE8UGKy/2EIu4UBzlMaD4bkbGB+P /T/L5NjIct/yoTKVbksJmQeEW03XfXLG9a9X1LXS/4oR030Rco1I3dVAjHsGkwj/ Ya9zlwz7DfZCOhdeqD5LiCApbzFcn4fRxofyhp/M2DkTQp3650yp0H2/nGBZJ3fH davxTMzZ7m34oC2cTcOMoDeYDjQRX2eYI3bQKlE50v9x/n5XLbfAmg== =vVay -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0

SuSE Security Announcement: samba (SuSE-SA:2001:021)
by Roman Drahtmueller 29 Jun '01

29 Jun '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: samba Announcement-ID: SuSE-SA:2001:021 Date: Friday, Jun 29th 2001 14:45 MEST Affected SuSE versions: (6.0, 6.1, 6.2) 6.3, 6.4, 7.0, 7.1, 7.2 Vulnerability Type: possible remote root compromise Severity (1-10): 7 SuSE default package: yes Other affected systems: systems using samba and the %m macro in the samba main config file Content of this advisory: 1) security vulnerability resolved: samba 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 Michal Zalewski discovered that a remote attacker can write to files owned by root if the samba config file /etc/smb.conf contains the %m macro to specify the logfile for logging access to the samba server. The %m macro substitutes the NetBIOS name - improper validation of this name allows an attacker to write to any file in the system. SuSE Linux distributions do not ship a default /etc/smb.conf config file that contains the %m macro. Therefore, SuSE distributions are not vulnerable to the bug in the out-of-the-box state. In addition to the remotely exploitable bug, there exists another vulnerability which is fixed with the update packages we provide below: temporary files are being handled insecurely so that an attacker with local access to the system can increase her privileges. This error was discovered by Marcus Meissner, Caldera. This specific problem has been fixed with the release of the samba-2.0.9 version. samba release version 2.0.8 intended to correct this local problem, but due to an error, 2.0.9 contained the complete fix. Only the 2.0.10 version as offered for the SuSE Linux distributions 6.3, 6.4, 7.0 and 7.1 fixes all known problems in the samba package. For the recently released SuSE-7.2 distribution we provide an update package to the version 2.2.0a. We thank Martin Walter, CC university of Freiburg, for his helpful contribution in debugging the Large File Support (LSF) of the 7.1 package. NOTES: * We have removed the samba packages from the update trees for the 6.0, 6.1 and 6.2 distributions on our ftp-server. These packages would introduce security risks if installed on a host. * The samba source rpm package in distributions after and including 7.0 generates both the samba.rpm and the smbclnt.rpm package. It is recommended to update both packages for these distributions. Please download the update package from locations described below and check the authenticity of the rpm package file using a method as described in section 3 of this security announcement. Use the command 'rpm -Uhv file.rpm' to apply the update. Special installation instructions: =================================== After successful installation of the update package, it is necessary to restart the samba server. To do this, use the following command rcsmb restart as root. i386 Intel Platform: SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/samba-2.2.0a-0.i386.rpm d0cab6f5d34645dc9e41f2ae0aed8a30 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/smbclnt-2.2.0a-0.i386.rpm aba5da72a8175c2119e82d01184dd320 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/samba-2.2.0a-0.src.rpm 243964fad8bda61039020acf7a13858f SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/samba-2.0.10-0.i386.rpm da1232db9259196a58e7e3b46065e8c8 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/smbclnt-2.0.10-0.i386.rpm a497089893fd375986ab5a031eddaf05 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/samba-2.0.10-0.src.rpm 07705a9cacb7f9f28b434a1e6a6fe3bb SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/samba-2.0.10-0.i386.rpm a20a0241fad9b3381758946e9f9ae16d ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/smbclnt-2.0.10-0.i386.rpm c0194e29ff9f6ae5da8500f6a6250bab source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/samba-2.0.10-0.src.rpm e412b83bbf653023cadbf163a3ec296f SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/samba-2.0.10-0.i386.rpm e740834c08f1a91efed8abfe1ffd1fd1 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/samba-2.0.10-0.src.rpm ed22708ec5fbc14cfdfc0cd45b3033e0 SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/n1/samba-2.0.10-0.i386.rpm da6aeaf7043bc03199e4c1d5c04d3be6 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/samba-2.0.10-0.src.rpm 84e325fc575143a576c42f386c88e44c Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/samba-2.0.10-0.sparc.rpm 5b702a797836de3352c96b0b33297d13 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n1/smbclnt-2.0.10-0.sparc.rpm 00c29e2ff26d00b60a81e095a78623c7 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/samba-2.0.10-0.src.rpm 1d9d41cfeab79ef851cb4666a0259731 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/samba-2.0.10-0.sparc.rpm 48ef896322723e4247b13db719a6d593 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/smbclnt-2.0.10-0.sparc.rpm fdacfbe34e46919515dc54d288b6e56a source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/samba-2.0.10-0.src.rpm b023db5df4e6b26ed8263d61de3c9915 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/samba-2.0.10-0.alpha.rpm 3302ca10f2e779ff168d44bc4280158a ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/smbclnt-2.0.10-0.alpha.rpm 440ff9a0fefb54ac85977e4598e39eed source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/samba-2.0.10-0.src.rpm 49f109c06957f200cd5112dc872273fc SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/samba-2.0.10-0.alpha.rpm 6e68f4d9156238874755bd9bac59d713 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/smbclnt-2.0.10-0.alpha.rpm c1935910e75c956ed8b2ce9e4c324d55 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/samba-2.0.10-0.src.rpm 210dde7e938ff7d1d303e80a13d11673 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/samba-2.0.10-0.alpha.rpm 9d6cf089b447ba4aefe1d70cf2771a22 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/samba-2.0.10-0.src.rpm 377b183857e179772481840caffd7db4 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/n1/samba-2.0.10-0.alpha.rpm e4871d1a0423bec9999fde9a9b85ab23 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/samba-2.0.10-0.src.rpm 51cf42a086a4a26619323311660dbfb8 PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/samba-2.0.10-0.ppc.rpm dfaa395540e2e01b3ccc7177f0f297c4 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/smbclnt-2.0.10-0.ppc.rpm ca9059bfbafe4553ae6bc79dad70ce31 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/samba-2.0.10-0.src.rpm df603b78073673c7f8988639b1cb2c1e SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/samba-2.0.10-0.ppc.rpm 65b2d0e71902afb4f3cafa67f2d5c628 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/smbclnt-2.0.10-0.ppc.rpm a1de2eb26df810831f65af2feb0f12f9 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/samba-2.0.10-0.src.rpm 17777fa091391825ebd9d90018f950bf SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/samba-2.0.10-0.ppc.rpm 4e44aaab59f3c624e77b83bbbc05bb18 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/samba-2.0.10-0.src.rpm 5893c01a4f1ddf8f8d2e77ac8ee785e9 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - Location of update packages on ftp.suse.de/ftp.suse.com: Licensing problems as well as US crypto-software export regulations keep us from publishing update packages that contain cryptographical software on ftp.suse.com, our US ftp server. Bandwith requirements keep us from moving the server to our German location. For these reasons, crypto-packages for SuSE Linux distributions before SuSE-7.1 can be obtained from the equivalent tree on ftp.suse.de. Distributions after and including SuSE-7.1 have their crypto-packages hosted on ftp.suse.com. This was possible with some efforts to remove all non-free cryptographical algorithms from our packages. - qpopper In our last security announcement (SuSE-SA:2001:020 gpg/gnupg) we announced that we investigate the buffer overflow that has been found in qpopper versions before 4.0.3. SuSE Linux distributions are not affected by this bug because a different version is being used. - dqs dex(a)raza-mexicana.org has found an exploitable buffer overflow bug in the dsh program from the dqs package on SuSE Linux distributions. To workaround the problem, do "chmod -s /usr/bin/dsh" and change the files /etc/permissions* to reflect the change. If you do not need the dqs package, then deinstall it (rpm -e dqs). Packages for most of the supported SuSE Linux distributions are available at the usual location ftp://ftp.suse.com/pub/suse/<arch>/<dist> for download and installation/update. Do not forget to change the files /etc/permissions* to remove the suid-bit from the dsh program. Please note that we will not issue a dedicated security announcement for this specific bug. - pcp Paul Starzetz discovered a security weakness in the setuid root program /usr/share/pcp/bin/pmpost. The common library in pcp trusts the environment that has been supplied by the user, regardless of privileged execution or not. By consequence, a user can specify the configuration file and therefore write to files owned by root. The problem is not based on insecurely following symlinks as stated by Paul Starzetz. The pcp package is not installed by default in SuSE Linux distributions. We have provided update packages for the SuSE Linux distributions version 7.1 and 7.2 that remove the setuid bit from the pmpost binary. Versions before SuSE-7.1 were not affected because the setuid bit was not set. We thank Keith Owens and Mark Goodwin from Silicon Graphics for responding quickly and for publishing a new version of the pcp package which will be included in future releases of the SuSE Linux distribution. For more information see the /usr/share/doc/packages/pcp directory of your SuSE Linux installation after installing the update package, or go to obtained from http://oss.sgi.com/projects/pcp/download . Please note that there will not be a dedicated security announcement for this specific bug. - xinetd A buffer overflow has been found in xinetd, all versions, all SuSE Linux distributions. It may be abused to remotely attack a host running xinetd. The xinetd package is not installed by default in SuSE Linux distributions. Manual interaction must have been applied to run the daemon. Update packages can be found at the usual location on our ftp server. The security announcement for this security problem is underway. - fetchmail (fetchml) New fetchmail packages are available on the ftp server. The packages cure a buffer overflow that can be exploited by sending a victim a specially designed email, waiting for the victim's fetchmail program to pick up the email. We are preparing a security announcement for this problem. - openssh update packages for the openssh package after (and including) SuSE-6.4 are available on our ftp servers ftp.suse.de (for < 7.1) or ftp.suse.com (for >= 7.1). We are currently checking for a non-security related irregularity in sshd's behaviour under faulty setup conditions. - exim SuSE Linux distributions do not contain the exim Mail Transport Agent (See http://www.exim.org/ for details) and are therefore not susceptible to the recently found security-related bugs. - webmin SuSE Linux distributions do not contain the webmin administration web frontend (See http://www.webmin.org/ for details) and are therefore not vulnerable to the recently found security-related problems in the software. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security 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 <security(a)suse.com> public key is listed below. =================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the cleartext signature shows proof of the authenticity of the text. 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 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org 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 L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA== =rVRn - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOzx3lXey5gA9JdPZAQEOMgf+NtdN7lTA4NKbedQLeZpFNDzZS7LFqDxJ LcKShs5ZA5S7xhGFsBP2yQBHvpaYjXzr805m7hsMUwkOMegRYbXYq5h59Bp9NCoo eB2bzcV2lyPe+N+wGJE7XJso7Xxrk+6s+xN++xLA6ajt1YF6Hm/XpYuX9zSaSpCf E6i6kQGtYa8HUCKZGv7h79z5RqDlDxZfKHZLJWRUvhqkUECFH9f6e1mDayDQu7ah ErIl0y1B11sDaGu/jqVrIqqY7yXzgnDyDUAVlTkm/CoNw9CmLytJUfyGE5fxSsdT 0zJanS/YoRb7thO+XWK0ZRR+s/1xt/2VkhnJf+cML4br0s7HicP5pQ== =5+5p -----END PGP SIGNATURE-----

1 0

SuSEfirewall 2.1 and NetMeeting 3.01
by michael.ryan＠storm.ie 29 Jun '01

29 Jun '01

Trying to allow external sources connect to a machine on our private network which is acting as a NetMeeting host. Gateway is a SuSE 6.4 box, ip masquerading up and running SuSE firewall 2.1 Anyone done this before? any advice on how this can be done securely? tnx in advance, MR

2 1

Nonworking MASQUERADING with SuSE 7.2
by Adrian Stachowski 29 Jun '01

29 Jun '01

Hello Everyone, I configured SuSE 7.2 to use the recent SuSEfirewall2 with iptables. My system: 2 NICs external eth0 : 10.10.127.99 Subnet: 255.255.255.0 external eth1: 10.10.128.99 Subnet: 255.255.0.0 ADSL-Dialup But no MASQUERADING As instructed I set START_FW2 START_PPPOED to "yes". my "firewall2.rc.config" is also properly configured (I hope) ------- FW_DEV_EXT="ppp0" FW_DEV_INT="eth1" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.0.0/16,0/0,tcp,80" --------- One thing is very odd: even after deactivating SuSEfirewall2, flushing all IPTABLES and setting them afterwards manually to --------- iptables -P FORWARD ACCEPT iptables -A FORWARD -i ppp0 -m state --state NEW,INVALID -j REJECT iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE echo 1 > /proc/sys/net/ipv4/ip_forward --------- no masquerading. I'm desperate! What did I wrong?

1 0

kinternet firewall in SuSE 7.2
by Vitaly Shishakov 28 Jun '01

28 Jun '01

dear all, when i set up a dial_up connection for kinternet using YaST2, there is a flag about startng firewall. what firewall does it start (i mean is it built in SuSEfirewall), and how should i tune it. (for example to allow incoming higports for ftp and icq) tahnx in advance, Vitaly

1 0

personal-firewall and an addon-script.
by Jost Schoeler 28 Jun '01

28 Jun '01

Hello, who can help me? I have Suse7.1 as NAT-Router and PacketFilter. Its running a PersonalFirewall but after the starting the personal-firewall I modified the system with "ipchains-restore < /etc/ipchains-rules to update the rules, I want to use. That's working fine, but when my dynamic-IP-Provider have canceled the Connection (after 24 hours) , I must always restart my script. What can I do after an IP-Change on PPP to do that automatic? Can I put the script in the IP-Up-Script? Sorry, my english isn't very good ;) Bye, Jost Schöler

5 4

SuSEfirewall needs active dhcp connection first?
by hysterion 28 Jun '01

28 Jun '01

Hello, firewall-newbie here. After I posted the following message to suse-ppc, Joss Winn kindly suggested that I also ask for advice here. Thanks in advance for any and all insights... hysterion -------- Original Message -------- Subject: Re: [suse-ppc] Firewall Date: Wed, 27 Jun 2001 22:10:02 -0400 From: hysterion <hysterion(a)mac.com> To: suse-ppc(a)suse.com Joss Winn wrote: > > On Mon, Jun 25, 2001 at 09:26:17AM +0100, Smith, Bradley wrote: > > > > Hi, > > > > What's the easiest way for me to configure a firewall (SuSE 7.1, 2001 iMac)? > > > > I *will* get around to reading up on ipchain etc. but for the moment it's > > most important that I have something protecting me from those nasty hackers! > > > > Cheers > > Brad > > You can (I think it is turned on by default anyway), use the > Personal Firewall. It uses the 2.2 ipchains. I just got cable access and set up SuSEfirewall for masquerading, and I second the recommendation. It's very easy to set up - just a few instructions in the config file, and it automatically generates appropriate ipchain rules (97 of them, in my case) at boot time. Probably the best examples you could study anyway... One caveat I found, however: it seems that I also need to connect to my isp (using dhcp) *at boot time*. Otherwise SuSEfirewall produces a different set of rules, one of which seems to get in the way when I later try to connect and ping: $ /sbin/dhcpcd -d -h CC******-A eth0 produces messages like Jun 26 22:17:12 gris dhcpcd[886]: broadcasting DHCP_DISCOVER Jun 26 22:17:12 gris kernel: Packet log: input DENY eth0 PROTO=17 10.118.32.1:67 *.*.*.*:68 L=576 S=0x00 I=43879 F=0x0000 T=255 (#37) Jun 26 22:17:12 gris dhcpcd[886]: broadcastAddr option is missing in DHCP server response. Assuming *.*.*.255 Jun 26 22:17:12 gris dhcpcd[886]: broadcasting second DHCP_DISCOVER Jun 26 22:17:12 gris kernel: Packet log: input DENY eth0 PROTO=17 10.118.32.1:67 *.*.*.*:68 L=576 S=0x00 I=43881 F=0x0000 T=255 (#37) Jun 26 22:17:12 gris dhcpcd[886]: DHCP_OFFER received from (24.2.0.9) Jun 26 22:17:12 gris dhcpcd[886]: broadcasting DHCP_REQUEST for *.*.*.* Jun 26 22:17:12 gris kernel: Packet log: input DENY eth0 PROTO=17 10.118.32.1:67 *.*.*.*:68 L=576 S=0x00 I=43883 F=0x0000 T=255 (#37) Jun 26 22:17:12 gris dhcpcd[886]: DHCP_ACK received from (24.2.0.9) $ ping www.suse.de then produces (no output and) messages like Jun 26 22:18:14 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.33:53 *.*.*.*:1024 L=246 S=0x00 I=12157 F=0x0000 T=52 (#37) Jun 26 22:18:19 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.34:53 *.*.*.*:1024 L=246 S=0x00 I=8282 F=0x0000 T=52 (#37) Jun 26 22:18:24 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.33:53 *.*.*.*:1024 L=246 S=0x00 I=14064 F=0x0000 T=52 (#37) Jun 26 22:18:29 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.34:53 *.*.*.*:1024 L=246 S=0x00 I=10180 F=0x0000 T=52 (#37) This seems to indicate that the culprit rule (#37) (which reads: -A input -s 0.0.0.0/0.0.0.0 -d 0.0.0.0/0.0.0.0 -p 17 -j DENY -l) gets in the way of dhcp and dns services -- even though I did set FW_SERVICE_DHCLIENT="yes" and FW_INCOMING_HIGHPORTS_UDP="dns". (The "10.118.32.1" seems very strange, too, but that's consistently what I get.) If I let connection happen at boot time, on the other hand, this rule disappears from the list, and everything works fine. Questions: - Is it true that the firewall prevents (dhcp-)connecting to the internet, except at boot time? If yes, I would suggest emphasizing this in the documentation (I couldn't find it). If no, I'll gladly send more details of exactly what I did - the above seems 100% reproducible. - Do later versions of the firewall behave in the same way? (I am using the stock versions from SuSE 7.0 ppc - kernel 2.2.16 and firewall 2.6.) - Any other reason I should upgrade to a later version? (The .rpm updates mentioned at http://www.suse.de/~marc/SuSE.html don't seem to exist on the ppc side.) hysterion

1 0

firewall question
by michael.ryan＠storm.ie 27 Jun '01

27 Jun '01

The SuSE Linux manual recommends http://www.little-idiot.de/firewall for more in-depth information on firewalls. I'm wondering if there exists an english version of this site ... ? tnx, MR

1 0

ODBC and ipchains packet filter
by Andreas Rittershofer 27 Jun '01

27 Jun '01

I have a linux server with mySQL behind a linux packet filter. My users want to update the database with ODBC connects from their windows boxes. Which ports in which directions have to be open to allow this? I opened 3306 already, but this seems not to be enough. mfg ar -- mailto:andreas@rittershofer.de http://www.rittershofer.de PGP-Public-Key http://www.rittershofer.de/ari.htm

2 1

evalution-7.{1,2}
by tom＠surfeu.com 27 Jun '01

27 Jun '01

Hi all, maybe it's little bit out of tipic question but I'd like know when or if will be one-cd Suse Linux 7.1 and 7.2 called evalution-XX on a ftp site. thanks --t0m

4 4

anonymous ftp + firewall
by Joerg Ritter 27 Jun '01

27 Jun '01

Hello, we have installed a SuSEfirewall with packet rules. The connections from inside to the internet are restricted to secure ports only. As a consequence the ftp port 21 is disabled. Now we want allow only anonymous ftp for downloading. Is this possible? We have tried to configure the squid proxy, but have found only restriction for soure/dest IP or time/user restrictions. ciao Jörg

2 1

LinuxTag
by Roman Drahtmueller 27 Jun '01

27 Jun '01

Hi together, who will be at the LinuxTag in Stuttgart from July 5th to July 8th? It may be a nice idea to have lunch together on Saturday, for those who will be there. A good time to talk about stuff, impulses, ideas or just simple questions. I'll be there. Who else? Roman.

4 4

RE: [suse-security] iptables?
by Reckhard, Tobias 27 Jun '01

27 Jun '01

> > You need to load the appropriate kernel module, iptable_nat. > > Shouldn't the kernel daemon take care of this? > I don't know, but it doesn't appear to. It didn't in the ipchains days either, you had to load the masquerading modules explicitly as well. Since iptables is set up with a script, it's hardly much of a problem to load the modules from that. Tobias

1 0

RE: [suse-security] iptables?
by Reckhard, Tobias 27 Jun '01

27 Jun '01

> Doesn't precompiled SuSE 2.4 kernel support iptables? When I run the > command > iptables -t nat ....... I get "can't initialize table nat iptables who? > (do > you need insmod?)... > You need to load the appropriate kernel module, iptable_nat. HTH Tobias

2 1

iptables?
by Oyku Gencay 27 Jun '01

27 Jun '01

Hi, Doesn't precompiled SuSE 2.4 kernel support iptables? When I run the command iptables -t nat ....... I get "can't initialize table nat iptables who? (do you need insmod?)... The iptables coming with 7.1 is 1.1.2 TIA Oyku

1 0

squid and SuSEfirewall2
by Joss Winn 26 Jun '01

26 Jun '01

Hello, I was hoping to work this out on my own but it's been hours and I've gotten nowhere. I just upgraded from a previous version of Marc's firewall2 to the latest one. With the previous firewall2, everything was fine and I was using squid and junkbuster together with the firewall. I am on a 56k dialup and use squid to speed up my own web browsing. I offer no external services at all. I have tried to figure out why this updated firewall isn't working for me, but I really don't understand it. The symptoms are: When I first boot up and dial up to browse the web, I can browse freely using squid and junkbuster. However, the second time I dial up and any time after that, I cannot go anywhere. The browser just keeps looking until it has timed out. I wonder if this has anything to do with the DNS lookup, although I really don't know how to check this. ANY help and advice would be much appreciated. Any settings in the YAST or the firewall config file would be great. Thank you Joss -- http://www.josswinn.org

2 2