May 2002 - openSUSE Security - openSUSE Mailing Lists

how to keep nimda and code red from filling apache logs
by Mathias Homann 25 Sep '03

25 Sep '03

Hi all, here's a bit of a step-by-step description on how to keep nimda and codered from filling your apache logs. Parts used: - SuSE 7.2 Professional - SuSEfirewall2 - iptables 1.2.3 - linux kernel 2.4.13-pre5 steps: 1. install kernel sources for a kernel >> 2.4.9, running 2.4.13- pre5 here, works fine so far 2. get the sources for iptables 1.2.3 from http://netfilter.samba.org 3. unpack sources somewhere 4. export KERNEL_DIR=$(where you put the kernel tree) 5. cd into unpacked iptables sources, there's a subdirectory named patch-o-matic there 6. apply wanted patches by running ./runme $(name.of.patch)patch for this here You'll want the string patch You can also apply other patches, like the irc-conntrack patch 7. now there's a little bug in this patch... here's a diff: --- linux/net/ipv4/netfilter/ipt_string.c~ Sun Oct 21 00:16:29 2001 +++ linux/net/ipv4/netfilter/ipt_string.c Sun Oct 21 16:54:45 2001 @@ -62,7 +62,7 @@ sk = skip[haystack[right_end - i]]; sh = shift[i]; - right_end = max(int, right_end - i + sk, right_end + sh); + right_end = max(right_end - i + sk, right_end + sh); } return NULL; 8. now, make config/menuconfig/xconfig... as usual. You can import your running kernel's config first. 9. enable the experimental stuff 10. go to networking options->netfilter, there's an option there to enable string matching; set that to M 11. compile and install kernel as usual; remember to uncomment the export INSTALL_PATH=/boot in the main makefile. 12. now build a rpm file for the new iptables stuff by installing the source rpm which comes with suse, then edit the spec file, put the iptables source in /usr/src/packages/SOURCE and rebuild. 13. now there are some small changes to the firewall config files. a) uncomment the last line in /etc/rc.config.d/firewall2.rc.config: FW_CUSTOMRULES="/etc/rc.config.d/firewall2-custom.rc.config" b) edit that file, I got the following stuff in mine: for forbidden_string in root.exe cmd.exe .ida; do iptables -I input_ext -p tcp --dport http -m string \ --string $forbidden_string -m state \ --state ESTABLISHED -j REJECT --reject-with tcp-reset done put that in the last supfunction defined in the custom rc file. c) change the FW_LOG setting in firewall2.rc.config from reading -log-level warning to -log-level kernel.warning 14. last: some small changes to /sbin/SuSEfirewall2 search in the script for the parts where the modules are loaded and unloaded; be sure to add ipt_string (and the other new modules you created by patching the kernel and enabling them in make config) to the modules loading/unloading code there. 15. reboot 16. if you try now to access (from outside, of course) one of the nimda or codered URLS, all you get is a 'connection reset by peer', and the request doesn't show in apache log files. btw, no guarantees, and the usual YMMV :) bye [L]

7 7

suse samba server
by jonathan 23 Jan '03

23 Jan '03

Hello I have basically a suse samba server setup. Eth0 is for the internet connection (cable). Eth1 is my internal network. I use eth1 for my samba server. When i have the shares/ drive letters mapped, whatever, Ill goto access them and that computer will just lockup or timeout for about 1 minute, then it will resume operation normally. I have approx. 5 comptuers on the suse server, and they all do this from windows xp to windows 98se. I am using set up addresses of 192.168.0.x, where is greater than 2. My question is have or is there something Ive setup wrong to cause this pause to occur. ? Its becomming very annoying..and frustrating. Im using kernel 2.4.18-64GB-SMP with a dual processor setup. If anyone has any ideas please let me know. Every package installed is orginal versions from the suse install cdroms. (no updates done). Anything come to mind. btw, ive replaced the switch, with a new netgear one, and all the networks at startech ST100 Realtek 8139 chipsets on 100Tx. Anyone... !

