July 2003 - openSUSE Security - openSUSE Mailing Lists

AW: [suse-security] Firewall2 log problem
by Ulrich Roth 15 Jul '03

15 Jul '03

Hi Edwin, > I just found strange problem on my server. I run > Susefirewall2 on 7.3, and i > just found that since 3 days ago my firewall didn't write the log > to /var/log/firewall and the file size is 0. I try touch > firewall to that file but still don't work. Stop the firewall, delete the file and restart the firewall. I think that will do the job. > I remember that several days ago I gz the file manually, and > remove the old firewallxxxxxx.gz to save space. Was it the cause? Probably. > Can anybody give the clue? If you move/rename a file while a process has it open for writing, this process will still write to that file. Try it out. But I don't know what happens if you zip the file. Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth(a)impact.de

2 1

SuSEfirewall2 config problem
by Kostyal Daniel 15 Jul '03

15 Jul '03

Hi. I am new with SuSEfirewall2 & iptables, and I have the following problem. I have 2 compures with SuSE 8.0. Both are running Samba and between them is a freeswan tunnel. At one end I have three LAN cards: eth0: 192.168.0.100 (local network) ; eth1: 85.136.12.19 (internet) ; eth2: 192.168.3.1 (this connects to another Linux box which is used as an Internert gateway (85.136.12.19 is used only for VPN) ). The default route is set to 192.168.3.2, to route all traffic to the internet gateway. How do I configure SuSEfirewall2? With the settings: FW_DEV_INT="eth0 eth2" FW_DEV_EXT="eth1 ipsec0" FW_ROUTE=yes FW_MASQARADE=yes FW_MASQ_NETS="192.168.0.0/24" FW_PROTECT_FROM_INTERNAL=no FW_AUTOPROTECT_SERVICES=no FW_SERVICES_EXT_TCP="22" FW_SERVICES_EXT_UDP="500" FW_SERVICES_EXT_IP="50 51" FW_SERVICES_INT_TCP="22 139" FW_SERVICES_INT_UDP="500" FW_SERVICES_INT_IP="50 51" FW_TRUSTED_NETS="192.168.0.0/24 192.168.1.0/24 85.136.12.141" # 85.136.12.141 is the other end of the tunnel SAMBA=yes FW_FORWARD="192.168.0.0/24,192.168.1.10/24 192.168.1.0/24,192.168.0.0/24" i cannot connect via ssh from the internal network and all my attempts to view the samba shares on the other end are rejected. HELP ME PLEASE

1 0

RE: [suse-security] Problems with a simple Firewall2 config
by Knut Erik Hauslo 15 Jul '03

15 Jul '03

OK... So in order to accomplish the following - i admit rather exotic configuration: - any client on the internal network (172.19.0.0/16) may access HTTP and FTP Servers on the external net - any client on the external network (192.168.1.0/24) may access HTTP server on the internal network You suggest I combine the SuSEfirewall2 with some other 3rd party solution? Something like this? 1. SuSEfirewall2: forwarding all requests from external network to my internal WEB-Server, no masquerading: FW_DEV_EXT="eth1" FW_DEV_INT="eth0" FW_ROUTE="yes" FW_SERVICE_SQUID="yes" FW_FORWARD="0/0,172.19.6.10,tcp,80" FW_TRUSTED_NETS="" # FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" remove this if using squid? FW_PROTECT_FROM_INTERNAL="no" FW_LOG_DROP_CRIT="yes" FW_LOG_ACCEPT_CRIT="no" FW_LOG_DROP_ALL="yes" FW_LOG_ACCEPT_ALL="no" FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" FW_ALLOW_PING_FW="yes" FW_IGNORE_FW_BROADCAST="yes" 2. Squid to handle all internal traffice Oh by the way, the customer mentioned that if possible, only HTTP 1.0 packets are allowed to pass the firewall/proxy.... :-S Cheers Knut Erik -----Original Message----- From: GentooRulez [mailto:paranoiac_user@freenet.de] Sent: Tuesday, July 15, 2003 2:34 PM To: suse-security Subject: Re: [suse-security] Problems with a simple Firewall2 config >There are no services ON THE FIREWALL that need to be accessed (I >allready ran into this problem ;-), they are all on serveres in either >network. Oops, i misunderstood you. >I changed my configuration, just to test. This is how (excerpt) it >looked: > FW_MASQ_NETS="172.19.0.0/16,0/0,tcp,20 172.19.0.0/16,0/0,tcp,21 >172.19.0.0/16,0/0,tcp,80" > FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" Looks good so far >Test-configuration > FW_MASQ_NETS="172.19.0.0/16" > FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" This is opening any destination port/protocol(icmp,udp,tcp) for inside boxes to get routed through the firewall. >It will work with my test-configuration, but then again, any user could >use any service on the external net, and that is not wanted only FTP >and HTTP. >How can I solve this, whitout doing something like this: > FW_MASQ_NETS="172.19.0.0/16,0/0,tcp,20 172.19.0.0/16,0/0,tcp,21 >172.19.0.0/16,0/0,tcp,80 172.19.0.0/16,0/0,tcp,1024:65535" >FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" >??? Using the firewall-script this ist the right way to limit the services to be accessed from the inside. The other way ist to disable masquaring und routing for the internal network completely and to setup following: http://www.squid-cache.org/ http://dansguardian.org/ (cacade, if you want so) and ftp-proxy from here http://www.suse.de/en/whitepapers/proxy_suite/ It is, all in all, the better and more secure solution and you can setup this fully tranparent to internal network. Hope that helps. Yours Michael

