November 2002 - openSUSE Security - openSUSE Mailing Lists

SuSEfirewall2: external ip aliases with forward / masq?
by Howard, Neal 26 Nov '02

26 Nov '02

Hello all, I've searched thru FAQs & archives for a couple days now and haven't found anything exactly like my problem, so I will describe it and maybe someone here can offer good advice. I have installed a SuSE 8.0 machine to be an Internet firewall. I have a whole Internet-routable public class C address range to work with on my external interface. I am running only private RFC1918 addresses on my interior network. I have some Windows PCs on the internal network that I need to allow a vendor on the outside to remotely manage via PCAnywhere. Thanks to Togan Muftuoglu's most excellent "Understanding and Using SuSE Firewall2" document, I have been able to configure SuSEfirewall2 to perform the FW_FORWARD_MASQ to make this work for one single internal Windows PC. Now I need to be able to have ip aliases on the external interface eth0 (let's call them A.B.C.100 as the primary address and A.B.C.101 and A.B.C.102 as the ip aliases on the external interface). The internal interface (eth1) of the firewall is 192.168.1.1 and there are no aliases on that one. My internal Windows machines are 192.168.1.10 , 192.168.1.11 and 192.168.1.12 and PCAnywhere is listening on the normal 5631/tcp and 5632/udp ports on each of these machines. I also need to be able to limit the inbound PCAnywhere connection requests to a specific source address. Let's call the vendor's address X.Y.Z.123. To get the firewall to work for the one PCA machine, I used these rules in the /etc/sysconfig/SuSEfirewall2 file: [mundane config stuff that's normally self-explanatory left out] FW_SERVICES_EXT_TCP="5631" FW_SERVICES_EXT_UDP="5632" FW_TRUSTED_NETS="X.Y.Z.123" FW_FORWARD_MASQ="X.Y.Z.123,192.168.1.10,tcp,5631 \ X.Y.Z .123,192.168.1.10,udp,5632" This work great for PCAnywhere to get thru to the one machine. Now I need to set up a similar forward/masq deal happening for some external ip aliases to get forwarded and masqueraded to the other two machines on these tcp/udp ports like: A.B.C.101 -> 192.168.1.11 (both 5631/tcp and 5632/udp) A.B.C.102 -> 192.168.1.12 (both 5631/tcp and 5632/udp) Also only allow X.Y.Z.123 from the outside to be permitted to use these services. In Togan's document, he mentions how to do this using alternative tcp and udp port numbers for multiple internal PCAnywhere machines (i.e. 5631/5632 for first pc, 5633/5634 for second, 5635/5636 for the third one, etc) and only one ip address on the SuSEfirewall2's external address, but my vendor is stubbornly demanding that I provide separate ip addresses for each machine and stick with the standard PCAnywhere port numbers. I already have the aliased external ip addreses on eth0, that part was easy. Does anyone know how to make SuSEfirewall2 scripts support them for my need? Or am I going to have to make an entire script of raw iptables commands from scratch to accomplish such an animal. If so, is there a way of getting the raw list of iptables commands that the SuSEfirewall2 startup processes generates into one big textfile so I may be able to see all that it is doing, and all in correct order, so that I may use it as a learn-by-example script? Thanks, Neal

2 1

block msn behind firewall
by security 26 Nov '02

26 Nov '02

Hi, Is there anyway to block access to msn messenger from masquerading internal network behind firewall, using SuSefirewall2 ??? thinks

2 1

Mail Gateway w/ Amavis and Postfix on SuSE 7.2
by christian.burri＠synecta.ch 26 Nov '02

26 Nov '02

Hello List, I have a small Problem with an Amavis installation... In /var/log/mail I get: Nov 25 18:47:43 horus amavis[13592]: Virus scanner failure: /usr/local/bin/uvscan (error code: 16777215) The mails go thru tho, also the X_Virus_Scanned Tag appears. What does the error message in the logs mean? Could it be Amavis had trouble opening a packed attachment or something? Cheers Chr. Burri .-. /v\ L I N U X // \\ >I know KungFu!!< /( )\ ^^-^^

2 2

Starting Firewall Initialization: (phase 2 of 3) failed
by Mario Ohnewald 26 Nov '02

26 Nov '02

Hello! I was playing agounf with QoS and the new Versions of IPtables witch works fine. But since then my Firewall2 wont initialize anymore! Starting Firewall Initialization: (phase 2 of 3) failed I can´t find any errors in messages, firewall or warn! Where am i supposed to look for hints now? I have already installed the "old" iptables to see if its works with them, but it doesnt. A debug mode for SuSEfirewall2 would be great now! :) Cheers, Mario p.s. I have SuSE7.3 with the standard 2.4.10 Kernel.

