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