November 2002 - openSUSE Security - openSUSE Mailing Lists

SuSE & The 2.2.19 kernel
by Mark Tinka 15 Nov '02

15 Nov '02

hi all... over the last 3 major SuSE Linux releases, the 2.4 kernel has become the default kernel.. for performance reasons, i have certain services the i run on the 2.2.19 kernel because they are much faster than when i use the 2.4 kernel.... i am running this 2.2.19 kernel on the SuSE 8.0 release, and i have no problems at all.. since the default 2.2.19 kernel that comes with earlier versions of the SuSE, up to SuSE Linux 7.3 i guess, has no support for some options, i had to recompile the kernel using the lx_sus22 RPM from the SuSE FTP server that has the SuSE-customised 2.2.19 kernel sources..... now, i would like to know if there are going to be any compatibility, security or design issues if we continue to use the 2.2.19 kernel with later versions of SuSE Linux, including SuSE Linux 8.1, without SuSE giving that much support on the 2.2 kernel in general..?... an example of the problem would be where the ReiserFS file system has a 2.2.19 "reiserfs.o" module compiled, but SuSE Linux 8.1 has shipped with a higher or modified version of the "mkreiserfs" utility.. what happens then..?.. all help appreciated... __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com

1 0

QOS trafic shaping
by Franck 15 Nov '02

15 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lo all, Is anyone have a little script or URLs to make a trafic shaping (QOS) with cbq Thanks - -- Franck \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ franck(a)linuxpourtous.com Fingerprint : 20F4 DBE5 7234 52D6 3610 BB17 D73C 1F7A 9E64 F6A1 http://www.linuxpourtous.com Clef PGP : http://www.linuxpourtous.com/download/franck_linuxpourtous.asc \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE91RCo1zwfep5k9qERAvoZAJ9qrxDEfSyJdiSVspqnI5j6Jc29aACfcm7J sQSpCoX5uFKlIk+B8JIb3xs= =di3a -----END PGP SIGNATURE-----

2 1

AGAIN :-) SuSEFirewall2 and FreeSWAN / IPSEC Problems
by Philipp Rusch 15 Nov '02

15 Nov '02

Hello list, I don't get my VPN to work through the firewall ... Negotiation of tunnel is okay, that one gets established, but my problem is: The firewall is blocking packets from ipsec0, no matter what I define in SuSEFirewall2-rules, either it blocks packets from roadwarrior's ip address to internal IPs as "unauthorized target", if I define FW_AUTOPROTECT_SERVICES="yes", or it drops those packets, if defined as FW_AUTOROTECT_SERVICES="no" . Configuration: SuSE 8.0/Kernel 2.4.18 FreeSWAN 1.98b, new X.509 Patches SuSEFirewall2 with : NO MASQuerading at all, I don't want to masq anything (we have "real" public IP on EXTernal interface and private IPs on INTernal) FW_DEV_EXT="eth0 ipsec0" FW_ROUTE="yes" ("no" gives same result) FW_SERVICES_EXT_UDP="500" FW_SERVICES_EXT_IP="50" FW_AUTOPROTECT_SERVICES="no" Do I miss something ? TIA ! Regards from Germany, Mit freundlichem Gruß, Philipp Rusch In addition to this I asked in another thread about pptpd / VPN Hello Harald and Steffen, some days ago I asked about IPSEC and SuSEFirewall2, so do I understand you correctly, that all I should do is to MASQ the internal interface and then FORWARD_MASQ from outside to internal like in: FW_FORWARD_MASQ=${FW_FORWARD_MASQ}" 0/0,192.168.xxx.yyy,50" after modifying the Firewall-scripts according to Harald's post ? -- SNIP -- > > Steffen is right. I do it like this with SuSEFirewall: > > FW_FORWARD_MASQ=${FW_FORWARD_MASQ}" 0/0,192.168.xxx.yyy,47 " > > 192.168.xxx.yyy is my MS VPN-Server. > But I have patched the SuSEfirewall2 script: > I use the version from SuSE8.0 and this is at line about 1320: > > test "$PROTO" = tcp -o "$PROTO" = udp -o "$PROTO" = 47 || { > echo "Error: The protocol with FW_MASQ_NETS must be tcp or udp or > 47 -> $NETS" > NET2="" > } > test ! "$PROTO" = 47 -a -z "$PORT1" && { > echo "Error: Port missing in FW_MASQ_NETS -> $NETS" > NET2="" > } > You see, I just have allowed 47 for PROTO and say it is now error if > $PROTO=47 has no port. (Be carefull with the linebreaks, I use kmail!) > > Greetings > Harald > > -- > Dr. Harald Wallus > netlike-gmbh > Am Listholze 78, D-30177 Hannover > Tel: +49(0)511 90 95 1-23 Fax: +49(0)511 90 95 1-90 > Email: wallus(a)netlike-gmbh.de Internet: http://netlike-gmbh.de >