2 1

Maybe OT: martian sources and new dev eth
by Miguel Albuquerque 26 Nov '02

26 Nov '02

Hi, I've noticed that since I installed a new network card, I have lots of "martian sources" on dev eth1 which it happens to be down. It looks like it grabs all broadcast/martian packets in the active netcard. Not exactly a problem but annoying, hun? Or maybe the card is damaged? Could some 1 explain me that? Regards, -- .-. e-SecureNet /v\ We Run SuSE Project Manager // \\ *The LINUX Experts* c/o Miguel Albuquerque /( )\ Av. Miremont 46 ^^-^^ 1202 - GE, SWITZERLAND Tel: +41 (22) 782 5344 Fax: +41 (22) 782 5348 mailto:mfoacs@e-securenet.ch http://www.e-securenet.ch "Was Sind und was Sollen die Zahlen?" Dedekind. ____________________________________________________________

2 1

boot files question
by Piet Roorda 26 Nov '02

26 Nov '02

I need disk space and there are too may files in my /boot what ensential files should be there in theory, regards, piet

4 3

PPTP Server
by Fabio Sena 25 Nov '02

25 Nov '02

People, Exists some restriction in a server VPN PPTP, to receive connections from customers saw modem and of customers who are in another one lan at the same time? Somebody has one options.pptp that it has accepted connection it saw modem and it saw Lan? I am not obtaining to make with that the PPTP SERVER, has accepted modem connections come, is only obtaining through lan, When I try to connect way modem to server PPTP, it it arrives to soon check the user and password and of timeout after. LAN---------------------/Internet/--------------VPNSERVER(PPTP) Accepted connection and functions correctly Modem------------------/Internet/---------------VPNSERVER(PPTP) time out []'s Fabio Sena

1 0

SuSE Security Announcement: pine (SuSE-SA:2002:046)
by Thomas Biege 25 Nov '02