1 0

Firewall2 log problem
by M. Edwin 15 Jul '03

15 Jul '03

Hi list, I just found strange problem on my server. I run Susefirewall2 on 7.3, and i just found that since 3 days ago my firewall didn't write the log to /var/log/firewall and the file size is 0. I try touch firewall to that file but still don't work. I remember that several days ago I gz the file manually, and remove the old firewallxxxxxx.gz to save space. Was it the cause? Can anybody give the clue? TIA Edwin

1 0

SuSE Security Announcement: nfs-utils (SuSE-SA:2003:031)
by krahmer＠suse.de 15 Jul '03

15 Jul '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: nfs-utils Announcement-ID: SuSE-SA:2003:031 Date: Tue Jul 15 14:00:00 MEST 2003 Affected products: 7.2, 7.3, 8.0, 8.1, 8.2 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 SuSE Linux Desktop 1.0 Vulnerability Type: remote code execution Severity (1-10): 7 SuSE default package: yes Cross References: CAN-2003-0252 http://isec.pl/vulnerabilities/ Content of this advisory: 1) security vulnerability resolved: Off by one bug in rpc.mountd. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - xpdf/acroread - lbreakout - Eterm - gnats - unzip 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The nfs-utils package contains various programs to offer and manage certain RPC services such as the rpc.mountd. iSEC Security Research has reported an off-by-one bug in the xlog() function used by the rpc.mountd. It is possible for remote attackers to use this off-by-one overflow to execute arbitrary code as root. Some of the products listed above seem not vulnerable to this one byte overflow due to the stack alignment generated by the compiler during the build. Nevertheless, since there is no easy workaround except shutting down the RPC services, an update is strongly recommended for every product listed above. This update needs to be applied to both NFS servers and clients, as the vulnerable function is used by mountd and statd. You can either restart these services manually, or use the corresponding init scripts: "rcnfsserver restart" (for the NFS server) "rcnfs restart" (for the NFS client) Depending on your setup, it may be less disruptive to restart the two daemons manually. 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.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/nfs-utils-1.0.1-109.i5… 964386359a4280b0f64b5d06cc0debb4 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/nfs-utils-1.0.1-109.i5… 5e67e844aa5d5c9d6fb3720f388813af source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/nfs-utils-1.0.1-109.src… 91695f1d03df64188c3a63126699a811 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/nfs-utils-1.0.1-109.i5… b212711af6445cb97773e30ed4284741 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/nfs-utils-1.0.1-109.i5… 8b267ea76f715f64b8a041c2f24cee07 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/nfs-utils-1.0.1-109.src… 6da708a468ca48dd4078cbeff2c842f6 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/nfs-utils-0.3.3-178.i386.rpm 3cec45e5a7fdac0e9d6c67d894e90b16 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/nfs-utils-0.3.3-178.i386.pat… 5f86c33e9564e39df6f74c376d6d0ccd source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/nfs-utils-0.3.3-178.src.rpm f105acb95d3a770c4b142fd265bdf6a7 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/nfs-utils-0.3.1-111.i386.rpm a4c43c562fc1d9ff65367795897d5fb5 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/nfs-utils-0.3.1-111.src.rpm dc56ab3deeb7a5ed6bde4e021ff35c10 SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/nfs-utils-0.3.1-112.i386.rpm 1905a8a632eaf00dd5ad81f498ad6493 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/nfs-utils-0.3.1-112.src.rpm a048236b106c8a32bce936a39bdc0403 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/nfs-utils-0.3.1-49.sparc.rpm 176b1636fa49520b3f700d399af39203 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/nfs-utils-0.3.1-49.src.rpm 2b3cd21df36acf2b6076993855ef179f PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/nfs-utils-0.3.1-60.ppc.rpm 0af7e6f702231a3194063a2c99473bb4 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/nfs-utils-0.3.1-60.src.rpm 6b4a8ea3c5e443d255e15123dc97b0e9 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - xpdf/acroread A problem regarding handling of external URLs by various PDF readers has been reported by CERT. Attackers could execute arbitrary commands as the user viewing the document by embedding shell meta characters in URLs. The xpdf PDF viewer as shipped with SuSE is not vulnerable to this attack due to its configuration. For the acrobat PDF reader we will provide updates on our ftp servers shortly. - lbreakout Various format string bugs in the code of the game lbreakout were reported for version 2-2.5. These bugs can be exploited remotely. SuSE Linux does not ship this vulnerable version of lbreakout. - Eterm A buffer overflow in eterm while handling the environment variable ETERMPATH can lead to local privilege escalation. SuSE do not ship eterm with higher privileges. - gnats Several security bugs were reported in gnats. These bugs will be fixed and update packages will released soon. - unzip Unzip can be tricked into overwriting files by using special zip archives. Fixed 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) iQEVAwUBPxPxoney5gA9JdPZAQF5BwgAmG7dWq7GyrN/BG/hCFNVRh6fGKFDq96p 2YXtWp1iEd4wFKV0F1c4hbrh1FBIU9BZPoba9Etjoyo9yqQYLkehP1rjReklyQE4 L7YWhULlxgqCml7nxAWHYL24ji90QtSF0WYQEVVTjKu8B87rUAwDa4LosEHdyUO+ 5TCBQ7V/AGMFoys3/71mWySpoW7EhGc8FqfUR7vaM8fPRc6o8HTTaqhJMG3X395i JOa5d2L9Wcp4u86wGUxsTIciEF8ZYw0mIJDRFw+2tkkAqtesv5iHa0Qgf4ql2nM8 x+LTk8Jv7gFaaEKATpDmF7c1Un6ufBIb2fpcfCheooRqYurRqaSnpA== =39z/ -----END PGP SIGNATURE-----

