August 2004 - openSUSE Security - openSUSE Mailing Lists

Firewall @ application level
by Christian (aka Neodaxus) 18 Aug '04

18 Aug '04

Hello, I'm looking for a free firewall at the application level for use with SuSE Linux. Maybe a firewall which also asks if a connection doesn't match the rules (like ZoneAlarm). Thanks, Christian

2 1

Susefirewall2 on 9.1 and emule
by John Lederer 17 Aug '04

17 Aug '04

I am afraid I am floundering with what should be a simple problem. I have a 9.1 box that operates as a firewall/router for a home network. Some of the workstaions are Windows XP. One of the windows XP staions wants to use emule. I have tried with and without masquerading, a midified /sbin/Susefirewall2 script, and an add on custom script. I have , in fact, gotten myself thorughly confused and tangled. Does anyone have an /etc/sysconfig/Susefirewall2 parameter script that works with emule that they would share? Many thanks, John Lederer ============================ Emule firewall requirments 1) /Local Port:/ 4662 /Remote Port:/ any /Protocol:/ TCP /Direction:/ incoming /Purpose:/ Client Port / Connections from other clients, Client to Client Source Exchange /Note:/ You can change this port in /Preferences -> Connection ->/ /Client Port/ This port has to be forwarded in a router. Changing this port in Preferences you must also change the forwarding in the router 2) /Local Port:/ any /Remote Port:/ 4662 /Protocol:/ TCP /Direction:/ outgoing /Purpose:/ Client Port / Connections to other clients, Client to Client Source Exchange /Note:/ 4662 is the default port, but other clients may have different settings. Change the /remote port/ to /any/ when configuring a firewall 3) /Local Port:/ 4672 /Remote Port:/ any /Protocol:/ UDP /Direction:/ incoming /Purpose:/ Clients source asking / extended eMule protocol, Queue Rating, File Reask Ping /Note:/ This port has to be forwarded in a router. Changing this port in Preferences you must also change the forwarding in the router. If you are not able to forward this port check the /disable/ box in /Preferences -> Connection -> UDP Port/ 4) /Local Port:/ any /Remote Port:/ 4672 /Protocol:/ UDP /Direction:/ outgoing /Purpose:/ Clients source asking / extended eMule protocol, Queue Rating, File Reask Ping /Note:/ 4672 is the default port, but other clients may have different settings. Change the /remote port/ to /any/ when configuring a firewall 5) /Local Port:/ any /Remote Port:/ 4661 /Protocol:/ TCP /Direction:/ outgoing /Purpose:/ Connection to server /Note:/ 4661 is the default port of a server. Many server use different ports. Configuring a firewall the /remote port/ again changes to /any/. 6) /Local Port:/ any /Remote Port:/ 4665 /Protocol:/ UDP /Direction:/ outgoing /Purpose:/ Source asking on servers /Note:/ Servers using the default port 4661 TCP (see #5) automatically set their port for source asking to 4665 UDP. If a server uses a different port in #5 the corresponding UDP port is set to [Connection Port + 4]. For firewalls the /remote port /here is /any./ 7) /Local Port:/ 4711 /Remote Port:/ any /Protocol:/ TCP /Direction:/ incoming /Purpose:/ Webserver /Note:/ This is the default port for the web interface. When using a router this port has to be forwarded or no connection to the webserver will be possible.

2 1

SUSE Security Announcement: rsync (SUSE-SA:2004:026)
by Thomas Biege 16 Aug '04

16 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: rsync Announcement-ID: SUSE-SA:2004:026 Date: Monday, Aug 16th 2004 16:00 MEST Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Database Server, SUSE eMail Server III, 3.1 SUSE Linux Enterprise Server 8, 9 SUSE Linux Firewall on CD/Admin host SUSE Linux Connectivity Server SUSE Linux Office Server Vulnerability Type: remote system compromise Severity (1-10): 2 SUSE default package: no Cross References: http://samba.org/rsync/#security_aug04 Content of this advisory: 1) security vulnerability resolved: - insufficient pathname sanitizing problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - KDE - mozilla/firefox - xine-lib - opera - acroread 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion The rsync-team released an advisory about a security problem in rsync. If rsync is running in daemon-mode and without a chroot environment it is possible for a remote attacker to trick rsyncd into creating an absolute pathname while sanitizing it. As a result it is possible to read/write from/to files outside the rsync directory. SUSE LINUX ships the rsync daemon with a chroot environment enabled by default, therefore the default setup is not vulnerable. 2) solution/workaround As a temporary workaround we suggest to keep the chroot-option of rsyncd enabled or to avoid the daemon-mode and use SSH as transport channel if possible. 3) special instructions and notes After applying the update, all instances of the rsyncd should be closed and the rsync daemon should be restarted. Please execute the following command as root: 'rcrsyncd restart' 4) package location and checksums 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. x86 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/rsync-2.6.2-8.9.i586.r… afa5b8894e2d1acff4b040e8ba515ae4 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/rsync-2.6.2-8.9.i586.p… c0bf6dcf573a9a4197da0977ea638f2a source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/rsync-2.6.2-8.9.src.rpm f31f409225560bd1ac1d5fb5f0d8c43e SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/rsync-2.6.2-26.i586.rpm 5d7be9a510a4a5fafccbc29c63b0dec8 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/rsync-2.6.2-26.i586.pa… 70809462c5d88bc8241b544100689efe source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/rsync-2.6.2-26.src.rpm f92d91816456f0e626ea1ee41ebe8b65 SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/rsync-2.6.2-26.i586.rpm 4f901dee110596bf2a48a24d8d094b71 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/rsync-2.6.2-26.i586.pa… c7260721ec51a569309cd4629a3a5ad1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/rsync-2.6.2-26.src.rpm fcd540a8e89c864b56cbad7d60696450 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/rsync-2.6.2-25.i586.rpm 193752687ef1d98a5ebec4ff471842b1 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/rsync-2.6.2-25.i586.pa… 9b6225e3bd2ff624f5f61bd6b033e8b8 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/rsync-2.6.2-25.src.rpm 0f649de8547008aa5e2a977ff209fca3 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/rsync-2.6.2-8.9.x8… 745a09fdbccc7ccfea9705f54a6825a3 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/rsync-2.6.2-8.9.x8… 725b10d1703f6ee41185564d08b151d3 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/rsync-2.6.2-8.9.src.r… 6145ed8346ebfd63863734b30fc3a8e9 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/rsync-2.6.2-26.x86… 20d3b3f8b3fde71ae1c3f0eed22feee0 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/rsync-2.6.2-26.x86… 9bc24b61361c74f37e4fd81e8e7faa98 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/rsync-2.6.2-26.src.rpm 599e9f0a19fd2890499c863cd0394598 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - KDE The KDE libs package contained two occurrences of insecure handling of temporary files in the mcoputils code (Thanks to Andrew Tuitt for reporting this to us) and in the dcopserver code. These two bugs can be exploited locally to remove and/or overwrite files with the privileges of the user running a vulnerable KDE application. A bug in the kdebase3 package allows the content of unrelated browser windows to be modified. This issue may be used to trick users into entering sensitive informations on a malicious web-site. New packages are available on our FTP servers. - mozilla/firefox We are currently testing new mozilla/firefox packages that include several fixes for security-related bugs. New packages are available on our FTP servers (for some products we have to delay the delivery of the update package). - xine-lib This update of xine fix' a buffer overflow in the vcd input source identifier. This buffer overflow is independent of the media format. The bug can be used to execute arbitrary commands. New packages are available on our FTP servers. - opera The web-browser opera is affected by several security bugs. Due to the nature of this package we are not able to provide security updates in a timely manner and have to wait for binary packages to be published by "Opera Software". - acroread iDEFENSE reported a buffer overflow and insecure handling of shell meta-chars in acroread code. We depend on the release of a new binary package by Adobe. An update will be available as soon as possible. ______________________________________________________________________________ 6) 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.2.2 (GNU/Linux) iQEVAwUBQSDIVXey5gA9JdPZAQECNQf/VieGW0TuUNSEs10A/K2kPDJGzUpOPEs7 KzH0FGH0zT1+Ng9rV8nsez59+OOW0Wlff5BrxKEkz/yNhecNfcoGmg6wmyNPbvBC 4paP85Ft5vNHcy8uipVvOGCqutduNXeZzmYiQXASI9khyylDwwuc8WYYodsBPIbu qKcIm8odxLkRQuyWnTMyOp+JMXYKiLuWjnODHAMIKfsKgDvgzfPdY5Tks8P3bsgd kpNC4DT/dd8q0a0KyGse93tS79l3LeMzdiuFgCe/pC0HNU5In/hgWnGmJ7tonzeT 2mHfL2m7TAEjpfZZpbLD2PTMCQRRybj2tGmAVlSg7XW+kTc9Ff/wRg== =GgJC -----END PGP SIGNATURE-----

1 0

SSH login password guesses
by Sven 'Darkman' Michels 16 Aug '04

16 Aug '04

Hi there, we already had a small thread about this topic but only for some log entries and not the problem itself ;) As we probably all noticed there're a bunch of ssh connects every day which try to login as root, test, user, admin, guest and maybe others. Now i saw a scan with more then 5000 attempts to login to serval servers. I read a lot about this topic now but noone really knows whats going on. So i try to sum up the information i got, maybe you know a littlebit more than i or just have the same "problem" and want to know more about it ;) First of all, it seems that there multiple tools or scripts out trying these logins. The simplest one only try root:root and guest:guest as login. Later on a few more usernames where added: guest, test, user, admin (and maybe others). After that someone seems to add some dictionary support to the tools. Now it tries many passwords for the root user (no pass guesses for the other ones so far). If some box has such a weak/guessable password, some of the "crackers" installed stuff like rootkits (e.g. suckit) or DDoS flood scripts/IRC Bots and other "bad" stuff. Today we found such a server in our network. The password wasn't changed by the customer so it was guessable. But unlike other reports no rootkit etc. was installed. All we found was some "uname -r" that was done. Maybe because of a very recent kernel and some other stuff they didn't like this box very much. A few analyses had been done yet: http://dev.gentoo.org/~krispykringle/sshnotes.txt http://lists.netsys.com/pipermail/full-disclosure/2004-August/025330.html http://isc.sans.org/diary.php?date=2004-07-28 and many other postings on the well known lists like dev-shed, full-disclosure, bugtraq etc. Most of the attackers seem not to be very skilled like you'll see in some postings: they leaved bash_history files and did other stuff you'll notice if you take a closer look to your box. For ppl who want to protect themselves against such attacks: - disable rootlogin (PermitRootLogin no in sshd_config) - use secure passwords - maybe just use ssh keys - don't use guessable accounts - put sshd on a different port then 22 (will only help for such "normal" scans, not if someone want to break *your* box.) - use features like hosts.allow/deny or iptables to allow ssh just for a couple of hosts (maybe isn't useable for ppl with nonstatic ips, but you still can limit ssh access to your isp, or use a vpn ;) Hope i didn't forget anything. If someone knows more about this topic, please let us know ;) Regards, Sven

