September 2002 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] Suse 8.0 with SuSEfirewall2 and Samba doesn't work
by operalight＠t-online.de 18 Sep '02

18 Sep '02

----- Original Message ----- From: "Bob Sprenger" <bobo(a)tub-web.com> To: "Torsten Schaefer" <operalight(a)t-online.de> Sent: Thursday, September 19, 2002 12:30 AM Subject: AW: [suse-security] Suse 8.0 with SuSEfirewall2 and Samba doesn't work hi Bob, > ------------------------ > > FW_SERVICE_SAMBA="no" > > Meaby you need this on yes ;-) > > > ------------------------ thats what I also tried out and what also was not working. but thanks Torsten

1 0

Package sendmail-tls with openssl vulnerability?
by Hatto von Hatzfeld 18 Sep '02

18 Sep '02

After updating the OpenSSL packages (and restarting the services ) I just tested the openssl vulnerability testing tool http://CERT.Uni-Stuttgart.DE/advisories/openssl-sslv2-master/openssl-sslv2-… and I am happy about what this test says about the https (443) and the pop3s (995) ports: PATCHED: detects small overflow, but crashes (0.9.6e) But on the smtp port 25 with option -s (i.e. with TLS) I get: VULNERABLE: does not detect small overflow What's wrong? Or: How to close this hole? Thanks and bye, Hatto von Hatzfeld

1 0

Suse 8.0 with SuSEfirewall2 and Samba doesn't work
by operalight＠t-online.de 18 Sep '02

18 Sep '02

Hi, I use Suse 8 on a PC which is working as an ADSL router for a small network of 3PC's. I also want to use this PC as a Samba server for my internal Network. Without suse firewall2 the sambanet is working well. If I start the susefirewall I'm not able to use the Samba network anymore. below my config file. Can anybody help me to get this problem fixed? best regards Torsten 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 rsync 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 445" FW_SERVICES_INT_UDP="137:138" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="DNS" FW_SERVICE_AUTODETECT="no" FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SAMBA="no" FW_REDIRECT="" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="no" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" 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"

1 0

SuSE Security Announcement: xf86 (SuSE-SA:2002:032)
by Sebastian Krahmer 18 Sep '02

18 Sep '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: xf86 Announcement-ID: SuSE-SA:2002:032 Date: Wed Sep 18 12:00:00 MEST 2002 Affecte products: SuSE Linux 8.0 Vulnerability Type: local privilege escalation Severity (1-10): 5 SuSE default package: yes Cross References: http://www.xfree.org/security Content of this advisory: 1) security vulnerability resolved: LD_PRELOAD vulnerability in the X11 library problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - Perl 5.6.1 glob overflow fix - new OpenSSH packages - sparc info 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The xf86 package contains various libraries and programs which are fundamental for the X server to function. The libX11.so library from this package dynamically loads other libraries where the pathname is controlled by the user invoking the program linked against libX11.so. Unfortunately, libX11.so also behaves the same way when linked against setuid programs. This behavior allows local users to execute arbitrary code under a different UID which can be the root-UID in the worst case. libX11.so has been fixed to check for calls from setuid programs. It denies loading of user controlled libraries in this case. We recommend an update in any case since there is no easy workaround possible except removing the setuid bit from any program linked against libX11.so. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. i386 Intel Platform: SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/x1/xshared-4.2.0-174.i386.rpm 2a515055a811de5b465d016ffa77a09c ftp://ftp.suse.com/pub/suse/i386/update/8.0/x2/xdevel-4.2.0-174.i386.rpm 67ddeb24b04b8c2badb7a039d9ea270e source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/xf86-4.2.0-174.src.rpm e44b3f6dd4a406bd422adc4f7fac63f2 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - perl New Perl 5.6.1 packages will soon be available which fix overflows in the globbing code of the Perl interpreter. Although we believe that there is not much impact by this bug, we recommend an update especially on systems offering remote services based on Perl. - openssh New openssh packages are available for the SuSE Linux distributions 7.0 - 7.3 (version 2.9.9p2). These packages have been rebuilt to contain the fixes in the openssl library, which is used by openssh. It is possible but not proven that the weaknesses in the openssl code (fixed and announced by SuSE-SA:2002:027) can be exploited in any way. We release the packages to prevent the possibility that the vulnerability exists. It is recommended to install the updates. - sparc Due to a lack of build power on the sparc architecture, we will discontinue providing security updates for the SuSE Linux 7.0 and 7.1 distributions for sparc. We estimate that more than 95% of all SuSE Linux for sparc users use the most recent version 7.3 so that the loss should be considerably small. In addition to the update directories on ftp.suse.com, we will also move the directories containing the distributions themselves into the discontinued/ tree on ftp.suse.com/pub/suse/discontinued/. By consequence, all updates will continue to be available, but the path indicates that these directories and files will remain there for archiving purposes only. Please note that mirrors of the SuSE ftp server ftp.suse.com might not contain the discontinued/ directory tree. ______________________________________________________________________________ 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 iQEVAwUBPYhK03ey5gA9JdPZAQF/WQf/V8vZceiSGlfYXdbrI6E1Lw8uUzXhfrvd +I8rPf2RjaQ5/VFqt4rDMYPxjkY/ymgiFlVyZpOrj0leHuWxUH4mD7Gtej4YGi43 8L5mMBj5uKtzaP5XZM5g8P18q2ZcjjhYxSE3oZC8SdB398D/vPaOARbSxppsxqI7 yg86MwZGMxHpG8xfto0hTKqMuNilAds1VoFBDuuLiVe50RSLfsBmrEJXn6eChdkZ rj90D+SUzsUWs7p3pAgsfnpyEM8K72u17TdIenu9UXh8Z3aUDLHDZsIC37OAKpng 2SOkZOVT2pZAQF0z1sQO8zg5fDhFdUW2hKWAsJYCKRtDSJ127BmUaQ== =Gdii -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

