October 2003 - openSUSE Security - openSUSE Mailing Lists

Problem with IPSec and SuSEfirewall2 SuSE-FW-ILLEGAL-TARGET
by R. Peters 03 Nov '03

03 Nov '03

Hi, after weeks of reading FAQ's, guides and everything I found about firewalls and FreeS/WAN I still have a big problem. But first I describe what is working and my network setup: roadwarrior (a.b.c.d) | internet | (d.e.f.g, static ip, ext. device, eth1, ipsec0) gateway with SuSE 8.2 and FreeS/WAN (10.10.11.3, int. device, eth0) | (10.10.11.0/24, int. network) LAN IPSec connection between roadwarrior and gateway external device works without any problem. But no matter what I try, if I try to ping the gateway's internal device (10.10.11.3) or the internal network I always get SuSE-FW-ILLEGAL-TARGET IN=ipsec0 OUT= MAC=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx SRC=xxx.xxx.xxx.x DST=10.10.11.3 LEN=60 TOS=0x00 PREC=0x00 TTL=128 ID=3540 PROTO=ICMP TYPE=8 CODE=0 ID=1280 SEQ=256 *SRC=xxx.xxx.xxx.x is the adress of my roadwarrior I did set up the Firewall as described in /usr/share/doc/packages/SuSEfirewall2/EXAMPLES Scenario4: FW_DEV_EXT="eth1 ipsec0" FW_DEV_INT="eth0" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_NETS="10.10.11.0/24" FW_SERVICES_EXT_UDP="500" FW_SERVICES_EXT_IP="50 51" FW_FORWARD="a.b.c.d,10.10.11.0/24 10.10.11.0/24,a.b.c.d" a.b.c.d is the adress of my roadwarrior I left all other options default for testing the IPSec connections. Even without routing and masquerading I still get the error above and the above settings for routing forwarding and masquerading did not change anything. I also tried to make a custon updown script to be executed when ipsec0 comes up, that didn't change anything too. If the firewall is disabled I can ping the gateway's internal device (10.10.11.3) from an external IPSec connection. With the firewall enabled I can only access the external device of the gateway - I cannot ping to the internal network. Any suggestions what I am doing wrong here? I guess I have to use a custom updown script that allows traffic between the roadwarrior and the internal network and is executed each time an IPSec connection comes up. I tried this script but still had the SuSE-FW-ILLEGAL-TARGET error: up-client:) iptables -I FORWARD 1 -s $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \ -d $PLUTO_PEER_CLIENT -j ACCEPT iptables -I FORWARD 1 -d $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \ -s $PLUTO_PEER_CLIENT -j ACCEPT ;; down-client:) iptables -D FORWARD -s $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \ -d $PLUTO_PEER_CLIENT -j ACCEPT iptables -D FORWARD -d $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \ -s $PLUTO_PEER_CLIENT -j ACCEPT ;; I checked the Pluto variables at execution time of the script and ip-adresses represented by those were correct. I appreciate any suggestions, thanks in advance, R. Peters

2 2

Problem with Passwd (Suse 8.2)
by Patrique Wolfrum 31 Oct '03

31 Oct '03

Hello, i have the following setup on my server: Suse 8.2 Professional as operating system and RSBAC and Pax as security enhancements. As server programs I have apache, mysql and samba installed and RSBAC configured accordingly. So far the system works fine. In order to prevent that some bad guy - who has somehow acquired root privileges - from changing the password of the RSBAC "security-officer", logging in as him and deactivating RSBAC, I wanted to "move" the right of changing password to a seperate user, creating a "password officer". For that I created a seperate "RC_FD" (filetype definition in the role based access model) for /etc/passwd and /etc/shadow, so I can define, which user shall have read-write access on them. Up to that point I have got it working. The problem is now, that passwd only allows root to change passwords from other users. With the tools of RSBAC I could persuade passwd to accept an other user as system administrator, as substitute for root. Is there a way, to get passwd accepting an other user as entitled to changing other users passwords ? Thank you very much in advance. With best regards. Patrique Wolfrum

1 0

SUSE Security Announcement: thttpd (SuSE-SA:2003:044)
by Thomas Biege 31 Oct '03

31 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: thttpd Announcement-ID: SuSE-SA:2003:044 Date: Friday, Oct 31st 2003 13:04 MEST Affected products: 7.3, 8.0, 8.1, 8.2, 9.0 Vulnerability Type: remote privilege escalation/ information leak Severity (1-10): 5 SUSE default package: no Cross References: CAN-2003-0899 CAN-2002-1562 Content of this advisory: 1) security vulnerability resolved: - buffer overflow - information leak (virtual hosting) problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - libnids - KDE - postgresql - frox - sane - ircd - fileutils - mc - apache1/2 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Two vulnerabilities were found in the "tiny" web-server thttpd. The first bug is a buffer overflow that can be exploited remotely to overwrite the EBP register of the stack. Due to memory-alignment of the stack done by gcc 3.x this bug can not be exploited. All thttpd versions mentioned in this advisory are compiled with gcc 3.x and are therefore not exploitable. The other bug occurs in the virtual-hosting code of thttpd. A remote attacker can bypass the virtual-hosting mechanism to read arbitrary files. 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/thttpd-2.23beta1-165.i… e33f3897cac1e1fe117eff8ca252ec0f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/thttpd-2.23beta1-165.i… cd5c2aeb6d31d6a6781f392af17a4989 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/thttpd-2.23beta1-165.sr… c6e2446bc94c8c00d35b7741b67df678 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/thttpd-2.23beta1-164.i… a491b55f562fa0f3b1679ee819140c72 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/thttpd-2.23beta1-164.i… bbb3dd624b19d8683223049a070d4cf2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/thttpd-2.23beta1-164.sr… 2710751ff1ee8fbab3c2934c5cb09f3d SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/thttpd-2.23beta1-163.i… 428db4fb2eccebb5ed16cb28161ba2a5 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/thttpd-2.23beta1-163.i… b32fb0a87d8d7de3ed1953e64da89bc8 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/thttpd-2.23beta1-163.sr… e64bc1488747a414f6bd60735f82385f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/thttpd-2.20c-98.i386.rpm 952dcca179b647afdeea02b987e3daf8 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/thttpd-2.20c-98.i386.patch.r… e596221f34a73ba6fdd29abcecb6e211 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/thttpd-2.20c-98.src.rpm 8500be9c635d1c5c9618ecca2a09a5e7 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/thttpd-2.20b-175.i386.rpm 16ffc5238c1f57b8a1e6e02989524e82 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/thttpd-2.20b-175.src.rpm b5c4b9c65182fcd2a326e3edad7b2dfb PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/thttpd-2.20b-112.ppc.rpm e7aaff82bd90c459849dd78b1cc47515 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/thttpd-2.20b-112.src.rpm 8ac31eb38063a891e37ed327a5ddbc0c ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - libnids New libnids packages were released to stop remote command execution due to a memory corruption in the TCP reassembly code. (CAN-2003-0850) Please download them from our FTP servers. - 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. - postgresql Several buffer overflow problems were fixed in the pg_to_asci() function of postgresql server. New packages are available on our FTP servers. - frox A denial-of-service attack in frox can be trigger remotely. The packages are currently tested and will be release as soon as possible. - 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. - fileutils A local denial-of-service attack can be triggered by abusing the -w option of ls(1). This attack can be turned into a remote denial-of- service by using network services, like wuftpd, that rely on the ls(1) command installed on the system. 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) iQEVAwUBP6JW93ey5gA9JdPZAQE7AAf+LMQ45cIOD3iSCFZ8g/RuWVI5yiY2CkE2 0KpivccK5qehDInv+spLFAZBOlFXjmkmPcyBZbaFkuTdo6PpnGicJ6gHdPvYzVZ1 +0I0T9u8dZUlAoeGnTVNtzcN8yEA9xcp1mjEXORoclR5zwwVFXRcp8rktde768yD kBvur0ZY9g4OyJEwb/UzdiKxKuKiFlq3llVz5ID8qDMIDQfORygVqjxI4pFDwff/ Pm9qxit7J2Q1tB3VZXBkUb+ba+Y6bLBFkhk64hHr+q3jtMZlrK6z2WMJsF/a5gqp JDaTp1BxChMeJ6Q5YTq8ZCUzKKu7Dg4d42+php7QiR9UIifk4ch2gQ== =6u83 -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de>, SuSE Linux AG, 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 -- ... stay with me, save and ignorant, go back to sleep... - Maynard James Keenan

1 0

YOU Woes
by Sturgis, Grant 30 Oct '03

30 Oct '03

Greetings All, I am having a problem with YOU that I hope someone here can help me with. Essentially, whenever I run YOU I get the error: Initialization failed. Try again. If failure continues, choose another SuSE FTP/HTTP server. I tried to get help from SuSE (we have support) some time ago, and they told me that I have UnitedLinux installed and not SLES. Silly me, I thought they were one and the same. Anyway, I can see the request going through our proxy server and the response is a 404 error: 1067289521.691 390 10.10.10.200 TCP_MISS/200 217 GET http://sdb.suse.de//youfix/ - DIRECT/195.135.220.8 text/html 1067289522.167 423 10.10.10.200 TCP_MISS/404 561 GET http://sdb.suse.de//youfix/i386/update/UnitedLinux/1.0/patches/directory.3 - DIRECT/195.135.220.8 text/html I have downloaded and installed the newest (I think) version of YOU: yast2-online-update-2.6.16-0 Any ideas / suggestions / pointers / advise is greatly appreciated. Thanks, Grant 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.

4 3

Audiostream caching
by Kaiser, Hans 30 Oct '03

30 Oct '03

Hello List, I'm searching for a possiblity to cache a realaudio, mp3 and/or a windowsmedia audio stream. The intension, is to reduce the traffic in the lan, because many guys hear the same stream (radiostation) in our house. Now it would be nice, if a proxy, or any other chaching instance would load the stream, and store it in a cache. So the guys could connect to the local streamingserver to hear the cached stream. Sorry for the post in the security list, but I think it is be best list for such questions. best regards, Hans

2 2

qmail installation script 1.3.6 final release
by Franck 29 Oct '03

29 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, A new version of the installing's script for qmail are released. All feedback are welcome for this final 1.3.6 :) http://www.linuxpourtous.com/download/qmail/install_qmail-1.3.6.tar.gz http://www.linuxpourtous.com/download/qmail/README http://www.linuxpourtous.com/download/qmail/CHANGELOG Changelog since 1.3.6-rc6 : * Testing installation script on Debian testing without error. * Added values.suse and values.debian for both installation. * This script works fine on SuSE Linux and Debian testing. * Added apt-debian.sh for installing all needed softwares on Debian. * Minor bug fix Best regards - -- Franck http://www.linuxpourtous.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/n8Im1zwfep5k9qERAuWsAJ4tWfX7u49mmKRFsxIFvXpCzsEtPwCeN0OX urulkBBpGKP7kCNU4/rL658= =DW0v -----END PGP SIGNATURE-----

1 0

SHELL=/bin/false but user can still log in
by Hollweg, Daniel 29 Oct '03

29 Oct '03

Hi List, I have an problem with my SuSe 8.2 installation with all current security patches applied. If I enter /bin/false as login shell in the /etc/passwd the user can still login and gets shell access. After rebooting the system the shell entry in the /etc/passwd is processed correct and a login attempt is closed as you would expect. Other entries like home dir in the passwd are parsed correct. Any ideas? Thanks and regards Daniel

6 6

kernel IPv6 changes affecting DNS?
by timo 29 Oct '03

29 Oct '03

I seem to have strange problems that are related to the ipv6 module being enabled. Behaviour seems (so far at least) to differ between kernel versions: k_deflt-2.4.19-74 and k_deflt-2.4.19-340. The problem is seen as slow startup of certain networked Java applications using JBoss services. I traced the issue to failing DNS replies, i.e. timeouts but the problem was that there was DNS AAAA queries (IPv6 related) going on. And the server was unable to answer these - as it is serving IPv4. Having found that out using ethereal I checked from web and found out that disabling the IPv6 module via /etc/modules.conf drops off IPv6 stuff and might help - actually did help. However, I checked with an older version of the kernel - and probably some other stuff as well - and the whole thing seems to work OK there, with IPv6 module. Is there some explanation I have missed? Is this behaviour correct now, or was it earlier? Does this affect performance and possibly security due extra delays with DNS timeouts? Is the correct solution to disable the module via: # alias net-pf-10 ipv6 (in /etc/modules.conf) or is there better ways of dealing with this? It has quite a big hit on the application since the "normal" startup time is in the range of 0.7 seconds and these DNS timeouted AAAA queries push it somewhere between 15 and 20 seconds! br, timo

1 0

Squid Update ?
by André Sänger 29 Oct '03

29 Oct '03

