openSUSE Security May 2004

security@lists.opensuse.org

85 participants
72 discussions

SUSE Security Announcement: mc (SuSE-SA:2004:012)
by thomas＠suse.de 14 May '04

14 May '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: mc Announcement-ID: SuSE-SA:2004:012 Date: Friday, May 14th 2004 16:00 MEST Affected products: 8.0, 8.1, 8.2, 9.0, 9.1 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7, 8 SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: local privilege escalation Severity (1-10): 3 SUSE default package: yes Cross References: CAN-2004-0226 CAN-2004-0231 CAN-2004-0232 Content of this advisory: 1) security vulnerability resolved: - buffer overflows - tmp file problems - format string bugs problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - sharutils - apache2* - xine* - sysconfig - clamav - exim - utempter - busybox - monit - ethereal - kphone 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The Midnight Commander (mc) is a file manager for the console. The mc code is vulnerable to several security related bugs like buffer overflows, incorrect format string handling and insecure usage of temporary files. These bugs can be exploited by local users to gain access to the privileges of the user running mc. There is no workaround known other then avoid using mc. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mc-4.6.0-327.i586.rpm c5ad0c60348bc462db2d71735247ee1d patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mc-4.6.0-327.i586.patc… 850b02c3908588ae83afd5027add43ec source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/mc-4.6.0-327.src.rpm 71c511d7bfbf7cc285aed54e164e4077 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mc-4.6.0-327.i586.rpm c12550eca593946915b2bf39759e78d1 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mc-4.6.0-327.i586.patc… 8879832d99052ac11fc40423027f4bb4 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/mc-4.6.0-327.src.rpm 585c3678406be16171b26ceaeb5600c7 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mc-4.5.55-758.i586.rpm 4fa2bd194e823ef8dce8b0ee4a7d5707 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mc-4.5.55-758.i586.pat… b22258254be06b2493d1ea39a5b97b00 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/mc-4.5.55-758.src.rpm 860f9fc3b3825031b8d7c10fbf793fcd SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap1/mc-4.5.55-758.i386.rpm bdf10b7c25fdececa1f369b0baeaa764 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap1/mc-4.5.55-758.i386.patch.rpm 7e3c66bb6f257688f858424f164e360d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/mc-4.5.55-758.src.rpm 46dd268a6e2f7c7596ed45fd9ab03c88 ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - sharutils This update fixes a buffer overflow in shar while handling the '-o' commandline option. The buffer overflow can be abused to execute commands remotely in conjunction with other systems (CGI, ...). New packages are available on our FTP servers. - apache2/-devel/-doc/-example-pages/-prefork/-perchild/-worker, apr, libapr0 These updates fix a memory leak in the mod_ssl module of apache2 (CAN-2004-0113), a possible remote DoS attack on accessing rarely used listening ports (CAN-2004-0174), and a problem with unescaped special characters in log files that could present a security hazard for terminal emulators (CAN-2003-0020). New packages are available on our FTP servers. - xine, xine-lib, xine-ui A buffer overflow exists in the xine library. Attackers could execute arbitrary code as the user utilizing the xine library. More information can be found on http://www.xinehq.de/index.php/security/XSA-2004-3. New packages are available on our FTP servers. - sysconfig This update fix the restart of the firewall after a dialup connection is established. Without this restart, all ports are closed on the dialup interface and the connection seems to be not working. This bug affects SUSE LINUX 9.1 only. New packages are available on our FTP servers. - clamav The ClamAV project recently changed the format of their virus definition database files to support detection of new sorts of viruses. This update is needed to make use of the files in the new format. New packages are available on our FTP servers. - exim The exim mailer contains a buffer overflow in its header parsing functions which may allow remote attackers to execute arbitrary code. Only installations with the "verify=header_syntax" config option enabled are vulnerable to this attack. SUSE Linux is not configured that way by default. CAN-2004-0400 has been assigned to this bug. New packages are available on our FTP servers. - utempter This updates addresses a possible symlink attack while using tty device files. This bug may lead to a local root compromise. New packages are available on our FTP servers. - busybox Busybox does not handle netlink sockets correctly, which allows local attackers to spoof netlink messages to the busybox process New packages are available on our FTP servers. - monit There exists security vulnerabilities in the monit HTTP interface, which could allow an attacker in the worst case to gain root access to the system. This issue only affects monit if monit is started with http server support. See http://www.tildeslash.com/monit/secadv_20040305.txt for details. New packages are available on our FTP servers. - ethereal Several buffer overflows in the ethereal code were fixed. These buffer overflows can be used to gain remote access to a system where ethereal is running on. (CAN-2004-0176, CAN-2004-0367, CAN-2004-036) New packages are available on our FTP servers. - kphone The kphone update fixes a possible denial-of-service attack in SIP client code. New packages are available on our FTP servers. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SUSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SUSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an 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.7 (GNU/Linux) iQEVAwUBQKTR0Xey5gA9JdPZAQEegAf9HUfimhQG0UgBPPsZMnBjubMbvlfBc/3C faIE7hm4eFrjBu77ZnI+h4lI9p5MWYNhePO3j1uYzRUDP46qMUchXP7nBw2dnbxW /LmELnz6QrmCqhXlB5l0Tkv9vGSLYA5MBRr+ZCdVqQD2oDwZ9mb/btxoY/1vgjeP KC9+S7wI/O129j5X6b1ElQCAqsFlZSq9YDzf8s4OIABeoz2Vnn0jTpfOB0fT2LxJ W6XA6P+9TMO4/inOCqZ3ytIvqHh1jDhKtsZS0nqdkAlOOuLEsP3YvM87a60h2Jlz /0aMy0ybfTnvjtETUch5KZsUdChHzRA64dbRZNSVeByF9HVFeJQmoQ== =2hkF -----END PGP SIGNATURE-----