3 2

[OT] Spam to addresses used in this mailinglist
by Hatto von Hatzfeld 15 Nov '02

15 Nov '02

Just a question: Have other users got spam replies to mails sent to this mailinglist? I don't talk about the misconfigured vacation scripts, but about this ugly fraudulent (german) dialer spam. I have just got this "reply": > From: jan.seewald(a)my-mail.ch > To: hatto(a)salesianer.de > Subject: Autoreply: Re: [suse-security] Update mount - Permissions in > vfat partition > Sender: jan.seewald(a)my-mail.ch > Message-Id: <B0010547098(a)mail.my-mail.ch> > Date: Wed, 13 Nov 2002 17:03:29 +0100 The contents was an invitation by "Petra" to visit her home page somewhere on www.netmails.com, which in reality contains a dialer. Maybe she doesn't know that MS Windows dialers will not work on a Linux system? ;-) So: Have others of you got similar spam, too? (Und von Jan Seewald wüsste ich gerne, wie er dazu kommt, so etwas mir zu schicken.) Thanks, and bye, Hatto

2 1

SuSE Security Announcement: Multiple vulnerabilities in BIND8 (SuSE-SA:2002:044)
by Olaf Kirch 15 Nov '02

15 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: bind8 Announcement-ID: SuSE-SA:2002:044 Date: Wed Nov 13 17:00:00 CET 2002 Affected products: (7.0), 7.1, 7.2, 7.3, 8.0, 8.1, SuSE Linux Database Server SuSE eMail Server III, 3.1 SuSE Firewall SuSE Linux Enterprise Server for S/390 SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 SuSE Linux Office Server Vulnerability Type: remote command execution Severity (1-10): 8 SuSE default package: yes Cross References: CVE CAN-2002-1219, CAN-2002-1220, CAN-2002-1221, http://www.isc.org/products/BIND/bind-security.html http://bvlive01.iss.net/issEn/delivery/xforce/alertdetail.jsp?oid=21469 Content of this advisory: 1) security vulnerability resolved: Remote command execution in bind8 name server. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: BIND4, reports of trojanized tcpdump/libpcap 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The security research company ISS (Internet Security Services) has discovered several vulnerabilities in the BIND8 name server, including a remotely exploitable buffer overflow. Circumstancial evidence suggests that the Internet Software Consortium (maintainer of BIND) has been made aware of these issues in mid-October. Distributors of Open Source operating systems, including SuSE, were notified of these vulnerabilities via CERT approximately 12 hours before the release of the advisories by ISS and ISC on Tue, Nov 12. This notification did not include any details that allowed us to identify the vulnerable code, much less prepare a fix. Mails to ISC went unanswered for 36 hours. The SuSE security team regrets that the Internet Software Consortium has withheld vital information from the Internet community for so long, putting the majority of BIND users at risk. We would like to express our concern that the approach chosen by ISC and ISS is likely to erode trust in the security community if it becomes a model for dealing with security issues. We apologize to SuSE customers for not being able to provide timely fixes for this problem. The advisories by ISS and ISC mention the following problems in detail: 1. There is a buffer overflow in the way named handles SIG records. This buffer overflow can be exploited to obtain access to the victim host under the account the named process is running with. In order to exploit this problem, the attacker must control an existing DNS domain, and must be allowed to perform a recursive query. The impact of this vulnerability is serious. In all SuSE products, named is configured to run as user "named" by default, so a potential attacker or virus/worm does not get immediate root access. However, this is merely an additional obstacle the attacker faces. It may be possible for the attacker to exploit other, unpatched local vulnerabilities such as the recently announced traceroute hole to obtain root privilege. It may also be possible for an attacker to obtain increased privilege by manipulating the DNS zones served by the victim BIND server. We recommend to upgrade to the provided packages. If this is not possible, we recommend to restrict recursive requests as a workaround. This can be done by adding a statement such as the following to /etc/named.conf: options { ... existing options ... # Restrict recursive queries to 192.168.1.*, # except 192.168.1.254. # Order does matter. allow-recursion { !192.168.1.254; 192.168.1/24; }; }; Alternatively, you can add "recursion no;" to the options section to turn off recursion completely. 2. There are several Denial Of Service problems in BIND8 that allow remote attackers to terminate the name server process. At least one of these vulnerabilities seems to be exploitable even when the attacker is not allowed to perform recursive queries, so that the workaround suggested above is not effective against this bug. Both vulnerabilities are addressed by this update, using patches originating from ISC. Due to the severity of this issue, we will provide update packages for SuSE Linux 7.0, even though support for this product has officially been discontinued. 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 packages using the command "rpm -Fhv file.rpm" to apply the update. After updating, make sure to restart the name server process by issuing the following command as root: rcnamed restart 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/bind8-8.2.4-260.i586.r… e1c07d8c1dd74374cc37e7fa692c9de1 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/bindutil-8.2.4-260.i58… b41734970bf88aa7b5d3debbf834b78d ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/bind8-devel-8.2.4-260.… f7236e5e621725e100dbd204e2692a66 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/bind8-8.2.4-260.src.rpm 02154fbdc935a2900d70ce6a16e96543 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/bind8-8.2.4-260.i386.rpm 07bc10c5c348c560084edb3c289459c9 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/bindutil-8.2.4-260.i386.rpm 4db27e9ad4ae038d81422a0c5b9a34d0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/bind8-devel-8.2.4-260.i386.r… a1b3958e0fbaed30ddecbf7753007dbf source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/bind8-8.2.4-260.src.rpm 0b66ae2b5c462f041625919fed7ab089 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/bind8-8.2.4-261.i386.rpm fe0654b3de751533874b08a860afea5e ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/bindutil-8.2.4-261.i386.rpm 043a8c1c0bb2cc23308a614dc7bdc0fe ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/bind8-devel-8.2.4-261.i386.r… 59aca78f5aacb3ff7ecbc252eb760956 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/bind8-8.2.4-261.src.rpm 355add6397435262c597ad662e3df119 SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/bind8-8.2.3-200.i386.rpm 1072a9fe708150bc14c70a72ca42dfd3 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/bindutil-8.2.3-200.i386.rpm 0713d9b200db862110493233bc1d8321 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/bind8-devel-8.2.3-200.i386.r… c681a91b38104cf47de4f4d454136a8a source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/bind8-8.2.3-200.src.rpm 8f51737bc0c84b7be08fe3bb1d4012b4 SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/bind8-8.2.3-200.i386.rpm f2c14f81038d7ba952def27981b4599c ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/bindutil-8.2.3-200.i386.rpm 961a5403a41e8031c054a081ebf92ba5 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/bind8-8.2.3-200.src.rpm 7f3c9b95591fb22f00dc0b22cdd5fcf1 SuSE-7.0: ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/bind8-8.2.3-200.i386.rpm 0a6b9e23cefa5cd9f06660571ebf85ff ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/bindutil-8.2.3-200.i386.rpm 3a6e0e81c2d8b05ee01a2a0b9c26e9a4 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/bind8-8.2.3-200.src.rpm 1c2cb2e531fe2834de84b22ad714de68 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/bind8-8.2.4-128.sparc.rpm c08454b933ed2365d9d2ab1322803af6 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/bindutil-8.2.4-128.sparc.rpm 47e063be85fadfa2e5d0fce1746a34b5 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/bind8-devel-8.2.4-128.sparc… 46a97b033cca0a01dcb39ef90275ce46 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/bind8-8.2.4-128.src.rpm 827a7f56273c7a25ac40ffba728e9150 AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/bind8-8.2.3-139.alpha.rpm 77f39990fabacb545657236a60fecbe0 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/bindutil-8.2.3-139.alpha.rpm 33bf9f28a7c9105c84216906694c7b7c source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/bind8-8.2.3-139.src.rpm df347649fc98de695837a88452814ee6 SuSE-7.0: ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/bind8-8.2.3-139.alpha.rpm 23f307cda6a0eefb3d9f1a0439950bdd ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/bindutil-8.2.3-139.alpha.rpm 0789b49749d93ddd79192506cda00f7a source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/bind8-8.2.3-139.src.rpm 356306a7f2c079e2726b3aa8da496e9b PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/bind8-8.2.4-200.ppc.rpm 4cbeb4719625f8735ec03c27e1b27b85 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/bindutil-8.2.4-200.ppc.rpm 37fca302d72c819e713f8038d730a527 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/bind8-devel-8.2.4-200.ppc.rpm f0f5cb7b808789606448a4d472c71400 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/bind8-8.2.4-200.src.rpm 5c810e6f144d0f2875bb06d2331f50d8 SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/bind8-8.2.3-121.ppc.rpm 47fcc451954f03a915b57b500bd56c57 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/bindutil-8.2.3-121.ppc.rpm 2c0de3b64d5c3d62cb840a534911ef31 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/bind8-8.2.3-121.src.rpm 235e142413ec35bcbdb86168b04b7a78 SuSE-7.0: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/bind8-8.2.3-121.ppc.rpm 44dc01f6b4fae1dfd87874db6d42e8d9 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/bindutil-8.2.3-121.ppc.rpm d46f45bef0f12c3c5b071443ac9e7f13 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/bind8-8.2.3-121.src.rpm 1bac32496ae66d4b0e35bc34d4e500ff ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: BIND4 In addition to the vulnerabilities in BIND8 discussed above, ISS report several vulnerabilities in BIND4. As stated previously, SuSE has discontinued support for BIND4 and recommends that users upgrade to BIND8 as soon as possible. Trojaned libpcap/tcpdump There have been reports that the source packages of tcpdump and libpcap available from several FTP servers have been modified to include a trojan. We have checked our source packages for this and found them to be clean. ______________________________________________________________________________ 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: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iQEVAwUBPdN4f3ey5gA9JdPZAQFYfgf/fBA6GtBHgChwqbfDmnbp0BQWrvnJKv97 4rwnnoF2HqsHRdR6d5W8xF4EOJaedzhotTFUDmy2CWUabWdpCgac79JSQ8iI+P8G N/Uv4o5kloBuvahTk0GHDoG5HVLQCaPbLZUnAWxcYzu57oQ+HaGJTF49cVfZhVkD KCGBwMgYwpWNUNQ3QcOl8liPqrNj6K512J4AivnjkCuXO0fsiXTuR7rPg7NgZzVn BoXhyt0Hvvk1zkkMf4JMGATdl6V5t2sK3YBsKPWEnd0yB3vqNYs3LUH3ArctsUXP c6DMP9p6++OJySP+Bb6Mg3h7JCbLqBMuuElppEbcApnE6JXFhGozBQ== =GZ1Z -----END PGP SIGNATURE-----