4 5

Urgggggg!!! SuSEFirewall2 is getting on my nerves!!!!!
by Chris Bek 08 Jan '03

08 Jan '03

Hi there SuSErs... Well I must be doing something really wrong because everything that I do with SuSEFirewall2 is just not working! I have a small network with 5 PCs (all Win9X) and a Linux box (Currently SuSE 7.3) acting as a server. The server is a DHCP server and a Samba server for the entire network. So far everything is working perfect!!! Users log on the network, logon script executes etc.... Then a new task came up: let's input the internet into the network. Configured a 56Kbps modem on the server with YAST. Manged to get my account setup and running. Made a test connection and netscape works great on the server as well as e-mail (pop3). I tried configuring SuSEfirewall to manage all incoming requests from the PCs of the network. The firewall warned me about masquerading etc. so I downloaded the latest version of SuSEfirewall2 from the internet and installed it. Since I only need direct masquerading to be done (no proxies are currently working on the net) I made all the necessary changes as outlined in the examples supplied with the software. Since I needed to have Samba to keep working on the network, I opened (among others) 139 port for samba to work. Double checked all the changes that I have made and run rcSuSEfirewall2 to see what happens. Strange enough when wvdial executes it tells me that DNS is not functioning properly since www.suse.com cannot be found (or something like that please forgive me I am away from the Linux station now). Further on, when I open mIRC or other like programs (winmx etc) from a station, I look at the activity of IPtraf (I check this to see what happens) and I see no connections being created whatsoever.... mIRC prompts me that there was an error trying to find the host.... I have made no changes to the Win9X PCs. Is there something that I am forgeting to do?? I undestand that it is impossible for all of you to react to this since I have no output of the SuSEfirewall.conf file being published to this message.... I understand. Can someone please send me their configuration file so I can see what you have done, on a system that currently is working fine?? In addition, is there something that I have to do regarding route or routing?? What about the Win9X PCs?? Is there something that I have to do there?? I thank you so very much for all your help is advance!!!! I am killing myself trying to figure this one out for about 2 weeks now and managed nothing more than thin air!!!!! Chris

11 10

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

Re: [SLE] Re: [suse-security] NSA SELinux
by JW 03 Jun '02

03 Jun '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 JM >JW writes: JM >I Hope this helps, it is hard to tell what this thread is about. It is about applying the SE Linux security patches to the the SuSE kernel 2.4.18 for 8.0. Currently, the NSA (the SE-Linux authors) work with RedHat. Some work has ben done before on patchign a SuSEsystem to work with SE-Linux, but no one has (yet) gotten very far. I dearly hope to change that... - -- - ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE89/3sQ5u80xXOLBcRAgksAJ4lLaPamFTUx/hkhZOJn+lqdv/2uQCfRQKE w5WGBDPonWHvtpiI++rKp00= =YSZC -----END PGP SIGNATURE-----

3 6

IPCHAINS -> IPTABLES on SuSE 7.2
by chemiegott＠gmx.net 01 Jun '02

01 Jun '02

Dear Mailinglist ! On our SuSE 7.2-Webserver has IPCHAINS and SuSEfirewall run. Today I've updated from Kernel 2.2 to 2.4 and replaced IPCHAINS with IPTABLES and SuSEfirewall with SuSEfirwall2. All run very well, but one problem remains. With the old configurations, the Users inside my LAN (IP: 192.168.0.x) were able to connect the server (IP: 192.168.0.100 internal, IP:196.123.22.100 external) directly without a proxy or anything else. With the upgrade this is not possible anymore, but i don't want to change anything on the workstations. Do you have any idea, how the Users inside can reach 196.123.22.100 directy. I've tried it with masquerading, but it doesn't work. Thanx in advance, Michael -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

3 3

template of a tripwire policy file for SuSE 7.3?
by William Bold 31 May '02

31 May '02

