April 2003 - openSUSE Security - openSUSE Mailing Lists

SuSE distributions and CERT Advisory CA-2003-10 Integer overflow in Sun RPC XDR library routines
by Herbert Huber 03 Apr '03

03 Apr '03

Hi, maybe I've missed some discussions in this list. But can anybody from SuSE make a statement whether the SuSE distributions are vulnerable by the latest xdrmem_getbytes() integer overflow or not. Regards, Herbert

3 2

VPN with SuSE Firewall on CD 2
by Hans-Martin Flesch 03 Apr '03

03 Apr '03

Hello, I have some trouble with the configuration of VPN wiht SuSE's Firewall: I did as described in the manual ( I did it not only once...) - there is the following message: ------------ Apr 3 10:43:30 fw1 ipsec_setup: (/proc/sys/net/ipv4/conf/eth0/rp_filter = `1', should be 0) -------------------- Is it a serious problem? But pluto starts and adds the connection. When I try to connect from outside the LAN with Win2000 / ipsec-Tool from ebootis.de I can't get any connection to the VPN-Gateway. I get the message "IP-Sicherheit wird verhandelt" and nothing else. "Route Print" shows no route to our LAN... Can somebody give me a hint please?! Martin

3 4

samba-client dependency problem
by Bob Vickers 03 Apr '03

03 Apr '03

One of the SuSE security updates recently published has a dependency problem: # rpm -Fhv samba-client-2.2.3a-171.i386.patch.rpm file /usr/lib/samba/smbwrapper.so from install of samba-client-2.2.3a-171 conflicts with file from package samba-2.2.3a-169 # rpm -qf /usr/lib/samba/smbwrapper.so samba-2.2.3a-169 samba-client-2.2.3a-169 This is on an 8.0 system. Is it OK to force this update? Thanks, Bob ============================================================== Bob Vickers R.Vickers(a)cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691

3 3

Kernel update problem yet again
by Mathias Homann 03 Apr '03

03 Apr '03

the latest kernel updates are bad, not only my SuSE 8.1 with the latest update crashes when starting X11 with nvidia drivers, but my 8.0 firewall can't do frees/wan anymore because /lib/modules/`uname -r`/kernel/net/ipv4/ipsec.o is missing, and the sources from km_freeswan don't compile... bye, [MH] -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und 823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt! gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C

2 2

SuSE Security Announcement: sendmail (SuSE-SA:2003:023)
by Roman Drahtmueller 03 Apr '03