5 6

Samba - Suse firewall
by operalight＠t-online.de 14 Nov '02

14 Nov '02

Hi, I have a problem to get samba running under susefirewall2 (SUSE8.0). The TCP port 139 is enabled in the FW rules, but if I'm running the FW in testmode I get the errormessage below. See also my firewallconfig below. Hopefully anyone is able to help - I wasted a lot of time without success. Thanks Torsten Nov 13 23:04:40 server kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth0 OUT= MAC=00:e0:7d:a2:68:29:00:10:5a:f1:4f:e1:08:00 SRC=192.168.0.22 DST=192.168.0.19 LEN=116 TOS=0x00 PREC=0x00 TTL=128 ID=37420 DF PROTO=TCP SPT=1254 DPT=139 WINDOW=32408 RES=0x00 ACK PSH URGP=0 FW_DEV_EXT="ppp0" FW_DEV_INT="eth0" FW_DEV_DMZ="" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="0/0" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_SERVICES="no" FW_SERVICES_EXT_TCP=" http https imap imaps pop3 pop3s rsync smtp ssh telnet" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_INT_TCP="139 ssh smtp domain netbios-ssn" FW_SERVICES_INT_UDP="domain syslog netbios-dgm netbios-ns" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SMB="yes" FW_FORWARD="" FW_FORWARD_MASQ="" FW_REDIRECT="" FW_KERNEL_SECURITY="no" FW_STOP_KEEP_ROUTING_STATE="no" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="no" FW_ALLOW_PING_EXT="no" FW_ALLOW_FW_TRACEROUTE="yes" FW_ALLOW_FW_SOURCEQUENCH="yes" FW_ALLOW_FW_BROADCAST="yes" FW_IGNORE_FW_BROADCAST="no" FW_ALLOW_CLASS_ROUTING="no"