Hello suse-security, I have installed the following version on SuSE8.2: # rpm -q squid squid-2.5.STABLE1-63 Now, I don´t see any Updates to this package offered by YOU, but when I look at ftp.suse.de:/pub/suse/i386/8.2/i586/squid-2.5.STABLE1-73.i586.rpm There is a new package with version number -73 ? Does the ftp-distribution use different version-numbers than the CD distribution in general? Or am I missing something? The reason I was searching for squid in the first place was that I wanted to use NT/Samba User Groups for Authentication, but didn´t find a wb_group.sh or wb_group.pl or wbinfo_group.pl on my system. What is recommended to get this workingon SuSE8.2? I found a perl script at http://www.squid-cache.org/cgi-bin/cvsweb.cgi/squid/helpers/external_acl/wb… and added the following line to squid.conf: external_acl_type nt_group %LOGIN /usr/local/libexec/wbinfo_group.pl That does the job, but I am not sure if this is the best way? -- Mit freundlichen Grüßen, André Sänger mailto:Andre.Saenger@gmx.de Landratsamt Coburg

7 18

Problems with secure socket layer on email server.
by philt 28 Oct '03

28 Oct '03

I am fairly new to linux and suse but I am trying to set up 8.2 pro as a mail server. I have recieved all of the updates. and found this in the documentation to create forward listeners ssl -L 25:myserver:25 myserver ssl -L 110:myserver:110 myserver I had to shudown my pop3 server to get the 110 port to allow that and I started it back up. I get the following mesage in outlook from a pc internal to the network The connection to the server has failed. Account: 'redmail.redoakhealthcare.com', Server: 'redmail.redoakhealthcare.com', Protocol: POP3, Port: 110, Secure (SSL): No, Socket Error: 10061, Error Number: 0x800CCC0E Etherreal from both machines shows 3 queries and acks In the mail log I get command stream end of file while user=??? host=thehostIamrunningoutlook on and its ip address. I would appreciate any help -- Absolute Internet Services (http://www.aiserve.net)

2 1

Re: [suse-security] Old question: what is SUSE going to do with harden_suse / Bastille
by Bo Jacobsen 28 Oct '03

28 Oct '03

> Hi, > > Am Samstag, 25. Oktober 2003 02:04 schrieb Bo Jacobsen: > > The standard SuSE installation is much to open. > > I agree upon that. But instead of hardening the system _after_ it has > already been set up, I'd prefer a clean install that's not "too open". > Maybe SuSE can introduce an install option such as "secure system" or > something similar. > > If only that fsck'ing portmapper wouldn't be run by default. That is the > same ...stuff like MS Windows with RPC bound to anything looking like > an interface -- remember W32/Blaster? Each time I set up a SuSE, I get > angry about that idiocy. > > Best wishes, > Lutz > I agree 100%. They need an install option named firewall, or some thing like that, that leaves out ANY stuff that should not run on a firewall. I actually find it a little strange that they have not implemented that a long time ago, since security has been a hot topic for a long time now. One of the advantages of being able to run a separate script like hardensuse, is that if something will not run, it can be difficult to figure out if it's a problem with the tightened security, or if it's something else. I have had some problems in the past, where something would not run after executing hardenSuSE, but I knew it had something to do with the things the script did, so I just had to run hardensuse step-by-step to find out what system changes caused the problem. Another advantage was that I could run hardensuse on systems that was used as normal file, print and email servers. I just had to NOT select the security options that I new would disrupt the programs running on the server, or I could just make changes afterwoods, to the specific programs. However implemented, it would be a lot better then the situation we have today where there is s no official, and simple, way to upgrade the security of a SuSE host. The normal SuSE installation even have world-read permission on all files in /root !!!. I find that more then a little open. Actually, SuSE's lack of priority on basic system secutity tools, has forced me to start looking at other systems like FreeBSD etc. Bo

3 3

SUSE 9 in Germany
by Ian David Laws 27 Oct '03

27 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone,. Would just like to inform u. that in the Mayersche book store in German they are selling SUSE 9 professional for €64.99 and the Personal for €49.95 as special offer until 15.1103 I think that is the date I saw but do not quote me. On there Internet side it is not published. So get of your bum and go get it. Ian - -- A child of five would understand this. Send someone to fetch a child of five. Groucho Marx - ---------------------------------------------------- This mail has been scanned for virus by AntiVir for UNIX Copyright (C) 1994-2003 by H+BEDV Datentechnik GmbH. PGP ID: 589F8449 Fingerprint: EB1C FACF 6BEB 540E 8AC0 F04E 2A25 A2F1 589F 8449 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/nVpaKiWi8VifhEkRAuNqAKCIz/hKdOHPfaKemf8dIDln+SjixACeNe2k FutWKxmnQzKuNSiPlfcswC0= =5yAf -----END PGP SIGNATURE-----

1 0

Cannot access SuSE 9.0 through PuTTY
by Radu Voicu 27 Oct '03

27 Oct '03

Hi there! I am trying to access my machine at work with PuTTY (the latest version) and I keep obtaining "access denied"... though, I can connect from any machine running Linux... so... what's wrong in this picture? :) Regards, Radu

6 9

About "opiekeys" in sendmail-Suse8.2 logs
by J.J. Gallardo 27 Oct '03

27 Oct '03

Hi: I have a machine running SuSE 8.2-2.4.20-64GB-SMP with sendmail-8.12.7-77. My file "/var/log/messages" (not mail) shows this ========= Oct 26 10:53:59 mxserver sendmail[1368]: OTP unavailable because can't read/write key database /etc/opiekeys: No such file or directory ========= since the last days but sendmail is running (sending and receiving) and seems to do it normally.I don't know the meaning of this log messages. There isn's any file named "/etc/opiekeys" in the system and searching at /etc/sendmail.cf, /etc/sysconfig/(send)mail i can't see anything relationed with this. Anybody knows the meaning of this log?

3 3

Re: [suse-security] SuSEfirewall2, two links and routing between them
by Fabiano Felix 27 Oct '03

27 Oct '03

Hi Marcelo, The only problem that I'm having is the describe into the first message, because this I believe that my setup is correct ("I" believe ;)) )... Well, I sent my configuration below: " FW_QUICKMODE="no" FW_DEV_EXT="eth0 eth1" # I have two Internet links FW_DEV_INT="eth2" # I have a DMZ and a LAN FW_DEV_DMZ="eth3" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="192.168.0.0/24 192.168.1.0/24" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="22 80" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_INT_TCP="80 3128" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_SERVICES_QUICK_TCP="" FW_SERVICES_QUICK_UDP="" FW_SERVICES_QUICK_IP="" FW_TRUSTED_NETS="192.168.0.0/24 200.171.207.195" FW_ALLOW_INCOMING_HIGHPORTS_TCP="yes" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_DNS="yes" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="yes" FW_SERVICE_SAMBA="no" FW_FORWARD="" FW_FORWARD_MASQ="0/0,192.168.1.2,tcp,5000 \ 0/0,192.168.1.2,tcp,1115" 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="no" FW_STOP_KEEP_ROUTING_STATE="yes" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="no" FW_ALLOW_PING_EXT="no" FW_ALLOW_FW_TRACEROUTE="yes" FW_ALLOW_FW_SOURCEQUENCH="yes" FW_ALLOW_FW_BROADCAST="no" FW_IGNORE_FW_BROADCAST="yes" FW_ALLOW_CLASS_ROUTING="no" FW_CUSTOMRULES="" FW_REJECT="no" FW_HTB_TUNE_DEV="" " Regards, Fabiano Felix Em Sex, 2003-10-24 às 15:09, Unidad de Soporte Técnico del Instituto Crandon escreveu: > some questions about that . . . > > * did you enable routing between dmz, internal and external nets ? > * did you allow the correct services in the dmz interface ? > > anycase, if you want, send me your firewall conf file so that I can help you > beter > > Greetings > Marcelo. > -- Original Message -- > From: "Fabiano Felix" <felix(a)getnet.com.br> > To: <suse-security(a)suse.com> > Sent: Friday, October 24, 2003 1:44 PM > Subject: [suse-security] SuSEfirewall2, two links and routing between them > > > > Hi all, > > > > I'm having a problem using SuSEfirewall2. I have the following > > environment: > > - 01 Internet link with 2Mb (ADSL); > > - 01 Internet link with 256Kb (F. Relay); > > - 01 DMZ; > > - 01 LAN. > > > > The ADSL connection is used to Internet access. The FR is used to > > provide a Windows Media Server, and the WM Server is on the DMZ. > > Accessing this service from Internet I don't have any problems, but when > > I try to access it from LAN, I receive the following message: > > " > > SuSE-FW-ACCESS_DENIED_INT IN=eth2 OUT= > > MAC=00:06:4f:06:78:59:00:50:da:64:58:e2:08:00 SRC=192.168.0.58 DST=200. > > 300.400.500 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=18893 DF PROTO=TCP > > SPT=2368 DPT=1115 WINDOW=64240 RES=0x00 SYN URGP=0 OPT > > (020405B401010402) > > " > > Searching into archives, I found that it is a (correct) firewall > > protection, but I need to solve this. I was wondering that is possible > > to correct this creating a custom rule. Can someone help me?? > > > > Regards, > > > > Fabiano Felix > > > > > > -- > > 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

1 0

Re: [suse-security] About "opiekeys" in sendmail-Suse8.2 logs
by J.J. Gallardo 27 Oct '03

27 Oct '03

Gerhard den Hollander wrote: > Hint: > type the error message you got above > OTP unavailable because can't read/write key database /etc/opiekeys > as a search string in Google. Really : it's monday and i'm still "sleepy"... i will search it (search first in google juancho, search first in google juancho...-:).

1 0

Problem with Authentification
by Gordon Cichon 27 Oct '03

27 Oct '03

Dear Madams and Sirs, we have here a small, trusted network (with trusted users) that consists of a heterogenous (i.e., Suse, Redhat, Solaris) set of machines and operates a common, unified file system (w/ autofs and nis). We also would like to provide a convenient mechanism to remotely login to the various machines. This is especially important for shell scripts which have to run various parts of our process on different machines which have different sets of softwa After an internal evaluation, we came to the conclusion that rsh/rlogin is a better solution than ssh. Ssh comes with an overhead about authentification that is not justified in our small, trusted network. Also its encryption limits its performance. e.g., when transferring large amounts of data through remote copy or pipes. We also don't like to switch off these mechanisms in ssh because we still would like to use a strongened ssh for connections outside our network. If we were selectively switching off ssh's security mechanisms, we would see a risk that we would introduce wholes in our security system (mainly because of human-cause configuration errors). We would like to keep rsh and ssh separated. My favorite solution would be to use /etc/hosts.equiv, e.g. > +@catnet in order to enable for the whole netgroup. (fyi. > ypmatch -k catnet netgroup yields: > catnet (veltins,,) (holsten,,) (spaten,,) (andechs,,) (becks,,) (paulaner,,) Then, I would like to rsh, e.g.: > rsh andechs pwd Alternatively, I could put either of those > @catnet gordon > +@catnet gordon > +@catnet > @catnet into .rhosts. That does not work either. The only thing that would is to put the whole list of hosts literally into .rhosts > holsten gordon BTW, in my /etc/nsswitch.conf, it says: > netgroup: files nis What is wrong with it? How can I get get good-old hosts.equiv back to work again? It might have something to do with PAM. I don't understand PAM though, and I don't find anything about my topic in its documentation. Best Regards, Gordon.

1 0

Old question: what is SUSE going to do with harden_suse / Bastille
by Bo Jacobsen 25 Oct '03

25 Oct '03

I find it a little strange that SuSE apparently ignores the need for such an important tool as the old harden_suse or Bastille. I still use parts of the old harden_suse (from SuSE 7.3 !!!) just to close the most apparent problems. The standard SuSE installation is much to open. My problem is that I'm not capable enough to keep harden_suse up to date with all the changes of the new systems. Now we are on version 9.0, and SuSE has still not included any tools to replace the old harden_suse. At least they could had updated harden_suse just so it could run without any modifications. In SuSE 8.1 they had included bastille. What happened to that. It was gone in version 8.2, and in 9.0 it's still not there. Any ideas on what's going on Bo

1 0

SuSEfirewall2, two links and routing between them
by Fabiano Felix 24 Oct '03

24 Oct '03

Hi all, I'm having a problem using SuSEfirewall2. I have the following environment: - 01 Internet link with 2Mb (ADSL); - 01 Internet link with 256Kb (F. Relay); - 01 DMZ; - 01 LAN. The ADSL connection is used to Internet access. The FR is used to provide a Windows Media Server, and the WM Server is on the DMZ. Accessing this service from Internet I don't have any problems, but when I try to access it from LAN, I receive the following message: " SuSE-FW-ACCESS_DENIED_INT IN=eth2 OUT= MAC=00:06:4f:06:78:59:00:50:da:64:58:e2:08:00 SRC=192.168.0.58 DST=200. 300.400.500 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=18893 DF PROTO=TCP SPT=2368 DPT=1115 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (020405B401010402) " Searching into archives, I found that it is a (correct) firewall protection, but I need to solve this. I was wondering that is possible to correct this creating a custom rule. Can someone help me?? Regards, Fabiano Felix

2 1

Re: [suse-security] Solved (?): mysql_connect: Access denied
by Thomas Roth 24 Oct '03

24 Oct '03

Hi Steffen, I don't quite understand all you wrote. On Friday 24 October 2003 09:03, Steffen Dettmer wrote: > > 1) I found that the PHP-script was actually read: supplying > > some special characters instead of the said parameters to > > mysql_connect() resulted in a parse error at that line of the > > script. > > How could you manipulate your script to use special characters in > mysql_connect? By changing the sources? Yes, I wrote the script in the first place, why shouldn't I be able to put something like mysql_connect(@@@) into it? Doesn't make sense, of course, but produces a parse error which in turn tells me that I edited the right script and the right connect()-statement: the most primitive way of debugging your programs: put write()-statements whereever you think there might be problems ;-) >Of course you have to > make sure that this isn't possible by passing malformed data on > the external interfaces. I think there are conditions where > variables can be taken from the CGI environment somewhat > automatically. I think that is a big pitfall as you might find > yourself in using not-sanitized data from untrusted source > (browser). Well, I at least hope the said script is not directly accessible to the outside, short of cracking the system and the like... There is a html-form to put in data, processsing the data is done by some other script, checking these data, and so on. > > 2) However, sensible values seemed never to be used for the > > connection attempt. (PASSWORD: NO in the error message) > > You cannot process sensible values with PHP, except if you have a > dedicated (logical) server for each user - at least when using > mod_php instead of CGI mode. The reason is the mod_ stuff - > performant but insecure: every script runs in the same > environment as the same user. PHP may try to put some security > from top-level, but this cannot work well because of the > complexity. Oh, sorry, I did not mean something that sophisticated, but mysql_connect(@@@) = nonsense mysql_connect($host,$name,$pass) = sensible > > 3)The trick was to switch off the sql.safe_mode in php.ini. > > (And that is not connected to the setting of php safe_mode ) > > Yep, another drawback of mod_php is the global configuration :) > Again, if you have one script (-system), then it's no problem of > course. Why did you need to set sql.safe_mode off? What does this > mean exactly? I would expect that you want sql.safe_mode plus a > possibility to connect (however, this seems to be *really* > secure :-)). After having found that the problem was with sql.safe_mode, it was of course easy to google for it.There seems to be basically only one explication: http://www.n3rd.net/ZendInformationCenter/ZendServerCenter/sql_safe_mode.htm Synopsis: If the SQL Safe Mode option is enabled the MySQL and Ingres extensions will ignore the supplied host, user and password information and will use only the default ones. It's also nice to read: (if I only had done it some weeks ago ;-<) http://www.phpbuilder.com/mail/php-install/2001091/0131.php The php-manual hasn't improved since - maybe people where then distracted from reading that posting by something else... Greetings Thomas