1 0

RE: [suse-security] Problems with a simple Firewall2 config
by Knut Erik Hauslo 15 Jul '03

15 Jul '03

There are no services ON THE FIREWALL that need to be accessed (I allready ran into this problem ;-), they are all on serveres in either network. I changed my configuration, just to test. This is how (excerpt) it looked: FW_MASQ_NETS="172.19.0.0/16,0/0,tcp,20 172.19.0.0/16,0/0,tcp,21 172.19.0.0/16,0/0,tcp,80" FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" Test-configuration FW_MASQ_NETS="172.19.0.0/16" FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" It will work with my test-configuration, but then again, any user could use any service on the external net, and that is not wanted only FTP and HTTP. How can I solve this, whitout doing something like this: FW_MASQ_NETS="172.19.0.0/16,0/0,tcp,20 172.19.0.0/16,0/0,tcp,21 172.19.0.0/16,0/0,tcp,80 172.19.0.0/16,0/0,tcp,1024:65535" FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" ??? Cheers Knut Erik -----Original Message----- From: GentooRulez [mailto:paranoiac_user@freenet.de] Sent: Tuesday, July 15, 2003 2:04 PM To: suse-security Subject: Re: [suse-security] Problems with a simple Firewall2 config I did not check your whole config, but this came up immediately: # Which services ON THE FIREWALL should be accessible from either the internet # (or other untrusted networks), the dmz or internal (trusted networks)? FW_SERVICES_EXTERNAL_TCP="80" Check this out Michael

1 0

Antwort: [suse-security] Problems with a simple Firewall2 config
by Joachim.Winter＠malberg-edv.de 15 Jul '03

15 Jul '03