03 Apr '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: sendmail, sendmail-tls Announcement-ID: SuSE-SA:2003:023 Date: Tuesday, April 1st 2003 18:45 MEST Affected products: 7.1, 7.2, 7.3, 8.0, 8.1, 8.2 SuSE Linux Database Server, SuSE Linux Enterprise Server 7, 8 SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: local/remote privilege escalation Severity (1-10): 7 SuSE default package: yes (until SuSE Linux 8.0 and SLES7) Cross References: http://www.cert.org/advisories/CA-2003-12.html Content of this advisory: 1) security vulnerability resolved: sendmail, sendmail-tls problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - glibc - vnc - openssl 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information sendmail is the most widely used mail transport agent (MTA) in the internet. A remotely exploitable buffer overflow has been found in all versions of sendmail that come with SuSE products. These versions include sendmail-8.11 and sendmail-8.12 releases. sendmail is the MTA subsystem that is installed by default on all SuSE products up to and including SuSE Linux 8.0 and the SuSE Linux Enterprise Server 7. The vulnerability was discovered by Michal Zalewski. It is not related to the vulnerability found by ISS in the first week of March as announced by SuSE Security in SuSE Security Announcement SuSE-SA:2003:013 (CERT Announcement ID CA-2003-07). The impact is believed to be a local root compromise with the possibility of a remote compromise. Even though the remote nature of the vulnerability is not confirmed, we believe that it is safe to assume that the vulnerability may be remotely exploitable. The nature of the flaw is a stack overflow in a function that is called frequently throughout the sendmail source code. The function is used for processing email addresses. There is no known workaround for this vulnerability other than using a different MTA. The vulnerability is triggered by an email message sent through the sendmail MTA subsystem. In that respect, it is different from commonly known bugs that occur in the context of an open TCP connection. By consequence, the vulnerability also exists if email messages get forwarded over a relay that itself does not run a vulnerable MTA. This specific detail and the wide distribution of sendmail in the internet causes this vulnerability to be considered a flaw of major severity. We recommend to install the update packages that are provided for download at the locations listed below. 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 performing the update, it is necessary to restart all running instances of sendmail using the command "rcsendmail restart" as root. Intel i386 Platform: SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/sendmail-8.12.6-109.i5… bb987c277374db2cf5ec81b7abe9a476 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/sendmail-8.12.6-109.i5… f90dc4e6f63b5c4e368e5db2fe7d09be source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/sendmail-8.12.6-109.src… dd838b1089f6686a1107e6d8159b1f98 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/sendmail-8.12.3-75.i386.rpm 9e6949e973085ae3b628c52cadcc2c9e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/sendmail-8.12.3-75.i386.patc… dac55a8afcb2487b8b80549b9a4d7b38 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/sendmail-8.12.3-75.src.rpm f6e8297e885d367a73ff9010a6cbb297 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/sendmail-8.11.6-164.i386.rpm 7591a1d397e161225b4d594bcfc5bb02 ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/sendmail-tls-8.11.6-166.i3… 52c213438e8782af09a4395d402d1fea source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/sendmail-8.11.6-164.src.rpm a7b6f85673913089758f0ef0208aac6a ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/sendmail-tls-8.11.6-166.src… 96cbfc4f2d85bdae71196ee80a4ebbd3 SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/sendmail-8.11.3-108.i386.rpm b107d5a44b234222de7e5fcb7998c192 ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/sendmail-tls-8.11.3-112.i3… 78a987bd0a38d067a8cffd6c6003abd8 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/sendmail-8.11.3-108.src.rpm 0a86a2d3158110479c44c6b8a09f2bb6 ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/sendmail-tls-8.11.3-112.src… acf234a4fa14d9d078df10cd774da0ce SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/sendmail-8.11.2-45.i386.rpm abec9a5d08d89cabc662708b38cadfad ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec2/sendmail-tls-8.11.2-47.i38… 36ab02484b69d9f6ac9d58b78cc0569d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/sendmail-8.11.2-45.src.rpm e7e267fbb800277472f797f351796c6d ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/sendmail-tls-8.11.2-47.src.… 83b8fae134f192c53fa32c2d73f8dc8c Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/sendmail-8.11.6-65.sparc.rpm f3a9cff90e3ac9493bcab36b11dc692c ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/sendmail-tls-8.11.6-65.sp… 63c14d646d8046df26c2899c0886bb24 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/sendmail-8.11.6-65.src.rpm 7f01e6aa454231f35f6ee50958bb6f29 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/sendmail-tls-8.11.6-65.src… e9086795f386471e6b2476febb419aa0 AXP Alpha Platform: SuSE-7.1: Limited package building resources are delaying the availiability of update packages for the SuSE Linux 7.1 for Alpha distribution. PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/sendmail-8.11.6-123.ppc.rpm 1dd1154f1b9ede1dc003be26919b4d23 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/sendmail-tls-8.11.6-122.ppc… a83a7f0885deb049a5a63d8114e47af4 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/sendmail-8.11.6-123.src.rpm 2a199a60d825c8d3d2a1514fb58aea59 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/sendmail-tls-8.11.6-122.src.… 621c390fbb8c44ffb1764d369c096d3f SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/sendmail-8.11.2-34.ppc.rpm c1657f4dbc2f4967fb3ca04c17e2f1f3 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec2/sendmail-tls-8.11.2-38.ppc.… 7f564cc83d85970cd7c0f61896c916e6 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/sendmail-8.11.2-34.src.rpm bd749453da2ff7513f09798d8b0b2e56 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/sendmail-tls-8.11.2-38.src.r… 1c347e9052b1b7dd02ae6630c56445db ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - glibc SuSE Security is working on glibc updates for the RPC XDR integer overflow security problem in glibc. The central function of the glibc package in a Linux system requires extensive testing of the update packages. The update packages will be provided for download at the usual location and publically announced as soon as the testing is completed successfully. - vnc VNC (Virtual Network Computing) uses a weak cookie generation process which can be exploited by an attacker to bypass authentication. New packages are currently being tested and will be available on our FTP servers soon. - openssl A paper regarding remote timing attacks against OpenSSL has been published by researchers of the Stanford University. It is possible to extract the private RSA key used by services using OpenSSL by observing their timing behavior. Fixed packages will be available on our FTP servers 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----- Roman Drahtmüller, SuSE Security. - -- - - | Roman Drahtmüller <draht(a)suse.de> // "You don't need eyes to see, | SuSE Linux AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: 2.6.3in Charset: noconv iQEVAwUBPonCaHey5gA9JdPZAQHVjQgAmVxPZOj3YOGkPYHvAOxIWd6LI29BcbtF 7OYY9j7qofdZdHmAjYS/tW9SveuhoOzWNrZYWMKUSpFZoy5hkqYkVa9MPtTgKRST +Yle2PM2KrNzvUdEYeNypD4feE7qZKmO3XVub5j53bPYEa6dOWCrF7UrOv1LPnGE x7Ffn9eYQW09Xqs9xp5GSJevz7qN2KT5XS76/XWqQgc3Pv8BXEAYZTISe8xk6dOc vjgQx7AcmZBLVV3fl+hF4OgTgT0vBcDxta8t1Fm0YexP2h/ObKBWvo8pV4gDAmBT esitAhzgU0dbEl3JkueOjqLs7JM09MESi/tqu2aOM1EgL/onSJi3Xw== =x4bK -----END PGP SIGNATURE-----