1 0

Probleme mit yppasswd
by Gordon Cichon 24 Oct '03

24 Oct '03

Hallo, ich habe hier ein frisch installiertes Suse 8.2 (CD-Version) mit einem Nis (yp) Server am laufen. Leider funktioniert das ändern der Passwörter nicht. Ich bekomme folgende Fehlermeldung: > gordon@andechs:~> yppasswd gordon > yppasswd is deprecated, use /usr/bin/passwd instead > > Changing password for gordon. > Old Password: > New password: > Re-enter new password: > Changing NIS password for gordon on veltins.catnet.et.tu-dresden.de. > Error while changing the NIS password. > Error: Password NOT changed > passwd: Authentication token manipulation error (Übrigens, mit /usr/bin/passwd ist es das ganz das Gleiche) Im syslog bekomme ich: > Oct 23 16:06:59 veltins rpc.yppasswdd[514]: update gordon (uid=1704) > from host 192.168.43.129 rejected > Oct 23 16:06:59 veltins rpc.yppasswdd[514]: Invalid password. Bei meinem gleichkonfigurierten Nis-Server unter Suse 7.1 geht das einwandfrei. Was ist denn da los? Warum geht das nicht? Vielen Dank für Eure Hilfe im Voraus. Viele Grüße, Gordon.

3 3

Problem mit rsh Authentifizierung(PAM?) oder Suche Alternative
by Gordon Cichon 24 Oct '03

24 Oct '03

Hallo, hier an unserer Universität unterhalten wir ein heterogenes Subnetz, in dem wir vor allem die Synthese und Simulation unserer digitalen Halbleiterschaltungen vornehmen. Leider kommen wir mit einer einzigen OS-Version nicht hin, und wir haben hier ein buntes Mischmasch von Betriebssystemen und Versionen. Zusammengehalten wird alles mit einer Konbination aus nis/autofs/samba, deren Server z.Zt. von Suse 7.1 auf Suse 8.2 umgestellt werden soll (ich hoffe immer noch auf eine hilfreiche Antwort auf meine frühere Mail bzgl. yppasswd ;-)). Unser Subnetz ist nach außen stark abgeschirmt, bei uns ist es viel wichtiger, daß die unterschiedlichen Systeme eng gekoppelt sind. Aus diesem Grund benutzen wir hier das System rlogin/rsh. Ssh wäre zwar sicherer, aber die damit zusammenhängenge Verschlüsselung würde die Performance zu stark beeinträchtigen. Ich suche nach einem System, mit dem man sich ohne Passwort und ohne Overhead auf einem anderen System einloggen kann. Dazu erscheint mir der Eintrag einer nis-netgroup in /etc/hosts.equiv die bequemste Lösung. Obwohl die netgroup per nis verteilt wird, und in nsswitch.conf eingetragen ist, beachtet der Suse rsh Server die Eintragung nicht. Eine Eintragung von @netgroup in ~/.rhosts funktioniert auch nicht. Die normale .rhosts Authentifizierung mit hostname und username funktioniert hingegen schon. Kann das sein, daß das irgendwie mit PAM zusammenhängt? Suse 8.2 hat eine Konfigurationsdatei für /etc/pam.d/rsh, in der Dinge stehen, die zu komplex sind, als das ich sie verstehen würde. Wie sagt man PAM, es soll die Nis netgroups verstehen? Woran könnte es sonst liegen? Gibt es ein anderes System als rsh, das das gleiche leistet? Viele Grüße, Gordon.

1 0

mysql_connect: Access denied
by Thomas Roth 24 Oct '03

24 Oct '03

Hello list, I've got that problem with mysql + php. Both run under SuSE 8.2, (php 4.3.1 as Apache module, mysql vers. 11.18). I have tried to follow the instructions, giving 'root' a password, setting up a mysql-user with fewer privileges etc. I have set up a table in db 'test' and put in some data. Now, when I try to connect via a php-script, access is denied: mysql_connect() [function.mysql-connect]: Access denied for user: 'roth@localhost' (Using password: NO) The first strange thing is that the username supplied to mysql_connect() in the script is not 'roth' (although this username exists on the system). Then I was somewhat successful by not supplying anything to the mysql_connect() function - until I realized that by default, there is a mysql-user '@localhost' without a password. Giving a password to '@localhost' of course leads with the access denial as above. I also found that the message ' Using password: NO' appears if you say on the commandline: 'mysql -u user' If you instead put int the -p ('mysql -u user -p '), you will be asked for the password, as it should be. But how can you do that via the web/apache/php? The only advice I've found is exactly what I did: to put the relevant data into the php script and use them in mysql_connect(). Somewhere I read that in case of an empty mysql_connect(), the identity of the apache-user will be used as the default mysql-user. But apache is definitly not running as the user that appears in the complaint above. Checking php.ini, I see that php runs in safe_mode. Well, I'm somewhat confused and would appreciate your help Thomas

2 2

spammer removed
by Roman Drahtmueller 23 Oct '03

23 Oct '03

Hi, I have removed some @promotionfactory.net email address from our list - if you have seen any spam from them lately, it is because you have posted to suse-security(a)suse.com lately. Thanks, Roman. -- - - | Roman Drahtmüller <draht(a)suse.de> // Nail here | SUSE Linux AG - Security Phone: // for a new | Nürnberg, Germany +49-911-740530 // monitor! --> [x] | - -

1 0

Strength and weaknesses of different encryption algorithems?
by Emmerich Eggler 22 Oct '03

22 Oct '03

Hello I've seen that there are recommandations of key lengths for different usage (private, corporate, government). There are certainly also recommondation of encryption algorithmens for different usage. Can someone point me to a webpage that covers this kind of questions? TIA Emmerich

3 2

AW: [suse-security] mysql_connect: Access denied
by Junge, Stefan 22 Oct '03

22 Oct '03

Hi Thomas, which entries are in the mysql user table ? 1. Connect to your MySQL DB (Console) # mysql -> Does this work without any authentication ? 2. Select the mysql Database # \u mysql 3. Select another pager for a better view # pager 4. Lets have a look to your user table ... # SELECT * FROM USER; You should have an entry like this ... Host localhost, User "empty", Password "empty" and with appropriate privileges Is your user 'roth' listed here ? ONLY for testing !!! Create a user with full privileges to all ! mysql > grant all privileges on *.* to testuser@% identified by 'testpassword' with grant option; This command creates the user 'testuser' with the access privilege 'from everywhere' with the right to to bequest his rights. With this user should be able to connect to the database with your PHP Script. Don´t forget to remove the user 'testuser' with his privileges ! Note: MySQL has its own user system - independent from the system users. Maybe this is a first step... Good luck Stefan > -----Ursprüngliche Nachricht----- > Von: Thomas Roth [mailto:thomas.roth@physik.tu-darmstadt.de] > Gesendet: Dienstag, 21. Oktober 2003 20:33 > An: suse-security > Betreff: [suse-security] mysql_connect: Access denied > > > > Hello list, > > I've got that problem with mysql + php. Both run under SuSE > 8.2, (php 4.3.1 as > Apache module, mysql vers. 11.18). > I have tried to follow the instructions, giving 'root' a > password, setting up > a mysql-user with fewer privileges etc. I have set up a table > in db 'test' > and put in some data. Now, when I try to connect via a > php-script, access is > denied: > > mysql_connect() [function.mysql-connect]: Access denied for user: > 'roth@localhost' (Using password: NO) > > The first strange thing is that the username supplied to > mysql_connect() in > the script is not 'roth' (although this username exists on > the system). > > Then I was somewhat successful by not supplying anything to the > mysql_connect() function - until I realized that by default, > there is a > mysql-user '@localhost' without a password. Giving a password > to '@localhost' > of course leads with the access denial as above. > > I also found that the message ' Using password: NO' appears > if you say on > the commandline: 'mysql -u user' > If you instead put int the -p ('mysql -u user -p '), you > will be asked for > the password, as it should be. > But how can you do that via the web/apache/php? The only > advice I've found is > exactly what I did: to put the relevant data into the php > script and use them > in mysql_connect(). > > Somewhere I read that in case of an empty mysql_connect(), > the identity of the > apache-user will be used as the default mysql-user. But > apache is definitly > not running as the user that appears in the complaint above. > > Checking php.ini, I see that php runs in safe_mode. > > Well, I'm somewhat confused and would appreciate your help > > Thomas > > > -- > 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 >

1 0

ipsec freeswan - connection established successfully, but packets are dropped ...
by Markus Feilner 20 Oct '03

20 Oct '03

Hello List, I am using SuSE 8.2 on two systems, together with freeswan ipsec. Both systems run: kernel 2.4.20-4GB freeswan 1.99_0.9.23 I have configured freeswan successfully with a Server-and-roadwarrior setup using Certs. By successfully I mean: in /var/log/messages I find a line like --------- Oct 16 21:54:26 Server ipsec__plutorun: 004 "VPN-ERMER" #2: STATE_QUICK_I2: sent QI2, IPsec SA established --------- or similar after starting ipsec on both systems and there are definitely no errors on both servers. On the server side we have the subnet x.x.89.0 to be accessible, on the roadwarrior side (which is connected via dsl) we have the x.x.0.0 subnet connected. My Problem: When i try to ping from one subnet to the other (of course from a different member of the subnet, not the machine running ipsec), the packets are routed correctly to the ipsec device, but there they vanish: ---------------------------- Server:/ # tcpdump -i ipsec0 tcpdump: listening on ipsec0 22:25:17.996878 217.229.160.84 > x.x.89.0: icmp: echo request (DF) 22:25:18.996902 217.229.160.84 > x.x.89.0: icmp: echo request (DF) 22:25:19.996909 217.229.160.84 > x.x.89.0: icmp: echo request (DF) (...) no answer is given to the ping and on the other side of the tunnel, nothing arrives - this happens to every packet that is sent to the tunnel, no matter which port, protocol and destination. As far as i can see, the packets are dropped, before they are given to ppp0: ----------------------------- Server:/ # ifconfig ipsec0 ipsec0 Link encap:IPIP Tunnel HWaddr inet addr:217.229.160.84 Mask:255.255.255.255 UP RUNNING NOARP MTU:16260 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:2002 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) ---------------------------- I stopped all Firewall rules, and checked the ipsec configuration over and over, but i can't find a solution. Can anyone help me? If you need, I can post both my ipsec.conf files and barfs, but i didn't want to cause big traffic. Perhaps someone already knows the solution.... Thanks!! -- Mit freundlichen Grüßen Markus Feilner -- Linux Solutions, Training, Seminare und Workshops - auch Inhouse Feilner IT Linux & GIS Erlangerstr. 2 93059 Regensburg fon: +49 941 70 65 23 - mobil: +49 170 302 709 2 web: http://feilner-it.net mail: mfeilner(a)feilner-it.net

7 13

