May 2001 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] forcing use of proxy
by Markus Gaugusch 31 May '01

31 May '01

See http://www.squid-cache.org/Doc/FAQ/FAQ-17.html#ss17.3 > We're using squid 2.2.stable5 as proxy on a SuSE 7.0 box and i would like ALL users to go through the proxy... I know we have some users that play with internet and disable their proxy parameters.... how can I ban "direct internet access" so only proxy > connections pass through (whatever is configure on users win stations) ? -- _____________________________ /"\ Markus Gaugusch ICQ 11374583 \ / ASCII Ribbon Campaign markus(a)gaugusch.dhs.org X Against HTML Mail / \

1 0

AW: [suse-security] forcing use of proxy
by Hirsch Wolfgang 31 May '01

31 May '01

I'd disable port 80 at the box and on client side you have to insert the port of squid (normally 3128). Regards wolfgang > -----Ursprüngliche Nachricht----- > Von: stephane parenton [mailto:sparenton@experia.com] > Gesendet: Donnerstag, 31. Mai 2001 11:56 > An: SuSE secure > Betreff: [suse-security] forcing use of proxy > > > Hi, > > We're using squid 2.2.stable5 as proxy on a SuSE 7.0 box and > i would like ALL users to go through the proxy... I know we > have some users that play with internet and disable their > proxy parameters.... how can I ban "direct internet access" > so only proxy > connections pass through (whatever is configure on users win > stations) ? > > Regards > Stephane > > --------------------------------------------------------------------- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com >

1 0

nice ssh-problem...
by Daniel Quappe 31 May '01

31 May '01

hi list, today i've got a problem while testing a system for rsyncing two systems via ssh. the external ssh-server normally wants to get request with a privileged port (eg. 1023). but i want to connect via my internal server which is masq. by my gateway/firewall. after this masq. the privileged request transforms into an un- privileged one...;-( are there any ideas somewhere out there...;-)?? many thanks in advance, bye daniel -- Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1! http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

3 2

OT: OpenSSL Rant :/
by Bill Jones 31 May '01

31 May '01

Probably off-topic, but I need to rant anyways: I do not see where nor any How-To on the procedure for installing my own self-signed certificate. I even did a new tarball d/l from OpenSSL's site itself: OpenSSL 0.9.6a 5 Apr 2001 built on: Mon May 28 00:19:23 EDT 2001 platform: linux-sparcv9 options: bn(64,32) md2(int) rc4(ptr,char) des(idx,cisc,16,long) idea(int) blowfish(ptr) compiler: gcc -DTHREADS -D_REENTRANT -mcpu=ultrasparc -DB_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall -Wa,-Av8plus -DULTRASPARC -DBN_DIV2W -DMD5_ASM It was successful, as was: /usr/ssl/misc/CA.pl -newca /usr/ssl/misc/CA.pl -newreq /usr/ssl/misc/CA.pl -signreq /usr/ssl/misc/CA.pl -pkcs12 "InSecurity.Org" I suppose my real issue is I wish I knew what I was doing more than just the 'trial and error' development approach... Thx for listening; -Sneex- :] ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

7 14

Fw: [suse-security] SuSEFirewall fails on system startup
by Suse_Mail_List 30 May '01

30 May '01

----- Original Message ----- From: al To: suse-security(a)suse.com Sent: Wednesday, May 30, 2001 4:35 PM Subject: Re: [suse-security] SuSEFirewall fails on system startup I am NEW to SuSE 7.1 and Linux in general, and have since become an avid user (also due to getting my system wacked by someone, which has prompted me to solidify my security) ... :) So alas I am here. In short I can not get my fore wall to start. I am using STATIC IP addresses so the follow up to this thread { [suse-security] SuSEfirewall does not start Stephan Dankers (Thu Apr 05 2001 - 11:48:58 CDT) a.. Re: [suse-security] SuSEfirewall does not start marsaro(a)interearth.com (Thu Apr 05 2001 - 14:13:33 CDT) } has not helped... below is an excerpt from my bootlog.... Starting Firewall Init........ No interfaces active! exiting ... SuSEfirewall: clearing rules now ... done failed Initializing random number generator done Setting up network device eth0 done Setting up network device eth1 done Setting up routing (using /etc/route.conf) done Starting Firewall Initialization: (phase 2 of 3) ............. ......... .... Starting inetd done Starting Firewall Initialization: (phase 3 of 3) Master Resource Control: runlevel 3 has been reached Failed services in runlevel 3: SuSEfirewall_init SuSEfirewall_setup SuSEfirewall_final Any input as always would be greatly appreciated, and also any security tips on the subject of TRIPWIRE (implementing soon), and an SSH-telnet and FTP client for 2K,NT and ME would be neat :) Thanks Aaron

