February 2002 - openSUSE Security - openSUSE Mailing Lists

How2 getting sshd quiete
by Michael Appeldorn 28 Feb '02

28 Feb '02

Hi list, if i telnet against a sshd like this telnet 192.168.1.2 22 i'll get e.g. that: Trying 192.168.1.2... Connected to 192.168.1.2. Escape character is '^]'. SSH-2.0-OpenSSH_2.99.99p5 ^^^^^^^^^^^^^^^^^^^^^^^^ How2 suppress this output. Hopefully without any recompile? echo "1" > \proc\sys\net\SECURITY_THROUGH_OBSCURITY Michael Appeldorn

2 1

SendMail 8.12.2 and Qpopper
by Nikos Psarrakis 28 Feb '02

28 Feb '02

Hi, I'm new in the mailing list and i don't consider myself as a Linux expert, but i'm willing to try. I' d like to know if anyone has tried SendMail ver. 8.12.2. We are running SendMail ver. 8.11 at the moment. Does it worth an update? We are also running Popper instead of Qpopper. In your opinion are there differences that should make us to choose Qpopper? Thanks in advance, i remain...

1 0

SuSEFirewall2 NAT Question
by amiky＠gic.parma.it 28 Feb '02

28 Feb '02

Hi I'm a new subscribed to the mailing-list i'd like to ask you a question about SuSeFirewall2 that i don't configure correctly Thank you for your interest this is the configuration scheme Internet | | Web server Web server | | | SuSE-Firewall------------------ | | | Internal LAN external address example (194.168.2.1 194.168.2.2 194.168.3) external fw interface: eth1 (194.168.2.1) dmz fw interface: eth2 (192.168.1.1) internal fw interface: eth0 (192.168.0.1) internal LAN: 192.168.0.1 netmask 255.255.255.0 ip internal of web sever 192.168.1.2 FW_DEV_EXT="eth1" FW_DEV_INT="eth0" FW_DEV_DMZ="eth2" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="192.168.0.1/24 192.168.1.0/24" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="www" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_DMZ_TCP="www" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SAMBA="no" FW_FORWARD="" FW_FORWARD_MASQ="194.168.1.2,192.168.1.2,tcp,80" 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="yes" FW_STOP_KEEP_ROUTING_STATE="no" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="yes" FW_ALLOW_PING_EXT="no"

1 0

SuSEFirewall NAT Question
by amiky＠gic.parma.it 28 Feb '02

28 Feb '02

Hi I'm a new subscribed to the mailing-list i'd like to ask you a question about SuSeFirewall2 that i don't configure correctly Thank you for your interest this is the configuration scheme Internet | | Web server Web server | | | SuSE-Firewall------------------ | | | Internal LAN external address example (194.168.2.1 194.168.2.2 194.168.3) external fw interface: eth1 (194.168.2.1) dmz fw interface: eth2 (192.168.1.1) internal fw interface: eth0 (192.168.0.1) internal LAN: 192.168.0.1 netmask 255.255.255.0 FW_DEV_EXT="eth1" FW_DEV_INT="eth0" FW_DEV_DMZ="eth2" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="192.168.0.1/24 192.168.1.0/24" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="www" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_DMZ_TCP="www" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SAMBA="no" FW_FORWARD="" FW_FORWARD_MASQ="194.168.1.1,192.168.1.2,tcp,80" 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="yes" FW_STOP_KEEP_ROUTING_STATE="no" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="yes" FW_ALLOW_PING_EXT="no"

1 0

SuSEfirewall2_setup error.
by Enrique Iglesias Rodriguez 28 Feb '02

28 Feb '02

Hi there. I'm setting up SuSEfirewall2 in a box and got a 'fail' in the 2nd initialization script (SuSEfirewall2_setup) and got no error at all. Is there any logfile where SuSEfirewall2 output goes? -- Enrique Iglesias Rodriguez System Administrator http://www.intelideas.net Madrid, Spain -- CtrInt

2 1

Re: [suse-security] iptables - pop
by spiekey 28 Feb '02

28 Feb '02