25 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: pine Announcement-ID: SuSE-SA:2002:046 Date: Monday, Nov 25th 2002 10:30 MEST Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 SuSE Linux Database Server SuSE eMail Server 3.1 SuSE eMail Server III SuSE Firewall Adminhost VPN SuSE Linux Admin-CD for Firewall SuSE Firewall on CD 2 - VPN SuSE Firewall on CD 2 SuSE Linux Enterprise Server for S/390 SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 for IA32 SuSE Linux Office Server Vulnerability Type: remote denial-of-service Severity (1-10): 4 SuSE default package: yes (7.1 - 8.0) no (8.1) Cross References: none Content of this advisory: 1) security vulnerability resolved: - heap buffer overflow while parsing mail address problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - sparc distribution - WindowMaker 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Pine, Program for Internet News and Email, is a well known and widely used eMail client. While parsing and escaping characters of eMail addresses pine does not allocate enough memory for storing the escaped mailbox part of an address. This results in a buffer overflow on the heap that will make pine crash. The offending eMail can just be deleted manually or by using another mail user agent. A possible temporary workaround is to filter the respective header lines by a mail delivery agent (such as procmail). 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. Intel i386 Platform: SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/pine-4.44-224.i586.rpm 8c32d5571d7488e31f693a884dedb81e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/pine-4.44-224.i586.pat… 467b8b318958b0ead3f30fa7b1f5a9a0 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/pine-4.44-224.src.rpm 9b1ff436719cf9752cda3ddd711e80a7 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/pine-4.44-222.i386.rpm 01d9e82164a5ce4037b84be1b2ed4228 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/pine-4.44-222.i386.patch.rpm 162c4265909af7805f7aeaf3e12e8763 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/pine-4.44-222.src.rpm d724e02b1ea3783e5bfb01ae9728d7cf SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/pine-4.33-266.i386.rpm 140c58adf7d0b2113d5bbbbb20de67e2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/pine-4.33-266.src.rpm 100c86e88ce357b0efacf7dfe2ab592c SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/pine-4.33-266.i386.rpm bd44232250b3def07cab81064dad11f2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/pine-4.33-266.src.rpm e28daa1f2d66135fcf5951c9b2dc19be SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/pine-4.33-263.i386.rpm 9bdd3394336a786b0711b8e98ab4a268 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/pine-4.33-263.src.rpm 630478b751a24e86c52fe645be9365c4 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/pine-4.33-97.sparc.rpm 5187b311c27f043178a12ae186d228a6 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/pine-4.33-97.src.rpm 9616303edadfd899785f3ac12d2dc02a AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/pine-4.33-85.alpha.rpm f5155d79236e3ec15c463f586f731c17 source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/pine-4.33-85.src.rpm 75365b21b97c8a2f722d95491f62d305 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/pine-4.33-143.ppc.rpm 98955d956701d7c6c3e0522468377044 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/pine-4.33-143.src.rpm d4cdfbf180711ae6e9bab31b87cbb3bd SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/pine-4.33-141.ppc.rpm 0b0512af4bdffc654bbd1774c2c8f8a9 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/pine-4.33-141.src.rpm 0ee371a8935abe58aa53221606960bbe ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - sparc distribution We have moved the update directories for the SuSE SPARC distributions 7.0 and 7.1 as well as the distribution directory for 7.1 to the discontinued/ tree on ftp.suse.com. We urge all of the sparc users to upgrade to the SuSE-7.3-sparc distribution, the latest in the row for the sparc platform. Resource limitations keep us from timely providing update packages for the older sparc distribution. - WindowMaker A bug was found in the image processing code of windowmaker. It could allow attackers to execute arbitrary code as the user running windowmaker by tricking the user into viewing special crafted malicious image files. New packages are currently being built and will be available soon. ______________________________________________________________________________ 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 un-installed 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 top-level 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 announcements 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 clear-text 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 iQEVAwUBPeIANHey5gA9JdPZAQHKlwf9EPQPcv2iqlHKQPGMeVqgKUsvA/psvxPF JHfwcZe64VvyL8o3Q/ERp2gWhBhfqI/yELMW+2nnILXEwPntZwL1P2/+BewecUFm XhOsKSdKQdaw77qyhJL+RAMf83nhZS5xRv5ckPfTgLAIIiigonQPCwq/8j5ciGmi XsEnr/aQKlaULqEEaUMyNvBuE155jIX4EDgK5WqrbJWhFuVdR4M5RqstGQx7OQ3U qltnex/G1BJ4eZPA33PW0BQEGgGFdlGHjcf6IB2A0ZTVqtUTI/F2SaFFJHBpeXBp Q+YLq/Tp0SNCGj9M5a0JN1qY1yGJxIvVscWv4Ta1z09kSBcgrDR8Ww== =ltD3 -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de> SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- Over thinking, Over analyzing, seperates the body from the mind. - Maynard James Keenan

1 0

samba machine accounts/samba living together with W2K
by Philippe Vogel 25 Nov '02

25 Nov '02

Hi! 1) I'm using Marc Heuses Seccheck and allways get errormessages that I don't want. The server is a samba/ldap pdc using shares of a W2K server. Why? W2K sucks with it's nasty ressource eating and complicated administration of ADS/Samba is 2-3x faster. Here some of the output: from /etc/passwd (machine$=machine accounts of samba/ldap with home=/dev/null): - Login datenschlund$ has non-alphanumeric characters. - Login datenschlund$ has more than 8 characters. from /etc/shadow: + Login mb124$ has non-alphanumeric characters. + Login datenschlund$ has non-alphanumeric characters. + Login datenschlund$ has more than 8 characters. - Group gr-lehrer has more than 8 characters. + user test : home directory is owned by users Same with files in user directorys. Why the probe more than 8 characters? I don't know what's the problem on linux with longer than 8 characters usernames! The $ in the username is not changeable otherwise samba would not add machines to the domain. Is there a way to get rid of that anoying log entrys or will I have to write my own sec check, that I partly allready have (mail, firewall, port access)? 2) Next thing is there anybody having knowledge of how to get gid and uid on file acl in a windoof environment taken from a samba pdc? I have top help me with local created groups that I put domain users on. There is a need to get group acls for some shares (I'm fucked up with the damn M$ rightsmanagement for directorys). Winbind does not help me because this is for using samba in a domain and give samba the uid/gid of other w2k-pdc's in a network environment. Philippe