3 2

Help for Remote detection of vulnerable OpenSSL versions
by Fred A. Miller 18 Sep '02

18 Sep '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Remote detection of vulnerable OpenSSL versions Remote detection of vulnerable OpenSSL versions RUS-CERT has developed a tool to remotely detect vulnerable OpenSSL implementations. Why is such a tool required? While the "Slapper" worm is spreading, many system administrators ask themselves whether their systems are vulnerable. Even if you apply vendor patches regularly, there are some risks which are hard to deal with: * Vendors might use OpenSSL to implement SSL services, but do not publicize it. Consequently, administrators might not know that they need to update. * Human error might leave systems vulnerable (e.g. people forget to restart services after applying patches, or are distracted by phone calls and miss a machine). * Other SSL implementations might have similar bugs. * Vendor upgrades often do not alter the version number, and their is no easy way to check if a patched version is running. * Vendor patches sometimes do not eliminate the vulnerability. As a result, full disclosure is essential; it makes independent regression testing possible. How does it work? It is difficult to tell OpenSSL 0.9.6e from vulnerable versions because the OpenSSL developers chose to terminate the process if a buffer overflow attempt is detected. Over the network, a crash due to a buffer overflow and an abrupt, but deliberate process termination look the same: in both cases, the TCP connection breaks down. At first glance, it appears that we are out of luck and cannot detect vulnerable versions. However, if we overrun the buffer by only a few bytes, the vulnerable version (without check) does not crash. This way, we can tell 0.9.6e from previous, vulnerable versions: small overflow large overflow pre-0.9.6e no crash crash 0.9.6e crash crash 0.9.6g error error (0.9.6g signals an SSL error over the network, as one would expect.) Other combinations are possible, of course, and this program tries to flag them in a reasonable way. (We consider malformed responses an indication of lack of care, and a potential security problem.) This program performs a third connection attempt (actually the first one), to test compatibility of the the SSL implementations. Obtaining and running the tool You can download a copy of the C source code here: <http://CERT.Uni-Stuttgart.DE/advisories/openssl-sslv2-master/openssl-sslv2-…> Compiling this program requires an OpenSSL development environment (including header files). You have to link this program with OpenSSL's "crypto" library (using "-lcrypto", not "-lcrypt"). On some systems, you have to link with "-ldl", too. After compilation, you can run this program using: $ ./openssl-sslv2-master [-s] host-IP [port] Then a test is performed against host-IP (an IP address in dotted-quad notation) and the TCP service running on port (a decimal number). port can be omitted, then the default port 443 is assumed. Note: You can use this program to test any SSL Version 2.0 server, not just HTTPS servers. For some services, a STARTTLS message is required to initiate the SSL handshake (e.g. SMTP, POP3, IMAP). This message is sent if you supply the "-s" option. Risks and limitations The server could crash (when the large buffer overflow is attempted), and fail to restart automatically. The program detects this, but obviously cannot undo any damage. If the server which is being tested does not support SSLv2, it often reacts in a strange way. The SSL protocol does not define a clear rejection message, so no proper diagnosis is return by the tool in such cases. To determine the cause of a handshake failure, you should use a full SSL/TLS implementation, such as "openssl s_client". Credits This program was inspired by the source code of the "Slapper" worm. Thanks to Helmut Springer for testing and spotting a few bugs. About RUS-CERT RUS-CERT <http://CERT.Uni-Stuttgart.DE/> is the Computer Emergency Response Team located at the Computing Center (RUS) of the University of Stuttgart, Germany. URL of the current version of this document: <http://cert.uni-stuttgart.de/advisories/openssl-sslv2-master.php> - -- Fred A. Miller Systems Administrator Cornell Univ. Press Services fm(a)cupserv.org, www.cupserv.org - --- SuSE Linux v8.0 Pro, KMail 1.4.3--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2ItlgACgkQB9vk4ichYXfIaQCgtRabpFtgk6YPij6e8rbV9Tj7 JMQAoKhzEdkI9YqBE9YlQkmfXR53+pjF =MVqB -----END PGP SIGNATURE-----

