November 2003 - openSUSE Security - openSUSE Mailing Lists

pcAnywhere-port forwarding
by root 11 Nov '03

11 Nov '03

Hi Guru's A beginner's big problem: I'm using SuSE 8.2 in the firewall. eth0 192.168.23.80 eth1 x.y.w.z I configured the susefirewall2, the client can ping the firewall. I need to enable to one outside client connect to my internal pc with pcAnywhere my pc: 192.168.23.201 win xp Outside Pc : 217.236.X.X I need two ports : 5631,5632 and i need forwarding it,from the firewall to my local maschine. I make a custom rule in : /etc/sysconfig/scripts/SuSEfirewall2-custom: iptables -A FORWARD -j ACCEPT -p tcp --dport 5631 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to 192.168.23.201:5631 iptables -A FORWARD -j ACCEPT -p tcp --dport 5632 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to 192.168.23.201:5632 The boot error message: Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.7a: unknown protocol `5631' specified Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.7a: unknown protocol `5632' specified Try `iptables -h' or 'iptables --help' for more information. What is the solution? Thanks a lot of your help. If it work, i will pay for all of you a beer :) Sorry for my english, and my long message.

2 1

Raid-1 Question
by Simon Hoerder 10 Nov '03

10 Nov '03

Hi, I'm sorry if my questions are rookie questions but I'd be glad for help anyway: I want to setup a server with SuSE Prof. 9.0 and a Software-Raid-1 system. First of all: Is there a possibility to create Software-Raid disks during the installation? (As far as I know, there is not - at least I never discovered one. But that's no real problem, I can work around it using a degraded raid.) Second: Can Grub handle booting from a Raid disk? The author of the software-Raid-HOWTO said, that grub has some problems booting from Raid-1 disks and that he don't know how to solve them. (On the other hand, there have been some changes since the last update of the HOWTO.) Are there any special tricks needed? Third (just in case we should jump to a Hardware-Raid solution): Are there any problems to install SuSE Prof. 9.0 on a Hardware-Raid-1 disk? Many thanks for your help, Simon Hoerder

4 3

SUSE Security Announcement: hylafax (SuSE-SA:2003:045)
by krahmer＠suse.de 10 Nov '03

10 Nov '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: hylafax Announcement-ID: SuSE-SA:2003:045 Date: Mon Nov 10 15:00:00 CET 2003 Affected products: 7.3, 8.0, 8.1, 8.2, 9.0 SuSE Linux Enterprise Server 7 SuSE Linux Standard Server 8 SuSE Linux Desktop 1.0 SuSE Linux Office Server Vulnerability Type: remote code execution Severity (1-10): 5 SUSE default package: No Cross References: CAN-2003-0886 http://www.hylafax.org Content of this advisory: 1) security vulnerability resolved: Format bug condition in hfaxd. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - ethereal - KDE - sane - ircd - mc - apache1/2 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Hylafax is an Open Source fax server which allows sharing of fax equipment among computers by offering its service to clients by a protocol similar to FTP. The SuSE Security Team found a format bug condition during a code review of the hfaxd server. It allows remote attackers to execute arbitrary code as root. However, the bug can not be triggered in hylafax' default configuration. The "capi4hylafax" packages also need to be updated as a dependency where they are available. After the update has been successfully applied the hfaxd server has to be restarted by issuing the following command as root: /etc/rc.d/hylafax restart 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/hylafax-4.1.7-67.i586.… 598081f0d8518014c122466549d3aee2 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/capi4hylafax-4.1.7-67.… b440a0ac3debb15af86c55ce9648a0c9 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/hylafax-4.1.7-67.i586.… b133d6a01100c51769edfe73842f21e5 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/capi4hylafax-4.1.7-67.… 48b02652d3efd052a99fe45346a40533 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/hylafax-4.1.7-67.src.rpm 44b246480b629ee9659ff2360999f4be SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/hylafax-4.1.5-190.i586… a17a36e3d9779aaddc074e634c1d16c2 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/capi4hylafax-4.1.5-190… f016a370c9428aaca1a4393e3fb1fa6c patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/hylafax-4.1.5-190.i586… f9be5873c7f8abaae23494f98463b451 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/capi4hylafax-4.1.5-190… 715001c063280b3ff8c3ec9c918776b9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/hylafax-4.1.5-190.src.r… cdf6cf2e9ad8e9f96a0a76ba03921c5a SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/hylafax-4.1.3-145.i586… 85ffa634af490894d049c2c350bd5637 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/capi4hylafax-4.1.3-145… c3766b389e79820e88375127ce47246f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/hylafax-4.1.3-145.i586… f6afb37c81542e75da229db6cd1f9571 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/capi4hylafax-4.1.3-145… e3f1e42ab4a12d056ad440e4607214c9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/hylafax-4.1.3-145.src.r… 6babcf169ecf60cbfc83a3f8575cdf3e SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/hylafax-4.1-303.i386.rpm e4492b144902043a38bfd71dbb683b23 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/hylafax-4.1-303.i386.patch.r… 02f80c2b8b28d176bbba8a6dccda4dce source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/hylafax-4.1-303.src.rpm c79d4be78cca347d5ecded4c6029f2b2 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n3/hylafax-4.1-303.i386.rpm b42d4ff0c43cec7e09fe4c1bbf5c8226 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/hylafax-4.1-303.src.rpm 8bdce70f21a0362882947a1d4de760ae Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n3/hylafax-4.1-122.sparc.rpm fa187f99f0a25df1815445dbbb6a0abe source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/hylafax-4.1-122.src.rpm 227353e1b80121f3ccfabc7fb888a485 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n3/hylafax-4.1-206.ppc.rpm 4388fa7fe1aa5173e3d33bdf1c477349 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/hylafax-4.1-206.src.rpm a95fd798a47396a077d7690a3e62986b ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - ethereal A new official version of ethereal, a network traffic analyzer, was released to fix various security-related problems. An update package is currently being tested and will be released as soon as possible. - KDE New KDE packages are currently being tested. These packages fixes several vulnerabilities: + remote root compromise (CAN-2003-0690) + weak cookies (CAN-2003-0692) + SSL man-in-the-middle attack + information leak through HTML-referrer (CAN-2003-0459) The packages will be release as soon as testing is finished. - sane The scanner service sane of SuSE Linux 7.3-8.1 is vulnerable to a remote denial-of-service attack. This attack can even be triggered if the attackers host is not listed in the saned.conf file. The packages are currently tested and will be release as soon as possible. - ircd The Internet Relay Chat daemon is vulnerable to a remote denial-of- service attack. The attack can be triggered by irc clients directly connected to the daemon. The packages are currently tested and will be release as soon as possible. - mc By using a special combination of links in archive-files it is possible to execute arbitrary commands while mc tries to open it in its VFS. The packages are currently tested and will be release as soon as possible. - apache1/2 The widely used HTTP server apache has several security vulnerabilities: - locally exploitable buffer overflow in the regular expression code. The attacker must be able to modify .htaccess or httpd.conf. (affects: mod_alias and mod_rewrite) - under some circumstances mod_cgid will output its data to the wrong client (affects: apache2) ______________________________________________________________________________ 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) iQEVAwUBP6+e5Hey5gA9JdPZAQE+jAf/eFK48eMC9RHFxdk32feeVB3vF4vxSefU 59UlWIC0qAyfBf0y2gEf5QKtqwJQzQi489xhjWUFAs5y41S+eYqW9L3bnmbCLdbA 7htB2v/2ZddJhukVPmWop/vaucRX/UDhNKMTzOX8WfmzVhUEvX+B7wkwzVaeood+ IcJzr0kfaW/WsggtIwVV9wbESkPMhguF93Aj2QDeHiFcuxSNcgcKwYkW4TUcgb13 GJ22dHi1aOVDXQmZfnQ/darX6WsKWB1Np/YfbBHRHyhOLS+Z/bKUCbUUb32IO9A8 u7apA51haVrNu2AbKYaoBHPYHefeuCoZISx6mlC5v4JYLexwEwAZzA== =24nB -----END PGP SIGNATURE-----