8 10

Sendmail update RPM (not necessarily a security matter...)
by Matt Gibson 03 Apr '03

03 Apr '03

[SuSE 7.2] Every time I use YOU to install a sendmail update, I end up with both sendmail and sendmail-TLS packages installed? Is this meant to happen? It causes a warning about the conflict when I use the "install software" option in YaST. Last time it happened, I removed sendmail-TLS and re-applied the sendmail package (from the update directory on the SuSE FTP server) -- are there any implications of this? Will I end up with the right sendmail binary? Thoughts, folks? Thanks, Matt -- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon

2 1

ip6tables
by Jon Hoffman 03 Apr '03

03 Apr '03

Hello, I have just finished setting up a 6to4 tunnel to start using IPv6. But I am trying to find a decent ip6tables tutorial/howto/sample firewalls...... But I am not having very much luck. Does anyone know of any good web sites for ip6tables? Thanks in advance. Jon Hoffman

2 1

Problem with firewall2
by Wolfgang Eul 02 Apr '03

02 Apr '03

Hi there! I'm using SuSE 8.0, now with SuSEfirewall2. It serves as a Router, File-, eMail- and Webserver. No problem so far. I use a DynDNS dynamic host adress (someone.ath.cx) and DSL - still no problem. Only when I try to connect (e.g. with a webbrowser) from inside the network to the dynamic hostname, there is a problem: nothing happens, no pages are shown. If i use the internal name of the server (linux1.net.intern), it works. If i try to ping the dynamic host name (someone.ath.cx), i get errors. On the server itself, this works. I guess, there is something that must be configured inside the firewall... Or is there a chance to use the local DNS to avoid the routing of the dynamic adress outside the server? Yours, Wolfgang

2 1

[suse-security] amavis/antivir update problem
by Markus Kohli 02 Apr '03

02 Apr '03

Hello List I'm using amavis with antivir (h+bedv) on 8.1. Today my update-cronjob delivered the following: ---------------------snip-------------------------------------------------- AntiVir has an update problem. A newer version of the following file(s) is available, however your license will not work correctly with the new version. You probably need to renew your license. --> /usr/lib/AntiVir/antivir --> /usr/lib/AntiVir/antivir.vdf AntiVir has NOT been updated. ---------------------snip----------------------------------------------------- I've checked the antivir-website, but haven't found anything about a new license... Is this just tactics and I'll have to go buy SuSE 8.2, or can I resolve this problem somehow? Sorry if I'm addressing the wrong list, but I don't feel like subscribing to yet another one just for this question. Kind regards Markus -- Blue-shifted: the only way to travel.

6 10

IPTables-Problem
by lars 02 Apr '03

02 Apr '03

