April 2002 - openSUSE Security - openSUSE Mailing Lists

Re: [Users] IPSEC and SuSEFirewall2 v2.1
by Robert Klein 01 May '02

01 May '02

> I have modified the SuSEfirewall2 Script (Version 2.1) for better > support of FreeSWAN/IPSEC. Nice idea. > Any comments/suggestions/feedback? Two questions: Is it possible to use more than one IPSEC device? E.g. FW_DEV_IPSEC="ipsec0 ipsec1" and: Can I use more than one remote network? E.g. FW_IPSEC_REMOTENET="192.168.3.0/24 192.168.4.0/24" Robert

3 2

Re: [suse-security] iptables blocking telnet 25 ?
by spam 30 Apr '02

30 Apr '02

Hi! from comp.mail.sendmail: ---snip--- #!/bin/sh COUNTRIES="kr cn tw" for i in $COUNTRIES; do lynx --dump 'http://www.apnic.net/apnic-bin/'\ 'ipv4-by-country.pl?country='$i \ |grep ]APNIC|awk '{print $2;}' done ---snip--- you run the script and save the result to file /etc/rogue-state-ips then you add this to your firewall script (depending on your os version) ---snip--- # blocking countries for i in `cat /etc/rogue-state-ips | grep /`; do $IPTABLES -A input -i eth0 -p tcp --dport 25 -j DENY -s $i done ---snip---

1 0

Infiltration possible?
by Pierre Bernhardt 30 Apr '02

30 Apr '02

Hi, I've got following messages in my firewalllog: Apr 30 01:53:26 starflake kernel: IN=eth0 OUT= MAC=00:e0:4c:90:79:54:00:50:fc:21:9a:82:08:00 SRC=62.176.78.125 DST=193.174.11.198 LEN=78 TOS=0x00 PREC=0x00 TTL=8 ID=2103 PROTO=UDP SPT=3268 DPT=137 LEN=58 Apr 30 01:53:26 starflake kernel: klogd 1.4.1, ---------- state change ---------- Apr 30 01:53:26 starflake kernel: Inspecting /boot/System.map-2.4.18-64GB-SMP Apr 30 01:53:26 starflake kernel: Loaded 13537 symbols from /boot/System.map-2.4.18-64GB-SMP. Apr 30 01:53:26 starflake kernel: Symbols match kernel version 2.4.18. Apr 30 01:53:26 starflake kernel: Loaded 548 symbols from 32 modules. Port 137 above is loged and filtered by my iptablerules. Some of ports on my computer are accessible from internet, e.g. 22 for ssh. My rules logs only forbidden acces. I dont understand the kernelmessages about the Inspecting of the Kernel-Modules at the same time as the forbidden port-access ist logged. What is your opinion? More Infos? Here are my iptables loaded for my interface on my computer: At the moment i have only running dhcp-server, sun-rpc, ssh, squid and cups on 631. Smaba, popd and imapd are not installed at the moment. Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp dpt:ssh ACCEPT tcp -- <my-net/my-nm> anywhere tcp dpt:smtp ACCEPT tcp -- <my-net/my-nm> anywhere tcp dpt:pop3 ACCEPT tcp -- <my-net/my-nm> anywhere tcp dpt:imap ACCEPT tcp -- <my-net/my-nm> anywhere tcp dpt:http-alt ACCEPT udp -- <my-net/my-nm> anywhere udp dpt:netbios-ns ACCEPT udp -- <my-net/my-nm> anywhere udp dpt:netbios-dgm ACCEPT tcp -- <my-net/my-nm> anywhere tcp dpt:netbios-ssn ACCEPT udp -- <nameserver> anywhere udp spt:domain ACCEPT tcp -- <nameserver> anywhere tcp spt:domain ACCEPT udp -- <my-net/my-nm> anywhere udp spt:bootpc dpt:bootps ACCEPT icmp -- anywhere anywhere icmp echo-reply ACCEPT icmp -- anywhere anywhere icmp echo-request ACCEPT icmp -- anywhere anywhere icmp destination-unreachable ACCEPT icmp -- anywhere anywhere icmp source-quench ACCEPT icmp -- anywhere anywhere icmp time-exceeded ACCEPT icmp -- anywhere anywhere icmp parameter-problem REJECT tcp -- anywhere anywhere tcp dpt:ident reject-with tcp-reset LOG all -- anywhere anywhere LOG level warning DROP all -- anywhere anywhere Chain FORWARD (policy DROP) target prot opt source destination Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp spts:1024:65535 dpt:http ACCEPT tcp -- anywhere anywhere tcp spts:1024:65535 dpt:ssh ACCEPT udp -- anywhere anywhere udp spts:1024:65535 dpt:domain ACCEPT tcp -- anywhere anywhere tcp spts:1024:65535 dpt:domain ACCEPT udp -- anywhere <my-net/my-nm> spt:bootps dpt:bootpc ACCEPT icmp -- anywhere anywhere icmp echo-request ACCEPT icmp -- anywhere anywhere icmp echo-reply ACCEPT icmp -- anywhere anywhere icmp destination-unreachable LOG all -- anywhere anywhere LOG level warning REJECT tcp -- anywhere anywhere reject-with tcp-reset REJECT udp -- anywhere anywhere reject-with icmp-port-unreachable DROP all -- anywhere anywhere

