August 2002 - openSUSE Security - openSUSE Mailing Lists

PAM and Samba
by Robert Rottscholl 13 Aug '02

13 Aug '02

Dear List, i want to implement a Samba server which authenticates the users via PAM stack against the linux password. How can I do this and is libpam-smb the correct library and where can i download the latest version? Thanks :-) Robert Rottscholl

3 2

Restriced SSH Account?
by Jens Gassmann 12 Aug '02

12 Aug '02

Hi, Where can i find an ssh-shell who allow's me to restrict an ssh-acount to edit and view only files in ther homedir? Thanks Jens -- Jens Gassmann mailto: j.gassmann(a)atomix.de Privat: 022 34 / 694 112 Mobil : 0179 / 136 10 16 Dienst: 0221 / 975 08 20 Web : http://www.atomix.de

5 5

AW: [suse-security] Restriced SSH Account?
by Jens Gassmann 12 Aug '02

12 Aug '02

Where can i find an restriced or configurely shell? I seek long but i find no one. -Jens -----Ursprüngliche Nachricht----- Von: Robert Davies [mailto:rob_davies@ntlworld.com] Gesendet: Montag, 12. August 2002 16:00 An: Jens Gassmann Betreff: Re: [suse-security] Restriced SSH Account? On Monday 12 August 2002 14:39, you wrote: > Hi, > > Where can i find an ssh-shell who allow's me to restrict an ssh-acount > to edit and view only files in ther homedir? ssh is not a true shell, it's more a secure(?) replacement for telnet or rlogin. Set the user's shell to one of the restricted shells, if you want different access depending on whether they are using ssh(1) or not to connect, you might need to do some hacking of source, or at least right your own dummy shell to decide which one should be used. Rob

2 1

Re: [suse-security] Restriced SSH Account?
by GentooRulez 12 Aug '02

12 Aug '02

What you searching for is called restricted shells, f.i. in a chroot envoirement - check google for it and read about circumvention of those shell e.g. here, too. http://www.opennet.ru/base/netsoft/1025195882_355.txt.html Yours Michael

1 0

NFS rules and performance
by Schoenwaelder Oliver 12 Aug '02

12 Aug '02

Hi list, we have two SuSE 8.0 (kernel 2.4.18 and all the latest patches) running on two sites, connected via internet. Server A has public ip address and server B is host on private LAN behind NATed gateway. Now we exported a directory on server A via nfs. At server B we mount this directory. For our firewall (iptables) we opened upd ports for rpc (111) and nfs(2049). And after each reboot we have to add/modify the mountd port (got with rpcinfo -p localhost). But I think there must be an exact definition of what to allow for nfs on client and server side. But what? And we have a very poor nfs performance. Doing an "ls" on one of subdirs with few files is ok, but with another subdir which contains 100+ files this proccess doesn't return in proper time (it takes minutes!!!). Any idea? Thx, Oliver

2 1

i4l advisory
by Alan Rouse 12 Aug '02

12 Aug '02

Just to confirm-the advisory only mentions suse 7.3 and 8.0. Are earlier versions unaffected? Thanks.

1 0

Laptops
by Thomas Wheeler 12 Aug '02

12 Aug '02

Hi Has any one been so brave as to put a scaled down version of suse on a Pentium 75 laptop with 16mb ram?.. Regards, Thomas Wheeler -=No Trees Were Harmed By Sending This Email, Only A View Electrons Were Seriously Discomforted =-

2 1

RE: [suse-security] FreeS/wan trough NATing Router
by GentooRulez 12 Aug '02

12 Aug '02

http://open-source.arkoon.net/ here is another ip-sec nat-t patch compiling works fine. tests comes soon Michael

1 0

SuSE Security Announcement: i4l (SuSE-SA:2002:030)
by Sebastian Krahmer 12 Aug '02