Hi, I have been searching on the net, but didn't succedd in finding a tripwire policy file for SuSE 7.3. Although it is recommended to create the policy file according to _your own_ configuration, a good starting point would be a template. Does anybody of you have created something like this or maybe even some scripts that help automate the process of creating a policy file? (The policy creation tool on wiretrip.com's website isn't really useful..) Any help is greatly appreciated. Regards, William B. __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

1 0

Re: [suse-security] NSA SELinux
by Matthias Jänichen 31 May '02

31 May '02

At 14:27 31.05.02 +0200, Mark Müller wrote: >We've looked at LIDS, RSBAC and SELinux and decided to give SELinux a >chance. RSBAC is easier to install, but it lacks LSM support and we don't >know where RSBAC is going after Amon has finished its master thesis. RSBAC is OpenSource, so you can continue yourself. There is already a small crew around him so I would not really worry about this. Personally I am sure Amon will keep RSBAC up. I am not exactly uptodate about his plans concerning LSM support. But that should be discussed on his list. You've probably seen the below annoncement. Please feel free to discuss future development on his list and follow the discusion announced below. All I want to do here, is to encourage you to give it a try.. I did and I trust it! Reg. Matthias ---------- Forwarded Message ---------- Subject: [rsbac] The "LIDS versus RSBAC versus MEDUSA DS9" discussion Date: Thu, 30 May 2002 21:31:33 +0200 From: Michal Medvecký <M.Medvecky(a)sh.cvut.cz> To: lids-user(a)lists.sourceforge.net, rsbac(a)rsbac.org, medusa(a)medusa.fornax.sk Hello, we are very proud to invite you to watch and participate the international academic conference OpenWeekend (http://en.openweekend.cz/) held on June 1st on the Czech Technical University (http://www.cvut.cz/) in Prague, Czech republic. The conference will mostly discuss the Linux kernel security. This discussion will include the meeting of the authors of three most significant kernel security patches - Medusa DS9, RSBAC and LIDS - Milan Pikula and Martin Ockajak of Medusa DS9, Amon Ott of RSBAC and Philippe Biondi of LIDS. These guys have never met before. Martin Ockajak and Milan Pikula from MEDUSA DS9 project How can you participate? Whole discussion will be streamed live in the RealMedia format on http://server1.streaming.cesnet.cz:8080/rams/ow2002.ram We will accept questions for tutors on the silcnet (http://silcnet.org) server silcnet.org, channel OW (not #OW!). The english part will start at about 3pm (GMT+2). More info in english at http://en.openweekend.cz/ and in czech - http://www.openweekend.cz/ If anyone would be interested in helping with re-distribution of the signal, please contact me at mailto: misko(a)openweekend.cz Regards, Michal Medvecky Czech technical university, Prague

1 0

System-wide Access Control: how to go about it
by JW 31 May '02

31 May '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok, this isn't exactly SuSE specific but it's for a SuSE system, so please bear with me. The reason I'm interestd in SE Linux (Re my previous few posts) is because it was suggested to me that I could use it to control what ports users have access to. I'm a little confused. I've never dealt with this kind of severe security restrictions before and i feel out of my leauge. Here's what I'm trying to do. I have system users who are jailed in a chroot. They will all be running their own system -- i.e. there own software and daemons, but _not_ their own kernel (tit's not VMware or usermode or anything like that) They will each have their own IP address. I have recompiled my kernel to allow common usesr to open ports < 1024 (yes, it works, yes, I'm a little crazy) In my dreams at least, I'd like to be able to prevent all of the following: 1. They cannot access the host filesystem system It's my understanding that on lInux, processes will still be able to access the host system. At least, I got that impression from an article I was reading on FreeBSD jailing, where proccesses _can't_ access the host system. 2. They cannot acess any files anywhere except in their $HOME Basically, something more then just chroot to keep them jailed away. 3. I want to be able to allow/disallow the ports they have access to. 4. I'd like to be able to prevent them from using any IP address but the ones allocated to them. This is currently the worst problem. By default, everything they do (wrt the network) will attempt to use the base ip. Some services like Apache can be set to use only one IP, which helps, and maight be sufficient, but I wish really badly that I could set up somethign in the hosts system that would make it appear as if there's only 1 IP on the system (per user) 5. Processes should not be able to "see" or interact with the host's/other users processes and filesystems. It was suggested to me that SE Linux would allow fine grained controll over things like this, but I'm a little confused after reading some other things. Can anyone offer any other suggestions/advise as to how I should go about this? Have any of you done anything similar before? Would you recommend any other form of system-wide acess control besides SE Linux? All advice, ideas and pointers appreciated. Please don't hesitate to ask for clarification if I did a bad job explaining any particular point (I usually do :-/ ) TIA! - -- - ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE89rT6Q5u80xXOLBcRAioZAJ9jdYPbQVBFJVzcy82NwF/SzuXS/gCfWnsj GUYVWZQJUcTex1KoBsmbxx4= =uhLG -----END PGP SIGNATURE-----