SuSEfirewall 2 configuration - computer name problem
by Andrei Bintintan 18 Oct '03

18 Oct '03

Hi I saw there was a little discuttion about suse firewall and samba, but I have another problem here. First of all I'm new in linux, so sorry if I ask stupid things... everyone has to learn right? I have a server in LAN which is web, mail, db server. Samba is also installed. Everything worked fine, but when I activate suse firewall I cannot see the computer name anymore. I have access with samba, I can ping the server but only with the IP address of the server, not with the name. Shortly the server name is not recognized anymore. I waste a lot of time with this... and I couldn't find the problem. The strange part is that I installed the same configuration under vmware and it works fine. I activated port 53 (domain name) but still doesn't work. Please advise. Thanx in advance. Andy.

2 1

fou4s - Fast OnlineUpdate for SuSE 0.10.0
by Markus Gaugusch 14 Oct '03

14 Oct '03

Hi, I'm happy to announce the final release of fou4s 0.10.0. For those who do not know, this software is meant to be an alternative for YOU (YaST OnlineUpdate), especially designed for administrators that need to keep many machines up-to-date in a convenient way. But I also use it on my desktop machines, so you may do so as well ;-) Since the last version many things have changed (hopefully, they have become better :) * SuSE 9.0 support * 2-level caching for even faster updates * Bandwidth limiting for downloads [--limit] * Check remote hosts for needed updates, even if fou4s is not installed there (you just need to be able to read the RPM database) [--host] * More support for foreign updates (packman, ...; hint: use --end!) * Files that are fully retrieved are no longer tried to be resumed * The language of the update descriptions can be chosen [--language] * New output formatting and summary Because of internal changes, the GpdList option should no longer be used. Just add your rsync servers to the Server= list (blank separated or add another Server= line) and run fou4s -u, etc as if it were a normal server. If you are updating to SuSE 9.0, please do a fou4s update FIRST, because the old version is not compatible. If you have already upgraded, run fou4s --auto --checkf -g, to install the new fou4s without signature checking (or just install the new fou4s version with rpm -Uvh ...). As usual, the software can be downloaded from http://fou4s.gaugusch.at/. Previous fou4s users are notified automatically, if the checkfou4s option is set in the cronjob. have a lot of fun ... Markus PS: For everyone who has not seen Terminator III: Machines will take over the world, if we don't keep our computers protected! -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(a)gaugusch.at X Against HTML Mail / \

1 0

test plz ignore
by Arjen Runsink 13 Oct '03

13 Oct '03

ignore

1 0

Re: [suse-security] Problem: permission bits changed on files automatically (SOLVED)
by David C. Grosvold 10 Oct '03

10 Oct '03

Stefan: On Monday 06 October 2003 07:17 am, Stefan Seyfried wrote: > On Fri, Oct 03, 2003 at 10:38:41AM -0500, David C. Grosvold wrote: > > Nope - that's not it, but your comment led me down a new path. Now that > > you mention it, it happens after the On-Line update when SuSEConfig runs. > > > > Guess what? I just had to change the setting of CHECK_PERMISSIONS in > > /etc/ sysconfig/security to "warn" rather than "set" and the problem is > > solved! > > but anyway, SuSEconfig should not do anything in a $HOME. What user are we > talking about? root or a mere mortal? The only thing which would explain > this (to me) is some weird bind-mount or symbolic link into a home, but > this is pure speculation. > > regards, > > Stefan What an interesting thought! We're talking about a mere mortal. I thought I had this solved until earlier today. I updated something in YaST, and once again, the permission bits on all the executables in my normal user's home directory and below were changed from 775 to 675. As far back as SuSE 7.3 I've maintained a symbolic link to /srv/www/htdocs in my "mere mortal" home directory for convenience during web development. To test, I removed the symbolic link, and reran SuSEconfig. The permission bits were NOT changed after removing the link. You might be on to something... Hmmmmm. -- --------------------------------------------------- Dave Grosvold dave(a)rcanyon.com ---------------------------------------------------

1 0

Apache Proxy Acces
by Jan Rüdiger 10 Oct '03

10 Oct '03

Hello I detected a lot of messages like this in my http-access.log 38.117.18.175 - - [01/Oct/2003:00:20:33 +0200] "QUIT" 302 - 38.117.18.177 - - [01/Oct/2003:00:20:40 +0200] "QUIT" 302 - 38.117.18.178 - - [01/Oct/2003:00:20:48 +0200] "POST http://134.155.65.115:25/ HTTP/1.1" 302 318 The Apache is beside a http server also a proxy for a local service running on port 20000. The Access to the Proxy is restricted by: <Directory proxy:*> Order deny,allow Deny from all Allow from 10.0.0. </Directory> Should i be aweare, because 302 means somehting like service temporary unavailable, but there where 318 bytes of data transmited? thanks four your help jan

1 0

Solved ! RE: [suse-security] SuSe Firewall 2 - FW_HTB_TUNE_DEV ???
by Cees Tool 10 Oct '03

10 Oct '03

Hi, > Oh I see you are using SuSEfirewall2 from SuSE 8.1 No, I have Suse 8.2, but I have done updates via Yast Online Update, maybe that goes wrong ?? I have seen more references to Suse 8.1 during upgrading. I will try to find-out what's going wrong with that.... Update after some tests: I have investigated data with "Ethereal", the online-update of Suse 8.2 gets it's updates from pub/suse/i386/update/8.1/.... So the update program was getting the wrong updates (8.1 instead of 8.2) all the time. This is probably also the answer of other minor problems with updating. Now the next thing is to find an updated version of "YOU" (yast online update), and I have to do this manually as the update-program can never find this..... (Probably I am not the only one with this problem ;) > I recomend you to download > SuSEfirewall2-3.1.95.noarch.rpm > from: > ftp.suse.com/pub/suse/i386/update/8.2/rpm/noarch/SuSEfirewall2-3.1- > 95.noarch.rpm [Cees Tool] I have done this, and indeed now the "FW-HTB*" references are in the Susefirewall2 script and it seems to work now ! Thanks all, for the information. Problem (almost) solved. Now I have to see if there is a solution for the wrong directory in yast online update.... Regards, Cees

4 7

RE: [suse-security] Problems with SuSEFirewall
by Sturgis, Grant 09 Oct '03

09 Oct '03

One solution is to have split DNS. The inside DNS points www to the inside address (i.e. 192.168.x.x) while the outside (public) DNS points to the public IP address. -GS -----Original Message----- From: Andrés Tarallo [mailto:atarallo@acm.org] Sent: Thursday, October 09, 2003 10:55 AM To: suse-security(a)suse.com Subject: [suse-security] Problems with SuSEFirewall Hi !!! I have a problem with a firewall I've configured with SuSEFirewall2 and SuSE Linux 8.2. My firewall has a public IP address, and a private IP for a LAN. In the LAN I have a WWW server and a email server. People who want to check their mail from the Internet just connect to the public IP in the firewall and I have set there rules to redirect the trafic to the mail server and WWW server in the LAN. This works fine, also the people in the lan browse the internet via a transparent proxy. My problem starts because the people on the private LAN want's to access the WWW server from the lan, in the same manner they do from the Internet. When they point their browser to http://www.company.com they get a error message from squid that says that the conection was refused. If i ping the WWW server from the LAN by it's name i get no answer. This problems is driving me mad, I don't know what to do. Thanks in advance for your advice. Andrés 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.

3 2

root has no shell
by Ulrich Kautz 09 Oct '03

09 Oct '03

Hello All, Ive got a big Problem. I changed the root shell to /bin/false. There is neither a user in the sudoers nor is there any other root-user or even a user in the root group. Is it possible to switch back the shell to /bin/bash or sh or something? Ive tried: sudo -- not in sudoers su -s /bin/bash -c "command" -- "using restricted shell: /bin/false" thanks in advance, Ulrich

19 27

Problems with SuSEFirewall
by Andrés Tarallo 09 Oct '03

09 Oct '03

Hi !!! I have a problem with a firewall I've configured with SuSEFirewall2 and SuSE Linux 8.2. My firewall has a public IP address, and a private IP for a LAN. In the LAN I have a WWW server and a email server. People who want to check their mail from the Internet just connect to the public IP in the firewall and I have set there rules to redirect the trafic to the mail server and WWW server in the LAN. This works fine, also the people in the lan browse the internet via a transparent proxy. My problem starts because the people on the private LAN want's to access the WWW server from the lan, in the same manner they do from the Internet. When they point their browser to http://www.company.com they get a error message from squid that says that the conection was refused. If i ping the WWW server from the LAN by it's name i get no answer. This problems is driving me mad, I don't know what to do. Thanks in advance for your advice. Andrés

1 0

AW: [suse-security] root has no shell
by Ulrich Roth 08 Oct '03

08 Oct '03

Hi Ulrich, > Ive got a big Problem. I changed the root shell to /bin/false. ROTFL! ;-) Okay, boot the machine using the SuSE CDs. Mount the appropriate partition and edit the passwd file. Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth at impact dot de

1 0

Secure dynDNS-Update with Router
by Andreas Thierer 07 Oct '03

07 Oct '03

Hi, i want to update my SuSE 8.2 / BIND 9.2 DNS-Server dynamically with TSIG-Keys. Is this possible, if the Client is behind a router? The Netgear RP314 ADSL-Router, as an example, has a builtin DynDNS-Client which happens to work only with dyndns.org (they don't use TSIG-Keys for authorisation). Exist any routers which are able to handle custom dynDNS-servers with TSIG-Keys? Best regards and thanks for any help Andy

2 1

RE: [suse-security] SuSe Firewall 2 - FW_HTB_TUNE_DEV ???
by Cees Tool 07 Oct '03

07 Oct '03

>From: Stefan Seyfried > > On Tue, Oct 07, 2003 at 11:18:57AM +0200, Cees Tool wrote: > > > Do you know if I can check somewhere if the SuseFirewall2 script does > > anything with the "FW_HTB_TUNE_DEV" variable ? > > just read /sbin/SuSEfirewall2, its all in there ;-) > That is the file I have examined too ;) But unfortunately there is no reference to "FW_HTB*" in there. I have searched this file. So probably it does nothing with the "FW_HTB_TUNE_DEV" setting. That's why I asked if I need to install any other thing to have this working.. Regards, Cees

3 3

SuSe Firewall 2 - FW_HTB_TUNE_DEV ???
by Cees Tool 07 Oct '03

07 Oct '03

Hello, I am using Suse 8.2 (kernel 2.4.20) and SuSe Firewall 2. I want to shape my upstream speed and tried to enter : FW_HTB_TUNE_DEV="eth0,125" But I do not see any change in upstream speed, even if I try to enter "eth0,10", my upstream speed remains the same (128 Kbps). From the help-text in sysconfig I understand that this parameter should do the trick, but maybe more has to be set. I cannot find more information. - Do I need to load any module for this ? (Which?) - Do I need to configure anything else to have this parameter work ? - Any other hints ? Regards, Cees

2 2

EXPLOIT?!?!
by Radu Voicu 06 Oct '03

06 Oct '03

"Affected: SuSE Linux 8.2Pro Not affected: SuSE Linux 7.3Pro, non-SuSE distributions Possibly affected: other SuSE distributions Vulnerable package: susewm Impact: Local user can gain root privileges Exploit type: Symlink attack Release date: October 6th 2003 Vendor status: SuSE was contacted on September 4th (> 1 month ago). No SuSE-patch yet. A symlink vulnerability exists in the shell script /sbin/conf.d/SuSEconfig.susewm, line 86. This shell script is part of the "susewm" package. This package is required by the package "kdebase3", so if KDE3 is installed on your system(s), you should be vulnerable." ...please read the link I provided for further details http://amor.rz.hu-berlin.de/~nordhaus/sec/vul/1_index.html

2 1

AW: [suse-security] Re: SSH and Apache warnings Nessus
by Hollweg, Daniel 06 Oct '03

06 Oct '03

> -----Ursprungliche Nachricht----- > Von: Stefan Andreas Tichy [mailto:listuser@pi4tel.de] > Gesendet: Montag, 6. Oktober 2003 14:42 > An: suse-security(a)suse.com > Betreff: [suse-security] Re: SSH and Apache warnings Nessus > > > On Mon, Oct 06, 2003 at 08:09:37AM +0100, Hollweg, Daniel wrote: > > I have two problems with a new installed SuSe Linux > Professional 8.2. > > All current patches are applied. Wehn I am scanning the box > with the > > nessus I get the following warnings: > > > > - You are running a version of OpenSSH which is older than 3.7.1 > > > > - You are running OpenSSH-portable 3.6.1p1 or older. > > If possible SuSE applies fixes to software versions > originally delivered > with some SuSE distribution. Therefore upgrading to the newest > versions is not neccessary. > > > > Is this O.K. and just an Nessus Problem with the SuSe version of > > SSH? > > Yes > > > > - The remote HTTP server allows an attacker to read > arbitrary files > > on the remote web server, simply by adding a slash in > front of its name. > > Example: GET //etc/passwd will return /etc/passwd. > > There has been a vulnerability in mod_rewrite, but it should be no > problem using apache installed with SuSE 8.2. > http://www.apacheweek.com/issues/00-09-22 > > > I already installed the newest SuSe Apache 1.3 package. > Where is the problem? > > Amazing is that the GET request does not return the whole > passwd but only two > > lines. > > Is this just some nessus information or did you reproduce the > problem? I tested it and it returns two lines of my /etc/passwd. Other files like /etc/inittab result in a Error 403. Here is a sample output: root:*:0:0::/:/etc/ftponly foo:x:502:503::/home/foo/public_html/./:/bin/false Regards, Daniel