2 1

FW question
by Miguel Albuquerque 24 Nov '02

24 Nov '02

In the option FW_ALLOW_CLASS_ROUTING="yes" --> virtual interfaces are included or not? (eth0:2 i.e. and so on...). If yes, I won't need to declare them in FW_DEV_INT, correct? And if yes, what does it implies in the security and performance scope? Thanks

2 1

after HARDEN_SUSE Xsession: login for <user> is disabled ??
by Linux User 24 Nov '02

24 Nov '02

Hi guys... I just have test the HARDEN_SUSE and when I try to login on KDE as Oracle user I get the following error: Xsession: login for oracle is disabled Any clue of how to enable it ? Thanks bye --ed

3 2

SuSEfirewall2 and SuSE 8.1
by Andreas Hallstein 23 Nov '02

23 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI, I am still struggling with getting my firewall to work. I have a ISDN dialup connection with a dynamic IP address. When I start SuSEfirewall2 at boot time the rules are correctly loaded, but after dialin the following messages appears in the syslog: Nov 22 21:47:08 Bilbo kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195.226.96.131 DST=195.226.100.219 LEN=223 TOS=0x00 PREC=0x00 TTL=252 ID=15433 DF PROTO=UDP SPT=53 DPT=1025 LEN=203 Nov 22 21:47:08 Bilbo kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195.226.96.131 DST=195.226.100.219 LEN=223 TOS=0x00 PREC=0x00 TTL=252 ID=15434 DF PROTO=UDP SPT=53 DPT=1025 LEN=203 Nov 22 21:47:08 Bilbo kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195.226.96.132 DST=195.226.100.219 LEN=138 TOS=0x00 PREC=0x00 TTL=252 ID=11395 DF PROTO=UDP SPT=53 DPT=1025 LEN=118 Nov 22 21:47:08 Bilbo kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195.226.96.131 DST=195.226.100.219 LEN=138 TOS=0x00 PREC=0x00 TTL=252 ID=15435 DF PROTO=UDP SPT=53 DPT=1026 LEN=118 Nov 22 21:47:13 Bilbo kernel: SuSE-FW-ILLEGAL-TARGET IN=ippp0 OUT= MAC= SRC=195.226.96.132 DST=195.226.100.219 LEN=138 TOS=0x00 PREC=0x00 TTL=252 ID=11396 DF PROTO=UDP SPT=53 DPT=1025 LEN=118 ...and so on. What I figured out is that the firewall rules are not reloaded after dialin, so that the new IP address of the ippp0 interface is not known to the firewall. In the ip-up script there are some settings regarding loading of the firewall, but I did not figure out so far if they work as expected. It seems to me as they are ignored. Of course I *could* reload the firewall manually after sucessful dialin, but on the other hand I expect from SuSE to provide an ip-up script that works also after a version change. It worked fine on my old 7.2 installation. regards Andreas ahallstein(a)tesionmail.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE93p6M5RlbrxDjpvMRArplAKCbbpW5+Rt83Lr9KjenWy1j0jTPjwCghsYw FxQrTT/pGtpT48lZBmpJc1I= =o6uU -----END PGP SIGNATURE-----

2 2

SuSE Security Announcement: samba (SuSE-SA:2002:045)
by Roman Drahtmueller 22 Nov '02