5 5

Re: [suse-security] NSA SELinux
by Mark Müller 31 May '02

31 May '02

Matthias Jänichen wrote: > If you need something to use today you should look at www.rsbac.org. > > RSBAC (Role Set Based Access Controll) is _working_ on Suse, > running for over two years on productive systems. We've looked at LIDS, RSBAC and SELinux and decided to give SELinux a chance. RSBAC is easier to install, but it lacks LSM support and we don't know where RSBAC is going after Amon has finished its master thesis. Mark

1 0

NSA SELinux
by Mark Müller 31 May '02

31 May '02

Hello, is SuSE currently supporting NSA SELinux kernel module or does someone work with it? I'd like to know if there is a port to SuSE because the included tools were written under Redhat in the original SELinux release. Thanks in advance, Mark

5 7

Re: [suse-security] NSA SELinux
by Matthias Jänichen 30 May '02

30 May '02

Hi! If you need something to use today you should look at www.rsbac.org. RSBAC (Role Set Based Access Controll) is _working_ on Suse, running for over two years on productive systems. Further information on RSBAC.ORG. Reg. Matthias

1 0

Checking Firewall Log
by Sec 29 May '02

29 May '02

How can I check the personal firewall log in Suse 8.0 pro to see for the IP addresses been stopped? Thanks

1 0

SE Linux and SuSE: has anyone tried it?
by JW 29 May '02

29 May '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just wondering if anyone has installed SE Linux on SuSE. I'd love to hear anyone's experiences. Esp. how hard/easy it was to install/configure, anything special you had to do to get it working, and what you like/dislike about it now that you have it working. Wouldn't mind hearing people's opinions about it too, but please send opinions directly to me and not the list (to keep traffic down). Thanks. - -- - ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE88t0UQ5u80xXOLBcRAnQlAKCN9YOAyGBS4nWFEzNpTz2s5+68MwCdF7k1 3MSBpHoyEL9y6/9ngoeK7gs= =w5Zw -----END PGP SIGNATURE-----

3 2

SuSE Security Announcement: tcpdump/libpcap (SuSE-SA:2002:020)
by Sebastian Krahmer 29 May '02