2 1

passwd on website
by Dominik Składanowski 06 Oct '03

06 Oct '03

Hello list. I need to have change system password through website. I tried chpasswd (https://chpasswd.sourceforge.net/) but on SuSE 8.2 Pro I can't pass compilation. Besides it is rather old soft... Anybody knows other possibility to do that? -- ++++++++++++++++++++++++++++++++++++++++++ Dominik Skladanowski e-mail: dominik.skladanowski(a)ch.pw.edu.pl ++++++++++++++++++++++++++++++++++++++++++

7 7

SSH and Apache warnings Nessus
by Hollweg, Daniel 06 Oct '03

06 Oct '03

Hi List! I have two problems with a new installed SuSe Linux Professional 8.2. All current patches are applied. Wehn I am scanning the box with the nessus I get the following warnings: - You are running a version of OpenSSH which is older than 3.7.1 - You are running OpenSSH-portable 3.6.1p1 or older. As I wrote before I installed the latest SSH Version from SuSe. Is this O.K. and just an Nessus Problem with the SuSe version of SSH? - The remote HTTP server allows an attacker to read arbitrary files on the remote web server, simply by adding a slash in front of its name. Example: GET //etc/passwd will return /etc/passwd. I already installed the newest SuSe Apache 1.3 package. Where is the problem? Amazing is that the GET request does not return the whole passwd but only two lines. Any suggestions? Thanks, Daniel

3 2

Problem: permission bits changed on files automatically
by David C. Grosvold 06 Oct '03

06 Oct '03

Anybody have any experience with this? On an intermittent basis, all of the files in my home directory with mode 0775 are changed to mode 0675 without my knowledge. I've checked the cron jobs for root to see if anything looks out of place, but nothing shows up. I'm running SuSE 8.2, with everything up to date, but this has been happening since version 7.3, it's just now become so frequent that I've decided I have to resolve it. I usually discover the problem when shell scripts or Perl scripts suddenly stop working when I call them from either the command line or cron. My SuSE system is on DSL, with a D-Link 604 DSL router, an internal network with Windoze 2000 (two laptops and a desktop) and an old SCO Unix 5.0 box. I have Samba 2.2.7a running to allow the Windoze boxes to use the SuSE box as a file exchange point, McAfee virusscan is installed on all Windoze boxes. I do cross-platform database development using Linux, Windoze, and Unix, but my primary box and my desktop are Linux. Windoze is there solely for development purposes. I've been a Unix/Linux system administrator for 15 years - my firs Unix box was a Unisys Tower (re-badged NCR Tower) with a Motorola 68020 processor and NCR Tower Unix (AT&T SystemV release 2.5). Things have come a mightly klong way since then. At any rate, if anyone can shed any light on this, it would be appreciated. -- --------------------------------------------------- Dave Grosvold dave(a)rcanyon.com ---------------------------------------------------

3 3

AW: [suse-security] Mail missplaced or lost
by Ulrich Roth 06 Oct '03

06 Oct '03

Hi David, > I have a system running SuSE 7.3 with all updates, and I noticed that > > the old mail (readed) was moving to the Trash folder or there was > another new folder instead with the old mail. I don't know when the > problem started but it is happening on multiple accounts, if > not in all. Did you ask your users if they did anything they didn't do before? Do they use a new mail program? Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth at impact dot de

1 0

Help seeting SuSEfirewall2
by Rafael E. Herrera 05 Oct '03

05 Oct '03

Hello, I would like to be able to have a machine with that allows remote connections through SSH. It should also accept traffic through 15 UDP ports. The SSH and 15 UPD ports traffic should be limited to two subnets: in the example below, they are 12.203.150.0/24 and 12.203.162.0/26. All other traffic should be rejected. The machine will not act as a router, I just want to use SuSEfirewall2 as a personal firewall. I only has one network card. Will the configuration file below satisfy the requirements I've stated? I suspect I'm allowing anybody to connect suing ssh by setting FW_SERVICES_EXT_TCP, is that correct? I'd appreciate any suggestion. Rafael -------------------------- FW_QUICKMODE="no" FW_DEV_EXT="eth0" FW_DEV_INT="" FW_DEV_DMZ="" FW_ROUTE="no" FW_MASQUERADE="no" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="ssh" FW_SERVICES_EXT_UDP="40001:40015" FW_SERVICES_EXT_IP="" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_SERVICES_QUICK_TCP="" FW_SERVICES_QUICK_UDP="" FW_SERVICES_QUICK_IP="" FW_TRUSTED_NETS="12.203.150.0/24 12.203.162.0/26" FW_ALLOW_INCOMING_HIGHPORTS_TCP="no" 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="" # Beware to use this! FW_FORWARD_MASQ="" # Beware to use this! FW_REDIRECT="" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="yes" 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="yes" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="no" FW_ALLOW_PING_EXT="no" FW_ALLOW_FW_TRACEROUTE="yes" FW_ALLOW_FW_SOURCEQUENCH="yes" FW_ALLOW_FW_BROADCAST="no" FW_IGNORE_FW_BROADCAST="yes" FW_ALLOW_CLASS_ROUTING="no" FW_CUSTOMRULES="" FW_REJECT="no" FW_HTB_TUNE_DEV=""

2 2

SuSE honeyd rpm's
by Thomas Jones 05 Oct '03

05 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I've taken the liberty of building the RPM's for honeyd 0.6a. I did a quick search on google and didn't find any available. So let me know if there is already one(or all) available. The pre-compiled 0.5 is nice; but i prefer to have everything in it's rightful place. It's getting late ---- so i may have fragged a path or something ----- would someone with a clean system be willing to do a install to check it out for me? These are not CVS pulls, so they should be stable. http://www.linux-howtos.com/releases/honeyd-0.6a-1.i386.rpm http://www.linux-howtos.com/releases/libdnet-1.7-1.i386.rpm http://www.linux-howtos.com/releases/libevent-0.7a-1.i386.rpm Let me know how they work. Thanks for your time. - -- Thomas Jones Linux-Howtos Network Administrator OpenGPG Key: 0x6A3DF6E9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/f+W+QT2komo99ukRAq9YAJwLqIDC1TVC/M21jAbVAHOw5TnaCgCeKrpg yY48xiX3TTTf6Ra/JeLImS0= =L//K -----END PGP SIGNATURE-----

1 0

Secure Mail Server
by João Reis 04 Oct '03

04 Oct '03

Hi to all. I would like to implement a secure Mail server. This is an internal mail server and belongs to the network behind the external firewall. I also would like to have a system which permits external users to connect to the internal mail server in order to fetch their internal mail or to send their mail througth this server (POP with SSL and SMTP). The only way i see to have external connection is to add a rule to my firewall teling it to redirect all POP and SMTP traffic to this internal server. Is there a more secure way to do this? Is it secure to implement this scheme? I think this way my internal mail is exposed to the world, but i don't see other solution to do what i pretend.... Any suggestion ? Thanks in advance, P.S : sorry about my english João Reis ==========================================================

4 3

AW: [suse-security] explicitly allow fragmented packets in ipsec environment - unset the DF bit
by mailinglists 03 Oct '03

03 Oct '03

Hi > > I can send 15 Kbyte (I haven't tried larger packets yet but > I'm sure they > > will go through the tunnel as well) pings to the other end > of an ipsec > > (freeswan-freeswan) tunnel. Checking my fragmented packets > the DF bit is > > not set. The other end of the tunnel, however, can "only" > send 1500 Byte > > pings to me. Those packets have the DF bit set. > The following is taken from > /usr/src/linux/Documentation/Configure.help: > > > TCPMSS target support > CONFIG_IP_NF_TARGET_TCPMSS > This option adds a `TCPMSS' target, which allows you to alter the > MSS value of TCP SYN packets, to control the maximum size for that > connection (usually limiting it to your outgoing interface's MTU > minus 40). > > This is used to overcome criminally braindead ISPs or servers which > block ICMP Fragmentation Needed packets. The symptoms of this > problem are that everything works fine from your Linux > firewall/router, but machines behind it can never exchange large > packets > [...] > > > This sounds quite a bit like your problem. One of your > systems seems to be > unable to send fragmented packets. And as 1500 bytes is > probably your MTU, > the host that cannot send fragmented packets cannot send > packets larger than > 1500 bytes. Maybe this is simply because you yourself are > blocking the "ICMP > Fragmentation Needed packets", so check your firewall > rules/logs. Don't need to. ICMP 3 allowed everywhere. > If that > doesn't help, maybe this kernel option will. I'll try. Thanks Philipp

1 0

explicitly allow fragmented packets in ipsec environment - unset the DF bit
by mailinglists 03 Oct '03

03 Oct '03

Hi I've stumbled over something that appears to be a bit strange to me. I can send 15 Kbyte (I haven't tried larger packets yet but I'm sure they will go through the tunnel as well) pings to the other end of an ipsec (freeswan-freeswan) tunnel. Checking my fragmented packets the DF bit is not set. The other end of the tunnel, however, can "only" send 1500 Byte pings to me. Those packets have the DF bit set. I wonder how it is possible to unset the DF bit in an IP implementation. Or is there a difference between the various linux distributions? My ipsec box is a redhat while the firewall box right behind it is a SuSE box. I also checked the /proc filesystem for an option to disable the DF bit, but could not find anything. Thanks for any suggestions, Philipp

2 1

Mail missplaced or lost
by David Soltero-Lugo 03 Oct '03

03 Oct '03

I have a system running SuSE 7.3 with all updates, and I noticed that the old mail (readed) was moving to the Trash folder or there was another new folder instead with the old mail. I don't know when the problem started but it is happening on multiple accounts, if not in all. I am using imapd and sendmail? is someone else seen something like this? thanks David

1 0

Re: [suse-security] Solved: How to apply IPSec NAT-Traversal Patch to SuSE8.2-Kernel ?
by J J 02 Oct '03

02 Oct '03

Apologies to Andreas and Elmar, evidently I didn't read Andreas' posting properly before I replied! :) Obviously avoiding recompiling your kernel will make life far simpler for you and it sounds like you don't need to recompile to get NAT-traversal running. The only reasons I can see that you might are (i) to enable the possibility of debugging with ipsec klipsdebug --all and (ii) for intellectual satisfaction/training/certainty! If you did want to pursue recompiling the kernel... Given that reiserfs.o is being built, my suggestions about configuration aren't applicable anymore! I have seen the effect you describe before: where an unchanged configuration still shows a change in .config - it seems to be harmless. Things like new comments, or sections that don't do anything (because an option is not switched on higher up) but are still being written. It's not too surprising if you look at how each file gets written. zcat /proc/config.gz is effectively an output from the kernel itself of saved config information so will be minimal. make xconfig is a complex tcl/tk script. If you want to progress this any further then we will probably need the exact error message, word for word, letter for letter that you're getting in the boot process with the new kernel, and exactly at what point in the boot process it occurs, what message lines do you see just before it. Does it occur absolutely immediately (like when the kernel starts) or a bit later, during the startup scripts? My guess is that it's pretty early. If you are going to abandon the new kernel build then that's cool and I wish you luck with freeswan - it's a first-rate product but can be tricky without kernel debug IMHO! All the best, Carl >From: Elmar Marschke <elmar.marschke(a)epost.de> >To: suse-security(a)suse.com >CC: AThierer(a)ctl.de, c_peto(a)hotmail.com >Subject: [suse-security] Solved: How to apply IPSec NAT-Traversal Patch to >SuSE8.2-Kernel ? >Date: Thu, 02 Oct 2003 16:41:06 +0200 > >Hi, >special thanks to Andreas and Carl (JJ), due to your hints i solved my >problem. Though i don't have a patched *and* running kernel yet, i >achieved my goal to connect several Private-IP-Subnets through my VPN. >Here's a short summary: > >@Andreas: >Andreas Thierer wrote: > > I also needed NAT-Traversal with FreeSWAN. > > First i wanted to apply the NAT-Traversal-Patch, like you, > > but then i saw, that the X.509-Patch has also an NAT-Traversal- > > functionality. This X.509-Patch is applied to the FreeSWAN- > > paket shipped with SuSE 8.2. >Yes, you're right. I just couldn't believe that it's so simple :-). >Obviously it's not necessary to apply the kernel patch... > > > See >http://www.freeswan.ca/patches/www.strongsec.com/freeswan/install.htm#secti… >..this brought the solution. >Perhaps one will have trouble when trying to connect several Networks that >incidentally use the same private IP-Range, but right now this is not the >case in my setup. > >@Carl: >J J wrote: > > Is your new kernel missing reiserfs.o in the /lib/modules/<kernel > > version>/kernel/fs/reiserfs/ directory? >no, it's existing there. > > > If not then you have probably got a faulty config. >Yes, now i suppose that's the reason, too. Unfortunately i can't imagine >why... Just as you described I did a zcat /proc/config.gz > .config and >then a make xconfig after i patched the kernel. But unfortunately what you >describe in the following lines... > > > You've already patched the kernel so future compiles will give you all > > the Ipsec options that you need. > > Then you should have a configuration > > that's identical to your working configuration but with any changes you > > choose to make. The obvious changes are to switch on Ipsec, the NAT > > traversal and X509 patches... >was not the case, there were no options for ipsec available, before i did >that "strange" makefile targets in .../kernel_modules/zz_freeswan. Is it >possible that patching went wrong although Ret.Code was 0 ? > > > If the build process did make reiserfs.o but you're still getting a > > kernel panic then the problem is probably in the initrd. >I don't think so. I studied mkinitrd -h, think that i did it all correctly >and the same procedure is successful at other occasions. > >Anyway, in further inquiries i found some hints that Kernel-Parameter >CONFIG_REISERFS_FS_POSIX_ACL could be concerned to my problem. In my >xconfig this is displayed black, not grey, but anyway it's not possible to >change it. Another thing that made me wonder: zcat /proc/config.gz > >.config; make xconfig -> save *without any changings* into file .config2 >and quit; then a >diff .config .config2 shows a lot of differences. Does anybody know why >this is so? >Apart from this many thanks to all contributors...:-) >Kind regards >Elmar > > >-- >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 > _________________________________________________________________ On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile

1 0

[suse-security] unsubscription
by Mitica 02 Oct '03

02 Oct '03

---------- Forwarded Message ---------- Subject: [suse-security] unsubscription Date: Mon, 25 Aug 2003 15:36:06 +0300 From: Catalin Nitipir <catalinn(a)breezecom.ro> To: suse-security(a)suse.com > unsubscription -- 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 ------------------------------------------------------- Xnet scaneaza automat toate mesajele impotriva virusilor folosind RAV AntiVirus. Xnet automatically scans all messages for viruses using RAV AntiVirus. Nota: RAV AntiVirus poate sa nu detecteze toti virusii noi sau toate variantele lor. Va rugam sa luati in considerare ca exista un risc de fiecare data cand deschideti fisiere atasate si ca MobiFon nu este responsabila pentru nici un prejudiciu cauzat de virusi. Disclaimer: RAV AntiVirus may not be able to detect all new viruses and variants. Please be aware that there is a risk involved whenever opening e-mail attachments to your computer and that MobiFon is not responsible for any damages caused by viruses. -------------------------------------------------------

1 0

How to apply IPSec NAT-Traversal Patch to SuSE8.2-Kernel ?
by Elmar Marschke 02 Oct '03

02 Oct '03

Hi all, i installed a VPN with a SuSE8.2 2.4.20-4GB kernel and a freeswan_1.99_0.9.23-20 as provided by the 8.2 distribution. Everything including x509-Support is tested and working fine. Now i want to add NAT-Traversal functionality. As written in /u/s/d/p/freeswan/README.SuSE the NAT-Traversal Patches (written by Mathieu Lafon) for the *freeswan-package* are already inserted in the package provided by SuSE. But to get it running one has also to patch the *kernel* with the fswan-nat-t-kernel.diff, they write, and which is provided in the same directory. I applied the patch to my kernel-sources (Return Code=0) and recompiled the kernel: - make oldconfig (perhaps wrong?? don't know what this exactly is doing..) -i took a look in make xconfig and noticed that there were no possibilities to do configuration for IPSec, but at that moment i did'nt care - changed the Makefile's Extraversion Number.. - make dep - make clean - make bzImage - make modules - make modules_install I prepared my bootloader and did mkinitrd for that kernel. Booting with that kernel was ok, but ipsec did'nt start anymore: "ipsec_setup:modprobe: can't locate module ipsec. Kernel appears to lack KLIPS." I booted my old kernel again and according to some mails of this list i took a look into .../kernel_modules/zz_freeswan/Makefile and tried: in that directory: - make insert Result: make xconfig in /usr/src/linux did'nt work anymore. - make kmodule Result: make xconfig didn't work yet. - make klink Result: make xconfig worked again! And it had configuration-options for IPSec!! I configured this -i took all the defaults i found there, the only thing i changed was the IPSec-Stuff- and compiled another kernel exactly as described above (except that i used xconfig instead oldconfig). Every step gave a Return Code of 0. Result when booting this new kernel: "Kernel panic: unresolved symbol reiserfs.o" (which is my boot partition). Question: can anyone give me a hint about the correct way to apply this patch and get a working kernel? *Which* make -steps / targets do i have to take in .../zz_freeswan/ (e.g. what about oldmod?) and perhaps in /usr/src/linux, and **in which order**? Any help would be greatly appreciated.. thnxalot! Kind regards Elmar

1 1

Alternative to openssl/openssh
by Philippe Vogel 02 Oct '03

02 Oct '03

Hello List! Are there any secure alternatives to openssl/openssh? It is no fun to patch these stuff almost every day or week or better said the last time too often! Why then secure communication, if there is too much insecurity in it? Maybe this leads back to telnet! Philippe

3 2

SuSE 7.3
by Philippe Vogel 02 Oct '03

02 Oct '03

Hello! At what date SuSE 7.3 will be discontinued? I want to decide, if I do an upgrade on an old system. Philippe

6 7

Re: [suse-security] SuSE 7.3
by m3047＠inwa.net 02 Oct '03

02 Oct '03

At 1:28 AM 10/2/03, Mathias Homann wrote: >Am Donnerstag, 2. Oktober 2003 01:20 schrieb Roman Drahtmueller: >> (someone) wrote: >> > At what date SuSE 7.3 will be discontinued? >> > I want to decide, if I do an upgrade on an old system. >> >> We're looking at mid November this year for the end of 7.3. > > >With all updates installed, would it be 'safe' to keep a 7.3 box running, or >should it be upgraded? I've still got a SuSE 6.4 box running and on the 'net. Really, it depends on what you use it for, and what you're willing to turn off, firewall, or manually patch. Things get zen after a while.. or else you get hacked I guess. (And I just bought a copy of 8.2. But, that's still too patchy for me to want to "open it up to the world".) -- Fred Morris m3047(a)inwa.net

1 0

Discontinued SuSE Linux Distributions
by Roman Drahtmueller 01 Oct '03

01 Oct '03

I'm also forwarding this to suse-security@, since this is what we do with announcements, too. Thanks, Roman. -----BEGIN PGP SIGNED MESSAGE----- Dear suse-security-announce subscribers and SUSE LINUX users, having provided security-relevant fixes for version 7.2 of our home user product, SuSE Linux, for two years, we would like to inform you that as of today, security fixes for SuSE Linux 7.2 will be discontinued for all architectures. Vulnerabilities found after Oct 1st 2003 will not be fixed any more for SuSE Linux 7.2. By consequence, the SuSE Linux 7.2 distribution directories on our ftp server ftp.suse.com have been moved to the /pub/suse/discontinued/ directory tree structure; the 7.2 directories in the update trees will follow later in October. The discontinuation of SuSE Linux 7.2 enables us to focus on the SUSE LINUX distributions of a newer release date to ensure that our customers can continuously take advantage of the quality that they are used to with SUSE LINUX products. This announcement holds true for SuSE Linux 7.2 only. As usual, SUSE will continue to provide update packages for the following home users distributions: SuSE Linux 7.3 SuSE Linux 8.0 SuSE Linux 8.1 SuSE Linux 8.2 and SUSE LINUX 9.0 for a two-year period after the release of the respective distribution. Please note that the maintenance cycles of SUSE LINUX Enterprise Server products and products based on the SUSE LINUX Enterprise Server operating system are not affected by this announcement. To learn more about SUSE LINUX business products, please visit http://www.suse.com/us/business/products/. If you have any questions regarding this announcement, please do not hesitate to contact the SUSE LINUX security <security(a)suse.de>. Best regards, Roman Drahtmüller, SUSE Security. - - | Roman Drahtmüller <draht(a)suse.de> // "You don't need eyes to see, | SUSE LINUX AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: SuSE Security iQEVAwUBP3tL0ney5gA9JdPZAQF7kgf9HUwDhmKShmj4Qknfm2wu9iqvuCOjKcq+ hCNREA+d7OwRHZacHdpkCXd0uIELBUknLD4q/6cNukRKFB+Td50wpVAaoJVAlGG7 yHmy54vXH7HTcTmPfOonphiusv6XmfTfOgap0yaSt2OoOG4p7TvP5HE16Vgi+HJB kfcWTPfXXit7yoOEYo4zfaaXXCz9WfqvDcdXUOvjmfalhgxmOr3f9/X7KcvhnayQ 4s0+/5hO+Pzzh2ODOaLwv+i4zC2+pDH1w9Ix/+snnjCxZefioG3u/xHaDqGGXTck Rg/y2oNDckNXuAop0B1lu+JdwSc8dSYhXDEenmsMpq2qG3vL13Y2TA== =OopL -----END PGP SIGNATURE-----

1 0

SuSE Security Announcement: openssl (SuSE-SA:2003:043)
by Thomas Biege 01 Oct '03

01 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: openssl Announcement-ID: SuSE-SA:2003:043 Date: Wednesday, Oct 1st 2003 16:12 MET Affected products: 7.2, 7.3, 8.0, 8.1, 8.2, 9.0 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7/8, SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: remote denial-of-service Severity (1-10): 5 SuSE default package: yes Cross References: CAN-2003-0543 CAN-2003-0544 CAN-2003-0545 Content of this advisory: 1) security vulnerability resolved: - problems with ASN.1 encoding - accepting client certificates even if disabled problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - whois - gdm2 - postgresql 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information OpenSSL is an implementation of the Secure Socket Layer (SSL v2/3) and Transport Layer Security (TLS v1) protocol. While checking the openssl implementation with a tool-kit from NISCC several errors were revealed most are ASN.1 encoding issues that causes a remote denial-of-service attack on the server side and possibly lead to remote command execution. There are two problems with ASN.1 encoding that can be triggered either by special ASN.1 encodings or by special ASN.1 tags. In debugging mode public key decoding errors can be ignored but also lead to a crash of the verify code if an invalid public key was received from the client. A mistake in the SSL/TLS protocol handling will make the server accept client certificates even if they are not requested. This bug makes it possible to exploit the bugs mentioned above even if client authentication is disabled. There is not other solution known to this problem then updating to the current version from our FTP servers. To make this update effective, restart all servers using openssl please. 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. Please note that this update includes openssl, openssl-devel and openssl-doc. openssl: Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-0.9.7b-71.i586… 88e30d20d288ecffe1e185b6ccc5099e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-0.9.7b-71.i586… 68ffad90868b2107e3d82cc8fc50f6b7 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-71.src.r… 1f5a12184b14ac5281f8da50da7deab6 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-19.i586… 20818d3b2d257bcf9258707e2adf8812 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-19.i586… 2fbea6d1b3c19ed67d76337deef05363 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-19.src.r… 24d40081aa2644a336279ecae878c1f3 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-99.i586… a2c35048358d85fffd5a5ab7b58f6683 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-99.i586… 08803c7ac279b8c9ad1dc4aef4146617 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-99.src.r… 8bb653a4f779a125498f47dbaff0dc2f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-86.i386.rpm 671dc039955089f8523064272a4aad49 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-86.i386.pat… 4ae58f8e66b2cc7c2cc936132558ea46 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-86.src.rpm 7577ca638434ebe20406bfab85ec72ad SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssl-0.9.6b-158.i386.rpm 30ba99434b63d09d46cb271fac1bbefa source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-158.src.rpm 3485c804df9a381131462ba97697d6fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssl-0.9.6a-83.i386.rpm d235ef6d8b990bfaadb974c205acdc40 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-83.src.rpm 5a753ed3919767077292f96728de3870 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/openssl-0.9.6b-90.sparc.r… 29caa7dd281c0891c8655bcd5367f1ca source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-90.src.rpm 6faf5fe6fa004eb5515c1777886c49c9 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssl-0.9.6b-151.ppc.rpm b057f2204c43fdca13fcae041a45e977 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-151.src.rpm 7792ee3de5ef30c66c90a5fe43ee4eb2 openssl-doc: Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-doc-0.9.7b-71.… 4a7d456b67a0456221cf69231270b4bd patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-doc-0.9.7b-71.… 5223616e4b4d8f4bf0c02c63af75106c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-71.src.r… 1f5a12184b14ac5281f8da50da7deab6 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-doc-0.9.6i-19.… fc79cc73f1a9ab5ddfd30cf6ddfb8ddc patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-doc-0.9.6i-19.… 55c3f3afc117c1d3d49ea875057c8d72 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-19.src.r… 24d40081aa2644a336279ecae878c1f3 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-doc-0.9.6g-99.… 0d094066c96a8880845e0775f9e60b73 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-doc-0.9.6g-99.… af8fcb4128569d603a018727eba8dc79 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-99.src.r… 8bb653a4f779a125498f47dbaff0dc2f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/doc4/openssl-doc-0.9.6c-86.i386… c06870e5a8c6ea57471c13fb975c2c9f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/doc4/openssl-doc-0.9.6c-86.i386… 911c9fd73b10b9db32e60834a82a79ee source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-86.src.rpm 7577ca638434ebe20406bfab85ec72ad SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/doc3/openssl-doc-0.9.6b-158.i38… 119950dc0267c7038c21acf6d875afdd source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-158.src.rpm 3485c804df9a381131462ba97697d6fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/doc3/openssl-doc-0.9.6a-83.i386… 2f664c56f018c857f2f11f2e2634fbfa source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-83.src.rpm 5a753ed3919767077292f96728de3870 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/doc3/openssl-doc-0.9.6b-90.spa… 6cbb149f6a3fb62eb7cc71e817e80426 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-90.src.rpm 6faf5fe6fa004eb5515c1777886c49c9 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/doc3/openssl-doc-0.9.6b-151.ppc.… 3f4235ab75c44e8e07c764ed2e4659da source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-151.src.rpm 7792ee3de5ef30c66c90a5fe43ee4eb2 openssl-devel: Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-devel-0.9.7b-7… 8cadccfaa0eeb50def65bdf1cfdba470 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-devel-0.9.7b-7… c7349b7e87b828ee90d7e0b87b0f5d38 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-71.src.r… 1f5a12184b14ac5281f8da50da7deab6 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-1… 970728b4b4ae97d162a226a51a49c5b4 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-1… f3cde2f53303041001edee7739dc4af1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-19.src.r… 24d40081aa2644a336279ecae878c1f3 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-9… b676506791a1d5ddbc97295443092e4b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-9… a9974f26f6a7280a71228b61b6a861cc source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-99.src.r… 8bb653a4f779a125498f47dbaff0dc2f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-86.i386… 6ecfb4d3546645282d62e65c3aec04ad patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-86.i386… 1dbd101b9b7619de55d264191465b701 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-86.src.rpm 7577ca638434ebe20406bfab85ec72ad SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/d2/openssl-devel-0.9.6b-158.i38… 0c2b11b0002d077219842e2b8e528af1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-158.src.rpm 3485c804df9a381131462ba97697d6fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/d2/openssl-devel-0.9.6a-83.i386… 4c206037061e780fdbc20254cfdc9e17 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-83.src.rpm 5a753ed3919767077292f96728de3870 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/d2/openssl-devel-0.9.6b-90.spa… 40e0b55f40c1dfd110d3494240c2b533 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-90.src.rpm 6faf5fe6fa004eb5515c1777886c49c9 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d2/openssl-devel-0.9.6b-151.ppc.… f3a7e90f86c2c095ff3eae5d75a1a3c8 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-151.src.rpm 7792ee3de5ef30c66c90a5fe43ee4eb2 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - gdm2 Due to a bug in GDM it is possible for local users to read any text file on a system by creating a symlink from ~/.xsession-errors. New packages are available on our FTP servers. - whois The client tool whois is vulnerable to several buffer overflows while processing its command-line arguments. In conjunction with using untrusted data from remote sources as input, like using whois in a CGI script and so on, this buffer overflows may be abused to compromise a system. New packages are available on our FTP servers. - postgresql The SQL database server postgresql of version 7.3.x prior 7.3.4 is vulnerable to buffer overflow attacks. New packages will be available soon. ______________________________________________________________________________ 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) iQEVAwUBP3sLUXey5gA9JdPZAQHR6gf+KcmkRZQ8hrjrFt9vP8SZmZJkO8ZjiVX4 js+qeRyIJCf0juZ5dI+I5FGkoaeifNAnuDPDFrMAwIZXF+tgDaLaQ9/nf6r+vZef Ri5wed4B588E7M0GGsvm3guzGSmkOJnwx+Q6aiFo7Sh98LBHUJ/xF2OerSo6Lz3Q k527BCA/EdF9AqlVKuzDynq9HIUiHhbG8ZqHZCNQJMKwOUFPbnhNoTGc2+i/oMeg 0MHSreVr0N9ThUcCVENe8tjzMqNEuTWKe2mIpcMM0dyz9gY10H1zFn3heEHglsCP xrFYt0mfPf5QNVtk2zq1OykKhgvi5vOdsKQ58LxqsFVBJ3N5xQswKw== =byxR -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de>, SuSE Linux AG, 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 -- ... bring the pieces back together, we discover communication... - Maynard James Keenan

1 0

New Openssl Vulnerability
by Ferdinand Schmid 01 Oct '03

01 Oct '03

HI, Are SuSE versions of openssl vulnerable to this ASN.1 issue? http://www.kb.cert.org/vuls/id/935264 I understand that SuSE backported the recent patches to 0.9.6 so we may not be affected. However, like Roman said in a previous post - we don't like to guess ;) Thanks, Ferdinand -- Ferdinand Schmid Architectural Energy Corporation Celebrating 21 Years of Improving Building Energy Performance http://www.archenergy.com

2 1

7.3 Kernel Update
by Ulrich Schneider 01 Oct '03

01 Oct '03

Hi ! i´m into updating the Kernel 2.4.10-4GB #1 Mon Nov 5 on a Suse 7.3 System to 2.4.18-279 ... As far as good ... reading Step 4 from http://www.suse.de/de/security/2003_034_kernel.html "The variable INITRD_MODULES .... The variable should contain your scsi adapter (if any) or filesystem driver modules." cat /etc/rc.config | grep INITRD INITRD_MODULES="eepro100 3c90x 3c90x" Shows only the three NIC´s but no scsi adapter or filesystem module. Is it safe to update the kernel? Sorry for being dumb today ... but it confused me quite a litte bit. Thanks Uli

3 3

Traffic analyzing | printing traffic
by BLeonhardt＠analytek.de 01 Oct '03

01 Oct '03

Hi, does any rule allow me to analyze how much traffic is going through my network for printing ? yours, bruno

1 0

Re: [SLE] Re: [suse-security] root login disabled for KDM - SOLVED
by Bob Pearson 01 Oct '03

01 Oct '03

On Wednesday 01 October 2003 7:57 am, Joe Morris (NTM) wrote: > >I have remote login and shutdown disabled via "Control Center->System > >Administration->Login Manager". System UID set to Below 0 and Above > > 65000. "unhidden with every hidden but root (before I had Below 500 and > > had "Selected only" which included "root"). > > Check to make sure /opt/kde3/share/config/kdm/kdmrc is a symlink to > /etc/opt/kde3/share/config/kdm/kdmrc. The control Center edits the > /etc/...file, but kdm reads the opt...file, so these need to be the > same. Often, an update will mv the symlink and install a default kdmrc > in the opt... replacing the one you see in CC. Check it out. Thanks. This was half the solution. It was NOT a symlink. Thanks also to Manfred Hollstein who wrote: --------------------------------------------------------------------------------------------- Make sure to set the following in /etc/opt/kde3/share/config/kdm/kdmrc in section [X-*-Core]: AllowRootLogin=true ------------------------------------------------------------------------------------------- I had multiple (well, two) [X-*-Core] sections but only the last mattered. Setting AllowRootLogin=true and making the symlink fixed the problem. Thanks to all. Regards, Bob Pearson

1 0

AW: [suse-security] root login disabled for KDM (KDE 1.4.1)
by Ulrich Roth 01 Oct '03

01 Oct '03

Hi Bob, > Unable to login to root via KDM. Message is "root logins are > not allowed". This has to do with the configuration of X. In the SuSE support database there is an abstract about this subject. Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth at impact dot de

1 0

SuSE Security Announcement: mysql (SuSE-SA:2003:042)
by krahmer＠suse.de 01 Oct '03

01 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: mysql Announcement-ID: SuSE-SA:2003:042 Date: Wed Oct 1 12:12:38 CEST 2003 Affected products: 7.2, 7.3, 8.0, 8.1, 8.2 SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7, 8 SuSE Linux Office Server UnitedLinux 1.0 Vulnerability Type: remote code execution Severity (1-10): 5 SuSE default package: no Cross References: - Content of this advisory: 1) security vulnerability resolved: Buffer overflow in mysql. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - OpenSSL 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information A remotely exploitable buffer overflow within the authentication code of MySQL has been reported. This allows remote attackers who have access to the 'User' table to execute arbitrary commands as mysql user. The list of affected packages is as follows: mysql, mysql-client, mysql-shared, mysql-bench, mysql-devel, mysql-Max. In this advisory the MD5 sums for the mysql, mysql-shared and mysql-devel packages are listed. To be sure the update takes effect you have to restart the MySQL server by executing the following command as root: /usr/sbin/rcmysql 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. i386 Intel Platform: SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-3.23.55-22.i586.… 41e8d3781aeedd2e48837293d261f9e2 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-shared-3.23.55-2… b75bdea7f484305c62415cd7412151af ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-devel-3.23.55-22… 264920dc6e1def4e26253cc3d82f2fc7 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-3.23.55-22.i586.… 82bac86826eb08ccf8c3204a792e0df1 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-shared-3.23.55-2… ea14dd33b2e390009513209e71229cd3 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-devel-3.23.55-22… b8e64deab45bdd05657a5447b4e279eb source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/mysql-3.23.55-22.src.rpm fd33faf5fe7efc9f9c5871db37ea88b4 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-3.23.52-106.i586… e7488a05d07282bbd8317f834c24f0d4 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-shared-3.23.52-1… e6db8d49932368487a334d803572ed4e ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-devel-3.23.52-10… 9c6c4ab2b8a461ca391a2453d05d9b71 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-3.23.52-106.i586… 37960d363c09a1123c25b11d6a753968 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-shared-3.23.52-1… 77d66503d21447bd1dd8339463c7b25b ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-devel-3.23.52-10… c747e07c307e9619cf04a3e2c8cc369f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/mysql-3.23.52-106.src.r… 952c96bc22740b252e151c27537e5c1b SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-3.23.48-81.i386.rpm 7126396c99deb931dda869fdc8e5e6ef ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-shared-3.23.48-81.i38… 6cfa50d58f7b23201f2056d6097c4161 ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap3/mysql-devel-3.23.48-81.i386… 23d978a491c8a0a0035142276ae9c806 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-3.23.48-81.i386.patch… 49833c754e880fba15e579ad32d6861c ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-shared-3.23.48-81.i38… 3eba782210bf2e3a714616571bea0066 ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap3/mysql-devel-3.23.48-81.i386… 9d6d58e8da20ea06bfd3207c44925190 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/mysql-3.23.48-81.src.rpm bc8db10701bdaee4da9776a6dc49fc29 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap3/mysql-3.23.44-28.i386.rpm f3171ff82e6d3fbf9913cfb58d984602 ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap2/mysql-shared-3.23.44-28.i38… db2fe45728f6073f15c6440538926828 ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap3/mysql-devel-3.23.44-28.i386… 278a0338ed3a6ae65c7328f422f7abfc source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/mysql-3.23.44-28.src.rpm c1076bca4b5a7d750f72811c097e92fa SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap3/mysql-3.23.37-62.i386.rpm 2b5af68cb036119322a8a666fa68046b ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap2/mysql-shared-3.23.37-62.i38… d1f95967eb77ff7b8761ec27795cb740 ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap3/mysql-devel-3.23.37-62.i386… e8cd7dda9473259239458b5e008c6924 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/mysql-3.23.37-62.src.rpm e3c0693bda7d898ffc5bfb8f23478e7e Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap3/mysql-3.23.44-24.sparc.rpm 52a66dfd5f2f330240dab5e59c412ef7 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap2/mysql-shared-3.23.44-24.sp… 6060be5ff51994e0ab73e8afc7ba2f26 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap3/mysql-devel-3.23.44-24.spa… 802c951032a42b1b21f51ab53af502c9 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/mysql-3.23.44-24.src.rpm 350c8fcc5522c08ca9096803cc34dd42 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap3/mysql-3.23.44-32.ppc.rpm 4dfbca3cbc9e9a3f8f36ab19a7bb4093 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap2/mysql-shared-3.23.44-32.ppc.… 068cbab05a37e74b9f57abcae7eb6b64 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap3/mysql-devel-3.23.44-32.ppc.r… c897ad4fa5a724c11efabbecfdd929c4 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/mysql-3.23.44-32.src.rpm aa219acd13b73c45e2b418e8df03a1ee ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - OpenSSL Critical bugs within the ASN.1 parsing routines have been reported recently. We are currently building new packages and will notify you in a separate advisory when the packages are available. ______________________________________________________________________________ 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) iQEVAwUBP3q+Jney5gA9JdPZAQEanQf+M0uzKuBuPf7EGBNql8hW5P8XWtVjABiv y7ngIxjah/vACuyTMdPzeMmu+yEdfejCc5jtyYEG0cahxJGpUQOLnJ6jyyDjw+S8 ic+UJ96YZ4j2FKplHaNtGgTpDFUmFtUXg+07vQ76fzfWM8iL1HQKQcFGFuHIauwi 3Ei26HHp8dgRAAVqTzCuEmlOgUkHKTSn4xLbwmdYyDoY9aRtkQ6d7hdN9sOPj7pp p0jlf4I3Xut6fqLJ/4ZbCVI4V1xABG9x+2XagBRAfzauxvLWOfpdrAGRFdX66k14 OvQo58dMxs7pqsubhRtFcYGQROdIjpKLbLSLaLbsypqSOkJrj8ibIQ== =U3Dc -----END PGP SIGNATURE-----

1 0

root login disabled for KDM (KDE 1.4.1)
by Bob Pearson 01 Oct '03

01 Oct '03

Environment: 8.2 Suse Professional i386 (athlon kernel-source-2.4.20.SuSE-100 ) KDE 3.1.4 from SuSE supplementary directory KDM RPM: kdebase3-kdm-3.1.4-34 /etc/passwd entry for root root:x:0:0:Konqi:/root:/bin/bash The name Konqi as root was added with a PNG file for KDM to display, cute little 64x64 pixel 3D dragon that he is. I have remote login and shutdown disabled via "Control Center->System Administration->Login Manager". System UID set to Below 0 and Above 65000. "unhidden with every hidden but root (before I had Below 500 and had "Selected only" which included "root"). Unable to login to root via KDM. Message is "root logins are not allowed". Nothing in /var/log about the attempt but this: Oct 1 06:33:34 cueball resmgr[1227]: accepted connection from user root Oct 1 06:33:34 cueball resmgr[1227]: disconnect from root # cat /etc/pam.d/login #%PAM-1.0 auth requisite pam_unix2.so nullok #set_secrpc auth required pam_securetty.so auth required pam_nologin.so #auth required pam_homecheck.so auth required pam_env.so auth required pam_mail.so account required pam_unix2.so password required pam_pwcheck.so nullok password required pam_unix2.so nullok use_first_pass use_authtok session required pam_unix2.so none # debug or trace session required pam_limits.so I suspect something wrong with my PAM configuration. I did no editing explicitly of these files. There is a /etc/pam.d/xdm but not a /etc/pam.d/kdm "login root" from command line fails and goes away before an error can be detected. "su - root" works. Anyone know what file I have to tweak or what I am doing wrong? TIA for any help. Regards. Bob Pearson -- I am unique and special, just like everyone else.

1 0

SuSE Security Announcement: lsh (SuSE-SA:2003:041)
by krahmer＠suse.de 01 Oct '03

01 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: lsh Announcement-ID: SuSE-SA:2003:041 Date: Wed Oct 1 10:24:45 CEST 2003 Affected products: 8.0, 8.1, 8.2 Vulnerability Type: remote code execution Severity (1-10): 5 SuSE default package: yes Cross References: - Content of this advisory: 1) security vulnerability resolved: Buffer overflow in lsh. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - node - proftp - OpenSSL 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information LSH is the GNU implementation of SSH and can be seen as an alternative to OpenSSH. Recently various remotely exploitable buffer overflows have been reported in LSH. These allow attackers to execute arbitrary code as root on un-patched systems. LSH is not installed by default on SuSE Linux. An update is therefore only recommended if you run LSH. Maintained SuSE products are not affected by this bug as LSH is not packaged on maintained products such as the Enterprise Server. For the updates to take effect execute the following command as root: /usr/sbin/rclshd 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. i386 Intel Platform: SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/lsh-1.5-114.i586.rpm 798f52402cda6c7e1733aed15bf0d9cb patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/lsh-1.5-114.i586.patch… 9308cdb133d2311a9dc4a10bbf613501 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/lsh-1.5-114.src.rpm 1e1b5beac002cf51d1eea0277934a69d SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/lsh-1.4.2-73.i586.rpm b5ff8ba104623fe9a77705154aad92f7 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/lsh-1.4.2-73.i586.patc… 6341acd3fe513921b7123d7c1d98cc43 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/lsh-1.4.2-73.src.rpm 0a2b95e911f8760009ad0d5b2fd7618e SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/lsh-1.3.5-188.i386.rpm bccfd85985bab8a324b25c1b2443bf2b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/lsh-1.3.5-188.i386.patch.r… 8a232720cb0a4b35d0899e9c6a4e80ae source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/lsh-1.3.5-188.src.rpm 8e3e30b134b12400559152bb5c53d0f8 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - node A format string vulnerability has been fixed in the new node packages available on our ftp servers. An update is recommended if you use this package. - proftp A off-by-one buffer overflow has been fixed in the proftp packages for SuSE Linux 7.2 and 7.3. Note that the bug that was fixed is different from the 'ASCII File Transfer Buffer Overrun Vulnerability' (CAN-2003-0831). The proftp packages shipped by SuSE are not affected by CAN-2003-0831. - OpenSSL Critical bugs within the ASN.1 parsing routines have been reported recently. We are currently building new packages and will notify you in a separate advisory when the packages are available. ______________________________________________________________________________ 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) iQEVAwUBP3qgJHey5gA9JdPZAQEutAf+L935tRS8xmYZFFjUhQdd5MHWOGCanB4I 8WabNy77o6SbztDcskEUUr0+SKjDQjqEEndY4tKFlxCDNWItxJbEYmDtLB2x2CTE dCZSqoJVNxeySWRfYMs8fmC3nEQCgVYgIqhpFhi/VaP89d5/IvITwnDOWOMej0nF pj2emi0cOz62KKSlq64D+uDZJxtMdg0KrVAO15O5TQJvQnze2CkEuWMivvVvmDML jGlTzznhvVey0Czc9LNNK6VPD/i+6zHCM/+XU/1b3Gl4gRAzLjebBsHzjW45bVAu Ed+Z0EPVi/ArzfFJ0P7CcZgnYuTOoqMAJMWagW5O+4pnUpny2aFS/w== =Gv9P -----END PGP SIGNATURE-----

1 0

Re: Re: Re: Re: Re: [suse-security] Dial timeout on isdn router with ip-tables logging
by BLeonhardt＠analytek.de 01 Oct '03

01 Oct '03

I will test / check that -- but I guess he won't hangup anyway ... bruno Keith Roberts <keith(a)topaz5.worldonline.co.uk> schrieb am 01.10.2003 12:00:06: > > > Hmm... > > I'm really not sure what to suggest next here... > > You have got me stumped with this one Bruno. > > > Just a few more thoughts. > > > Does your router have any blocking rules in it? > > If you turn IPTables logging off (not the firewall itself) > > does your ISDN script work correctly? > > > Regards - Keith > > > > > > On Wed, 1 Oct 2003 BLeonhardt(a)analytek.de wrote: > > > > > > > > > > > Good morning ;-) > > > > I am not block all outgoing traffic from the local box just the dns-requests > coming from the box itself - I have bind8 running on the machine. > > All other blocking-rules are in the forward chain ... so if I run win ther > won't be a connection established all 3 min. :-) ... default policy (from the > linux-box) for outgoing connections is allow (accept) ... > > > > bruno > > > > > > Keith Roberts <keith(a)topaz5.worldonline.co.uk> schrieb am 30.09.2003 17:30:55: > > > > > > > > > > > On Tue, 30 Sep 2003 BLeonhardt(a)analytek.de wrote: > > > > > > > > > > > > > > > > > > > > > > > Yes, that's it. > > > > > > > > I don't know why... all possible outgoing traffic has been blocked ( for > > > testing ) but he will not hangup... :-( > > > > > > > > > > That MAY be your problem. > > > > > > I'm NOT using ISDN, but on my dial-up modem connection, when > > > I hit CTRL-C, to kill wvdial, there are a few packets sent > > > out from my modem, to cleanly terminate the dial-in > > > connection. > > > > > > Sometimes my dial-in connection will stay live, if I do NOT > > > finish wvdial in the correct manner. eg CTRL-Z instead of > > > CTRL-C. > > > > > > If you are blocking ALL outgoing packets, this may be why > > > the connection stays open - because the signal to terminate > > > your ISDN connection is not reaching your ISDN service > > > provider. > > > > > > > > > Here's my 56K modem start sequence: > > > > > > topaz:/home/keith # wvdial > > > --> WvDial: Internet dialer version 1.42 > > > --> Initializing modem. > > > --> Sending: AT&F0&C1 > > > AT&F0&C1 > > > OK > > > --> Modem initialized. > > > --> Sending: ATDT1470 0808 9933 030 > > > --> Waiting for carrier. > > > ATDT1470 0808 9933 030 > > > CONNECT 38400 > > > --> Carrier detected. Starting PPP immediately. > > > --> Starting pppd at Tue Sep 30 15:20:53 2003 > > > --> pid of pppd: 1255 > > > --> pppd: Using interface ppp0 > > > --> pppd: local IP address 62.64.219.8 > > > --> pppd: remote IP address 213.120.78.69 > > > --> pppd: primary DNS address 212.74.114.193 > > > --> pppd: secondary DNS address 212.74.112.66 > > > --> pppd: Script /etc/ppp/ip-up run successful > > > --> Default route Ok. > > > --> Nameserver (DNS) Ok. > > > --> Connected... Press Ctrl-C to disconnect > > > > > > [1]+ Stopped wvdial > > > > > > > > > I've just checked this by hitting CTRL-Z. > > > > > > My line is still live! > > > > > > I now have to turn my modem OFF to break the connection. > > > > > > > > > Now, trying to redial I get: > > > > > > > > > topaz:/home/keith # wvdial > > > --> WvDial: Internet dialer version 1.42 > > > --> Cannot open /dev/ttyS1: Device or resource busy > > > --> Cannot open /dev/ttyS1: Device or resource busy > > > --> Cannot open /dev/ttyS1: Device or resource busy > > > > > > Because the wvdial script was not stopped correctly. > > > > > > Now I kill the bash shell in KDE to remove the device lock, > > > and free up the modem! > > > > > > > > > HTH - Keith > > > > > > > > > > > > > > > > >

1 0

Re: [suse-security] Secure Mail Server
by Marc Samendinger 01 Oct '03

01 Oct '03

On Tue, Sep 30, 2003 at 04:24:23PM +0100, João Reis wrote: > Hi to all. Hi João, > I would like to implement a secure Mail server. > > This is an internal mail server and belongs to the network behind the > external firewall. > > I also would like to have a system which permits external users to > connect to the internal mail > server in order to fetch their internal mail or to send their mail > througth this server (POP with SSL and SMTP). ^^^^^^^^^^^^^^^^^^^^^ IMHO this should read "((POP and SMTP) with SSL)" :) And don't forget to use smtp-auth or pop-before-smtp, so you don't end up as an open relay. > João Reis marc

1 0

Re: Re: Re: Re: [suse-security] Dial timeout on isdn router with ip-tables logging
by BLeonhardt＠analytek.de 01 Oct '03

01 Oct '03

Good morning ;-) I am not block all outgoing traffic from the local box just the dns-requests coming from the box itself - I have bind8 running on the machine. All other blocking-rules are in the forward chain ... so if I run win ther won't be a connection established all 3 min. :-) ... default policy (from the linux-box) for outgoing connections is allow (accept) ... bruno Keith Roberts <keith(a)topaz5.worldonline.co.uk> schrieb am 30.09.2003 17:30:55: > > > On Tue, 30 Sep 2003 BLeonhardt(a)analytek.de wrote: > > > > > > > > > > > Yes, that's it. > > > > I don't know why... all possible outgoing traffic has been blocked ( for > testing ) but he will not hangup... :-( > > > > That MAY be your problem. > > I'm NOT using ISDN, but on my dial-up modem connection, when > I hit CTRL-C, to kill wvdial, there are a few packets sent > out from my modem, to cleanly terminate the dial-in > connection. > > Sometimes my dial-in connection will stay live, if I do NOT > finish wvdial in the correct manner. eg CTRL-Z instead of > CTRL-C. > > If you are blocking ALL outgoing packets, this may be why > the connection stays open - because the signal to terminate > your ISDN connection is not reaching your ISDN service > provider. > > > Here's my 56K modem start sequence: > > topaz:/home/keith # wvdial > --> WvDial: Internet dialer version 1.42 > --> Initializing modem. > --> Sending: AT&F0&C1 > AT&F0&C1 > OK > --> Modem initialized. > --> Sending: ATDT1470 0808 9933 030 > --> Waiting for carrier. > ATDT1470 0808 9933 030 > CONNECT 38400 > --> Carrier detected. Starting PPP immediately. > --> Starting pppd at Tue Sep 30 15:20:53 2003 > --> pid of pppd: 1255 > --> pppd: Using interface ppp0 > --> pppd: local IP address 62.64.219.8 > --> pppd: remote IP address 213.120.78.69 > --> pppd: primary DNS address 212.74.114.193 > --> pppd: secondary DNS address 212.74.112.66 > --> pppd: Script /etc/ppp/ip-up run successful > --> Default route Ok. > --> Nameserver (DNS) Ok. > --> Connected... Press Ctrl-C to disconnect > > [1]+ Stopped wvdial > > > I've just checked this by hitting CTRL-Z. > > My line is still live! > > I now have to turn my modem OFF to break the connection. > > > Now, trying to redial I get: > > > topaz:/home/keith # wvdial > --> WvDial: Internet dialer version 1.42 > --> Cannot open /dev/ttyS1: Device or resource busy > --> Cannot open /dev/ttyS1: Device or resource busy > --> Cannot open /dev/ttyS1: Device or resource busy > > Because the wvdial script was not stopped correctly. > > Now I kill the bash shell in KDE to remove the device lock, > and free up the modem! > > > HTH - Keith > > > >

1 0