22 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: samba Announcement-ID: SuSE-SA:2002:045 Date: Wednesday, November 20th 2002 16:00 MET Affected products: 7.2, 7.3, 8.0, 8.1 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7+8, SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: possible remote code execution Severity (1-10): 7 SuSE default package: no Cross References: http://www.samba.org/ 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 Samba developer Steve Langasek found a security problem in samba, the widely known free implementation of the SMB protocol. The error consists of a buffer overflow in a commonly used routine that accepts user input and may write up to 127 bytes past the end of the buffer allocated with static length, leaving enough room for an exploit. The resulting vulnerability can be exploited locally in applications using the pam_smbpass Pluggable Authentication Module (PAM). It may be possible to exploit this vulnerability remotely, causing the running smbd to crash or even to execute arbitrary code. The samba package is installed by default only on the SuSE Linux Enterprise Server. SuSE Linux products do not have the samba and samba-client packages installed by default. The samba packages in SuSE Linux version 7.1 and before are not affected by this vulnerability. For the bug to be exploited, your system has to be running the smbd samba server, or an administrator must have (manually) changed the configuration of the PAM authentification subsystem to enable the use of the pam_smbpass module. The samba server process(es) are not activated automatically after installation (of the package). The samba subsystem on SuSE products is split into two different subpackages: samba and smbclnt up to and including SuSE Linux 7.2, on SuSE Linux 7.3 and newer the package names are samba and samba-client. To completely remove the vulnerability, you should update all of the installed packages. We wish to express our gratitude to the samba development team and in particular to Steve Langasek and Volker Lendecke who provided the patches and communicated them to the vendors. Please know that the samba team will release the new version 2.2.7 of the samba software to address the security fix at the same time as this announcement gets published. More information about samba (and the security fix) is available at http://www.samba.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. SPECIAL INSTALL INSTRUCTIONS: ============================== After successfully installing the update packages, you should restart the samba server process(es) to make the changes in the system effective. If you do not have a samba server running on your system, no further action is required. If you have a samba server running, please run the following command as root: rcsmb restart # SuSE Linux, all versions rcnmb restart # only on SuSE Linux 8.1 Intel i386 Platform: SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.5-124.i586.r… f0a94ef6cc49165d4dace59caaf359d7 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-client-2.2.5-124… f694fb4aaabffa98b6a76941cb2c0eaf patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.5-124.i586.p… af43bc1d5dc1b097389933f34ca5a625 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-client-2.2.5-124… bff278f9366df7efe72fa880c4f7618f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/samba-2.2.5-124.src.rpm 674adb466663259c2117852b9525a29a SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/samba-2.2.3a-165.i386.rpm 8c7edd09c5acfc269467ecbcdcdfc21c ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/samba-client-2.2.3a-165.i386… bfc08a1d64f0d85670041c7046d1e775 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/samba-2.2.3a-165.i386.patch.… 7d08c2c07137d9da0b3d1a301295a084 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/samba-client-2.2.3a-165.i386… 887230d4ed61bec496dff73c50fa3de0 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/samba-2.2.3a-165.src.rpm b208c4d5bcceb7f9cc18df75b7831d2d SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/samba-2.2.1a-206.i386.rpm dc4232333a0babbb257cff346609625f ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/samba-client-2.2.1a-206.i386… 163a565a5a0b0320eae6ba1d0ebdfb27 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/samba-2.2.1a-206.src.rpm 6086e3bb296a320c28fced9068c931fc SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/samba-2.2.0a-45.i386.rpm 184b17987ca99325782f4c7f9e04b6a6 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/smbclnt-2.2.0a-45.i386.rpm b9926ade015ccaf271088da246814abb source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/samba-2.2.0a-45.src.rpm 384ec49b0b8a81d8ecf7c84ef0fa2689 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/samba-2.2.1a-69.sparc.rpm 61b72787bc8e0b333662962a60bce0c2 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/samba-client-2.2.1a-69.spar… 6acd0ffd218d721d7c10b17e1194738d source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/samba-2.2.1a-69.src.rpm 77f57a3277bb1a270ae79bc94ee28345 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/samba-2.2.1a-141.ppc.rpm d127afabc7d5b764289f9b65ad4c4cd1 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/samba-client-2.2.1a-141.ppc.r… 894132f3b5041a54ec871d67eef072e5 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/samba-2.2.1a-141.src.rpm ccff812fdddd3af9d62a399f63e0405e ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - 7.0 update trees We will move the SuSE Linux 7.0 update tree structure to the /pub/suse/discontinued/ tree shortly, following the announcement about discontinued products on Tue, 29 Oct 2002. ______________________________________________________________________________ 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 un-installed 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 top-level 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 announcements 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 clear-text 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 iQEVAwUBPdvAOHey5gA9JdPZAQFBcwf6A+8lmCVrRiCgRW/SH+pzBMJ2+p8iywDd BhChCR0ekyrNcxwMRut1vFVRbt0iSzD3Kl43dAPOrTcvypkoBnxW4+/l1mD7/fqH WsF22vwhV/8u33tYFN7wsUxpBHzBSq3CguJF4XP5BpNCkvJvrLh5f5QDgonUoO+P 2z0sYNgSARxEKgniyp8YSm6UmC63ijzDhLb/JuDxNu/8652Xx35pptdOtBiriB9C yGKgJoy97co96oQrzS9ZRKjSGBfE5g6Q8/nAyDuCFpPOiIvDaLlkcab0u2Boawe+ GuCM6QwB7xmb6ElCehtCGxn9v6gE86hNFCOVrjIOhKgOrlY0V8h21w== =MrgG -----END PGP SIGNATURE-----