1 0

FLASH !
by Corneliu MUSAT 30 Apr '02

30 Apr '02

http://pagitta.com/flash/flashmenu.html ;o) Tzupiiiic ! -- Cornel. tel.:4092743604

2 1

SuSE Security Announcement: sudo (SuSE-SA:2002:014)
by Sebastian Krahmer 30 Apr '02

30 Apr '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: sudo Announcement-ID: SuSE-SA:2002:014 Date: Tue Apr 30 16:00:00 MEST 2002 Affected products: 6.4, 7.0, 7.1, 7.2, 7.3, 8.0, SuSE Firewall Adminhost VPN, SuSE Linux Admin-CD for Firewall, SuSE Linux Enterprise Server, SuSE Linux Connectivity Server Vulnerability Type: local privilege escalation Severity (1-10): 6 SuSE default package: yes Other affected systems: All systems with sudo installed. Content of this advisory: 1) security vulnerability resolved: Heap overflow in sudo. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The sudo program allows local users to execute certain configured commands with root priviledges. Sudo contains a heap overflow in its prompt assembling function. The input used to create the password prompt is user controlled and not properly length-checked before copied to certain heap locations. This allows local attackers to overflow the heap of sudo, thus executing arbitrary commands as root. We would like to thank GlobalInterSec for finding and researching this vulnerability. As a temporary workaround you may remove the setuid bit from sudo by issuing the following command as root: "chmod -s /usr/bin/sudo". 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/ap1/sudo-1.6.5p2-79.i386.rpm b54f68ff4b32f9d920f2f1ff887d1ddc source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/sudo-1.6.5p2-79.src.rpm fd1ccf6fe52c6b999c5ed24a2f3a4e65 SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap1/sudo-1.6.3p7-83.i386.rpm 80edbf5caf02c519cf2c01d6ba76d22f source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/sudo-1.6.3p7-83.src.rpm 77962932840740ce5e3dfe57a887592d SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap1/sudo-1.6.3p6-92.i386.rpm 669aa8db134e39f462cb9f2648f6735f source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/sudo-1.6.3p6-92.src.rpm 249b1ef0135dcfede3648982900e277c SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/ap1/sudo-1.6.3p6-91.i386.rpm 6b3b84f0a4c687e91da179937b87048a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/sudo-1.6.3p6-91.src.rpm bf59a6b200a0fb130f3528ce23698be0 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/ap1/sudo-1.6.3p6-90.i386.rpm 5b67ef9fed383242111953d942c62174 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/sudo-1.6.3p6-90.src.rpm c35f6390b360500b7b649e4590a748cc SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/ap1/sudo-1.5.9p1-87.i386.rpm 82d98116eccc73c7a0ce03a51e9b5378 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/sudo-1.5.9p1-87.src.rpm e75e2608036a963a7339fe4632a2550b Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap1/sudo-1.6.3p7-33.sparc.rpm bd492b6d601ceb30486e3e970a2211a3 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/sudo-1.6.3p7-33.src.rpm d2435d180cdd76647e1f1416e93c2420 SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/ap1/sudo-1.6.3p6-37.sparc.rpm bbad36265f93fac25d59f8c26b1ccd52 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/sudo-1.6.3p6-37.src.rpm a328d2eb0fdc816341a68febfeb5a33a SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/ap1/sudo-1.6.3p6-36.sparc.rpm 48e7b360b45bae0b3e9e90b3bf945f75 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/sudo-1.6.3p6-36.src.rpm bd8f11a8916340e0d243ae1cc647df26 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/ap1/sudo-1.6.3p6-40.alpha.rpm 4505dd58fe309ef0a4515db6a6980ec4 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/sudo-1.6.3p6-40.src.rpm 85dfbe40da4d93d54d3c16f6489a7f32 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/ap1/sudo-1.6.3p6-40.alpha.rpm b67858459774e5e04c9c22e84d5899ff source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/sudo-1.6.3p6-40.src.rpm 6d0537068d16785bfdbca936c6395abb PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap1/sudo-1.6.3p7-65.ppc.rpm 1734f578b1fa87c26e51a11e3dc90d18 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/sudo-1.6.3p7-65.src.rpm ebff8b3e7b86ef9bb69fb13da37903ce SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/ap1/sudo-1.6.3p6-45.ppc.rpm 4318adbde184c1c8fff6eb581f02c11e source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/sudo-1.6.3p6-45.src.rpm 771f9e7f6d1fc1ba4df119147e48ddcd SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/ap1/sudo-1.6.3p6-45.ppc.rpm 6ae150cfa793f20e49ed751aa686fdea source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/sudo-1.6.3p6-45.src.rpm ede5fedf45ffe6b59c43e082fcef50f4 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/ap1/sudo-1.5.9p1-85.ppc.rpm 0677a205615f631a41ca308be03db7bd source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/sudo-1.5.9p1-85.src.rpm 71da4a7d43043b20eefd5e05048616d8 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - ifup-dhcp could be tricked into executing arbitrary commands as root by DHCP servers handing out illegal values (e.g. containing spaces), because it sourced dhcpcd's info file, where not all variable values are quoted. This problem has been fixed. ______________________________________________________________________________ 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 uninstalled 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 toplevel 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 annoucements 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 cleartext signature shows proof of the authenticity of the text. SuSE GmbH 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 iQEVAwUBPM6l7Hey5gA9JdPZAQHErAf/dsMrQSaSHlJHFirNNw9XTsyHFb8uxArI JRgmYIQZValzHicRhxXwRTYRPta3jDx40HH2UqY3VxgWMcHl5fRDne6inYNqlNg5 N70ER3lnHhFyei5er3sX/Rx9sOM/4ONXOk5ZsD/Bdooj0pGJ5hcU9xI1akNxm76k C1B4I8NW7Z9BnH1tiekNYChRv+lG9cw73ElpHGBNJNt0yIpWp3/idjG8/+J9YUod ToRV7owlXwTK/N7DTiYbOVTnRZOGKmRc7WC11xPL19xuIDT8GcmHH590jbCWaYNp DWSoooGuP1w1M1JSS/b+oSIDk4j6/5u9xGmSolDUjjHK/VKjY+dE7w== =lMC8 -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0