Hi there, someone who can give me an advice for my firewallscript? Suse Linux 8.1 Kernel 2.4.19 -- in /etc/sysconfig and-so-on all Susefirewall, suseconfigs deleted. Gateway with eth0 = extern, eth1 = intern. I took a book about firewall-design as blueprint and then adpted it to our situation here. the machine should be a router between a private network and the internet. i can do pop, http et.al. with policy set to iptables -P OUTPUT/FORWARD/INPUT ACCEPT with policy set to iptables -P O/F/I DROP nothing works except icmp; no dns, no http, no pop or smtp. I can set the icmp-chain to DROP and then pinging from the gateway is disabled, so the rules basically seems to work well. with iptables -P ACCEPT on all 3 chains everything works fine; but what about security then? i´m a bit confused about that; anyone a suggestion what my fault might be. !!The use of iptables -P .... DROP at the beginning as well as at the end of the script was recommended by the author of the book, Wolfgang Barth!! here´s the entire script: echo ³firewall initialising² # variables iptables="/usr/sbin/iptables" ex="eth0" in="eth1" ns="x.x.x.x" # Default Policy: $iptables -P INPUT DROP $iptables -P FORWARD DROP $iptables -P OUTPUT DROP # flush everything $iptables -F $iptables -t nat -F # NAT $iptables -X # local $iptables -A OUTPUT -o lo -j ACCEPT $iptables -A INPUT -i lo -j ACCEPT # Forwarding and Masquerading $iptables -t nat -A POSTROUTING -o $ex -j MASQUERADE echo 1 > /proc/sys/net/ipv4/ip_forward # connections $iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT $iptables -A INPUT -m state --state NEW,INVALID -j DROP # icmp $iptables -A OUTPUT -p ICMP --icmp-type echo-request -j ACCEPT $iptables -A INPUT -p ICMP --icmp-type echo-request -j ACCEPT # Nameserver $iptables -A FORWARD -i $in -o $ex -m state --state NEW,ESTABLISHED,RELATED -d $ns -j ACCEPT $iptables -A FORWARD -i $ex -o $in -m state --state NEW,ESTABLISHED,RELATED -s $ns -j ACCEPT # HTTP $iptables -A FORWARD -i $in -o $ex -m state --state NEW,ESTABLISHED,RELATED -p TCP --dport http -j ACCEPT # POP und SMTP $iptables -A FORWARD -i $in -o $ex -m state --state ESTABLISHED,RELATED -p TCP --dport http -j ACCEPT $iptables -A FORWARD -i $ex -o $in -m state --state ESTABLISHED,RELATED -p TCP --dport http -j ACCEPT # the remainder: $iptables -A FORWARD -o $ex -j LOG --log-level info --log-prefix out_ $iptables -A FORWARD -i $ex -j LOG --log-level info --log-prefix in_ $iptables -A INPUT -j DROP $iptables -A FORWARD -j DROP $iptables -A OUTPUT -j DROP echo ³firewall up² -- http://www.ruebenschweine.de Try also: http://www.warzenpower.de +++ http://www.lars-und-sandra.de +++ http://www.r100rt.de Diese email wurde automatisch generiert, Sie können deshalb nicht darauf antworten; webmaster(a)warzenpower.de

1 0

RE: [suse-security] Kernel Panic after Security Update
by Habichtsberg, R. 02 Apr '03

02 Apr '03

