February 2000 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement - mysql
by marc＠suse.de 12 Feb '00

12 Feb '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: mysql < 3.22.30 Date: Fri, 11 Feb 2000 21:54:49 GMT Affected SuSE versions: all Vulnerability Type: remote database access SuSE default package: no Other affected systems: all unix systems using mysql < 3.22.30 ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note, that that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description A bug in the authentication function of mysql allows anyone who knows a valid username to successfully authenticate as that users in no more than 32 tries. 2. Impact Remote users may gain access to the mysql database data. 3. Solution Update the package from our FTP server. Please note that it will take some time until rpms for 6.1 are available, because the security patch does not work on that tree. As a workaround, you might try the rpm for SuSE 6.2 ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (6.1 updates are not available yet. You might try the 6.2 rpm in the meantime.) f54f552d0d7137ae9c2fa44968e32e25 ftp://ftp.suse.com/pub/suse/axp/update/6.3/pay1/mysql-3.22.30-4.alpha.rpm ff61bdf78c72bb8906578533581188b5 ftp://ftp.suse.com/pub/suse/i386/update/6.2/pay1/mysql-3.22.30-4.i386.rpm 7e8415360e52a100ffb759099dbc8f25 ftp://ftp.suse.com/pub/suse/i386/update/6.3/pay1/mysql-3.22.30-4.i386.rpm ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are send to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - ------BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - ------END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOKXYLney5gA9JdPZAQF2XwgAlNWcXOQbDIBJvZNEVAG4jcjdMWUk+CKJ nuB3DRyYTfzN1bY7xw3YzdMLWjZtcy3viEjTIfNKsworG6KbOaNuZ/99IxOJjH6a p+D1RX9XP5E5nxKtiqCnNgsWRp/LAwzQJbsoD/68RPQ7vZwVjGVe1eFYeTh+w7xO 3GD9Y2MNuPi6oUTY9XytWihOO5HbGYcmVV2Ii1bOqNuh7RNVczA+Q3Tc1uD83mrW sfak1Zn1aI403hwxMAKdnRtXxtCNYeqdchIh389U65qOdvty978gqKBmEHcJXhGq XK17XmPRY2yu7zxu3RO5+yI42QUX8378Ghh6v0v+KRFXH00QuCktvw== =/NcB -----END PGP SIGNATURE-----

1 0

md5 checksums
by Till Rotter 12 Feb '00

12 Feb '00

Hi Everybody! Please, can somebody tell me how to verify a md5 checksum? I read the rpm manpage and it says something about md5 checksums there, but I don't know how to pass a given checksum to rpm. In the manpage it says something about a database, but surely the checksum of an update-package wouldn't be in a database, would it? If it were, it wouldn't be provided along with the package now, would it? Thanks in advance, Till Rotter

4 3

Web attack used university computer
by Fred A. Miller 11 Feb '00

11 Feb '00

http://www.msnbc.com/news/367495.asp?0a=2104480

1 0

SuSE Security Announcement - mount
by marc＠suse.de 10 Feb '00

10 Feb '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: util < 2.10f Date: Thu Feb 10 20:03:43 CET 2000 Affected SuSE versions: all Vulnerability Type: (unlikely) local root compromise SuSE default package: yes Other affected systems: all linux systems using util < 2.10f ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update it as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description The mount/umount command doesn't do proper bounds checking on user input. 2. Impact If an attacker executes mount/umount with a long relative pathname, it will overwrite dynamic allocated memory of the realpath function. It is possible that an attacker could gain root privileges by modifying the heap data, however we were not able to exploit it. 3. Solution Update the package from our FTP server or remove the suid bits. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (For SuSE 6.0, please use the 6.1 updates) 8fffa6e7ce36b51f190652189629a2c0 ftp://ftp.suse.com/pub/suse/axp/update/6.1/a1/util-2.10f-4.alpha.rpm 121bf103d58cc9e959f910a0437285bd ftp://ftp.suse.com/pub/suse/axp/update/6.3/a1/util-2.10f-0.alpha.rpm 96166ddbe17ef1aabf6531a34e48d386 ftp://ftp.suse.com/pub/suse/i386/update/6.1/a1/util-2.10f-3.i386.rpm 285c0d41b2932b068fdac3f860e3446e ftp://ftp.suse.com/pub/suse/i386/update/6.2/a1/util-2.10f-4.i386.rpm 452143c94bcae39ec9adc5922be9acc9 ftp://ftp.suse.com/pub/suse/i386/update/6.3/a1/util-2.10f-4.i386.rpm ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are sent to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - ------BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - ------END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOKM1+ney5gA9JdPZAQGAJAgAnX7rqJwG9/PVSaextxIcoV33tZMAVq11 xMCUYWk6iF2fBA+cVNbG0LwwGRP0bd7NzzJxLyfNZ/WgLNLh0hHa9sE7Gg8XLc33 +S7C75ec+lFX2TOpalmdCM2BrgQFpXNLE0mY52D7l4SO63U3bAjFbMHpDQQFPSwJ 8g66zH3owVSppv792ASqc41k5s6nemd99tb7I3jL1XBUk9cdKUYzPUxaY5bdLCzp DLrUYozppU2qNork9T+iCz9ZFLiEZNjrZirqfcaemWnySAvPJIsO9wbyNfIsC2oS gwZe6QrtZHGO5Wx0db/ZLECpPXx3B0Vt5KSTk+gW53SJAV8M9hN57g== =e00I -----END PGP SIGNATURE-----