1 0

How long will SUSE produce security updates for SUSE 9.0 Pro?
by Benjamin Arai 08 Nov '03

08 Nov '03

How long is SUSE planning to supply security updates for SUSE 9.0 Pro? -- Benjamin Arai Araisoft Corp. benjamin(a)araisoft.com Phone: (626) 390-8973

7 7

RE: [suse-security] ROOTKIT ?
by Sturgis, Grant 08 Nov '03

08 Nov '03

What does: netstat -anp|grep LISTEN say? Grant -----Original Message----- From: Michael Maldener [mailto:MALDENER.de@t-online.de] Sent: Thursday, November 06, 2003 3:57 PM To: suse-security(a)suse.com Subject: [suse-security] ROOTKIT ? Hallo Linux-Friends, I scanned my own box (my own dynamic IP) when I was online with: netcat -v -z 80.131.118.62 1-65535 p5083763E.dip.t-dialin.net [80.131.118.62] 33352 (?) open p5083763E.dip.t-dialin.net [80.131.118.62] 32769 (filenet-rpc) open p5083763E.dip.t-dialin.net [80.131.118.62] 32768 (filenet-tms) open p5083763E.dip.t-dialin.net [80.131.118.62] 6000 (?) open p5083763E.dip.t-dialin.net [80.131.118.62] 631 (ipp) open p5083763E.dip.t-dialin.net [80.131.118.62] 111 (sunrpc) open p5083763E.dip.t-dialin.net [80.131.118.62] 22 (ssh) open And now I am afraid not be alone on my box !? What could I do now to close the unwanted ports? I took a fresh new /etc/services from www.iana.org/assignments on my system. rose:~ # grep '6000' /etc/services .... x11 6000-6063/tcp X Window System x11 6000-6063/udp X Window System ... rose:~ # But why the port 6000 is not shown by netcat? only a ? Although it is in my /etc/services! Is this port necessary for a local machine, when I dont want X-forwarding? for ipp I have to look how? to deactivate this in cups? What can i do, to find out what is behind 33352 (?) open 32769 (filenet-rpc) open 32768 (filenet-tms) open ____________________________________ The same thing when I was yesterday offline: 46837 (?) open 32769 (filenet-rpc) open 32768 (filenet-tms) open 6000 (x11) open 631 (ipp) open 111 (sunrpc) open 80 (http) open 22 (ssh) open Best Regards and thank you in advance from Mick ; ~ {o} under shock Now I do logout and go to sleep. -- # MfG Michael Maldener + Das beste Linux ist die Pluralitaet aller Linuxica ;) -- 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 This electronic message transmission is a PRIVATE communication which contains information which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender of the delivery error by replying to this message, or notify us by telephone (877-633-2436, ext. 0), and then delete it from your system.