I can get to ww.gmx.de, just the pop doesnt work. Everything looks fine in tcpdump, unfortunatelly, it wont tell me if it denys my packet or not? Does it? Spiekey ----- Original Message ----- From: "Joerg Trowski" <jotro(a)gmx.de> To: "spiekey" <spiekey(a)hotmail.com> Sent: Wednesday, February 27, 2002 4:11 PM Subject: RE: [suse-security] iptables - pop > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi! > > Do you have any problems to reach some homepages (e.g. GMX)? So if, > it's not a setup-problem of your firewall. If not ignore this mail > ;-0 > > Joerg > > > -----Original Message----- > > From: spiekey [mailto:spiekey@hotmail.com] > > Sent: Wednesday, February 27, 2002 2:56 PM > > To: suse-security(a)suse.com > > Subject: [suse-security] iptables - pop > > > > > > Hello! > > For some reason i can´t get my mail from my gmx pop account, > > this is my > > IPTABLES script: > > > > ---SNIP--- > > > > #Default DROP policy. I set the other eth+ on Accept, to make > > sure its not > > their fault! > > iptables -P INPUT DROP > > iptables -P FORWARD ACCEPT > > iptables -P OUTPUT DROP > > > > IFACE="ppp0" > > > > > > ---SNIP--- > > > > # POP > > # Allow POP, i tried everything to get is workins, as u can see ;) > > iptables -A INPUT -i $IFACE -p tcp --dport 110 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > iptables -A OUTPUT -o $IFACE -p tcp --sport 110 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > > > iptables -A INPUT -i $IFACE -p tcp --dport pop3 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > iptables -A OUTPUT -o $IFACE -p tcp --sport pop3 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > > > iptables -A INPUT -i $IFACE -p udp --dport 110 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > iptables -A OUTPUT -o $IFACE -p udp --sport 110 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > > > iptables -A INPUT -i $IFACE -p udp --dport pop3 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > iptables -A OUTPUT -o $IFACE -p udp --sport pop3 -m state --state > > NEW,ESTABLISHED -j ACCEPT > > > > ---SNIP--- > > > > Anyone any idea what i did wrong? > > > > > > Cheers, Spiekey > > > > -- > > 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 > > -----BEGIN PGP SIGNATURE----- > Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> > > iQA/AwUBPHz3K5SHm0LcQT0JEQKvTACguPVmUqkdz6Xd0TDthHUtqBCqsZUAoMwx > H6mhcAi7JdtRUBaevu8+7j26 > =yTbV > -----END PGP SIGNATURE----- > >

2 1

Resend: SuSE Security Announcement: cups (SuSE-SA:2002:006)
by Thomas Biege 28 Feb '02