1 0

Delegate [Fwd: Re: application proxies?]
by Rainer Link 10 Feb '00

10 Feb '00

Hi! IIRC, there was a small discussion about DeleGate in the past (some weeks ago, I think). Therefore I decided to forward you this post from BugTraq. best regards, Rainer Link -------- Original Message -------- Subject: Re: application proxies? Date: Thu, 10 Feb 2000 00:59:49 -0500 From: Omachonu Ogali <oogali(a)intranova.net> Reply-To: Omachonu Ogali <oogali(a)intranova.net> To: BUGTRAQ(a)securityfocus.com DO NOT USE DELEGATE. Here are some of my findings with delegate, and I'm still not done yet. -- snip -- Delegate Problems ================= Start of access.c: * Line 41 defines a fixed-length variable (authority - 1024 bytes). - scan_AUTH() does no bound checking and blindly uses strcat() to append to the variable. * Line 57 defines a fixed-length variable (xauth - 1024 bytes). - findAuth() does no bounds checking and blindly passes all three variables to sprintf(). * Line 66 calls sprintf() again to output into a fixed-length variable (xauth - 1024 bytes). * Line 74 defines a fixed-length variable (userhost - 256 bytes). - auth_manager() does no bound checking and blindly passes two variables to sprintf() with no bounds checking. * Line 87 defines a fixed-length variable (auth - 256 bytes). - auth_anonftp() does no bounds checking and blindly passes the anonymous FTP password to sprintf(). * Line 116 defines a fixed-length variable (hostb - 256 bytes). - NotifyPlatform() calls getClientHostPort() which calls getClientHostPortAddr() blindly copies (strcpy) the address passed from NotifyPlatform into a 32-byte buffer defined in the 'Connection' structure. * Line 145 defines a fixed-length variable (myuri - 256 bytes). - clientIF_HP() calls _clientIF() which blindly outputs (sprintf) the host and port information into the variable 'myuri' after receiving its data from 'myhp'. * Line 145 defines a fixed-length variable (client - 256 bytes). - makeForwarded() calls getClientHostPort() which calls getClientHostPortAddr() which blindly copies (strcpy) the address passed from NotifyPlatform into a 32-byte buffer defined in the 'Connection' structure. * Line 146 defines a fixed-length variable (myhp - 256 bytes). - clientIF_HP() calls _clientIF() which returns data that is not bound-checked into the variable 'myhp' for latter consumption by sprintf(). * Line 168 defines a fixed-length variable (atype - 128 bytes). - makeAuthorization() calls sscanf() to retrieve arguments and cannot bound check the data resulting in a buffer overrun. * Line 168 defines a fixed-length variable (afmt - 128 bytes). - makeAuthorization() calls sscanf() to retrieve arguments and cannot bound check the data resulting in a buffer overrun. * Line 169 defines a fixed-length variable (gauth - 256 bytes). - makeAuthorization() calls strfConn() to return the protocol desired into 'gauth', and two more strings are appended (strcat) without bounds checking. * Line 169 defines a fixed-length variable (eauth - 256 bytes). - makeAuthorization() calls str_to64() specifying the size as eauth as 512 bytes instead of 256 bytes. * Line 215 defines a fixed-length variable (host - 256 bytes). - makeClientLog() does not perform bound checking on the results returned by strfConn() allowing for a buffer overrun. * Line 215 defines a fixed-length variable (iuser - 256 bytes). - makeClientLog() does not perform bound checking on the results returned by strfConn() allowing for a buffer overrun. * Line 215 defines a fixed-length variable (auser - 256 bytes). - makeClientLog() does not perform bound checking on the results returned by strfConn() allowing for a buffer overrun. * Line 320 uses strcpy() blindly. - No bounds checking is performed before copying 'clhost' into Client_Addr which is the 32-byte fixed-length variable 'cl_Addr' in the structure Connection defined in delegate.h. * Line 321 uses strcpy() blindly. - No bounds checking is performed before copying 'clhost' into Client_Addr which is the 128-byte fixed-length variable 'cl_Host' in the structure Connection defined in delegate.h. * Line 429 defines a fixed-length variable (buf - 1024 bytes). - scanIdent() does not perform bounds checking on the variable passed and blindly copies it (strcpy) into 'buf'. Allows an attacker to create their own identd trojan/daemon and pass arbitrary code. * Line 449 defines a fixed-length variable (addrhostport - 256 bytes). - getClientHostPortAddr() does not perform bounds checking on the results returned from getpeerName(). Allows an attacker to create their own fake DNS reply and pass arbitrary code. * Line 449 defines a fixed-length variable (addr - 256 bytes). - Suffers from insufficient bounds checking on the result returned by getpeerName() and receives data from sscanf(). * Line 449 defines a fixed-length variable (host - 256 bytes). - Suffers from insufficient bounds checking on the result returned by getpeerName() and receives data from sscanf(). * Line 456 uses strcpy() blindly. - No bounds checking is performed before copying 'addr' into Client_Addr which is the 32-byte fixed-length variable 'cl_Addr' in the structure Connection defined in delegate.h. * Line 457 uses strcpy() blindly. - No bounds checking is performed before copying 'host' into Client_Addr which is the 128-byte fixed-length variable 'cl_Host' in the structure Connection defined in delegate.h. * Line 528 defines a fixed-length variable (host - 1024 bytes). - No bounds checking is performed on 'hostport' before its blindly passed into 'host' by sscanf(). * Line 549 defines a fixed-length variable (user - 128 bytes). - A fixed-length variable is passed to getClientUser0() and it suffers from insufficient bounds checking noted on line 429. * Line 584 defines a fixed-length variable (host - 256 bytes). -- snip -- On Wed, 9 Feb 2000, Zahemszky Gabor wrote: > > Hello, > > > > I'm preparing an article on FreeBSD firewall tools. So far I plan to > > cover ipfw & natd, ipfilter & ipnat, fwtk, kern.securelevel, and > > mention snort and nessus as a sideline. > > > > I'd like to present as many applications as possible. The major lack > > I see is a choice of application-level proxies such as fwtk. Are there > > some I'm not aware of? > > If I remember well, delegate is another proxy (but somebody pointed out, > that there are so many unsafe - strcpy/etc - functions in it). > > ZGabor at CoDe dot HU > > -- > #!/bin/ksh > Z='21N16I25C25E30, 40M30E33E25T15U!' ;IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ ';set $Z ;for i { [[ $i = ? ]]&&print $i&&break;[[ $i = ??? ]]&&j=$i&&i=${i%?};typeset -i40 i=8#$i;print -n ${i#???};[[ "$j" = ??? ]]&&print -n "${j#??} "&&j=;typeset +i i;};IFS=' 0123456789 ';set $Z;X=;for i { [[ $i = , ]]&&i=2;[[ $i = ?? ]]||typeset -l i;X="$X $i";typeset +l i;};print "$X" > > > To Unsubscribe: send mail to majordomo(a)FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > Omachonu Ogali Intranova Networking Group