2 1

Microsoft's bounty for catching virus writers
by Keith Roberts 08 Nov '03

08 Nov '03

Hi list! Something that may be of interest to anyone that has not heard about this yet. Microsoft has anounced a $5 million dollar fund set apart for rewarding anyone that can give information to the FBI, Interpol etc, that would result in the conviction of virus writers/distributors. _________________________________________________________________ Microsoft places $250,000 Bounty on MSBlast worm and Sobig virus authors First two targets of new $5 Million "Fink Fund" created to aid law enforcement's pursuit of malware authors and perpetrators. _________________________________________________________________ Please see for more details: http://www.microsoft.com/presspass/press/2003/nov03/11-05AntiVirusRewardsPR… Regards - Keith Roberts

1 0

AW: [suse-security] External packets from localhost[Scanned]
by Jörg Brandenburg 07 Nov '03

07 Nov '03

I have also noticed this packages. It started here at the end of September and we had more than 1700 packets since then. I found out that this packets definitely come from "outside" and not from a misconfigured machine in my own network. Unfortunately I don't know any more about this. Joerg -----Ursprüngliche Nachricht----- Von: Hemsley, Trevor [mailto:Trevor.Hemsley@atosorigin.com] Gesendet: Freitag, 7. November 2003 16:44 An: suse-security(a)suse.com Betreff: [suse-security] External packets from localhost[Scanned] Has anyone else noticed a large number of packets arriving on their external interfaces recently where the source address is 127.0.0.1? Over the past day and a half I've seen 300 packets with destination ports between 1001 and 1994 with the most widely used ones being 1770, 1869, 1514, 1274, 1001 and 1256. Looking back through my logs, it seems that this started happening at the beginning of September and has been getting worse in each log file since that date. Looks most weird and I can't think of anything legitimate that could be doing it. Trevor Hemsley, Security Specialist, Atos Origin Ltd, Whyteleafe, +44-(0)1883-628139 [This e-mail and the documents attached are confidential and intended solely for the addressee ; it may also be privileged . If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.] -- 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

