January 2002 - openSUSE Security - openSUSE Mailing Lists

RE: [suse-security] remote admin: ssh vs. webmin
by Barry Gill 10 Jan '02

10 Jan '02

:: you can look into sudo ...and you can set PermitRootLogin ::to "no" in sshd_config if you dont want to log in as root. ::hope this helps The other nice thing about sudo is that you can set only specific commands can be run via sudo, and you can LOG all activity. :)

1 0

SuSEfirewall2 - question
by James Bliss 10 Jan '02

10 Jan '02

I hope this is an easy question. I have setup access to my external interface from my internal macines in the custom configuration file. But this only allows for www access. I need to setup so that my internal network can access an application throught the external nic on port 5000 - this is a chat application. How do I do this? Currently I get the error SuSE-FW-NO_ACCESS->FWEXT. network: Internet | | | (eth1) SuSE box (web server and chat server) (eth0) | | | 192.168.*.* internal network I can access it through the eth0 IP address, but cannot access it through the eth1 IP address. I can access teh web server through the IP address of either network interface. I need this for testing purposes. Thanks, Jim

2 1

Xchat Vulnerability
by adam 10 Jan '02

10 Jan '02

Just so everyone knows, the version of xchat provided with SuSE 7.1 has been tested and is vulnerable to this attack. ========================================================================== ======= xchat 1.4.2 and 1.4.3 IRC session hijacking vulnerability ======== ========================================================================== It is possible to trick xchat IRC clients (1.4.2, 1.4.3) into sending commands to the IRC server they are on, potentially allowing for social engineering attacks, channel takeovers, and denial of service. Vendor updates for affected versions soon. http://security-archive.merton.ox.ac.uk/bugtraq-200201/0101.html </paste> Adam Daniel Technical Consultant ----------------------------------------------------------------------- FORENSIC DATA SERVICES PTY LIMITED http://www.forensicdata.com.au ------------------------------------------------------------------------ The information contained in this e-mail is confidential and is intended solely for the addressee. If you received this e-mail by mistake please notify us immediately and delete all copies of this message. You must not disclose or use in any way the information in the e-mail. It is the responsibility of the recipient to virus scan this e-mail and any attachments included.

1 0

AW: AW: [suse-security] IP Forwarding - HELP
by OKDesign oHG Security Administrator 10 Jan '02

10 Jan '02

Here are two URL for iptables which were sent to me in answer to my question about masquerading: http://bolug.uni-bonn.de/wissen/masquerading.html http://www.fruehbrodt.org/artikel/netfilter.html Stephan -----Ursprüngliche Nachricht----- Von: nico(a)edoc.co.za [mailto:nico@edoc.co.za] Gesendet: Mittwoch, 9. Januar 2002 07:45 An: OKDesign oHG Security Administrator Betreff: Re: AW: [suse-security] IP Forwarding - HELP Hi, I'm trying to achive exactly the same with a Linux 2.4 kernel. Would you mind sending me the info as well? Thanks Nico > Hi Dan, > > it depends on which Kernel-version you use. If you use 2.4 you need > iptables. Exactly this point was discussed during the last days (I'm > sure on this 'cause it was me who asked about Masquerading *g*). If > you use 2.2 or earlier you need ipchains. Which syntax should be used > has been written in my first post about this. If you don't have it > anymore, tell me. I can write it again. Back to the roots of your > question: IP-forwarding alone is not enough. You need Masquerading > because the (ethernet-)IP of your Windozebox is a private IP and not > able to be routed over the internet. So the linux-box has to change > the sender-IP of the packets to his official IP (granted from your > provider, most likely to be a dynamic one) in order to enable > answer-packets to find the way back to you. Then your router (the > linux-box acts exactly like a router) send the answers back to your > windozebox. This is what masquerading means. Again, tell your > kernelversion and we can tell you the syntax. > > Stephan > > -----Ursprüngliche Nachricht----- > Von: Dan Banyard [mailto:dan@www.edentify.com.au] > Gesendet: Mittwoch, 9. Januar 2002 04:20 > An: suse-security(a)suse.com > Betreff: [suse-security] IP Forwarding - HELP > > > Hi > > I have two machine, one Windows NT box and a Linux box (which is > connected to the www via a modem) and these two machine are connected > directly via ethernet. > > I am trying to set up my Linux box so I can get access to the www from > the Windows NT box via the Linux box. So far I have enabled IP > Forwarding in the rc.config file. I am really unsure what to do now > to get this to work - I have read countless linux documents about > setting up masquerading but the examples don't seem to comply with > Suse. Do I have to enable the firewall to get this working ? are > there others things I have to set ? > > Any help would be great. > > Thanks > > Dan > > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com > > > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com > >