29 May '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: tcpdump/libpcap Announcement-ID: SuSE-SA:2002:020 Date: Wed May 29 14:00:00 MEST 2002 Affected products: 6.4, 7.0, 7.1, 7.2, 7.3, 8.0, SuSE Linux Database Server, SuSE eMail Server III, SuSE Firewall Adminhost VPN, SuSE Linux Admin-CD for Firewall, SuSE Linux Live-CD for Firewall, SuSE Linux Enterprise Server for S/390, SuSE Linux Connectivity Server, SuSE Linux Enterprise Server 7 Vulnerability Type: remote command execution Severity (1-10): 6 SuSE default package: yes Other affected systems: All systems with vulnerable tcpdump. Content of this advisory: 1) security vulnerability resolved: Buffer overflow in tcpdump. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The tcpdump program may be used to capture and decode network traffic. Tcpdump decodes certain packets such as AFS requests in a wrong way resulting in a buffer overflow. Since running tcpdump requires root privileges this may lead to a root compromise of the system running tcpdump. We strongly recommend an update for administrators using tcpdump to monitor their networks since the only safe workaround is to not use it at all. Additionally to the fixed tcpdump packages we provide new libpcap packages. Libpcap on which most network monitoring programs rely also contained overflows which however are only exploitable by local attackers if you installed programs using libpcap setuid. This is not found in a default install. More information about tcpdump and libpcap may be found at http://www.tcpdump.org Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. i386 Intel Platform: SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/tcpdump-3.6.2-300.i386.rpm f6b5499e4857575fa162ae24cde181c8 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/tcpdump-3.6.2-300.src.rpm 2dd114976f858d0a66c83f409dbf25a0 SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/tcpdump-3.6.2-300.i386.rpm dc7fba8709f74476ee463e3b7d3d9042 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/tcpdump-3.6.2-300.src.rpm d2d6a940df5c40e54a6b30e3698458ef SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/tcpdump-3.4a6-376.i386.rpm 601bc08d351e8100767bbfd502efd44b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/tcpdump-3.4a6-376.src.rpm af87a4ad56fc853800c6af5982899f18 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/tcpdump-3.4a6-375.i386.rpm a3251d65bfa05948ce3796ac9e5fdf5b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/tcpdump-3.4a6-375.src.rpm 84ba69db15e1ff569cf674f7d61428f1 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/tcpdump-3.4a6-374.i386.rpm 63d57b2062a91d5fabeb43a5543d245e source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/tcpdump-3.4a6-374.src.rpm 204195b01bc25f84209029bed0eb00cd SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/tcpdump-3.4a6-372.i386.rpm ebb48c115355dc4ba1f45b1f8c36f9aa source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/tcpdump-3.4a6-372.src.rpm d2087aea083c4f6b93a518eee00c979e Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/tcpdump-3.6.2-58.sparc.rpm bb422a4c2d025d3b8a805345a200576a source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/tcpdump-3.6.2-58.src.rpm e0f85bd701865ca1f3d0923d1b9eb24c SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n1/tcpdump-3.4a6-318.sparc.rpm eaf6237823690fe4cb72df39b2b75a5f source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/tcpdump-3.4a6-318.src.rpm 458f7aaa2ed33606007d345d371bf8c4 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/tcpdump-3.4a6-318.sparc.rpm 6137a3ecadd2bfd95b51039fef52187b source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/tcpdump-3.4a6-318.src.rpm 0227535bdc5f7bd6980e77737cc6182c AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/tcpdump-3.4a6-329.alpha.rpm 614dfa16b71456692bc1d92b9db0998b source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/tcpdump-3.4a6-329.src.rpm e5a05bdbe3d5a29f0840c488e703268b SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/tcpdump-3.4a6-330.alpha.rpm 0f1fbdfdcf8f4e1a90424df1b3ad05bc source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/tcpdump-3.4a6-330.src.rpm d48289b8926c3fa7602b6ad026ae4130 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/tcpdump-3.4a6-330.alpha.rpm bf9ef22920ff73802e3b02005476527b source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/tcpdump-3.4a6-330.src.rpm 1fa595c3febfc97f45642faffdd1dfb1 PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/tcpdump-3.6.2-189.ppc.rpm 303f6a00defddc3b8a3be1ab386021cf source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/tcpdump-3.6.2-189.src.rpm 552355e0f15582d47d64fd3a97542cf3 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/tcpdump-3.4a6-317.ppc.rpm 4dd468ba517be7c7f52a8b2ac7c2beb0 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/tcpdump-3.4a6-317.src.rpm 69be109e360246794c66ed55e199ee95 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/tcpdump-3.4a6-316.ppc.rpm 1b51e5529fa559d8453588f09d9b8585 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/tcpdump-3.4a6-316.src.rpm 20d1da2b898a483df771809747851967 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/tcpdump-3.4a6-315.ppc.rpm 97cd7574108f3fcb9f52a7213d626481 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/tcpdump-3.4a6-315.src.rpm 67c63c89e26c2a17df6fef3585f41481 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - Perl-Digest-MD5 The Perl Digest-MD5 module fails to handle utf8 characters properly and thus calculates wrong hash sums for certain input. New packages are already available on our ftp servers. ______________________________________________________________________________ 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> or <security(a)suse.de>. The <security(a)suse.de> 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 Linux AG 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 mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPPS7U3ey5gA9JdPZAQGGzQgAluto4ljBhn1o2NZUAQeyX57dCXBwF7X+ d3Y+R7EkUG9jktmIuRqpUBIRz21ckTLGbZkXblNZYKl/EPYTZDGYaG3/GfYJ8NKN 5X/VL1LY+WqPYzEMQtkIBGIBIltD6jTQAJ4TSnKqvYAFajW2lN4ZahDQET1Xr9ma Vw5DnmPVsW1kYCbgL8qz+q0u4d7IUqF07A2iTUeGpfy4cyD8KbYFoZM3UeKe1T6g 73TlkbeP1ifZDOetGGQBc/wVpKUUUrp6srDJc1rUh2sEB0u5+c3o0zawP1ltPqZV KyVuofDRLs+BwRHm10eMbjbTsm9d1Wv8TZwSRU27Zh8SDZxqMiF0LQ== =7hKT -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0