External packets from localhost
by Hemsley, Trevor 07 Nov '03

07 Nov '03

Has anyone else noticed a large number of packets arriving on their external interfaces recently where the source address is 127.0.0.1? Over the past day and a half I've seen 300 packets with destination ports between 1001 and 1994 with the most widely used ones being 1770, 1869, 1514, 1274, 1001 and 1256. Looking back through my logs, it seems that this started happening at the beginning of September and has been getting worse in each log file since that date. Looks most weird and I can't think of anything legitimate that could be doing it. Trevor Hemsley, Security Specialist, Atos Origin Ltd, Whyteleafe, +44-(0)1883-628139 [This e-mail and the documents attached are confidential and intended solely for the addressee ; it may also be privileged . If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.]

1 0

Re: [suse-security] DHCP and IP Numbers ?
by Ken Schneider 07 Nov '03

07 Nov '03

On Fri, 2003-11-07 at 10:11, Greg Byshenk wrote: > On Fri, Nov 07, 2003 at 09:51:34AM -0500, Ken Schneider wrote: > > On Fri, 2003-11-07 at 09:39, remote wrote: > > > > I have a question about how DHCP is working. You see, I try to set up > > > a small cluster of boxes to do some parallel computing. The Name > > > Resolution in this cluster is supposed to work with DHCP. Things seem > > > to run smoothly, but after some time, my parallel process is > > > interrupted, with no error message at all. I `d like to know if DHCP > > > reassigns new IPs after a certain amount of time and if this could > > > interrupt my parallel processes (I tried both MPICH and rsh). > > > You should NEVER put servers on DHCP, servers should only ever have > > fixed addresses. > > Nonsense. I am running a large number of machines (including servers > and a 70-CPU cluster) on DHCP. That part would then be BOOTP -NOT- DHCP. > > That said... for servers, one should almost certainly be using DHCP > reservations / fixed addresses. > > Try a search on 'fixed-address' in dhcpd.conf(5). > -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)

1 0

DHCP and IP Numbers ?
by remote 07 Nov '03

07 Nov '03

Hi ! I have a question about how DHCP is working. You see, I try to set up a small cluster of boxes to do some parallel computing. The Name Resolution in this cluster is supposed to work with DHCP. Things seem to run smoothly, but after some time, my parallel process is interrupted, with no error message at all. I `d like to know if DHCP reassigns new IPs after a certain amount of time and if this could interrupt my parallel processes (I tried both MPICH and rsh). Any suggestions ? Thanks, Jörg

6 6