4 11

Susefirewall Squid
by Frédéric Poulet 22 Nov '02

22 Nov '02

Hi, I read that use Squid with Susefirewall allow to have more security, is it true ? I would want try Squid how i can config Squid and Susefirewall, i don't find example ? Thanks ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

4 3

Setting firewall to disable one external address
by Jevoš Peter 22 Nov '02

22 Nov '02

Hello I've one question how can I set SuSEfirewall2 to drop all packet (tcp, udp, icmp) from exactly one external public address, for propably reason much more requests for DNS server thanx a lot for your answers peter

1 0

CA-2002-07.html
by Soeren Mindorf 22 Nov '02

22 Nov '02

Hi, I have read this announcment http://www.cert.org/advisories/CA-2002-07.html and I ask myself are SuSE affected? If not, which patchlevel I need? Regards Soeren

6 6

script-help
by Piet Roorda 21 Nov '02

21 Nov '02

I know it is not within the goal of this group but, who is willing to help me with a small script. regards, piet

1 0

Re: [suse-security] SuseFirewall2 DMZ
by Frédéric Poulet 21 Nov '02

21 Nov '02

Thanks --- Jörn_Ott <suse-security(a)ott-service.de> a écrit : > Hi Frédéric, > > > I read that FW_FORWARD_MASQ don't be used for security reason. > > How i can create a DMZ without using FW_FORWARD_MASQ but visible from > > internet ? > > Usually you should have a block of real IP adresses for your DMZ. Then your > firewall should be configured as router to pass any request to one of those > adresses on to the machines in the DMZ. > > If you don't have that option, you must fwd/masq to reach the DMZ or use > programs like rinetd to forward connections to the firewall automagically > to a machine in the DMZ (or internal network). Both are possible security > risks. > > cya > Jörn > > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

AW: [suse-security] Problems creating usernames with dots
by Peer Stefan 21 Nov '02

21 Nov '02

Hi Mario, > From: Mario Viana [mailto:marioj@secrel.com.br] > Hello, > > Well, maybe it´s a little off-topic , but does anybody know > why SuSE 8.0 > don´t accept creating a username with dots, e.g. , while I > try creating the > user suse.br : > > # useradd suse.br > useradd: invalid user name 'suse.br' Because . is not a valid character for users. What about "chown user.group file" ? Does the . belong to the username or is it the username-group delimiter? > > I have seen all the configuration files in /etc/sysconfig, Suse DB and > Google and I haven´t found anything related to this topic. =(( Dotted usernames were a bug until SuSE 8.0. regards, Stefan

9 9

Re: [suse-security] SuseFirewall2 DMZ
by Frédéric Poulet 21 Nov '02

21 Nov '02

