January 2002 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement: rsync (SuSE-SA:2002:004)
by Sebastian Krahmer 25 Jan '02

25 Jan '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: rsync Announcement-ID: SuSE-SA:2002:004 Date: Fri Jan 25 17:00:00 CET 2002 Affected SuSE versions: 6.4, 7.0, 7.1, 7.2, 7.3 Vulnerability Type: remote command executionn Severity (1-10): 7 SuSE default package: no Other affected systems: All systems with vulnerable rsync. Content of this advisory: 1) security vulnerability resolved: rsync negative array indexing 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 rsync program allows users and administrators to synchronize files and whole directory structures on different machines. It is common practise to allow remote users to mirror ftp servers via anonymous rsync access. There exist several signedness bugs within the rsync program which allow remote attackers to write 0-bytes to almost arbitrary stack-locations, therefore being able to control the programflow and obtaining a shell remotely. These bugs have been fixed. It is recommended (also stated in the rsync documentation) to use the "use chroot" option in rsyncd's configuration file (/etc/rsyncd.conf) to limit the impact of a possible attack. Since this workaround does not completely solve the security problem, we recommend to update the package as described below. We want to express our gratitude to Andrew Tridgell and Martin Pool, the rsync authors and maintainers, for their excellent cooperation in this matter. 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. To be sure that the update takes effect, kill any existing instances of the rsync-program. In case you run rsync via the inetd superserver, you do not need to restart any of your services. Inetd will automatically use the new binary. If you used run your rsync-service with the "rsync --daemon" command, restart your rsync with "rync --daemon" again, this time using the new binary. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/rsync-2.4.6-288.i386.rpm ce6d9226a8a9a5644ece29926c1f51d7 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/rsync-2.4.6-288.src.rpm 0e354408f232b25fe0089b97073009a3 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/rsync-2.4.6-289.i386.rpm 1ff42b8149e21644d23fe71c40a3ec5a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/rsync-2.4.6-289.src.rpm 83407b4dfad94d21af60ba3e8025e6cd SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/rsync-2.4.6-288.i386.rpm 26533f97af4474b450ad43a171c5571f source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/rsync-2.4.6-288.src.rpm dcd1345446871320962e91d979ddb25b SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/rsync-2.3.2-124.i386.rpm f16f81e5a0a11ba951b6f923cbae2abd source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/rsync-2.3.2-124.src.rpm cd36ce735b4ca91f92fc2f3c7603037f SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/rsync-2.3.2-123.i386.rpm c9330c9123757f89ed94382874122c82 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/rsync-2.3.2-123.src.rpm d97478d6fe9f2419b8700c52be4d888a Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/rsync-2.4.6-135.sparc.rpm 669f52233aed0766dd72788741691558 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/rsync-2.4.6-135.src.rpm 85ddaa9518d19f6341a68ce254668f0b SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/rsync-2.4.6-135.sparc.rpm d68ebcdba8caa16360e225fc9d28dc54 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/rsync-2.4.6-135.src.rpm b9f1f43d0248b763aef46bd610233285 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/rsync-2.3.2-5.sparc.rpm 50b9cefa5f4bf86fc1e20184c15fb542 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/rsync-2.3.2-5.src.rpm ffbc3ff43c339cbbe12317bb98587df3 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/rsync-2.4.6-123.alpha.rpm 3b602bd23179a7b6ce162d2d377394af source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/rsync-2.4.6-123.src.rpm 65f9d53cb48b8456466a27d9cde04339 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/rsync-2.3.2-30.alpha.rpm 2056422feb3b2b53285413ca746f2f4e source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/rsync-2.3.2-30.src.rpm 88c3a630df0e3073a8be55b0008371a0 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/rsync-2.3.2-31.alpha.rpm 18ea59b5c4d4641b62cef9c11f535ae8 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/rsync-2.3.2-31.src.rpm 091659d90d3e079c0f8d4518c2c42f9f Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/rsync-2.4.6-150.ppc.rpm f5576fca06f5d22b1410aaba399e0791 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/rsync-2.4.6-150.src.rpm 1baeeffafe1c7dd75189cbfe704bddf0 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/rsync-2.4.6-151.ppc.rpm 04102efb5a83b5190fe6b02146ec522b source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/rsync-2.4.6-151.src.rpm 4a21e9f5b36f6767436c6ea92f5d17e7 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/rsync-2.3.2-133.ppc.rpm 897e0010ccf09c85a8c8797dc77394e1 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/rsync-2.3.2-133.src.rpm 7ff150ba5f39ab527aa67308154273e2 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/rsync-2.3.2-133.ppc.rpm 65ac31f12bacb9284fd2286aec7beab0 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/rsync-2.3.2-133.src.rpm 4b43552a939f080a3e93fe65a88bd139 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - pine The popular mail client "pine" was found vulnerable to an attack where shell metacharacters inside an URL could be used to execute arbitrary commands if pine passes the URL to an external viewer on the commandline. The pine packages on SuSE products are not vulnerable to this weakness because they contain a patch that works around this problem since it is not new. - xchat We are working on updates for the xchat packages in the SuSE Linux 7.0 and 7.1 distributions that are vulnerable to an encoding bug while receiving and decoding ctcp datagrams. This bug can lead an xchat IRC client to execute IRC protocol specific commands to an IRC server such as channel mode changes. ______________________________________________________________________________ 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 mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBmQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCk YS3yEKeueNWc+z/0Kvff4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP +Y0PFPboMvKx0FXl/A0dM+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR 8xocQSVCFxcwvwCglVcOQliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U 8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0S cZqITuZC4CWxJa9GynBED3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEh ELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtB UVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOo AqajLfvkURHAeSsxXIoEmyW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1n KFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohc BBMRAgAcBQI57vSBBQkDwmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8s AJ98BgD40zw0GHJHIf6dNfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQ EQIABgUCOnBeUgAKCRCeQOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACe OO1HIbActAevk5MUBhNeLZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vf iUUE1VQnt+T/EYklES3tXXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEI SZxbzdXGnqIlcT08TzBUD9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9g TPSr+/fT3WeVnwJiQCQ30kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23p QUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1y PqZd5CvvznYvB6bWBIpWcRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IX SzyohEJB6XG5+D0BuQINBDnu9JIQCACEkdBN6Mxf5WvqDWkcMRy6wnrd9DYJ8UUT mIT2iQf07tRUKJJ9v0JXfx2Z4d08IQSMNRaq4VgSe+PdYgIy0fbj23Via5/gO7fJ EpD2hd2f+pMnOWvH2rOOIbeYfuhzAc6BQjAKtmgR0ERUTafTM9Wb6F13CNZZNZfD qnFDP6L12w3z3F7FFXkz07Rs3AIto1ZfYZd4sCSpMr/0S5nLrHbIvGLp271hhQBe RmmoGEKO2JRelGgUJ2CUzOdtwDIKT0LbCpvaP8PVnYF5IFoYJIWRHqlEt5ucTXst Zy7vYjL6vTP4l5xs+LIOkNmPhqmfsgLzVo0UaLt80hOwc4NvDCOLAAMGB/9g+9V3 ORzw4LvO1pwRYJqfDKUq/EJ0rNMMD4N8RLpZRhKHKJUm9nNHLbksnlZwrbSTM5Lp C/U6sheLP+l0bLVoq0lmsCcUSyh+mY6PxWirLIWCn/IAZAGnXb6Zd6TtIJlGG6pq UN8QxGJYQnonl0uTJKHJENbI9sWHQdcTtBMc34gorHFCo1Bcvpnc1LFLrWn7mfoG x6INQjf3HGQpMXAWuSBQhzkazY6vaWFpa8bBJ+gKbBuySWzNm3rFtT5HRKMWpO+M 9bHp4d+puY0L1YwN1OMatcMMpcWnZpiWiR83oi32+xtWUY2U7Ae38mMag8zFbpeq PQUsDv9V7CAJ1dbriEwEGBECAAwFAjnu9JIFCQPCZwAACgkQqE7a6JyACspLIgCb BQd/++0pB9yZWDhqxHtTpdCXRsAAnik7bYHlTxQfohiXYsEJcWrDn7l8 =ojbD - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPFF+6ney5gA9JdPZAQEjBwf7B2B8w1lFpiL8bgy3ttUzNRTFIRnre7yq QLcn8XdhF1iSvtDpgiajVsutYrRbEeVImcAWmXeLOIZMY/qwc4uLBwxrF2ng0Uph QhAebyewpFtMmIQrb/7AAOcudpgbHWsSRJYacbqYutQvJJ73vuFh+HOjErFoFx8p ZqtVC5IvOuE+HomaS/WBPjBdvIDrHSUaJq+fFFTYKozAEg/PpM++vePI5xauaEoP t6Wvazswwe1Qlx2rV2NvE/4TLFyxL2fHEQTtEIdSsa6za7WXmC2QqIhv4Y5zdckA 8CpPFJ0M/nTzmEf40i67myIGtOVgjb5MWaOv2ybya9ORPIHScdZxSQ== =8z44 -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