1 0

bandwidth management
by michael.ryan＠storm.ie 30 May '01

30 May '01

Hi all, A little off-topic but can anyone recommend a bandwidth management tool for SuSE 6.4 ... (I'd like to restrict bandwidth usage for certain machines on our internal net) Thanks in advance, Michael

3 2

SuSE Security Announcement: man (SuSE-SA:2001:019)
by Roman Drahtmueller 30 May '01

30 May '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: man Announcement-ID: SuSE-SA:2001:019 Date: Tuesday, May 29th 2001 20:30 MEST Affected SuSE versions: 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1 Vulnerability Type: local privilege escalation Severity (1-10): 4 SuSE default package: yes Other affected systems: most linux systems shipping the mandb package Content of this advisory: 1) security vulnerability resolved: man 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 Two vulnerabilities have been found in the man package that is installed by default in all SuSE Linux distributions. The first error is a format string bug in the error handling routine of the man command that can allow a local attacker to gain the privileges of the user "man" on SuSE Linux systems (the man command in /usr/bin is installed setuid man). After getting write access to the /usr/bin/man binary, an attacker can place a cuckook's egg into the executable, waiting for root to view manpages. The second problem is a segmentation fault that can be caused by the options "-S ::: foo" to the man command. On other Linux distributions, this problem has been found exploitable. On SuSE and Debian systems, the code responsible for the bug is different from the one found in other distributions and is not exploitable. We consider the existence of this bug a beauty flaw that will be fixed in future releases of the SuSE Linux distribution, but the fix was not included in the man packages that can be found on our ftp server. Since the error() format string bug was discovered earlier than we announced that the SuSE Linux distributions 6.0, 6.1 and 6.2 will be discontinued, we also provide fixed packages for the said distributions for the i386 Intel architecture. We strongly encourage our usership to upgrade their systems to a newer distribution. Both bugs are fixed in the upcoming release of SuSE Linux 7.2. A temporary workaround (as discussed in earlier SuSE security announcements) is to remove the setuid-bit of the /usr/bin/man file. This will cause errors to be printed when viewing a manpage, because the formatted manpages can't be saved to the /var/cache/man directories any longer. The sideeffects of this workaround are of mostly cosmetical nature on fast hardware. If you changed the file modes of the man command binary using the command chmod 755 /usr/bin/man , then please also change the occurrences of the same path in the files /etc/permissions*, provided you have set the variable CHECK_PERMISSIONS to "set" in /etc/rc.config. Download the update package from locations described below and check the authenticity of the rpm package file using a method as described in section 3) of this security announcement. Use the command `rpm -Uhv file.rpm' to apply the update. In some rare cases, the older man package contains files that conflict with the new version. This should not be considered a problem in this particular case of the man packge; use the options "--nodeps --force" to override. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/man-2.3.10d69s-190.i386.rpm bc914ab44fcdeb2fa809176d2b807bea source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/man-2.3.10d69s-190.src.rpm 96dfa2df00ae4a1045c6d038bd02290b SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/man-2.3.10d69s-194.i386.rpm 533fa405f82ef5bbcfb4b4a6c188d0da source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/man-2.3.10d69s-194.src.rpm b935e02d444a613beccec50db65c1cf7 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/man-2.3.10d69s-191.i386.rpm a7cd2aa52a72f739d7c0cac5073f546b source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/man-2.3.10d69s-191.src.rpm e9fd012fbea95c2787de0ee0612da8ce SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/a1/man-2.3.10d69s-191.i386.rpm 807b23473f0813c9c6385d08cc55b698 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/man-2.3.10d69s-191.src.rpm 0ff51500ef8914870cb1785ae3b999b6 SuSE-6.2 ftp://ftp.suse.com/pub/suse/i386/update/6.2/a1/man-2.3.10d69i-19.i386.rpm edbbe4c94b18802dc23a823d55d59761 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.2/zq1/man-2.3.10d69i-19.src.rpm eeeed80772476bb306d256e48ad99f95 SuSE-6.1 ftp://ftp.suse.com/pub/suse/i386/update/6.1/a1/man-2.3.10-85.i386.rpm 775db984e6129f10ede2b091bf725f0d source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.1/zq1/man-2.3.10-85.src.rpm 5c4b93a1cf941adeb853bff9263ca3a5 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/man-2.3.10d69s-182.sparc.rpm 39e097e929dbf4ca7626d5c7dcaf4980 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/man-2.3.10d69s-182.src.rpm df6900385722e5a7ddae18338eb0ef4c SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/man-2.3.10d69s-182.sparc.rpm 6c3bda62c576bd92ff7b741a3124e64e source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/man-2.3.10d69s-182.src.rpm c42b095b229f6b4c45bf7814ae0e1498 AXP Alpha Platform: SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/man-2.3.10d69s-194.alpha.rpm 3d83a75ff11426bc56fd9663bccee9be source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/man-2.3.10d69s-194.src.rpm 2033a16bc31ec5d81136eabf2508fd6d SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/man-2.3.10d69s-191.alpha.rpm f1ee85f46386298748bdb3d76d69e9f2 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/man-2.3.10d69s-191.src.rpm 82792838d464a1fbb14b2c5d79f4d064 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/a1/man-2.3.10d69s-190.alpha.rpm 5334e0f9efe1de48d7905166ced83c1b source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/man-2.3.10d69s-190.src.rpm 43992649e6ab51000bed5ac4e2f8fcae PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/man-2.3.10d69s-162.ppc.rpm 5bff5425484c5076023235b3779f22c6 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/man-2.3.10d69s-162.src.rpm 5caba422258827b139e21f6dab7f9b39 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/man-2.3.10d69s-162.ppc.rpm 832b8078f1c6b2d8d6edae98d26c3d44 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/man-2.3.10d69s-162.src.rpm 4d5647b6276fb6d641410e7eddc106f9 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/man-2.3.10d69s-163.ppc.rpm 13afa53aacaa939fd1b9dd509d995c2d source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/man-2.3.10d69s-163.src.rpm 2ffd94df5356669d89c1490a326c205d ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - netscape Netscape before Version 4.77 contains a bug that allows a remote attacker to store JavaScript code in the comment filed of GIF files that are contained in a viewed page. This code can be executed. Update packages for the SuSE Linux distributions 6.3, 6.4, 7.0 and 7.1 can be found on our ftp server at ftp://ftp.suse.com/pub/suse/i386/update/7.1/xap1/netscape-4.77-21.i386.rpm 1e2de825b3386d80a3731760b9e7f323 ftp://ftp.suse.com/pub/suse/i386/update/7.0/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.4/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.3/xap1/netscape-4.77-21.i386.rpm 13f303944c9ac0863591b03c4eb75501 The packages are gpg-signed. See the section above about downloading and verifying rpm packages. The complexity of the netscape browser suggests by nature that more security related problems will be found, we will not issue a dedicated security announcement for the netscape package any more. Security- inclined users may please see the future security announcements in section 2) for information about security related problems with the netscape package. - gpg/gnupg The gpg update package that can be found on our ftp server upgrade your installation of gpg to the version 1.0.5. We have experienced stability problems when the turkish locale was used. We recommened our users to wait for the official SuSE Security Announcement about gpg/gnupg before performing the upgrade since we expect more changes to the package. - pine Most of the supported distributions have pine update packages in the update area of the ftp server that update the pine package to version 4.33. Many vulnerabilities have been found in versions before 4.33, and it is recommended to perform the upgrade. Please note that not all packages have been built yet. See the update directory for your distribution (like i386/update/7.0/n1) for pine-4.33 packages. - dqs dex(a)raza-mexicana.org has found an exploitable buffer overflow bug in the dsh program from the dqs package on SuSE Linux distributions. To workaround the problem, do "chmod -s /usr/bin/dsh" and change the files /etc/permissions* to reflect the change. If you do not need the dqs package, then deinstall it (rpm -e dqs). We are working on update packages that fix the problem. - samba Insecure temporary file handling is the cause for a new samba version 2.0.9 that can be found as rpm packages in the n1/ directory of your distribution. It is recommended to install the update package if your users have local shell access to your samba server (this bug is not remotely exploitable). We are currently investigating some oddity in the behaviour of the samba package and will send a security announcement as soon as we have clarified the problems. The problems were present in earlier releases/versions of the samba package as well. By consequence, the installation of the update package is of low risk for the functionality of your system. ______________________________________________________________________________ 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 --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =================================================== SuSE's security contact is <security(a)suse.com>. The <security(a)suse.com> public key is listed below. =================================================== Regards, Roman Drahtmueller <draht(a)suse.de>. - - | Roman Drahtmüller <draht(a)suse.de> // "The best way to pay for a | SuSE GmbH - Security Phone: // lovely moment is to enjoy it." | Nürnberg, Germany +49-911-740530 // - Richard Bach | - - ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA== =rVRn - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOxPuI3ey5gA9JdPZAQFQ6Af/RQcFiRc+py8vrcWHVefHS4QslSfR2TeL XNe0rX/RtrqYUhOWpJyyZgUNi90kr4scohpYlN0xJSrwGrRdWToHPYTUl78iETdJ G24O34XVBuIn4qab31v48yphYlCvrKgc+zXhjZ+JdEAZFnmgOUQ7s2ICu/Xfk2DV gB/YpiVNB6GeQUmEm8wODBinlzNX/XexxO04z24QH2BWwOFPXhUU47KAMeCexnj4 kzcczKx004CQKcHLgsFaBp22mpZDRRaxvoXYWFAuPJuOGlrvJZ1FB4Xy3T3R84bu qO9oSR/CWPjzRoAdI/HbwIQLml2GSO+bynx/OyGYFjMR+lzpBHWGZQ== =Pqq3 -----END PGP SIGNATURE-----

1 1

freeSwan with kernel 2.2.19
by Guido Tschakert 30 May '01

30 May '01

Hello list, I want to use FreeS/WAN 1.8 with SuSE7.1. The problem is, that I have updated the Kernel to 2.2.19 and the IPSEC-Module is compiled for Kernel 2.2.18.(insmod does not load the module). Is there an easy solution to use this module with the 2.2.19-Kernel or do I have to compile this module. (And how can I do it in a simple way without compiling all modules or the whole FreeS/WAN-packet) TIA Guido I -- ----------------- Guido Tschakert SRC GmbH, SysAd -----------------

1 0

(offtopic) "Should-be Dead" shell sessions still alive
by RoMaN SoFt / LLFB!! 30 May '01

30 May '01

Sorry for writing to this ml, but I didn't want to subscribe the other Suse ml only for asking this Q. In my SuSE 6.4 boxes when a shell session is broken (the user doesn't issue the normal "logout" command but disconnect telnet/ssh, for example) the bash login process keeps alive forever. I think this doesn't happen on 7.0-*. Do I have to update some package or change any configuration line at /etc/*? Example: game1:/usr/local/apache/conf # who davnav pts/2 Apr 3 17:26 (192.168.0.233) parker pts/3 Apr 6 12:07 (192.168.0.68) parker pts/5 Apr 6 12:34 (192.168.0.68) parker pts/6 Apr 17 10:57 (192.168.0.69) parker pts/7 Apr 17 13:58 (192.168.0.69) parker pts/10 Apr 26 13:34 (juan.herreraii) parker pts/12 May 8 10:23 (juan.herreraii) parker pts/13 May 9 09:54 (juan.herreraii) parker pts/14 May 10 08:12 (juan.herreraii) roman pts/15 May 9 14:53 (roman) roman pts/16 May 10 09:24 (roman) game1:/usr/local/apache/conf # \ps aux | grep parker parker 32722 0.0 0.2 2248 1324 pts/3 S Apr06 0:00 -bash parker 304 0.0 0.2 2248 1312 pts/5 S Apr06 0:00 -bash parker 23811 0.0 0.2 2252 1316 pts/6 S Apr17 0:00 -bash parker 24161 0.0 0.2 2252 1316 pts/7 S Apr17 0:00 -bash parker 15142 0.0 0.2 2256 1320 pts/10 S Apr26 0:00 -bash parker 9671 0.0 0.2 2256 1320 pts/12 S May08 0:00 -bash parker 11943 0.0 0.2 2256 1320 pts/13 S May09 0:00 -bash parker 20885 0.0 0.2 2256 1320 pts/14 S 08:12 0:00 -bash parker 21117 0.0 0.2 1992 1296 ? S 09:55 0:00 proftpd: parker - juan.herreraII: IDLE root 21121 0.0 0.0 1136 444 pts/16 S 09:56 0:00 grep parker game1:/usr/local/apache/conf # cat /etc/SuSE-release SuSE Linux 6.4 (i386) VERSION = 6.4 game1:/usr/local/apache/conf # Thanks in advance ;) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** RoMaN SoFt / LLFB ** roman(a)madrid.com http://pagina.de/romansoft ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 1

Problems compiling freeswan 1.4
by audun.fosselie.hansen＠satcom.nera.no 30 May '01

30 May '01

Audun-Fosselie Hansen/NOSAT/NERA 2001-05-29 14:09 To: suse-security(a)suse.com cc: Subject: Problems compiling freeswan 1.4 I know version 1.4 is old, but it is for testing and not for use in the real world. I have installed the freeswan source file from Suse 7.0 and are running rpm -bc SPECS/freeswan.specs. The compiling ends with the following messages: + test -e /usr/src/linux/.config + grep CONFIG_IPSEC /usr/src/linux/.config CONFIG_IPSEC=m + yes '' + make -C /usr/src/linux oldconfig make: Entering directory `/usr/src/linux-2.2.16' make: *** No rule to make target `oldconfig'. Stop. make: Leaving directory `/usr/src/linux-2.2.16' Bad exit status from /var/tmp/rpm-tmp.96871 (%prep) Anyone who can tell me what to do?? I am not too experienced in this kind of problems. Audun Hansen

2 1