1 0

Re: [suse-security] SuSEfirewall2 and dyndns
by GentooRulez 18 Sep '02

18 Sep '02

You may want to FW_REDIRECT="192.168.1.0/16,name.dyn.dns,tcp,22,22" to redirect all traffic to your dnsdns-ssh directly to your internal nic. You need to reset firewall script each time your dyn-dns script refresh the dns ip entry. Yours Michael

2 1

Linux/Slapper.worm
by Rudi Koesters 18 Sep '02

18 Sep '02

Hi ! Im ask myself, if I update the package openssl, what about mod_ssl and openssh, the ssh client/server suite ? Do I have to recompile them as well ? I think both setup on openssl, and if these libraries change, both won't work anymore, or what ?? rudi

2 1

RE: [suse-security] Linux/Slapper.worm
by Alan Rouse 18 Sep '02

18 Sep '02

bliss(a)attbi.com wrote: >The SuSE announcement for SSL says it fixes the bug in CA-2002-23. Well, no it doesn't. Now maybe you think I should ASSUME that's what it means. But that is not what it says. Here's what it does say: Cross References: CAN-2002-0656, CAN-2002-0657, CAN-2002-0655, CERT Advisory CA-2002-23 Nowhere else does "CA-2002-23" appear in the announcement. Now, what does "Cross References" mean?... Back to guessing. Now, I have to decide if an email from someone at attbi.com is authoritative in answering my question... More guessing. Sorry but these discussions would not happen if things were explicitly stated instead of implied in these announcements. I'm certainly not the only one who thinks this.

2 1

how to enable ipsec over firewall?
by Jochen Staerk 18 Sep '02

18 Sep '02

Hi List, I need to have access to an external cisco VPN 5000 system from a windows box through a Suse Linux Masquarading Router (NAT to german T-DSL), the Suse Linux is 6.4 with a 2.2er kernel. In case someone knows about the 8er 2.4 kernel-firewall2-config please answer as well we might be able to update this. As far as I understand, Ip Port 50 and UDP 500 play a special role - but aren't all ports masquaraded by default? I mean, I can use HTTP, FTP (passive), HTTPS, peer to peer networking, do I have to add extra rules for 500 or 50? How do I do that? Do I need to apply a kernel patch? Thanks in advance Jochen

3 3

[suse-security] Susefirewall2 + Squid
by Andreas Meier 18 Sep '02

18 Sep '02

Hallo List, Ich habe zwei Fragen ueber Susefirewall2 ( Suse 8.0) Ich habe Squid installiert und squid nach meinen Wuenschen eingerichtet. Mein Router hat die ip 192.168.154 was muss ich jetzt hier eintragenbei FW_REDIRECT= cut from /etc/sysconfig/SuSEfirewall2 FW_SERVICE_SQUID="yes" FW_REDIRECT="0.0.0.0/8,0/0,tcp,3128" ??? Vielen Dank fuer Eure Hilfe Andreas Meier mailto:a.meier.home@gmx.net

2 1