2 1

Latest kernel still hangs?
by suse＠tremor.com 16 Aug '04

16 Aug '04

I really don't have the ability to test the latest kernel on my servers due to location, but the last update prior to the latest one (2.6.5-95 I believe) caused my servers to hang on boot, mainly after try to access the transaction logs on my filesystems. Has anyone tried the latest kernel update on a system that hung before? For noting, my servers are newer DL320 G2 series, with the latest BIOS, with ReiserFS as the filesystem.

4 5

Samba Updates SuSe 9.1 Professional
by dannowwillis＠att.net 16 Aug '04

16 Aug '04

The June Samba update (going from 3.02 to 3.04) for SuSe Professional 9.1 brought my Samba server to its knees. I had to revert back to 3.02. Has anyone running a Samba server as a member server of an NT 4 domain successfully applied the latest patches to Samba 3.05? I like to be current on patches, but once bitten, twice shy... Thanks, Dan Willis

1 0

nmap broken again in 9.1 ?
by David Uvalle 16 Aug '04

16 Aug '04

Hi Im trying to run nmap as root to use some features i need but it doesnt scan anything, as user it scan normally am on suse 9.1, with kernel 2.6.5-7.104-default have all the patches from Yast/Online Update until today, maybe the last kernel upgrade broke something i dont know Thanks for your help guys -- */*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* David Uvalle Zepeda Chief Security Officer. Radikal Systems S.A de C.V. http://www.radikalsystems.com

7 13

Re: [suse-security] So, is Suse working on a fix for the mysqld problem?
by Hans-Peter Winkler 15 Aug '04

15 Aug '04

Hello, > > If so, will you bring out a new 8.0 kernel as well, even if 8.0 has > > reached its EOL? > > > The latter. There are some few packages in the queue for 8.0, but they > are just waiting for their publication date and have been ready for > quite some time... > It should be possible, however, to run an 8.1 kernel on an 8.0 system - > and the 8.1 kernel is an extremely reliable one. I haven't seen a crash > so far. has anyone tried the 8.1 kernel update on an 8.0 system yet? I am too affected by the bug in the kernel. Or is there any specific date for the "some few packages in the queue for 8.0" to be released (including an updated kernel)? Rgds hpwi -- NEU: WLAN-Router f�r 0,- EUR* - auch f�r DSL-Wechsler! GMX DSL = superg�nstig & kabellos http://www.gmx.net/de/go/dsl

1 0

PROTO_IPSEC_ESP SA not found (maybe expired)
by mailinglists 14 Aug '04

14 Aug '04

Hi I've changed from redhat 9 SuperFreeSwan 1.99.8 to suse 9.1 FreeSwan 2.05. With a few changes done on ipsec.conf it all should have worked fine. I can start conns, the freeswan deamon negotiates all its SAs with the other sides. And I can ping the other sides. But I fail to get any other communication through any tunnel. I never have seen before the "PROTO_IPSEC_ESP SA(0x79b5f800) not found (maybe expired)" error message. As a matter of fact I recompiled the kernel with ESP, IPCOMP and IPIP compiled into the kernel not just added as modules. This dropped a number error messages at the initial Freeswan start-up. However it did not change the situation. Then I dropped the SuSE FreeSwan daemon and installed newest StrongSwan 2.1.5 release. No change. So problem probably not deriving from FreeSwan. I can ping, the rtt is normal. But I don't get neither UDP nor TCP nor traceroute through any tunnel. Does anybody know a work around (please don't say change distro). Philipp

1 0

Static NAT w/ iptables problem
by Markus Trümper 13 Aug '04

13 Aug '04

Hello, I'm trying to set up a firewall to do static NAT between two networks: internal network 192.168.1.0/24 server 192.168.1.3 | LAN_IF 192.168.1.7 Firewall EXT_IF 10.80.137.1, 10.80.137.10 | DMZ 10.80.137.0/24 'server' should be reachable from the DMZ by talking to 10.80.137.1. That address has no other purpose. My rules so far don't work. I can not reach 'server' by talking to x.x.x.1 on the external IF of the Firewall. Any idea why? ------------------------------------------------ ifconfig eth1 add 10.80.137.1 echo "Clearing current rules ..." iptables -F iptables -X iptables -t nat -F iptables -t nat -X iptables -t mangle -F iptables -t mangle -X # LAN: 192.168.1.0/24 LAN_IF=eth0 # EXT: 10.80.137.0/24 EXT_IF=eth1 # 'server': EXT_DS=10.80.137.1 DS=192.168.1.195 IPTABLES=/sbin/iptables # (Connections originating from the DMZ) $IPTABLES -t nat -A PREROUTING -d $EXT_DS -i $EXT_IF -j DNAT --to-destination $DS $IPTABLES -A FORWARD -p all -i $EXT_IF -o $LAN_IF -d $DS -m state --state NEW -j ACCEPT $IPTABLES -A FORWARD -t filter -i $EXT_IF -m state --state ESTABLISHED,RELATED -j ACCEPT # (Connections originating from internal) $IPTABLES -t nat -A POSTROUTING -s $EXT_DS -o $EXT_IF -j SNAT --to-source $DS $IPTABLES -A FORWARD -t filter -i $LAN_IF -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT ------------------------------------------------ Thanks in advance Markus --------------------------------------------------------------------------------- | Dipl. Inform. Markus Trümper | | | | Daewoo Automobile Deutschland GmbH | | email: m.truemper(a)daewoo-automobile.de | Lindenstraße 110 | | www: http://www.daewoo-automobile.de | 28755 Bremen | | Telefon: +49 (0)421 668-4138 | Germany | | Fax: +49 (0)421 668-4192 | | ---------------------------------------------------------------------------------

1 0