AFAIK the private Network Addresses are proteced at the external Interface. That's why you cannot get any connection from the "external". These addresses where blocked because they can be faked. mfg Joachim Winter |---------+----------------------------> | | "Knut Erik | | | Hauslo" | | | <KNUTH(a)voelcker.c| | | om> | | | | | | 15.07.2003 13:12 | | | | |---------+----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | An: <suse-security(a)suse.com> | | Kopie: | | Thema: [suse-security] Problems with a simple Firewall2 config | >------------------------------------------------------------------------------------------------------------------------------| Hi all, This should be rather easy going, but I am experiencing problems. My network looks as follows: +-- External Net 192.168.1.0/24 --> (Eth1) SuSE 8.1 Firewall2 (Eth0) <--- Internal Net 172.19.0.0/16 On my Internal Net there's a web-server, which machines on the extern net may access. Using my Sniffer i can see packets going into the internal net, but I receive nothing back, because the initiating machine sends packets with destination port 80 TCP and sources port > 1024 TCP which I have not explicitely opend. The other way around is working fine (accessing HTTP and FTP resources on the external network). The configuration file: FW_DEV_EXT="eth1" FW_DEV_INT="eth0" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="172.19.0.0/16,0/0,tcp,20 172.19.0.0/16,0/0,tcp,21 172.19.0.0/16,0/0,tcp,80" FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_PROTECT_FROM_INTERNAL="no" FW_LOG_DROP_CRIT="yes" FW_LOG_ACCEPT_CRIT="no" FW_LOG_DROP_ALL="yes" FW_LOG_ACCEPT_ALL="no" FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" FW_ALLOW_PING_FW="yes" FW_IGNORE_FW_BROADCAST="yes" What am I doing wrong? Any hints are deeply appreciated. Cheers, Knut Erik -- 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

1 0

Re: [suse-security] Problems with a simple Firewall2 config
by GentooRulez 15 Jul '03

15 Jul '03

I did not check your whole config, but this came up immediately: # Which services ON THE FIREWALL should be accessible from either the internet # (or other untrusted networks), the dmz or internal (trusted networks)? FW_SERVICES_EXTERNAL_TCP="80" Check this out Michael

1 0

Problems with a simple Firewall2 config
by Knut Erik Hauslo 15 Jul '03

15 Jul '03

Hi all, This should be rather easy going, but I am experiencing problems. My network looks as follows: +-- External Net 192.168.1.0/24 --> (Eth1) SuSE 8.1 Firewall2 (Eth0) <--- Internal Net 172.19.0.0/16 On my Internal Net there's a web-server, which machines on the extern net may access. Using my Sniffer i can see packets going into the internal net, but I receive nothing back, because the initiating machine sends packets with destination port 80 TCP and sources port > 1024 TCP which I have not explicitely opend. The other way around is working fine (accessing HTTP and FTP resources on the external network). The configuration file: FW_DEV_EXT="eth1" FW_DEV_INT="eth0" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="172.19.0.0/16,0/0,tcp,20 172.19.0.0/16,0/0,tcp,21 172.19.0.0/16,0/0,tcp,80" FW_FORWARD_MASQ="0/0,172.19.6.10,tcp,80" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_PROTECT_FROM_INTERNAL="no" FW_LOG_DROP_CRIT="yes" FW_LOG_ACCEPT_CRIT="no" FW_LOG_DROP_ALL="yes" FW_LOG_ACCEPT_ALL="no" FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" FW_ALLOW_PING_FW="yes" FW_IGNORE_FW_BROADCAST="yes" What am I doing wrong? Any hints are deeply appreciated. Cheers, Knut Erik

1 0

Re: [suse-security] Creating rpm of locally compiled kernel
by Susi-Security 14 Jul '03

14 Jul '03

Am Montag, 14. Juli 2003 12:54 schrieb Simon Oliver: > Markus Gaugusch wrote: > >>Some time ago someone suggested that we create rpms (or dummy rpms) for > >>locally compiled kernels so that yast update doesn't overwrite the local > >>kernel. > > > > Use "make rpm" instead of "make bzImage modules" to create an RPM of the > > kernel. But I think it would be easier for you if you used fou4s and use > > the IgnoreList and RemarkList features (to ignore kernel upates or only > > notify the user, but don't install them). > > When I "make rpm" I get the following error: > > ... > kernel-2.4.2064GBSMP/./.version > File /usr/src/kernel-2.4.20.tar.gz: No such file or directory > make: *** [rpm] Error 1 > maybe you've to change the file: ./include/linux/version.h too. > It looks like rpm expects the tar file to have a different name: I > traced back and found that the rpm build comamnd was as expected: > > rpm -ta /usr/src/linux-2.4.20.SuSE/../kernel-2.4.2064GBSMP.tar.gz ; \ > > Any ideas?

3 2