12 Aug '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: i4l Announcement-ID: SuSE-SA:2002:030 Date: Mon Aug 12 11:00:00 CEST 2002 Affected products: 7.3, 8.0, SuSE Linux Database Server, SuSE eMail Server 3.1, SuSE eMail Server III, SuSE Firewall Adminhost VPN, SuSE Linux Admin-CD for Firewall, SuSE Linux Live-CD for Firewall, SuSE Linux Connectivity Server, SuSE Linux Enterprise Server 7 Vulnerability Type: local privilege escalation Severity (1-10): 5 SuSE default package: Yes Other affected systems: No Content of this advisory: 1) security vulnerability resolved: buffer overflows in ipppd problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The i4l package contains several programs for ISDN maintenance and connectivity on Linux. The ipppd program which is part of the package contained various buffer overflows and format string bugs. Since ipppd is installed setuid to root and executable by users of group 'dialout' this may allow attackers with appropriate group membership to execute arbitrary commands as root. The i4l package is installed by default and also vulnerable if you do not have a ISDN setup. The buffer overflows and format string bugs have been fixed. We strongly recommend an update of the i4l package. If you do not consider updating the package it is also possible to remove the setuid bit from /usr/sbin/ipppd as a temporary workaround. The SuSE Security Team is aware of a published exploit for ipppd that gives a local attacker root privileges so you should either update the package or remove the setuid bit from ipppd. 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.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/i4l-2002.7.31-0.i386.rpm cfd29e3bfb2466dc15eafae8c8280b3d source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/i4l-2002.7.31-0.src.rpm fdb75de724d373dee4d21ce3e9be176e SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/i4l-2002.7.23-0.i386.rpm 1d5fff19d48eb1b0652c21c139fdf53d source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/i4l-2002.7.23-0.src.rpm b0b5ac3c6f03f848170a158b5fee4e72 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/i4l-2002.7.23-0.sparc.rpm 2fd232a50e27055831fd35337e6d73e7 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/i4l-2002.7.23-0.src.rpm cdef29bad89fcc6c2e4d0be38377edfa PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/i4l-2002.7.23-0.ppc.rpm 90939fabf3b1fcd8dd143e969b830dea source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/i4l-2002.7.23-0.src.rpm 220bb5b9c5f16605beff26b961eba11a ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - docbook In past some distributors provided updates for their docbook packages to fix a problem within the docbook configuration-files which allowed evil input-files to create arbitrary files within the users scope. However the supplied configuration-fixes can easily be circumvented by offering certain style-sheet files along with the evil input-file. Because of this fact SuSE does not offer updates for the docbook packages but rather strongly recommends to not process untrusted files with the docbook utilities. - openldap2 Andrew McCall reported a problem within the openldap2 package which could lead to a denial of service attack against the slapd server. This problem has been fixed. New openldap2 packages will soon be 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: 2.6.3i Charset: noconv iQEVAwUBPVeImney5gA9JdPZAQHucgf9FaNs22ccTGur7PSNRPY7XXR/UGiP3A8H qr2dAVMm1/9oTqTM20F+kYEl34cAG5DT3JnHocLYKTL3zZVDEW9QaM8xFBK4LWGp VH8Zjfg0m9UzYEKUJ7lu0B2lYByQUdwroqJ5BqKZOxEG7Oopa65rc8tI5iyGgdMr j+C1pBszdGS3oVBcA17gIMxJcrjgFrKYFMwnw9UgtpoZat+5qO2XJvf1O2ZQc+lU OJPZ8WmEzDs4BHaLEIH4xSAauR7PGr0t0NsraWVFT86AK2xJuKGZGX2oi552XxwV pEIHufu8MqGlN/Y3N+PxW38RLCcGsnj1y3NqChT4+GSOoQKNbwJWbg== =Ds1S -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0

Q: RPC-Bufferoverflow
by Markus Brückner 12 Aug '02

12 Aug '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, according to http://cert.uni-stuttgart.de/archive/bugtraq/2002/07/msg00430.html there is a buffer-overflow in every RPC-Implementation derived from the original SUN-RPC-Code. As I didn't see any discussion or announcement on suse-security oder suse-security-announce I just wanted to ask whether a system using NFS (and therefor the RPC-Portmapper) as an Installation medium is affected by this vulnerability? System is SuSE 8.0, Kernel is a vanilla 2.4.18. Thx in advance Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9VZnZzNmNmbjGoU8RAvANAJ94OrirmBQA/PWW48/7qSFlSAqOfACgzZqx phBa9hXpQ1GuzyL/KLoG5V8= =R9j/ -----END PGP SIGNATURE-----

2 1