How modify my firewall configuration to have a ftp service wich runs correctly from intern network ? --- Christian Andersson <chrisand(a)cs.lth.se> a écrit : > > On Tuesday 19 November 2002 20:20, Frédéric Poulet wrote: > > What i don't understand that is why i see my ftp server from internet and > > it's run correctly but from intern network i have errors ! > > It's because of your firewall configuration. > > -- > Ch > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 4

AW: AW: [suse-security] Problems creating usernames with dots
by Ulrich Roth 21 Nov '02

21 Nov '02

> If you want/need to have system users with dots in > their names, then this doesn't work. E. g., you have a system > with two users Peter Meier and Peter Huber. Why not have > system user names peter.meier and peter.huber? Why does it always have to be a dot? Ten years ago in Fido we used underscores, if I remember well, so the user names would be Peter_Meier and Peter_Huber. Or what about dashes? Or even no character (PeterMeier and PeterHuber)? But such long user names aren't shown completely when doing an "ls -la". Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth(a)impact.de

4 4

Build Key expired
by Albert Brandl 21 Nov '02

21 Nov '02

Hi! The key build(a)suse.de ID 9C800ACA 1024 bit DSA key, expires 2002-10-19 has expired two days ago. Unfortunately, the security updates are still signed with this key, which prevents the verification of their validity. Furthermore, I haven't found a reference to the new key @www.suse.com. Please publish a new key and use it to sign all packages. Best regards, Albert Brandl

3 2

Problems with NIS SuSE 8.0
by Harald Steden 21 Nov '02

21 Nov '02

Hello list! I set up a network of 4 Clients with NIS + NFS connected to one server. So far everything works fine since ~ 3/4 year. But sometimes it happens that if you login, every password is accepted or none. Which means that you can login with any account and no password verification. The NIS Server is running with SuSE 8.0 and all patches installed. Clients are running SuSE 7.3 and 8.1, both versions show the same behaviour. Has anybody seen this behaviour and a solution for it. Thanks for hints and tips, Harald Steden

1 0

Re: [suse-security-announce] SuSE Security Announcement: samba (SuSE-SA:2002:045)
by Mathias Homann 21 Nov '02

21 Nov '02

Roman Drahtmueller sagte: [ announcement of fixes for samba deleted ] what about http://www.heise.de/newsticker/data/ps-20.11.02-001/ ?? why update with patched ooold versions when there's a official 2.2.7 for security fixes? bye, [MH]

2 1

Re: [suse-security] Problems creating usernames with dots
by Mario Viana 21 Nov '02

21 Nov '02

Hi people, 1) As you see below, quotes and others tricks didn´t work in 8.0 : XXX:~ # useradd suse\.br useradd: invalid user name 'suse.br' XXX:~ # useradd suse"."br useradd: invalid user name 'suse.br' XXX:~ # useradd "suse.br" useradd: invalid user name 'suse.br' 2) I´ve already tried to set an alias, like .qmail-suse.br . It didn´t work. 3) I know that is possible creating the users by myself in /etc/passwd , but this is not a good solution for me. I have thousands of users. I wondering what really have changed in 8.0 ? Only the useradd source code? -- ========================= José Mário Viana Network Admin SecrelNet ISP - Brazil ========================= ----- Original Message ----- From: "Bob Sutter" <bob.sutter(a)kobie.com> To: "Mario Viana" <marioj(a)secrel.com.br>; <suse-security(a)suse.com> Sent: Wednesday, November 20, 2002 12:57 PM Subject: RE: [suse-security] Problems creating usernames with dots I just put the name in quotes and it added it just fine. -----Original Message----- From: Mario Viana [mailto:marioj@secrel.com.br] Sent: Wednesday, November 20, 2002 8:44 AM To: suse-security(a)suse.com Subject: [suse-security] Problems creating usernames with dots Hello, Well, maybe it´s a little off-topic , but does anybody know why SuSE 8.0 don´t accept creating a username with dots, e.g. , while I try creating the user suse.br : # useradd suse.br useradd: invalid user name 'suse.br' I have seen all the configuration files in /etc/sysconfig, Suse DB and Google and I haven´t found anything related to this topic. =(( -- ========================= José Mário Viana Analista de Sistemas SecrelNet Infomática Ltda ========================= -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

2 1