3 2

Folder options.
by Russell Koehler 25 Jan '02

25 Jan '02

I was wondering if anyone new a way of preventing users from creating Directories on SUSE 7.3. I need the users to be able to read, write, copy, and move files, but not create folders. I am running SAMBA with a W2000 Domain controller. all users run W98SE. My kernel is 2.4.16.

2 1

status of new kernel 2.4.16
by Bob Vickers 25 Jan '02

25 Jan '02

Hello, A couple of times recently Roman (I think) has promised an imminent security announcement associated with the new 2.4.16 kernel. It hasn't arrived yet...could I ask whether there is a specific problem delaying it or whether it is general work overload? I'm not trying to get at SuSE here, and I know it delays you further if you have to answer too many "is it nearly ready?" messages; I am just looking for information to make an informed decision about whether to upgrade yet. One of our main production machines has stability problems on 2.4.7 so I would like to upgrade, but I don't want to move to 2.4.16 if it is being held back for stability reasons. Thanks, Bob ============================================================== Bob Vickers R.Vickers(a)cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691

2 1

SuSEFirewall-Masq and ipchains with 2.4.x
by R. Ullenboom 25 Jan '02

25 Jan '02

Hi, boot.msg when initializing SuSEFirewall: "WARNING: FTP/IRC/REALAUDIO etc. masquerading does not work with ipchains and the 2.4. kernel. Either move to a stable 2.2 or use SuSEFirewall2" I did change to SuSEFirewall2 at SuSE-FTP-update7.3. Install OK. Kernel 2.4.4. But the error-msg appears at least. What's wrong? Thanks 4 help, René