1 0

Re: [suse-security] Suse Firewall 2 and VPN access
by Armin Schoech 14 May '04

14 May '04

Hi, > The problem came when we started to use the others company VPN > servers that give the VPN clients their own networks IP > (192.168.108.0). > > Question : > How can i allow a range of IPs from the other companies network to > go through my firewall ? > > Little net drawing : > > INET ----- other companies network -----///// FW \\\\\\ ----- my network > ... 192.168.108.0 192.168.100.0 > --> have a look at 10) in /etc/sysconfig/SuSEfirewall2. Machines inside the trusted nets are allowed to access your net. You can restrict netmask, protocol and ports to restrict access to your network. FW_TRUSTED_NETS="192.168.108.0/24" would allow full access from "other companies network" to "my network". You can also enter single addresses here if needed. See the explanatory comments in /etc/sysconfig/SuSEfirewall2 HTH, Armin -- Am Hasenberg 26 office: Institut für Atmosphärenphysik D-18209 Bad Doberan Schloss-Straße 6 Tel. ++49-(0)38203/42137 D-18225 Kühlungsborn / GERMANY Email: schoech(a)iap-kborn.de Tel. +49-(0)38293-68-102 WWW: http://armins.cjb.net/ Fax. +49-(0)38293-68-50

1 0

Suse Firewall 2 and VPN access
by Jorge Canelhas 14 May '04

14 May '04

Hi all I have my network accessing the internet using another companies network, to separate my network (192.168.100.0 on eth0) from the other companies network (192.168.108.0 on eth1) i use a linux computer with suse firewall 2 with masq suport and squid, obvious that the other companies network is on the untrusted device. The problem came when we started to use the others company VPN servers that give the VPN clients their own networks IP (192.168.108.0). Question : How can i allow a range of IPs from the other companies network to go through my firewall ? Litle net drawing : INET ----- other companies network -----///// FW \\\\\\ ----- my network ... 192.168.108.0 192.168.100.0 Thanks in advance Jorge Canelhas ------------------------- Are u a retro computing fan ? check : http://www.retroreview.com

1 0

RE: [suse-security] place for db-server
by sematin＠mtn.co.ug 13 May '04

13 May '04

Imho, since it is used both internally and externally, then it ought to be in the DMZ. It can be a potential source of compromsie from external sources if placed on the internal network. Noah. > -----Original Message----- > From: Christian Mang [mailto:cmang@wegatec.de] > Sent: 13 May 2004 10:38 > To: Suse-Security(a)Suse.Com > Subject: [suse-security] place for db-server > > > Hi List, > > I am not sure about the right place for our database server. > We have an external and an internal firewall (SuSE 9.0) with a DMZ. > The application server is used for internal and external > work. It needs a database server on its own machine. Should I > take it in the DMZ or in the internal network? What is the > (security related) best decision? > > Thanks > Christian > > > > > -- > Check the headers for your unsubscription address > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > >

2 1

place for db-server
by Christian Mang 13 May '04

13 May '04