RE: [suse-security] iptables blocking telnet 25 ?
by Peer Stefan 30 Apr '02

30 Apr '02

Hi, > From: Axel Leitner [mailto:axel.leitner@muenchen-mail.de] > Hello, > > I want to filter, secure 110 with authentication, open 25 > only to relayable > hosts, drop all other trying access 25, if you know the trusted hosts then it's no problem to open port 25 for them. just add the according iptables-rule for each host/subnet ... 'secure 110' is plain pop3, it is unencrypted and therefore to be regarded as insecure. you can activate SSL-encryption via pop3, which is called pop3s (it uses port 995). > domain blocking is not my intend because blacklists have more > disadvantages than the right affect on security. black lists may not increase the security of your system, but they do help to keep spam away from you. and that's what you asked for. > > Axel > > > Why would you use iptables for that? Reasonable MTAs nowadays have > > a feature which honors blacklists. > > If you want to do the blocking yourself you will need some script > > or whatever to collect the IP addresses of spamming hosts - and the > > tricky part will be how you know IN ADVANCE if a host will > spam you ;-) > > By uing blacklists your can increase your chance because a spamming > > host will mabye already make it into the blacklist database bofore > > he attempts to spam you. > > > > Hope I made sense ;-) > > > > Erwin > > > > --- > > Axel Leitner wrote: > > > > > Hello everybody, > > > > > > has someone a suggestion how to block unauthorizied spam > access with an > > > iptables rule thru 25/tcp ? > > > > > > Bye > > > > > > Axel > > > > > > > > > > > > > > > -- > > Erwin Zierler | web- / host- / postmaster - stubainet.at > > | erwin.zierler(a)stubainet.at / webmaster(a)stubainet.at > > | Tel.: 0 5225 - 64325 Fax 99 Mobil: 0664 - 130 67 91 > > > > > > -- > > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-security-help(a)suse.com > > Security-related bug reports go to security(a)suse.de, not here > > > > > > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > 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