Antw: [suse-security] Ping doesn't work
by Annette Meriste 29 May '02

29 May '02

Hi again, To ping to the firewall, check first if the kernel parameter icmp_echo_ignore_all is set to "0" And then the same thing with incoming pakets: $iptables -A INPUT -i $IFACE -p icmp \ --icmp-type echo-request -j ACCEPT $iptables -A OUTPUT -o $IFACE -p icmp \ --icmp-type echo-reply -j ACCEPT Icmp type 8 is the echo-request and the 0 is the echo-reply Cheers, Annette >>> "Annette Meriste" <annette.meriste(a)cablecom.ch> 29.05.02 12:19:11 >>> Hi Wilfired, A ping needs echo request and the echo reply. Try something like this: $iptables -A OUTPUT -o $IFAE -p icmp \ --icmp-type echo-request -j ACCEPT $iptables -A INPUT -i $IFACE -p icmp \ --icmp-type echo-reply -j ACCEPT You could specify the state too. Ex. ESTABLISHED, RELEATED Cheers, Annette ------------------------------------------------------------------------------------------------------------------------------- Cablecom GmbH Security Team Zollstrasse 42 CH-8021 Zürich Voice: +41 1 277 99 21 Fax: +41 1 277 93 22 E-Mail: annette.meriste(a)cablecom.ch >>> "Wilfried Philippi" <philippi(a)madex.com> 29.05.02 12:10:14 >>> Hello List, i have a Problem with our Firewall. We use Iptables and the Gateway works normaly, all wanted Connections are accepted and the unwanted are dropped. So it seems the System works. But i can't send a Ping to the System. when I send a Ping from one of the Windows Workstation's i get a Time Overflow ( in German for People who can undestand that : Zeitueberschreitung). I think i have a Port closed who is needed for Ping. What must i change in the Sccript that Ping works? SSH Connections to the Machine works. Any Suggestins? Thanks for Help. Wilfried -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

1 0

Antw: [suse-security] Ping doesn't work
by Annette Meriste 29 May '02

29 May '02