2 1

sendmail behind SuSEFirewall
by R. Ullenboom 25 Jan '02

25 Jan '02

Hi, I'm trying to initialize an TDSL-Gateway. Masq. over SuSEFirewall and transpararent Proxy with Squid seems to work. (From MS-Client: Ping from DOS-Kommand-Line to Internet-Adress: REACHED; Internet-Surfing from Webbrowser over Squid and also Downloads) Before i'm going to install this Firewall in our 3-Man-Office, I'd like to test some things at home. Sendmail's running on my Workstation in the Office. In the future it should exchange it's eMails behind the Firewall. Which ports do I have to aktivate in Susefirewall (FW_SERVICES_EXTERNAL_TCP und FW_SERVICES_INTERNAL_TCP)? Do I have to fill-in other Parameters somewhere else? Which way is the best to test sendmail-Firewall-Passing ("telnet 'pop3-server_Internet' 110" or stupid MS-Outlook-Client or someth. else?) Thanx for help, Rene

1 0

snort Alert
by Dietmar Strasdat 25 Jan '02

25 Jan '02

Hello List, today i view my logs for warnings and other Problems with my Router Kernel 2.2.19 on SuSE 7.0 Snort alerts me following messages [**] FTP99cmp [**] 01/25-12:49:02.510018 172.16.2.5:56704 -> 172.16.2.6:1492 UDP TTL:58 TOS:0x0 ID:45067 Len: 8 [**] Back Door [**] 01/25-12:49:02.921419 172.16.2.5:56704 -> 172.16.2.6:1999 UDP TTL:58 TOS:0x0 ID:5981 Len: 8 [**] iNi Killer/Phase Zero/Stealth Spy [**] 01/25-12:49:03.645493 172.16.2.5:56704 -> 172.16.2.6:555 UDP TTL:58 TOS:0x0 ID:27091 Len: 8 [**] Remote Grab [**] 01/25-12:49:04.464164 172.16.2.5:56704 -> 172.16.2.6:7000 UDP TTL:58 TOS:0x0 ID:16456 Len: 8 [**] Shivka-Burka [**] 01/25-12:49:05.683546 172.16.2.5:56704 -> 172.16.2.6:1600 UDP TTL:58 TOS:0x0 ID:28222 Len: 8 [**] Hackers Paradise [**] 01/25-12:49:05.809637 172.16.2.5:56704 -> 172.16.2.6:31 UDP TTL:58 TOS:0x0 ID:65451 Len: 8 [**] Silencer, WebEX [**] 01/25-12:49:06.161501 172.16.2.5:56704 -> 172.16.2.6:1001 UDP TTL:58 TOS:0x0 ID:45491 Len: 8 [**] Ripper Pro [**] 01/25-12:49:06.525815 172.16.2.5:56704 -> 172.16.2.6:2023 UDP TTL:58 TOS:0x0 ID:18956 Len: 8 [**] Trojan Cow [**] 01/25-12:49:06.558256 172.16.2.5:56704 -> 172.16.2.6:2001 UDP TTL:58 TOS:0x0 ID:60477 Len: 8 [**] Sockets De Troie [**] 01/25-12:49:06.579138 172.16.2.5:56704 -> 172.16.2.6:5000 UDP TTL:58 TOS:0x0 ID:8426 Len: 8 [**] Attempted Sun RPC high port access [**] 01/25-12:49:06.623967 172.16.2.5:56704 -> 172.16.2.6:32771 UDP TTL:58 TOS:0x0 ID:41745 Len: 8 [**] Sockets De Troie [**] 01/25-12:49:06.655303 172.16.2.5:56704 -> 172.16.2.6:5001 UDP TTL:58 TOS:0x0 ID:30473 Len: 8 [**] Hackers Paradise [**] 01/25-12:49:07.470151 172.16.2.5:56704 -> 172.16.2.6:456 UDP TTL:58 TOS:0x0 ID:49981 Len: 8 [**] Back Orifice [**] 01/25-12:49:07.915080 172.16.2.5:56704 -> 172.16.2.6:31337 UDP TTL:58 TOS:0x0 ID:8186 Len: 8 [**] Satanz Backdoor [**] 01/25-12:49:08.362728 172.16.2.5:56704 -> 172.16.2.6:666 UDP TTL:58 TOS:0x0 ID:9630 Len: 8 172.16.2.5 is my Router IP, in the firewall i have set tcp and udp highports enabled. The 172.16.2.6 is a win client in my home LAN. nmap to the client 172.16.2.6 offers following open ports Port State Service 135/tcp open loc-srv 139/tcp open netbios-ssn 445/tcp open microsoft-ds 1025/tcp open listen 135/udp open loc-srv 137/udp open netbios-ns 138/udp open netbios-dgm 445/udp open microsoft-ds 500/udp open isakmp Do I have a problem? -- Best regards, Dietmar mailto:earthmate@gmx.net