5 4

Re: Masquerading unter Kernel 2.4
by OKDesign oHG Security Administrator 09 Jan '02

09 Jan '02

Allright, for the first i'd like to thank those who pointed me into the right direction towards iptables; I didn't know that Kernel 2.4 per default only uses iptables and no ipchains anymore. I now got it to work with iptables. My second problem is only partially solved. The error was/is definitely that rp-pppoed does not set the new defaultroute properly to ppp0 but to eth1, which is wrong. I checked /etc/ppp/options, but couldn't find any relevant option. So I extended ip-up with "route del default" and "route add default ppp0", which works; but this couldn't be the way it should be done. Any ideas what could be the reason why rp-pppoed doesn't change the default-route ? And one last question (okay, at least by now *g*): How do I tell linux to forward requests to a specific port to a specific machine in the LAN ? With Kernel 2.2 I used ipmasqadm, but this order is also unknown to Kernel 2.4... Thanks in advance Stephan

6 8

Attack or not?
by Erwin Zierler - stubainet.at 09 Jan '02

09 Jan '02

Hi all, I have recently found the following lines in /var/log/messages on one of my servers running SuSE 7.0, kernel 2.2.16, openssh-2.1.1p1-19: Dec 28 09:21:10 server -- MARK -- ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ [many many more of this] ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ Dec 28 14:34:46 server syslogd 1.3-3: restart. This server is connected to the internet via ADSL and sits behind a Zyxcel Prestige 310 where port 22 is NATed to the server. This is for remote administration - everything else on the Zyxcel is closed to the outside world. Looks to me like a buffer overflow with following crash, but then there is this time gap between the long line of ^@'s and the server restart 09:21 - 14:34 which worries me. I have not reached anyone there so I'll have to wait until next week to find out whether they maybe did a hard-boot or something. last shows: reboot system boot 2.2.16 Fri Dec 28 14:34 (1+20:48) reboot system boot 2.2.16 Fri Dec 28 11:56 (1+23:26) Checking the system with chkrootkit gave me only one wierd line: Checking `wted'... 1 deletion(s) between Fri Dec 28 11:56:50 2001 and Fri Dec 28 11:56:50 2001 Anyway, I wonderd if anyone has seen something similar yet and if I have to worry. Thanks in advance for your input. Erwin

10 11

SuSE Security Announcement: mutt (SuSE-SA:2002:001)
by Roman Drahtmueller 09 Jan '02

09 Jan '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: mutt Announcement-ID: SuSE-SA:2002:001 Date: Monday, Jan 7th 2001 20:30 MET Affected SuSE versions: 6.4, 7.0, 7.1, 7.2, 7.3 Vulnerability Type: local privilege escalation Severity (1-10): 6 SuSE default package: yes Other affected systems: systems with the mutt mailer installed Content of this advisory: 1) security vulnerability resolved: mutt 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 mutt, a popular mail client for Linux-like systems, is vulnerable to a buffer overflow that is remotely exploitable. We have added patches to the versions of mutt as shipped with the affected distributions to fix the problem. We recommend to install the update package for your product and to restart all running instances of mutt. We thank Joost Pol for reporting the problem to the makers of mutt. 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. NOTE: The SuSE Linux 7.0 distribution was shipped with two packages that contain the mutt mail program: "mutt" and "muttssl". For legal reasons, the muttssl package is available from the German ftp server ftp.suse.de. You can find out which version of the mutt package you are using with the following command: rpm -qf /usr/bin/mutt You only need to download and install the update package for the package that is installed on your system. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/mutt-1.3.22.1i-105.i386.rpm 65dd9854d16c9e3178aaff935486ab8a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/mutt-1.3.22.1i-105.src.rpm 6efacb822144a49de85bb417f677dba6 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/mutt-1.3.16i-71.i386.rpm 012e18c5cd2122218b396ae3600fa875 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/mutt-1.3.16i-71.src.rpm 5755b3e620a49bcb93893c524ecceb1b SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/mutt-1.3.12i-51.i386.rpm 40df9d8f98dcebc7057849a246f16e21 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/mutt-1.3.12i-51.src.rpm c689f09724acc63065a66e291dedc85b SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/mutt-1.2.5i-38.i386.rpm 1e7d85e9f499ebf4b3fe749d8669de9e ftp://ftp.suse.de/pub/suse/i386/update/7.0/sec1/muttssl-1.2.5i-14.i386.rpm a61d53a1e65299b558c799654e57203f source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/mutt-1.2.5i-38.src.rpm 543834be481fc61d8390a72cd42feeb0 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/7.0/zq1/muttssl-1.2.5i-14.src.rpm e67f148dee40a385136bc31240d51be6 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/mutt-1.0.1i-30.i386.rpm 53bae9b840be86683d670b784ec28c8c source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/mutt-1.0.1i-30.src.rpm c9ebd840ac72c5a3cfe9f45444f9a5e9 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/mutt-1.3.22.1i-27.sparc.rpm 946ba6c36bd8c46d1ab494f54b288dc6 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/mutt-1.3.22.1i-27.src.rpm 9009e2d4e4f32d437422b8e8ed12ef55 SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n1/mutt-1.3.12i-6.sparc.rpm 50f4f657a6a8bba819a34b2a05a9ea17 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/mutt-1.3.12i-6.src.rpm e7d3565e2063d76909c1a44e347f71de SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/mutt-1.2.5i-6.sparc.rpm fe06ca8880f38ea3064764614515f283 ftp://ftp.suse.de/pub/suse/sparc/update/7.0/sec1/muttssl-1.2.5i-8.sparc.rpm 3bdec5870cdddb5be68a8da3ff093de8 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/mutt-1.2.5i-6.src.rpm e3492d0390a7271def3955030a5451a0 source rpm: ftp://ftp.suse.de/pub/suse/sparc/update/7.0/zq1/muttssl-1.2.5i-8.src.rpm 3946004fc966f4135f47ff419bc2d1d6 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/mutt-1.3.12i-5.alpha.rpm 0cf2bd45bf05aded0468cad34774cac6 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/mutt-1.3.12i-5.src.rpm 7b04b3b10bb07c1d05ecd2322fd92be9 The AXP Alpha mutt packages for older distributions than 7.1 are currently being built and will appear at the usual location shortly. PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/mutt-1.3.22.1i-63.ppc.rpm 023ad9fde88518a3c07e183712305fd7 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/mutt-1.3.22.1i-63.src.rpm ed935acf49c36bcb290f4db37c7ae800 The PPC packages for SuSE Linux 7.1 are currently being built and will appear at the usual location shortly. SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/mutt-1.2.5i-12.ppc.rpm 476ed5e796692adda068a49ed2baf95e ftp://ftp.suse.de/pub/suse/ppc/update/7.0/sec1/muttssl-1.2.5i-11.ppc.rpm f4cb8011468d3e476fd7e24f733aec70 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/mutt-1.2.5i-12.src.rpm 550d058119f86c54a04d7506dbc1e878 source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/7.0/zq1/muttssl-1.2.5i-11.src.rpm caa60a063952cb54582bf7a0885d5d81 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/mutt-1.0.1i-30.ppc.rpm 2ae9d12e448f9f519441c74aeeb64d4d source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/mutt-1.0.1i-30.src.rpm e2ae04f334216cbcd82f906a3a2bb83f ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - SuSE Security receive reports about successful exploitation of the problems in the secure shell package (ssh-1.2.27) on SuSE systems. Please read the secure shell security announcement from February 2001, available at http://www.suse.de/de/support/security/adv004_ssh.txt . More additional information can be found in the openssh announcement at http://www.suse.de/de/support/security/2001_045_openssh_txt.txt . ______________________________________________________________________________ 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 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> 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 cleartext signature shows proof of the authenticity of the text. 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.6 (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 iQEVAwUBPDn2jHey5gA9JdPZAQHEUgf+Pxt00zDCMrVl1U4E9JwUUzuvhOAVIROd r90BInckzQa4yxD0k+BixBV3sNRK932QP0Yn3fPsNPRF6XfQNYdOLIybCrOESgY4 8SzwTSnIFjKptbFCWF8Ye/xB+FSd8Ffk/M7t6BtlYOS+7VPMB67nof/FiUyo3ceB ypdNfmmXvtde0bvQCypjNVfQ/V2omVir4E9vT+zNWrUs4RbvTAxnrgMIdlpzOmV0 AnETYIgiW8TLedJy6cJzHCPuGyH2RvQEDv16xbGxgFqHKwT2ZuSweCQ+kSCnFDus mpNPvRs1bLsspoPCHl8TZ05uppVfb4qN7hxIT9psdPU8/ABEPB+r+w== =4rJj -----END PGP SIGNATURE-----

2 2

[Fwd: IMP 2.2.7 (SECURITY) released]
by Martin Sckopke 09 Jan '02

09 Jan '02

The following mail was sent to suse-security a while ago. Today I looked up the patches on the update directory and still no IMP 2.2.7 :-( Is anything wrong with the patch or is there any other reason not to supply a patch to a security problem? While I'm at it: the recommended kernel for Suse EMail Server II still seems to be 2.2.16. Version 2.2.19 never seems to have made it to the update directory. Any reason? Keep up the (otherwise) good work, Martin -------- Original-Nachricht -------- Betreff: [Fwd: IMP 2.2.7 (SECURITY) released] Datum: Fri, 16 Nov 2001 09:02:40 +0100 Von: Martin Sckopke <m.sckopke(a)gis-systemhaus.de> Firma: GiS An: suse-security(a)suse.com I found the following message on Bugtraq. Is suse working on a fix for Suse EMail-Server II? The patch on the update-server is still 2.2.6. Martin "Brent J. Nordquist" wrote: > > The Horde team announces the availability of IMP 2.2.7, which fixes a > potential session hijacking vulnerability using a cross-site scripting > (CSS) attack. We recommend that all sites running IMP 2.2.x upgrade to > this version. > > The Horde Project would like to thank João Pedro Gonçalves from the > Phibernet Information Network <megas(a)phibernet.org> for discovering this > problem and alerting us. From his description: > > > - It's possible to hijack an imp/horde session using a cross-site > > script attack, quite similar to the one explored by Marc Slemko in his > > "Microsoft Passport to Trouble" paper. > > > > - After hijacking the cookies, the attacker can use the session and read > > the victim's mail. > > > > - All stable imp webmail versions, up to 2.2.6 including are vulnerable, > > the devel version, 2.3 and 3.0 Release Candidate 1 are not affected by > > this vulnerability. > > This release also has a new Chinese (Simplified) translation. > -- The three golden rules to ensure computer security are: Do not own a computer; do not power it on; and do not use it (Robert (Bob) T.Morris) GiS - Gesellschaft fuer integrierte Systemplanung mbH Martin Sckopke Tel. +49-6201-503-74 Junkersstr. 2 Fax +49-6201-503-66 D-69469 Weinheim m.sckopke(a)gis-systemhaus.de

1 0

IP Forwarding - HELP
by Dan Banyard 09 Jan '02

09 Jan '02

Hi I have two machine, one Windows NT box and a Linux box (which is connected to the www via a modem) and these two machine are connected directly via ethernet. I am trying to set up my Linux box so I can get access to the www from the Windows NT box via the Linux box. So far I have enabled IP Forwarding in the rc.config file. I am really unsure what to do now to get this to work - I have read countless linux documents about setting up masquerading but the examples don't seem to comply with Suse. Do I have to enable the firewall to get this working ? are there others things I have to set ? Any help would be great. Thanks Dan

3 3

Firewall2 configuration
by James Bliss 09 Jan '02

09 Jan '02

Hello everyone, I had thought that I was very familiar with SuSEfirewall2 and configuring it. But, I have run into a problem which I have not been able to come up with a solution for. I have included: iptables -A INPUT -i eth1 -s <internal IP range> -d <external IP address of eth1> -j ACCEPT this is in the fw_custom_before_antispoofing() section of the firewall2-custom.rc.config file. I have written an applet which needs to communicate on a port other than normal http, currently I have it coded to connect using port 7000. I am not able to connect using this applet from my internal machines attempting to connect to the external IP address of my server. Can anyone tell me where I need to put a rule to allow this (the proper place). I had thought the above code would handle this but it does not allow for connections from internal boxes to the external IP address of the server for higher ports. Thanks for everyone's help. Jim

1 0