Hi Wilfired, A ping needs echo request and the echo reply. Try something like this: $iptables -A OUTPUT -o $IFAE -p icmp \ --icmp-type echo-request -j ACCEPT $iptables -A INPUT -i $IFACE -p icmp \ --icmp-type echo-reply -j ACCEPT You could specify the state too. Ex. ESTABLISHED, RELEATED Cheers, Annette ------------------------------------------------------------------------------------------------------------------------------- Cablecom GmbH Security Team Zollstrasse 42 CH-8021 Zürich Voice: +41 1 277 99 21 Fax: +41 1 277 93 22 E-Mail: annette.meriste(a)cablecom.ch >>> "Wilfried Philippi" <philippi(a)madex.com> 29.05.02 12:10:14 >>> Hello List, i have a Problem with our Firewall. We use Iptables and the Gateway works normaly, all wanted Connections are accepted and the unwanted are dropped. So it seems the System works. But i can't send a Ping to the System. when I send a Ping from one of the Windows Workstation's i get a Time Overflow ( in German for People who can undestand that : Zeitueberschreitung). I think i have a Port closed who is needed for Ping. What must i change in the Sccript that Ping works? SSH Connections to the Machine works. Any Suggestins? Thanks for Help. Wilfried -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

1 0

Using Netcat
by Majid Leo 29 May '02

29 May '02

How can I start using netcat on my Suse 8.0 pro.? Thanks

4 3

SuSEfirewall2 and http,ftp and ssh
by michael.blinzinger＠t-online.de 28 May '02

28 May '02