1 0

4 February 2000 IETF Excludes Wiretapping
by Fred A. Miller 10 Feb '00

10 Feb '00

GOOD NEWS!! Fred ____________________________ 4 February 2000 IETF Excludes Wiretapping The Internet Engineering Task Force (IETF) has voted against incorporating wiretapping capabilities into the next generation of Internet protocols. The IETF says that because it is an international standards organization, incorporating net wiretapping would subject the rest of the world to US law. The IETF also expressed concerns that built-in net tapping capabilities hold the potential for abuse. http://www.wired.com/news/print/0,1294,34055,00.html http://www.currents.net/newstoday/00/02/04/news4.html -- ----/ / _ Fred A. Miller ---/ / (_)__ __ ____ __ Systems Administrator --/ /__/ / _ \/ // /\ \/ / Cornell Univ. Press Services -/____/_/_//_/\_,_/ /_/\_\ fm(a)cupserv.org

1 0

Antwort: Re: [suse-security] netstat -s
by gerhard.possler＠westernacher.de 09 Feb '00

09 Feb '00

Hi, ok, some details: ping www.ibm.de from that particular system show : host unknown but from any other system I get an response. this is an 3Com Fast Ethernet PCI card in a Firewall (!!?). So I think it is an (security) problem, or? alex medvedev <alexm(a)pycckue.org> am 09.02.2000 19:23:20 An: suse-security(a)suse.com Kopie: Thema: Re: [suse-security] netstat -s hi, does not sound like security problem. sounds like the socket buffer space is too small. maybe tx/rx queue size on the adapter? btw, i can ping both sites :) On Wed, 9 Feb 2000 gerhard.possler(a)westernacher.de wrote: > Hi, > can tell me somebody what that is: > > by using: netstat -s > > I receive: > > TcpExp: > 10 packets pruned from receive queue because of socket buffer > overrun > 221088 packets dropped from out-of-order queue because of socket > buffer overrun > > the problem is I cannot ping www.ibm.de but www.de.ibm.com > www.ibm.de is an alias of www.de.ibm.com --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com ------------------------------------------------------------------------ Gerhard Possler "Wer neue Wege geht, braucht starke Partner." Westernacher AG Am Hubengut 3 76149 Karlsruhe, Germany phone: +49-721/9772-0 fax: +49-721/9772-249 http://www.westernacher.de