Hi List, I am not sure about the right place for our database server. We have an external and an internal firewall (SuSE 9.0) with a DMZ. The application server is used for internal and external work. It needs a database server on its own machine. Should I take it in the DMZ or in the internal network? What is the (security related) best decision? Thanks Christian

2 1

Re: [suse-security] SuSEFirewall doesn't work?
by Manuel Balderrábano 12 May '04

12 May '04

Hil! At last I got it! I had a bad FW_MASQ_NETS. Thanks a lot, Philippe, Tom and Arjen! My problem was El Martes, 11 de Mayo de 2004 19:47, Philippe Vogel escribió: > Hello! > > > What I need is to redirect all incoming connections on port 80 to > > another computer on the DMZ. > > NIC-config for the examples: > > w.x.y.z external IP (eth0) NIC: dhcp via pppoe or static IP from provider > FW_DEV_EXT="eth0" > 192.168.0.x internal net (eth1) NIC: 192.168.0.1 > FW_DEV_INT="eth1" > 192.168.1.x dmz net (eth2) NIC: 192.168.1.1 > FW_DEV_DMZ="eth2" > > FW_MASQUERADE="yes" > FW_MASQ_NETS="192.168.0.0/24 192.168.1.0,tcp,20:22 192.168.1.0,tcp,80 > 192.168.1.0,tcp,443 192.168.1.0/24,tcp,1024:65535" > > > Example for Portforwarding with used masquerading: > > /etc/sysconfig/SuSEfirewall2: #14.): > > FW_FORWARD_MASQ="0/0,192.168.1.2,tcp,80" > > or with iptables: > > Redirect Traffic from external to Port 80 to IP 192.168.1.2 > > iptables -A PREROUTING -t nat -j REDIRECT -p tcp -i eth0 -d > 192.168.1.2 --dport 80 > > Redirect Traffic from external to Port 80 to IP 192.168.1.2 on Port 81 > > iptables -A PREROUTING -t nat -j REDIRECT -p tcp -i eth0 -d > 192.168.1.2 --dport 80 --to-ports 81 > > > Example for 192.168.0.0 - 192.168.0.255 net for transparent Proxy: > > /etc/sysconfig/SuSEfirewall2: #15.): > > FW_REDIRECT="192.168.0.0/24,0/0,tcp,80,3128" > > or with iptables: > > iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j > REDIRECT --to-port 8080 > > Philippe > > > -- > Check the headers for your unsubscription address > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > > -- --------------------------------------------------------------------------------- Manuel Balderrábano e-mail: garibolo(a)wanadoo.es ---------------------------------------------------------------------------------

1 0

yast
by cybervision8＠vsnl.net 12 May '04

12 May '04

how do i upgrade/install any pakage with yast with depancy resoveing/checking .

5 5

RV: unsubscribme
by sads 12 May '04

12 May '04

unsubscribme -----Mensaje original----- De: sads [mailto:terasis@prodigy.net.mx] Enviado el: Miércoles, 12 de Mayo de 2004 10:23 a.m. Para: suse-security(a)suse.com Asunto: unsubscribme

1 0

RE: [suse-security] yast-re
by GarUlbricht7＠netscape.net 11 May '04

11 May '04

"cybervision" wrote on Tue May 11 2004 - 17:14:03 CEST: > how do i upgrade/install any pakage with yast with dependancy > resoveing/checking on the net ,say kde 3.2 > > sorry last time i miss main subject >thx > Hi, A similar question was just asked on the SLE list: See the thread entitled: "Upgrade KDE", especially Graham Smith's answer: http://lists.suse.com/archive/suse-linux-e/2004-May/0992.html Hope this helps, Gar -- PS You need to install just about all the packages SuSE provides or you will have unresolved dependencies, but Graham Smith's answer covers that .. -- __________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp

1 0

Re: [suse-security] SuSEFirewall doesn't work?
by Arjen de Korte 11 May '04

11 May '04

On Tuesday 11 May 2004 19:10, Manuel Balderrábano wrote: > Sure! But by that option all connections will appear as comming from the > firewall. I may have totally misunderstood what you're trying to achieve. I thought you were trying to route incoming traffic to your firewall to port 80 on a machine in your DMZ and that this machine had a private (non-routable) IP. With the FW_FORWARD_MASK the source address of incoming traffic to your webserver won't be rewritten, only the destination address is. Outgoing traffic will have the source address rewritten to the IP of your firewall, but wasn't that is the whole idea about PAT? Best regards, Arjen

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

openSUSE Security May 2004