> Hello > > I`m running a SuSEfirewall2 on SuSE 8.0 Pro and want to connect to > ftp,http,ssh on my Server. How do I have to configure it? I`ve tried it > with several setups but it doesn`t work. > > Thank You > > Michael Blinzinger

1 0

which Anti-Virus Program could you recommend ??
by sc＠optomed.de 27 May '02

27 May '02

Hi list, i want to scan a Samba-File Server for Viruses. At this time i am testing F-Secure AV for Linux an it runs fine, but a Server licence costs 300 Euro. (Workstation 90 Euro - but i think i need Server-Licence ?) For me its important to have good update - support to always get the newest signatures (ok, what is newest) It would be nice if you could tell me your choises and experiences, thx a lot - Andreas (box: Suse 7.3 / Samba / mostly Win9x clients)

7 8

Virtual IP adress on the firewall, the dmz and DNAT / MASQUERADE
by Kai-H. Weutzing 27 May '02

27 May '02

Hi, my problem was that I have a box with three interfaces (ext, dmz, int) and many IPs on the ext-interface and one (or more) server in the dmz. In the moment the SuSEfirewall2 (v2.1) on my SuSE 8.0 installation can't do that (look in the TODO file). So I spend some time in patching the SuSEfirewall2 script and it works well for me. The patch is very small: 1310c1310,1311 < ERROR=`echo $NETS | $AWK -F, '{print $6}'` --- > DEST=`echo $NETS | $AWK -F, '{print $6}'` > ERROR=`echo $NETS | $AWK -F, '{print $7}'` 1337a1339 > test -z "$DEST" || DEST="-d $DEST" 1339c1341 < $IPTABLES -A PREROUTING -j DNAT -t nat $PROTO $NET1 $PORT1 --to-destination ${NET2}${PORT2} -i $DEV --- > $IPTABLES -A PREROUTING -j DNAT -t nat $PROTO $NET1 $PORT1 $DEST --to-destination ${NET2}${PORT2} -i $DEV Short description: - edit the test of the arguments of FW_FORWARD_MASQ and add the variable DEST for the IP adress on the firewall - add line for test the variable DEST, if set add '-d ' for later use in the iptables command - edit the iptables command for PREROUTING; added the DEST variable And the point 14 in /etc/sysconfig/SuSEfirewall2 gets a fifth argument: The IP adress on that the firewall listen on the ext-interface, e.g. a www-server: FW_FORWARD_MASQ="0/0,192.168.13.130,tcp,80,80,<public IP adress on ext-interface>" Warning: With that parameter file u can't start the unpachted SuSEfirewall2 script because it controlls how many arguments are given. btw. of cource you must configure the public IP adress on the firewall-box (/etc/sysconfig/network ...)! I test this config but maybe there are some points I can't see with my config... Comments are welcome... Greetings Kai

1 0

sendmail with SMTP-Authentication for roaming users...
by Info 27 May '02

27 May '02

Hi! I´ve Suse 8.0, installed sendmail with TLS and Auth... this works fine... but my problem: I want to allow smtp-relaying only for authenticated users... (that have dynamic ip). I can´t find the right configuration or documentation to do this.... Can someone help me? another question: I where nice to have TLS on POP3 also... any suggestions about? greetings from vienna... André

3 2

Re: [suse-security] Securing SuSE Linux 7.3 (fwd)
by Markus Gaugusch 27 May '02

27 May '02

---------- Forwarded message ---------- Date: Thu, 23 May 2002 11:15:19 +0200 From: Albert Brandl <albert.brandl(a)lindeverlag.at> To: Markus Gaugusch <markus(a)gaugusch.at> Subject: Re: [suse-security] Securing SuSE Linux 7.3 On Tue, May 21, 2002 at 05:08:37PM +0200, Markus Gaugusch wrote: > > dd if=/dev/sda of=/dev/sdb bs=16M > You will have two problems with this: > Minor: Only data lost during the last week can be restored. If you delete > a file, go on holiday for two weeks and want to restore it later, > there is no chance. > Major: Changes in the filesystem during this "backup" will most likely > ruin your copy ... ! Another problem is that this setup does not protect you against most disasters. If e.g. your computer catches fire, chances are that your second harddisk does not survive this. If someone carries your computer away, he/she won't leave the second disk so that you can restore from it. It's thus a good idea to save backups offsite. It's also crucial to have more than one backup - "Unix Backup & Recovery" (W. Curtis Preston, O'Reilly 1999) gives a very good introduction to the subject. There are several open source products for backing up stuff. If you want to use cdroms, see e.g. http://mondo.soureforge.net. We are using AMANDA for backing up to DAT and DLT tapes. AMANDA is also included in the SuSE distribution, see http://www.amanda.org for an introduction (I've found the FAQ-o-matic quite helpful for configuring my system). Best regards, Albert

5 5

Spamming ...
by Martin Schichl 27 May '02

27 May '02

Morning! Since some days I get Returned Mails from unknown mail-users which seems that someone is spamming from our machine. But when i analyze the header of the original mail i fin a line: >> Received: from 210.97.42.1 (HELO scc.co.at) (210.97.42.1) << Although the IP of scc.co.at is 193.81.182.39 The IP 210.97.42.1 will change permanently when reading other similar mails. My questions: 1) Is it possible that someone beoke into our machine and sent this mail directly over scc.co.at 2) What can I do to stop those spammers ... ThanX Martin The header file of the original Message --------------------------------------------------------------- X-Track: 92154: 2 X-Rocket-Spam: 210.97.42.1 X-YahooFilteredBulk: 210.97.42.1 Return-Path: <rjnr3245i37(a)scc.co.at> Received: from 210.97.42.1 (HELO scc.co.at) (210.97.42.1) by mta514.mail.yahoo.com with SMTP; 28 Feb 2002 15:32:36 -0800 (PST) Reply-To: <rjnr3245i37(a)scc.co.at> Message-ID: <001a07e37abc$2777d8d5$6ce83be4@lplwmr> From: <rjnr3245i37(a)scc.co.at> To: <doctorbutcher(a)yahoo.com> --------------------------------------------------------------- ----------------------------------------------------------------- Dipl.-Ing. Martin Schichl SC&C Software, Communication & Consulting GmbH & Co KEG Grottenhofstr. 3, A-8053 Graz Tel. +43/(0)316/265-205, Fax +43/(0)316/265-234 mschichl(a)scc.co.at, http://scc.co.at

9 12

Install harden_suse
by oliver.z 27 May '02

27 May '02

Hey security team I am new in the Linux-world and would like to have some support in installing harden_suse. How I install it and with what switch-options? thnxs Oliver

2 1