1 0

netstat -s
by gerhard.possler＠westernacher.de 09 Feb '00

09 Feb '00

Hi, can tell me somebody what that is: by using: netstat -s I receive: TcpExp: 10 packets pruned from receive queue because of socket buffer overrun 221088 packets dropped from out-of-order queue because of socket buffer overrun the problem is I cannot ping www.ibm.de but www.de.ibm.com www.ibm.de is an alias of www.de.ibm.com Thanks! ------------------------------------------------------------------------ Gerhard Possler "Wer neue Wege geht, braucht starke Partner." Westernacher AG Am Hubengut 3 76149 Karlsruhe, Germany phone: +49-721/9772-0 fax: +49-721/9772-188 http://www.westernacher.de; ------------------------------------------------------------------------ Gerhard Possler "Wer neue Wege geht, braucht starke Partner." Westernacher AG Am Hubengut 3 76149 Karlsruhe, Germany phone: +49-721/9772-0 fax: +49-721/9772-188 oder Home Office: 0931-6668106 http://www.westernacher.de

2 1

firewall 1.9 configuration for MS PPTP VPN?
by Drew A. Harris 09 Feb '00

09 Feb '00

I'm running version 1.9 of the suse firewall and I need to get my VPN client on a win95 workstation to pass through. If I open everything with ipchains, it works. What do I need to change in the rc.firewall to allow these vpn (pptp) packets through without compromising my security? I'm quite ignorant about firewalls, so please give me "der kinder" version. Thanks, DREW. ************************************************************************* Drew A. Harris, DPM, MPH President, NJ Public Health Association Chief, Podiatric Surgery & Director, Wound Healing Center St. Elizabeth Hospital, Elizabeth, NJ 911 North Wood Avenue -- Linden, NJ 07036 908-925-1350--Fax: 908-925-1359 dharris(a)njpha.org *************************************************************************

1 0

SuSE Security Announcement - make-3.77
by thomas＠suse.de 09 Feb '00

09 Feb '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: make-3.77-44 and earlier Date: Wed Feb 9 17:28:43 CET 2000 Affected SuSE versions: 6.1, 6.3 Vulnerability Type: locale root compromise SuSE default package: no Other affected systems: all linux systems using make ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update it as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description If GNU make is fed with Makefiles via stdin it creates temporary files in /tmp without checking for links. 2. Impact A malicous user could execute commands with the privileges of the user executing make. This security hole could lead to local root compromise if root passes Makefiles to make through stdin. 3. Solution Update the package from our FTP server. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (For SuSE 6.0, please use the 6.1 updates) e387c78a7046a05d3948c85519904dc6 ftp://ftp.suse.com/pub/suse/axp/update/6.1/d1/make-3.78.1-4.alpha.rpm fb82691700e3238ed938b41f2933a1f0 ftp://ftp.suse.com/pub/suse/axp/update/6.3/d1/make-3.78.1-5.alpha.rpm 54e6b458a2e7ba096ad3b0743fef7073 ftp://ftp.suse.com/pub/suse/i386/update/6.1/d1/make-3.78.1-3.i386.rpm 099cdc6529b36e085b239af1c0337faf ftp://ftp.suse.com/pub/suse/i386/update/6.2/d1/make-3.78.1-2.i386.rpm e5eee118d92e61d4b17b3bef112760af ftp://ftp.suse.com/pub/suse/i386/update/6.3/d1/make-3.78.1-2.i386.rpm ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are sent to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - ------BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - ------END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOKGPg3ey5gA9JdPZAQFavwf8DK5Ff0IBQomqGbPeErxoAkVonQbqqltM eC6nTvLBO7rs2WzEtlIiWZ07us+SAlEKyI0K1BFlQYIyximCIfizZlHF7GTm/iDb 9qtJnDnG4OLHkdwlRcul51y2PmwIQ94Kl+cFauHdPr2mC7x+9KZugKUDlg/5oe9+ kd7ybcYwdREyfTsoyIbrorRqVBeXpzUbD9w5J5FAW310DAgOdysT667MQ4cA9WaB 2Bp5K3WaSaAFInknQZsDlxHKEsgAcdoOQvCaz02glkB3ipXBzK+dBGbbMesU8Evl 1MKkfVW0nyA45GVk+UZX2UtRRv+Zatg/ENYmryOY0QEO1l0wBiPdkA== =il3b -----END PGP SIGNATURE-----

1 0