iptables blocking telnet 25 ?
by Axel Leitner 30 Apr '02

30 Apr '02

Hello everybody, has someone a suggestion how to block unauthorizied spam access with an iptables rule thru 25/tcp ? Bye Axel

3 3

RE: [suse-security] Firewall Linux? Firewall software
by Paxton, Michael 30 Apr '02

30 Apr '02

Oracle generally requires an application proxy to use SQL*net/Net8 through a firewall. Oracle provides its proxying code "free of charge" to firewall vendors. (Of course free of charge doesnt necessarily mean compatible with open licensing arrangements). The application proxy is also part of Oracle connection manager which, presumably, you could set up on your firewall box. In theory connection manager + any firewall software = oracle friendly firewall I guess. This is, of course, only if you are using SQL*Net/Net8 to communicate between client and server. Michael Paxton ------------------------------------------- Michael Paxton - Michael.Paxton(a)aihw.gov.au Data & Information Technology Unit Australian Institute of Health & Welfare -----Original Message----- From: Reckhard, Tobias [mailto:tobias.reckhard@secunet.com] Sent: Tuesday, April 30, 2002 2:22 PM To: suse-security(a)suse.com Subject: RE: [suse-security] Firewall Linux? Firewall software > Chaps and chapesses, does anyone out there know a good > location or doc for > firewall security with Oracle? Metalink (Oracle's site > doesn't seem to be > too hot). Inside / Outside the firewall pro's and con's > issues, how to set > up that sort of thing. On Linux of course. Is there a > firewall version of > Linux? Is it not just normal Linux with some packages > installed and some > tweaking? Am I barfing up the wrong tree? Why would you want something specific to Oracle? The dangers facing servers are very similar, be it that they serve web, news, mail, directory or database content and functions. The differences from a firewalling perspective lie in the direction of communication and the protocol used, the question whether an application layer gateway is available, and the ports used. IMHO, you'd be a fool not to shield an Oracle database with a firewall if you're allowing access from a potentially hostile environment. Many people prefer to place 'staging' databases in DMZ networks that hold only the bare records necessary to perform their function and that exchange data with the production database on the internal network, so that the latter never has direct contact with the hostile environment. Really, apply common sense and security principles and you'll get a sound design, no matter what type of service you're dealing with. > This message is confidential and may also contain privileged [snip] You do realise that your disclaimer is twice as long as the mail you wrote? <shrug> Tobias -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com 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] Firewall Linux? Firewall software
by Reckhard, Tobias 30 Apr '02

30 Apr '02

> Chaps and chapesses, does anyone out there know a good > location or doc for > firewall security with Oracle? Metalink (Oracle's site > doesn't seem to be > too hot). Inside / Outside the firewall pro's and con's > issues, how to set > up that sort of thing. On Linux of course. Is there a > firewall version of > Linux? Is it not just normal Linux with some packages > installed and some > tweaking? Am I barfing up the wrong tree? Why would you want something specific to Oracle? The dangers facing servers are very similar, be it that they serve web, news, mail, directory or database content and functions. The differences from a firewalling perspective lie in the direction of communication and the protocol used, the question whether an application layer gateway is available, and the ports used. IMHO, you'd be a fool not to shield an Oracle database with a firewall if you're allowing access from a potentially hostile environment. Many people prefer to place 'staging' databases in DMZ networks that hold only the bare records necessary to perform their function and that exchange data with the production database on the internal network, so that the latter never has direct contact with the hostile environment. Really, apply common sense and security principles and you'll get a sound design, no matter what type of service you're dealing with. > This message is confidential and may also contain privileged [snip] You do realise that your disclaimer is twice as long as the mail you wrote? <shrug> Tobias

1 0

[suse-security] Partitions
by Michael Stern 29 Apr '02

29 Apr '02

> Although I'm not a suse expert all I did was make a partition called > /cryptomaniac and have it format it as reiser FS instead of ext2. > Added the > password, and now when suse boots it asks for the password. > > I need information about secure partitions, I have HD 40G, I like a web > > server an mail server. I wouldn't store that important data an the server anyway. crypto-fs is good if you have a laptop and need to know noone can easily decipher your data in case it's being stolen. if you have a server and mount an encrypted-partition at server-bootup, anyone compromising your server will be able to see your data, and even if you haven't mounted the partition there is nothing really preventing a possible intruder to install a keylogger and trojan your system. better use your time to secure the server and install an IDS and take other precautions such as a dedicated log-host, signed files, etc. michael

1 0