6 15

Request of servers wins and servers dns, By VPN PPTP
by Fabio Sena 14 Nov '02

14 Nov '02

Good Night gentlemen, Favours the tips of the gentlemen I obtained, to make a Server VPN in SuSE with PPTP, already I obtain the VPN, only that when I receive the IP from creaks it specified in the VPN server, I do not obtain to make nothing, Therefore my request of ms-dns, ms-wins is DROPs for the FW, for Anti-spoofing, some of the gentlemen knows as I can decide this? In mine opitions.pptp, is with the options of ms-dns and ms-wins, is necessary? or the Client Vpn would assume this automatically? Fabio Sena Brasil-PE

1 0

PAM userdb
by Togan Muftuoglu 14 Nov '02

14 Nov '02

Hi I am trying to create virtual users as explaind in the vsftpd EXAMPLES I have done evryhing per the steps but when I try to login via the virtual user here defined in the ftplogins.txt is the message I get vsftpd: PAM unable to dlopen(/lib/security/pam_userdb.so) vsftpd: PAM [dlerror: /lib/security/pam_userdb.so: undefined symbol: __db_ndbm_open] Here are the steps I did db_load -T -t hash -f ftplogins.txt /etc/sunftp_login.db chmod 600 /etc/sunftp_login.db add the two lines below the TM remark /etc/pam.d/vsftpd so it looks like this #%PAM-1.0 # Uncomment this to achieve what used to be ftpd -A. # auth required pam_listfile.so item=user sense=allow # file=/etc/ftpchroot onerr=fail auth required pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed # Uncomment the following line for anonymous ftp. auth sufficient pam_ftp.so auth required pam_unix.so auth required pam_shells.so account required pam_unix.so password required pam_unix.so session required pam_unix.so # NOTE TO SELF #ALL ABOVE IS DEFAULT EXCEPT ANONYMOUS #added by TM for VSFTP Virtual User auth required pam_userdb.so db=/etc/sunftp_login account required pam_userdb.so db=/etc/sunftp_login VSFTP : vsftpd-1.1.0-3 taken from people/mmj db-utils: db-utils-3.1.17-121 PAM : pam-0.75-57 I found one message where it is the same problem (yet pam version is lower) http://www.redhat.com/mailing-lists/pam-list/msg05292.html Now Any ideas either to solve this or any workarounds to give virtual users upload ability (not anonymous) -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx

1 0

SuseFirewall2 DMZ
by Frédéric Poulet 14 Nov '02

14 Nov '02

Hi, I set up a ftp server on my server, i see it from my firewall but not from internet and from intern network ! Somebody has an idea ? ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 11

Re: [suse-security] MS Vpn Server pptp in SuSE 8.0
by Steffen Dettmer 14 Nov '02

14 Nov '02

* Hannu Hirvonen wrote on Tue, Nov 12, 2002 at 12:20 +0200: > On Tuesday 12 November 2002 12:12, you wrote: > > What does that mean? I thing, it should be no problem to open > > protocol 47 with iptables. > > That is protocoll 47, not port 47. You know, protocoll 1 is ICMP, protocoll 6 > is TCP, protocoll 17 is UDP etc., 47 is GRE (General Routing Encapsulation). Yes, I know that we don't talk about TCP or UDP ports but about IP protocols. My man iptables reads as it follows: -p, --protocol [!] protocol The protocol of the rule or of the packet to check. The specified protocol can be one of tcp, udp, icmp, or all, or it can be a numeric value, So I would expect "--protocol 47" to match any IP protocol 47, (of course without any content inspection). With ipchains, I'm sure that this works for protocol 50 (IPSec ESP) as I use it in production :) oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.

3 3