Hi, after Radu Voicu (thanks to him) gave me hints to install the 2.4.19 updates including modulils-2.4.19 onto SuSE 8.0 I did so on one server with the k_deflt version. That server seems to work (I'm not really sure because in this moment I have to note that the server is in swapping state and doesn't do much more. I started a dbimport which a week before didn't cause any problem). On another server I installed the k_smp-2.4.19 version of the update because from the default SuSE 8.0 installation it was the k_smp-2.4.18 version installed here. Unfortunately this failed completely: The server didn't start again. (Hangs when trying to load teh kernel). My solution I thought hopefully of was to install the complete SuSE 8.2 Paket. I'm not sure if it is the best way out if this kernel update misery (look my postings before). Mit freundlichen Grüßen, Reinhard Habichtsberg, Unilux AG IT-Systemverwaltung Tel.: +49 6578 189 281 Fax.: +49 6578 189 229 mailto:reinhard.habichtsberg@unilux.de > -----Original Message----- > From: Radu Voicu [SMTP:suse@ploiesti.rdsnet.ro] > Sent: Tuesday, April 01, 2003 3:23 PM > To: Habichtsberg, R. > Subject: Re: [suse-security] Kernel Panic after Security Update > > Well... that's why I give you my address as an alternative... so you can be > sure about things you want to install... > > Anyway, I am glad I could help. > > Regards, > Radu > > ----- Original Message ----- > From: "Habichtsberg, R." <reinhard.habichtsberg(a)unilux.de> > To: "Radu Voicu" <suse(a)ploiesti.rdsnet.ro> > Sent: Tuesday, April 01, 2003 3:47 PM > Subject: RE: [suse-security] Kernel Panic after Security Update > > > Hi Radu, > > only for info: > ftp://213.157.173.130/suse/8.1/suse/i586/modutils-2.4.19-37.i586.rpm > That link didn't work for me. I took the rpm-file form the SuSE Server. > > Kindly reagard,, > Reinhard Habichtsberg, Unilux AG > IT-Systemverwaltung > Tel.: +49 6578 189 281 Fax.: +49 6578 189 229 > mailto:reinhard.habichtsberg@unilux.de > > > > -----Original Message----- > > From: Radu Voicu [SMTP:suse@ploiesti.rdsnet.ro] > > Sent: Monday, March 31, 2003 3:08 PM > > To: Habichtsberg, R. > > Subject: Re: [suse-security] Kernel Panic after Security Update > > Importance: High > > > > well, it's rather simple... you took the compiled kernel from FTP (I > <SNIP> >

1 0

problem with SQUID
by payam payami 02 Apr '03

02 Apr '03

Hi, I use suse 7.3 Internal network connect to internet by setting port 3128 in IE but when i set in squid.conf for authenticate_program that get windows login for users, IE don't get any windows and Internal network (clients) connect to internet normally without login I set these options in squid.conf: authenticate_program /usr/sbin/pam_auth acl password proxy_auth payam acl users src 192.168.1.0/255.255.252.0 http_access allow users http_access allow password Is here any problem with this configuration that IE can't get windows login when want to browsing? Thanks for your help, Payam __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

7 6

iptables on SuSE 7.3, webserver and our intranet
by Manfred Rebentisch 02 Apr '03

02 Apr '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, a customer of mine is using suse 7.3 and iptables v1.2.2. The iptables command are called direct, not with SuSEfirewall. Normally I use shorewall, I am not a specialist for iptables commands, I did not write the commands, but have to support them now. The server is an internet-webserver. Because of some attacs the firewall is important. There are a postfix E-Mail-Server and there are Websites on the Server. Accessing in no problem from the internet. BUT: from the intranet we cannot call the websites and load the E-Mails from the server. I think, it is not a DNS problem, but a firewall problem. With "iptables -t nat -L" I get (names changed for public) for PREROUTING - Chain: DNAT tcp -- anywhere linus.localnet.de tcp dpt:http to:172.21.85.11 DNAT tcp -- anywhere linus.localnet.de tcp dpt:domain to:172.21.85.11 DNAT udp -- anywhere linus.localnet.de udp dpt:domain to:172.21.85.11 DNAT tcp -- anywhere linus.localnet.de tcp dpt:smtp to:172.21.85.11 DNAT tcp -- anywhere linus.localnet.de tcp dpt:pop3 to:172.21.85.11 DNAT tcp -- 172.21.85.0/24 linus.localnet.de tcp dpt:http to:172.21.85.11:80 DNAT udp -- 172.21.85.0/24 linus.localnet.de udp dpt:http to:172.21.85.11:80 DNAT tcp -- anywhere linus.localnet.de tcp dpt:smakynet to:172.21.85.11:22 ((I did not now, what "smakynet" is)). The INPUT-Chain shows (here a part of all): ACCEPT tcp -- 172.21.85.0/24 linuso.localnet.de tcp dpt:http ACCEPT tcp -- 172.21.85.0/24 linus.localnet.de tcp dpt:http ACCEPT tcp -- 172.21.85.0/24 anywhere tcp dpt:http THe OUTPUT-Chain shows (a part too): ACCEPT all -- anywhere anywhere ACCEPT tcp -- anywhere anywhere tcp dpt:http Under the POSTROUTING I get: MASQUERADE all -- 172.21.85.0/24 anywhere Which iptables command is nessacary for getting access from the intranet (172.21.85.0) to the webserver (172.21.85.11)? Many thanks in advance. Manfred Rebentisch - -- COMPARAT Software-Entwicklungs-GmbH Mobile Voice Solutions Prießstr. 16, 23558 Lübeck Tel: 0451/479 56 60 http://www.comparat.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+iJ6c385pq8Zuir4RAqcMAKCLh4sTz72LgFxT6NxQY+PbfvCNhACfWkZY V7TJBaV80T5hFIlGRQvpfTw= =hdyt -----END PGP SIGNATURE-----

2 1

Need help masquerading PPTP/GRE
by Brian Topping 01 Apr '03

01 Apr '03

Good day all! I'm having some issues with my masquerading setup. I moved the machine to a new IP address, and masquerading for PPTP/GRE suddenly stopped working from the outside. I've sniffed packets, the authentication is happening fine and the initial GRE is sent from the client to the server, but the GRE never passes over the masquerade. I've enclosed my SuSEFirewall2 config below. Can anyone assist? I believe the problem may have to do with the fact that the router was up for 311 days before i moved it to the new ip address and there must have been some change which only showed up after reboot. To be sure, I've pulled down the 2.1 version of SuSEfirewall2, and I am running a 2.4.10 kernel from the 7.3 distro. Thanks kindly, Brian i=============i # ########### # Scenario 4: # This company has got a more complex setup: # # Internet # | # | Webserver # | | # SuSE-Firewall------- # | # |---Mailserver # | # |---Database # | # Internal LAN # # All Mail is delivered to the firewall. It also provides DNS service to # internal and external. # There's a DMZ where a Webserver resides (port 80 and port 443) which # needs # to connect to the Firewall to deliver mail to internal, send syslog # messages and do domain lookups. It needs also direct access to the # internal # database (bad idea!). # All mail which is delivered to the firewall, is sent to the internal # mailserver. The mailserver sends all mail to the internet to the # firewall. # Internal PCs which access the internet should be masqueraded. # external fw interface: eth2 # dmz fw interface: eth1 # internal fw interface: eth0 # ip of database: 192.168.1.3, tcp port for database is 4545 # ip of webserver: 200.200.200.200 (this is an official, assigned # address!) # internal LAN: 192.168.1.0 netmask 255.255.255.0 # # TODO: the nameserver on the firewall needs to be setup # "split-brained". See # the DNS How-to. The mailserver on the firewall needs to be setup as a # forwarder/relayer. The mailserver on the internal network gets the # firewall # as forwarder/relay configured. START_FW2="yes" FW_CUSTOMRULES="/etc/rc.config.d/firewall2-custom.rc.config" FW_DEV_EXT="eth0" FW_DEV_DMZ="eth1" FW_DEV_INT="eth2" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="192.168.0.0/24" FW_SERVICES_EXT_TCP="22 25 53 123" FW_SERVICES_EXT_UDP="53 123" FW_SERVICES_DMZ_TCP="25 53" FW_SERVICES_DMZ_UDP="53 123 514" FW_SERVICES_INT_TCP="22 25 53 80 123" FW_SERVICES_INT_UDP="53 123" FW_SERVICE_DNS="yes" DNS_PORT="53" #FW_FORWARD_MASQ="61.0.0.0/8,192.168.0.100,tcp,8888 0/0,192.168.0.2,tcp,1723 0/0,192.168.0.2,tcp,443 " FW_FORWARD_MASQ="0/0,192.168.0.100,tcp,8888 0/0,192.168.0.2,tcp,1723 0/0,192.168.0.2,tcp,443 " FW_FORWARD="204.152.97.10,0/0,tcp,80 204.152.97.10,0/0,tcp,21 192.168.1.100,204.152.97.10 204.152.97.10,192.168.1.100 204.152.97.10,192.168.0.11,tcp,3306 204.152.97.10,192.168.0.11,tcp,11009 0/0,204.152.97.10,tcp,25 204.152.97.10,0/0,tcp,25 0/0,204.152.97.0/24,tcp,22 0/0,204.152.97.0/24,tcp,21 0/0,204.152.97.0/27,tcp,80 0/0,204.152.97.10,tcp,443 0/0,204.152.97.11,tcp,443 204.152.97.10,0/0,tcp,110" FW_INPUT="0/0,204.152.97.1,udp,53" FW_ALLOW_PING_DMZ="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" # # 7.) # Do you want to protect the firewall from the internal network? # REQUIRES: FW_DEV_INT # # If you set this to "yes", internal machines may only access services # on # the machine you explicitly allow. They will be also affected from the # FW_AUTOPROTECT_SERVICES option. # If you set this to "no", any user can connect (and attack) any service # on # the firewall. # # Choice: "yes" or "no", defaults to "yes" # # "yes" is a good choice FW_PROTECT_FROM_INTERNAL="no" # # 8.) # Do you want to autoprotect all running network services on the # firewall? # # If set to "yes", all network access to services TCP and UDP on this # machine # will be prevented (except to those which you explicitly allow, see # below: # FW_SERVICES_{EXT,DMZ,INT}_{TCP,UDP}) # # Choice: "yes" or "no", defaults to "yes" # FW_AUTOPROTECT_SERVICES="no" # For VPN/Routing which END at the firewall!! FW_SERVICES_DMZ_IP="" FW_SERVICES_EXT_IP="" # For VPN/Routing which END at the firewall!! FW_SERVICES_INT_IP="" # # 10.) # Which services should be accessible from trusted hosts/nets? # # Define trusted hosts/networks (doesnt matter if they are internal or # external) and the TCP and/or UDP services they are allowed to use. # # Choice: leave FW_TRUSTED_NETS empty or any number of computers and/or # networks, seperated by a space. e.g. "172.20.1.1 172.20.0.0/16" # Optional, enter a protocol after a comman, e.g. "1.1.1.1,icmp" # Optional, enter a port after a protocol, e.g. "2.2.2.2,tcp,22" # FW_TRUSTED_NETS="" # # 12.) # Are you running some of the services below? # They need special attention - otherwise they won´t work! # # Set services you are running to "yes", all others to "no", defaults to # "no" # FW_SERVICE_AUTODETECT="no" # Autodetect the services below when starting # # if you use dhclient to get an ip address you have to set this to "yes" # ! FW_SERVICE_DHCLIENT="no" # # set to "yes" if this server is a DHCP server FW_SERVICE_DHCPD="no" # # set to "yes" if this server is running squid. You still have to open # the # tcp port 3128 to allow remote access to the squid proxy service. FW_SERVICE_SQUID="no" # # set to "yes" if this server is running a samba server. You still have # to open # the tcp port 139 to allow remote access to SAMBA. FW_SERVICE_SAMBA="no" # # 15.) # Which accesses to services should be redirected to a localport on the # firewall machine? # # This can be used to force all internal users to surf via your squid # proxy, # or transparently redirect incoming webtraffic to a secure webserver. # # Choice: leave empty or use the following explained syntax of # redirecting # rules, seperated by a space. # A redirecting rule consists of 1) source IP/net, 2) destination # IP/net, # 3) protocol (tcp or udp) 3) original destination port and 4) local # port to # redirect the traffic to, seperated by a colon. e.g.: # "10.0.0.0/8,0/0,tcp,80,3128 0/0,172.20.1.1,tcp,80,8080" # FW_REDIRECT="" # # 16.) # Which logging level should be enforced? # You can define to log packets which were accepted or denied. # You can also the set log level, the critical stuff or everything. # Note that logging *_ALL is only for debugging purpose ... # # Choice: "yes" or "no", FW_LOG_*_CRIT defaults to "yes", # FW_LOG_*_ALL defaults to "no" # FW_LOG_DROP_CRIT="yes" # FW_LOG_DROP_ALL="yes" # FW_LOG_ACCEPT_CRIT="yes" # FW_LOG_ACCEPT_ALL="yes" # # only change/activate this if you know what you are doing! FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" # # 17.) # Do you want to enable additional kernel TCP/IP security features? # If set to yes, some obscure kernel options are set. # (icmp_ignore_bogus_error_responses, icmp_echoreply_rate, # icmp_destunreach_rate, icmp_paramprob_rate, icmp_timeexeed_rate, # ip_local_port_range, log_martians, mc_forwarding, mc_forwarding, # rp_filter, routing flush) # Tip: Set this to "no" until you have verified that you have got a # configuration which works for you. Then set this to "yes" and keep it # if everything still works. (It should!) ;-) # # Choice: "yes" or "no", defaults to "yes" # FW_KERNEL_SECURITY="no" # # 18.) # Keep the routing set on, if the firewall rules are unloaded? # REQUIRES: FW_ROUTE # # If you are using diald, or automatic dialing via ISDN, if packets need # to be sent to the internet, you need to turn this on. The script will # then # not turn off routing and masquerading when stopped. # You *might* also need this if you have got a DMZ. # Please note that this is *insecure*! If you unload the rules, but are # still # connected, you might your internal network open to attacks! # The better solution is to remove "/sbin/SuSEfirewall2 stop" or # "/sbin/init.d/firewall stop" from the ip-down script! # # # Choices "yes" or "no", defaults to "no" # FW_STOP_KEEP_ROUTING_STATE="no" # # 19.) # Allow (or don't) ICMP echo pings on either the firewall or the dmz # from # the internet? The internet option is for allowing the DMZ and the # internal # network to ping the internet. # REQUIRES: FW_ROUTE for FW_ALLOW_PING_DMZ and FW_ALLOW_PING_INTERNET # # Choice: "yes" or "no", defaults to "no" if not set # FW_ALLOW_PING_FW="yes" # FW_ALLOW_PING_EXT="no" ## # END of rc.firewall ## # # #-------------------------------------------------------------------------# # # # EXPERT OPTIONS - all others please don't change these! # # # # #-------------------------------------------------------------------------# # # # # 20.) # Allow (or don't) ICMP time-to-live-exceeded to be send from your # firewall. # This is used for traceroutes to your firewall (or traceroute like # tools). # # Please note that the unix traceroute only works if you say "yes" to # FW_ALLOW_INCOMING_HIGHPORTS_UDP, and windows traceroutes only if you # say # additionally "yes" to FW_ALLOW_PING_FW # # Choice: "yes" or "no", defaults to "no" # FW_ALLOW_FW_TRACEROUTE="yes" # # 21.) # Allow ICMP sourcequench from your ISP? # # If set to yes, the firewall will notice when connection is choking, # however # this opens yourself to a denial of service attack. Choose your poison. # # Choice: "yes" or "no", defaults to "yes" # FW_ALLOW_FW_SOURCEQUENCH="yes" # # 22.) # Allow/Ignore IP Broadcasts? # # If set to yes, the firewall will not filter broadcasts by default. # This is needed e.g. for Netbios/Samba, RIP, OSPF where the broadcast # option is used. # If you do not want to allow them however ignore the annoying log # entries, # set FW_IGNORE_FW_BROADCAST to yes. # # Choice: "yes" or "no", defaults to "no" # FW_ALLOW_FW_BROADCAST="no" # FW_IGNORE_FW_BROADCAST="yes" # # 23.) # Allow same class routing per default? # REQUIRES: FW_ROUTE # # Do you want to allow routing between interfaces of the same class # (e.g. between all internet interfaces, or all internal network # interfaces) # be default (so without the need setting up FW_FORWARD definitions)? # # Choice: "yes" or "no", defaults to "no" # FW_ALLOW_CLASS_ROUTING="no"

1 1

Question about updated suse kde packages
by BoneMachine 01 Apr '03

01 Apr '03

Hi list, Recently SuSE created new packages for KDE. In the description on the site SuSE mentiones "Fixes security issues due to possible buffer overflows and missing shell quotings." What buffer overflows and what shell quotings are this? Can somebody please give some sort of reference like a CAN/CVE identifier or a CERT advisory related to these issues ? kind regards, Bone Machine --- "Everything is gonna burn, we all take turns, I get mine to" - The Pixies ---

2 1

vsftpd (too secure for me)
by Mario Neubert 01 Apr '03

01 Apr '03

Hello list, does anyone know, how can I show dotted(hidden) files in a ftpclient. Users on my server with vsftpd should can access files like .htaccess. Thanks in advance Mario

3 5