28 Feb '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: cups Announcement-ID: SuSE-SA:2002:006 Date: Wednesday, Feb 27th 2002 12:10 MET Affected SuSE versions: 7.1, 7.2, 7.3 Vulnerability Type: remote privilege escalation Severity (1-10): 5 SuSE default package: no Other affected systems: all systems running CUPS Content of this advisory: 1) security vulnerability resolved: CUPS bufferoverflow in IPP 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 We re-release SuSE Security Announcement SuSE-SA:2002:005 with the new announcement ID SuSE-SA:2002:006 due to minor packaging errors that can result in a malfunction of the printing subsystem. The erroneous packages have been removed from the ftp server. The new packages are in place as announced in the URL list below. The well known Common Unix Printing System (CUPS) was found vulnerable to a buffer overflow in the Internet Printing Protocol (IPP) handling code. The buffer overflow could be exploited by a remote attacker as long as their IP address is allowed to connect to the CUPS server. 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. After updateing the RPM package run "rclpd restart" as root to make the package upgrade effective. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/d3/cups-devel-1.1.10-83.i386.rpm 8d5053ad177a11625184d0758487fc44 SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/cups-1.1.10-83.i386.rpm d13c2a15aec1e32d33e67e3c5dfbfcbe SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/cups-client-1.1.10-83.i386.r… f6869afd7a3ca8d25094e8beb685be69 SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/cups-libs-1.1.10-83.i386.rpm cabe0639064f8d8f4e0966b52f11d879 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/cups-1.1.10-83.src.rpm 44565cf9eef0354eda24c79eb6754615 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/d3/cups-devel-1.1.6-104.i386.rpm b248ca457d8240380bb5c52a27b18eef SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/cups-1.1.6-104.i386.rpm 828f470a6fbee50cfc7405c39aa1d81d source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/cups-1.1.6-104.src.rpm 8447e7162c38ecd5f63742de98d80e76 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/d3/cups-devel-1.1.6-105.i386.rpm 4ea2040b5c7b46b2e55dacd7073ce9ac SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/cups-1.1.6-105.i386.rpm 268428ba6b0470de8ae381552f185420 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/cups-1.1.6-105.src.rpm 93195300593a49fe6236b5abbfca8806 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/d3/cups-devel-1.1.10-36.sparc.… 0970928774ba45661812d2e818b9bbb2 SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/cups-1.1.10-36.sparc.rpm 4587059b86c2cefd9097d778ec125ab8 SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/cups-client-1.1.10-36.sparc… b26a1937a8bd286328ab164e1cc91ebe SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/cups-libs-1.1.10-36.sparc.r… afed35a5212b217bab1556e0e5df39e6 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/cups-1.1.10-36.src.rpm bb1662c9b437b0b88c56a39df9b4b6ad SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/d3/cups-devel-1.1.6-38.sparc.r… 0a093efb86b0eb024a21ab5532c2f08a SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/cups-1.1.6-38.sparc.rpm 69966f1ee23d904a5085d302a49678d6 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/cups-1.1.6-38.src.rpm b4921596bdec11a93da1031c43caa700 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/d3/cups-devel-1.1.6-34.alpha.rpm a1883596165edd8b1fa597dcb9e21d70 SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/cups-1.1.6-34.alpha.rpm 96d90d112b52262dbd01b01aac5b64d3 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/cups-1.1.6-34.src.rpm 2d648e906fc29c64682c7797adbbdcac PPC PowerPC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d3/cups-devel-1.1.10-63.ppc.rpm 04d9a84650c335ecc550c4e55e57a576 SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/cups-1.1.10-63.ppc.rpm 1776913fc7df901ce37fe3f41ce3fcb8 SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/cups-client-1.1.10-63.ppc.rpm 75d676e87d82d58555bf24d3261d0da6 SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/cups-libs-1.1.10-63.ppc.rpm 34f744fc2e7b60db32abc89fbda9fbfd source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/cups-1.1.10-63.src.rpm fa19fa9c5e0558d426de857f2bf45ac6 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - squid A heap overflow in squid's URL constructing functions is fixed and new packages are currently being built. - ucd-snmpd The UCD snmpd contains various security releated bugs. We are currently reviewing the code and available fixes to ensure they all get fixed. Patches will be available as soon as possible. It is strongly recommended to filter SNMP (TCP and UDP packets with destination of port 161) traffic. - hanterm/wmtv The recently reported vulnerabilities in hanterm and wmtv do not affect SuSE installations because they are not installed setuid or setgid. - cipe We are about to prepare kernel update packages that fix a DoS problem in the kernel modules for the cipe encrypted tunneling software. ______________________________________________________________________________ 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.3in Charset: noconv iQEVAwUBPH2KIXey5gA9JdPZAQE89wf/YtPBnhhWmZhxnOeVkam2dj2QBv1Gh17f uZ0ibPLEybRhaeXyCrtLe8tzQaH8Ofdir1jFWLvImf6EyKnwF8r9m8zArc1fR4ym SHyseGukEWUhYHoVBXn39Tn+c/Jh5SILpLWD2w/WTLPeCEkSCTTREe85oTykjJNH cXMXpaFuQ4+DZogQcjM61kaIlcf3dVnu7f5Iswzf3Z7kDIOVb5AhJ2ZmoDlGhaNj nPt83sC90ePBWPkNXB0JaqUMjZTA5y1svipkKQZj71A/WC3jujRa0++e7q9Sm4ms lofWxbLpgJYSFi9PKa3tUN3qpvwe+eJ/DQZ53Y118sJvYkkfdC7l3w== =Dg+7 -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de>,SuSE GmbH,Deutschherrnstr. 15-19,90429 Nuernberg Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- Trete durch die Form ein, und trete aus der Form heraus.

1 0

php remote vulns?!?
by gabriel rivera 27 Feb '02

27 Feb '02

Hello, The existence of seemingly severe remote holes in PHP has been announced today. http://security.e-matters.de/advisories/012002.html I was wondering if suse was aware of the problems and would be releasing updated packages... Thanks, Gabriel