1 0

RE: [suse-security] after ip ....
by Barry Gill 25 Jan '02

25 Jan '02

every ISP has an abuse(a)isp.name email address. This is the only real way to get something done although in truth it will depend on the nature of the offence. Many ISP's don't have the man power to chase down offenders and many (especially when it is a dial up port) will not be helpful in determining who the offending user is. Many ISP's will blackhole IP addresses that continuously offend, so it would be a good idea to get hold of your own ISP and complain so that you do not waste your local loop bandwidth to deliver packets to /dev/null

1 0

AW: [suse-security] Which ISP owns some IP?
by Peer Stefan 25 Jan '02

25 Jan '02

it does reveal the soa-record and therefore the e-mail address of the zone-admin. postal address, phone-number, name etc. are not shown. grant you that. -stefan -----Ursprüngliche Nachricht----- Von: Kurt Seifried [mailto:listuser@seifried.org] Gesendet: Freitag, 25. Jänner 2002 11:29 An: suse-security(a)suse.com Betreff: Re: [suse-security] Which ISP owns some IP? I think you mean whois, dig doesn't give contact info/etc. whois 1.2.3.4(a)whois.arin.net for american ip's. ripe, apnic and so on for other regions. Kurt Seifried, kurt(a)seifried.org A15B BEE5 B391 B9AD B0EF AEB0 AD63 0B4E AD56 E574 http://www.seifried.org/security/ -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

1 0

Re: [suse-security] Which ISP owns some IP?
by Peer Stefan 25 Jan '02

25 Jan '02

try http://www.whois.net/ or the command-line tool whois. or you're a dns guru and know how to use dig *hint* :-) regards, stefan -----Ursprüngliche Nachricht----- Von: Juan Carlos S.C [mailto:juancarlos.silla@dyr.es] Gesendet: Freitag, 25. Jänner 2002 12:05 An: lista seguridad suse Betreff: [suse-security] Which ISP owns some IP? Hello * : How can i know the owner of an IP address. There is no reverse mapping for dial-up address but each ISP has his own range of IP's. Could I know from where connecctions come, far away from traceroute? Yes, it could be IP spoofing but ... Thanks. -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

3 2

RE: [suse-security] which cipher for ssh2
by Reckhard, Tobias 25 Jan '02

25 Jan '02

> Wasn't arguing, was just making sure people understand that > an 80 bit key, a > 90 bit key and a 112 bit key are _SIGNIFICANTLY_ different Agreed, people generally have difficulty grasping the exponential increase in the difficulty to break a key by increasing its number of bits. > Dah. But then you can do things like 3des which is usually 2 > keys for an > effective length of 112, but the attacker has to do 3 crypto > operations, so > an attack becomes expensive. Imagine the keyscape of 3pgp > (yes I know pgp is > a program and not the algorithm used for crypto, but you get > the idea ;). I s'pose you mean the asymmetric part in PGP's operation (you and I and many others, but some not, know that it employs hybrid cryptography). The question that remains though, is, can it work the way Triple-DES works. Triple-DES is only good if the order of operations is encrypt with key 1, *decrypt* with key2, encrypt with key 1 or 3, depending on how many 56-bit keys you have. I'm not sure that this applies to other algorithms in a similar manner. Could be you're just doubling the difficulty by encrypting again with a key of same length as the first, not exponentiating it. > 99 times out of 100 with modern crypto it's weak > passphase/mistake in key > recovery/creation/etc that does it in, the math is rarely > wrong, unless it's > a closed system or amateur system (something to be learned from that I > think). Agreed. Tobias

1 0