2 1

Request to SuSE
by Peter Nixon 27 Feb '02

27 Feb '02

Hi Guys. I would like to bounce an idea off the list which I think would be of value. I propose that SuSE setup a suse-security-announce-pending mailing list where SuSE would officially notify of Pending problems in SuSE packages. Like most of you I recieve alot of email every day, (Bugtraq, CERT, SuSE-Security, SAGE-AU, SLUG, and a dozen other application specific mailing lists, plus of course my normal work and personal correspondence). Now of course I run _plenty_ of filters and everything is reasonably manageable, however as I am in the nice position that _every_ single piece of infrastructure I have under my control (with the exception of my routers, Sat Equipment, Load Balancers and 1 of my firewall levels) is SuSE Linux. To put it another way, every listening port on my network is on a SuSE box. Now I may be at the far end of the scale regarding SuSE's customers in this regard, but it would be very usefull to me if I only _had_ to keep track of one mailing list to know if I have to disable some service or other until a fix comes out. Now, I know that this is not too much extra work because invariably whenever something new hits BugTraq that affects SuSE, a question gets sent to SuSE-Security to ask if this affects SuSE or not. Take the current outstanding issue with ucsnmpd for instance. The question has already been asked (and answered by Roman) as to whether SuSE is vulnerable or not. So as the time was take by Roman to do this, (and say that there is an update pending) i think this info should be sent to an announcement list as a matter of course as soon as an issue breaks (If SuSE already has a patch ready due to coordination with other vendors etc, then it becomes unnecessary) As it was I had already read about the SNMPD problem (and disabled it on servers where it could conceviably cause a problem) on 4 other mailing lists before the response from Roman. As far as I'm concerned, the speed of _notification_ is more important than the speed at which a patch is released. I am quite comfortable disabling a service for days if necessary if I know there is a problem coming. Unfortunately to have this choice I currently have to wade through BugTraq etc every morning rather than just keeping an eye on a single low traffic SuSE maillist and leaving my bugtraq reading until lunchtime/weekends etc.. This idea is obviously of less use to people who run more hetrogenous networks than I do, but as I'm sure SuSE would love to have more companies in my situation, this is something that should be looked at. Any comments? -- Viel Spaß Peter Nixon - nix(a)susesecurity.com SuSE Security FAQ Maintainer http://www.susesecurity.com/faq/ "If you think cryptography will solve the problem, then you don't understand cryptography and you don't understand your problem."

7 6

Re: [suse-security] Network design
by Togan Muftuoglu 27 Feb '02

27 Feb '02

Hi Ryan, * Ryan Swenson; <Ryan.Swenson(a)togethersoft.com> on 27 Feb, 2002 wrote: >Togan - you are lucky given your current setup... here some answers. I have been rereading Building Inetrnet Firewalls probably the 10th time and I hope at least I designed it with minimum mistakes :-) >1. Stategically you can decide where you want to put an IDS however in your scenerio you are even more or best capable of using 2 IDS. One on your external FW, and one on your Internal firewall. You may have a single Database inside on your management system as well as now a single management www or some console. > >You could now watch all in/out traffic leaving your external space and apply policies here. >Internally you could now see all traffic leaving and entering your internal firewall which correlates some of the external NAT/MASQ traffic as well as Internal NAT/MASQ traffic. In this you could also have Porn or Info rules. > > >2. Single Snort IDS is best place between external and internal firewall. Or more so installed on the external firewall but configured as such to see traffic destined... Personally I offload Snort to its own box, and use a switch thats capable of SPAN. > I had the idea of putting snort to its own box also but I was confused where to put the box ( Guess time to reread Snort Usage, FAQ and Maillist > >2. Put the Squid server on the Internal Firewall. thats a given. Agrred > > >3. Syslog server inside internal network. Suggestion is Syslog-ng for security enhancement. Use logwatch + scanlogd on the syslog server. > >4. if you can afford it obtain Cisco 3500XL switches for the money. Not only do they provide L2 but also allow limited IOS feautures. They support 2 GBIC links, you simply assign vlans to best cut down storms and provide segmentation. It depends to the goverment office ( I have told them about the promotional campaign here we have in Turkey for the 3524XL series) Thanks for the valuable info -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx

1 0