November 2003 - openSUSE Security - openSUSE Mailing Lists

tls for qpopper
by mailinglists 19 Nov '03

19 Nov '03

Hi I set up TLS for Qpopper and it works nicely. Unfortunately all M$ MUAs only support SSL tunneling. Is there a way to set up Qpopper in a way to support SSL tunneling without using stunnel? Thanks & regards, Philipp

2 1

SUSE Security Announcement: sane (SuSE-SA:2003:046)
by Thomas Biege 19 Nov '03

19 Nov '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: sane Announcement-ID: SuSE-SA:2003:046 Date: Tuesday, Nov 18th 2003 14:30 MEST Affected products: 7.3, 8.0, 8.1 SuSE Linux Desktop 1.0 Vulnerability Type: remote denial-of-service Severity (1-10): 5 SUSE default package: yes Cross References: CAN-2003-0773 CAN-2003-0774 CAN-2003-0775 CAN-2003-0776 CAN-2003-0777 CAN-2003-0778 Content of this advisory: 1) security vulnerability resolved: several security vulnerabilities problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - ethereal - KDE - KDE wrong file permissions - ircd - mc - apache1/2 - proftpd - gdm2 - epic/epic4 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The sane (Scanner Access Now Easy) package provides access to scanners either locally or remotely over the network. Several bugs in sane were fixed to avoid remote denial-of-service attacks. These attacks can even be executed if the remote attacker is not allowed to access the sane server by not listing the attackers IP in the file sane.conf. Per default saned only accepts local requests. As a temporary workaround saned can be started via xinetd or inetd in conjunction with tcpwrapper to restrict remote access. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Intel i386 Platform: SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/sane-1.0.8-143.i586.rpm 5b728bc3ac724be64aa736dbebe2aa23 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/sane-1.0.8-143.i586.pa… 77ab2574c35513136076c4b2a77e9cbf source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/sane-1.0.8-143.src.rpm 6ddec5bdadb07f985a08e592cd4c68b3 SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/gra2/sane-1.0.7-217.i386.rpm 9438d81c7bd8b41dee948696f138c771 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/gra2/sane-1.0.7-217.i386.patch.… f461a294ab7d3638bf4b3e83f3910143 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/sane-1.0.7-217.src.rpm ea888fa0c4e6aaf41e23caaf4f68a1d2 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/gra1/sane-1.0.5-295.i386.rpm 53d25817ed9c53cf6078d3794862a13e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/sane-1.0.5-295.src.rpm 593a886a54482c841baa0fe9d43690c6 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/gra1/sane-1.0.5-114.sparc.rpm bdb7ce58c8d363a03dadc719c2421d84 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/sane-1.0.5-114.src.rpm 4d0f4994f1fc730edfcefa2d33fe456d PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/gra1/sane-1.0.5-179.ppc.rpm 83643306b81f0e89d4a5c96001a65ea5 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/sane-1.0.5-179.src.rpm fa277cfb3ec68aedb24de2ff2d13673f ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - ethereal A new official version of ethereal, a network traffic analyzer, was released to fix various security-related problems. An update package is currently being tested and will be released as soon as possible. - KDE New KDE packages are currently being tested. These packages fixes several vulnerabilities: + remote root compromise (CAN-2003-0690) + weak cookies (CAN-2003-0692) + SSL man-in-the-middle attack + information leak through HTML-referrer (CAN-2003-0459) The packages will be release as soon as testing is finished. - KDE wrong file permissions Due to a missing synchronisation during SuSE Linux 8.2 beta-testing phase some configuration files of KDE on SuSE Linux 8.2 are world- writeable. Please check the files in /etc/opt/kde3/share/config and add an appropritae line to /etc/permissions.local, like: /etc/opt/kde3/share/config/kmailrc root.root 0644 /etc/opt/kde3/share/config/kioslaverc root.root 0644 /etc/opt/kde3/share/config/kdeglobals root.root 0644 Set the new permission with 'chkstat -set /etc/permissions.local' as root. - ircd The Internet Relay Chat daemon is vulnerable to a remote denial-of- service attack. The attack can be triggered by irc clients directly connected to the daemon. Update packages are available on our FTP servers. - mc By using a special combination of links in archive-files it is possible to execute arbitrary commands while mc tries to open it in its VFS. The packages are currently tested and will be release as soon as possible. - apache1/2 The widely used HTTP server apache has several security vulnerabilities: - locally exploitable buffer overflow in the regular expression code. The attacker must be able to modify .htaccess or httpd.conf. (affects: mod_alias and mod_rewrite) - under some circumstances mod_cgid will output its data to the wrong client (affects: apache2) - proftpd A remote denial-of-service attack in the FTP server proftpd was fixed. The denial-of-service can be triggered by a one-byte buffer overflow with a fixed character. Therefore the bug can not be abused by an attacker to execute arbitrary code. If the binary is compiled with version 3.x of gcc this bug may not even lead to denial-of-service condition due to stack alignment. Update packages are available on our FTP servers. - gdm2 Two remote denial-of-service attacks were fixed in GDM. Update packages are available on our FTP servers. - epic/epic4 The well known IRC client epic can probably be exploited remotely by a malicious server. Update packages are available on our FTP servers. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SUSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SUSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an un-installed rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SUSE in rpm packages for SUSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SUSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SUSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)suse.de> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SUSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBP7o6Lney5gA9JdPZAQEtlAgAkgmF1N4phGHJiuWFOImYfObmzA/NWvG8 a7MdiWzoduVdrTtByzlBqRhxZyEdtGtfHngrMuj1pKhWrZK8uOqiYx6wIWqpfq0o 0P/wt5XnLAVQNpfm3CvqoC546bw/Xtt8LL7epsGgl2YnsAIj1Nn5qF28TBOArleB p/O2DavFGx+ASMQSfMNrRMp65chQWwaSypWk8AZBIwD+dqELQ06BeTSuBNix10vJ 37BMQOC5HUdkfx8p/YE6NShXErGANLHOcJBQKlg+5V+1WEbDWZ7Urpa0Sqi0zWTh WLa20xUpp6NfVMvhCqeCY7zdA35LNiGFkaU/O9+goMygBDzihdS5Ig== =mL8i -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de>, SUSE LINUX AG, Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- ... stay with me, save and ignorant, go back to sleep... - Maynard James Keenan

4 6

ulimit problem KDM/PAM with KDE 3.1.4 on SuSE Linux 9.0 - cannot get core dumps
by Bob Pearson 15 Nov '03

15 Nov '03

I cannot get core dumps logging in under KDM in KDE 3.1.4. I cannot get the dang core limit raised from zero! I do not know if it is a KDM or PAM problem. I have a freshly installed SuSE Linix Professional 9.0 system for the x86 (AMD Athlon) with a KDM patch applied. I have the following RPMs installed: kdebase3-kdm-3.1.4-36.i586.rpm kdebase3-kdm-3.1.4-48.i586.patch.rpm pam-modules-9.0-5 pam-0.77-124 $ rpm -qa | grep kdm kdebase3-kdm-3.1.4-48 I found this link on the Internet: http://cert.uni-stuttgart.de/archive/debian/laptop/2003/06/msg00209.html # ls -l /etc/security/limits.conf -r-------- 1 root root 1514 2003-11-11 19:09 /etc/security/ limits.conf And the two lines added to it: bobp hard core 60000 * hard core 60000 I have /etc/pam.d/xdm, /etc/pam.d/login and /etc/pam.d/other and to include session required pam_limits.so debug I get the following output in /var/log/messages: Nov 14 13:49:51 cueball kdm[2276]: pam_unix2: session started for user bobp, service xdm Nov 14 13:49:51 cueball pam_limits[2276]: reading settings from '//etc/ security/limits.conf' Nov 14 13:49:51 cueball pam_limits[2276]: process_limit: processing hard core 60000 for USER Nov 14 13:49:51 cueball pam_limits[2276]: process_limit: processing hard core 60000 for DEFAULT I have commented out the following line in /etc/profile #ulimit -Sc 0 # don't create core files And a getrlimit(2) shows: RLIMIT_CORE current = 0 max = 0 Does anyone have core dumps working under SuSE 9.0 using KDM? Does anyone have any suggestions? Thanks. I have a trouble ticket from SuSE on this but no response as of yet, it is driving me crazy. TIA. Best Regards, Bob Pearson -- _/_/_/ Bob Pearson Linux user number 333508 _/_/_/ gottadoit(a)mailsnare.net http://counter.li.org _/_/_/ I am unique and special, just like everyone else.

1 0

BUG or CRACKER
by MALDENER.de＠t-online.de 13 Nov '03

13 Nov '03

Hallo, Dear Linux-Friends, I found something curious in my Home Dir. : A file named ?$2@ and I could by no means delete it execpt with the mc. ?$2@ and with echo: ^W$2@ German text below, I dont speak very good english, but understand German,French and Englisch. You could relply in those Languages. Thank you in Advance ---German text---- Ich fand folgende Datei bei mir in $HOME: ?$2@ Sie liess sich nicht auf der Konsole (egal mit welcher Maskierung) sondern nur mit dem mc loeschen! Nach dem Loeschen mit dem mc musste ich im xterm folgende "Ausgabe" feststellen: (Ich hatte vom xterm aus den mc gestartet und nach Beenden des mc kehrte ich wieder in den xterm zurueck.) ich@rose:~> rm %!#%! .!#.! /!#/! &!#&! /!#/! C!#C! H!#H! E&#E& G!#G! F$#F$ [@#[@ C!#C! H&#H& E!#E! F##F# q<#q< ZC#ZC C!#G% F!#F! I(#I( x?#x? R!#R! :!#:! /!#/! 8!#8! /!#/! &!#&! )*#)* x:#x: %!#%! (-#(- w:#w: %!#*# ]>#]> y8#y8 ?$2@ (Es sollte wohl so einiges an Variablen-Inhalt geloescht werden) Wahrscheinlich war diese "Ausgabe" die Kommandofolge, die der mc mit der "Datei"?$2@ gemacht hat? P.S. mit dem Entfernen der "Datei"?$2@ war ja auch das mit nur echo sichtbare: ^W$2@ verschwunden. Die beiden Dateien ?$2@ und ^W$2@ stehen somit in einem Zusammenhang. Mir ist trotz Studium der man bash nicht klar was hier ablaeuft: 1. regulares Verhalten vom mc (temporaere Datei ? nach crash) 2.Bug des mc 3. Crackerkonstrukt?? -- # MfG Michael Maldener + Das beste Linux ist die Pluralitaet aller Linuxica ;)

4 5

Penetration test and NAT/PAT
by Barry Gill 12 Nov '03

12 Nov '03

Hello All, I want to run Nessus against my corporate gateway to see what threats we face from the outside world. The router that we have connecting us to the internet is a Cisco 805 running PAT. Is there a way to run nessus that it can be set to target the internal IP's (10.0.0.0) through the external IP of the router that anyone knows of? Or is there a tool that woill do this for us?. Please advise, thanks. Barry

2 1

blocking http download
by security 12 Nov '03

12 Nov '03

Hi guys, I am using Susefirewall2, squid on my firewall but still have probleme with http download. Is there anyway to block the http download ??? thinks --

3 2

Re: [suse-security] pcAnywhere-port forwarding
by Juan Erbes 11 Nov '03

11 Nov '03

¿Is not better if configures the firewall with Yast? You need to open the ports 5631:5632, and You can make this with Yast in expert mode. Mensaje citado por: root <root(a)katacnc.hu>: > > Sorry, my name... > ---------- Továbbított üzenet ---------- > > Subject: pcAnywhere-port forwarding > Date: 2003. november 11. 13.04 > From: root <root(a)katacnc.hu> > To: suse-security(a)suse.com > > Hi Guru\'s > > A beginner\'s big problem: > I\'m using SuSE 8.2 in the firewall. > eth0 192.168.23.80 > eth1 x.y.w.z > I configured the susefirewall2, the client can ping the firewall. > I need to enable to one outside client connect to my internal pc with > pcAnywhere > my pc: 192.168.23.201 win xp > Outside Pc : 217.236.X.X > I need two ports : 5631,5632 and i need forwarding it,from the firewall to > > my > local maschine. > I make a custom rule in : /etc/sysconfig/scripts/SuSEfirewall2-custom: > iptables -A FORWARD -j ACCEPT -p tcp --dport 5631 > iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to > 192.168.23.201:5631 > > iptables -A FORWARD -j ACCEPT -p tcp --dport 5632 > iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to > 192.168.23.201:5632 > > > The boot error message: > Try `iptables -h\' or \'iptables --help\' for more information. > > iptables v1.2.7a: unknown protocol `5631\' specified > > Try `iptables -h\' or \'iptables --help\' for more information. > > iptables v1.2.7a: unknown protocol `5632\' specified > > Try `iptables -h\' or \'iptables --help\' for more information. > > What is the solution? > Thanks a lot of your help. > If it work, i will pay for all of you a beer :) > Sorry for my english, and my long message. > > ------------------------------------------------------- > > > -- > Check the headers for your unsubscription address > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > > > __________________________________ Registrate desde http://servicios.arnet.com.ar/registracion/registracion.asp?origenid=9 y participá de todos los beneficios del Portal Arnet.

2 1

unsuscribe
by Grutsch, Gerhard 11 Nov '03

11 Nov '03

Hi, please unsuscribe my from that d-list. Gerhard Grutsch Support services, LAN WAN communications ggrutsch(a)statestreet.com 0049-89-55878-151

1 0

pcAnywhere-port forwarding
by root 11 Nov '03

11 Nov '03

Sorry, my name... ---------- Továbbított üzenet ---------- Subject: pcAnywhere-port forwarding Date: 2003. november 11. 13.04 From: root <root(a)katacnc.hu> To: suse-security(a)suse.com Hi Guru's A beginner's big problem: I'm using SuSE 8.2 in the firewall. eth0 192.168.23.80 eth1 x.y.w.z I configured the susefirewall2, the client can ping the firewall. I need to enable to one outside client connect to my internal pc with pcAnywhere my pc: 192.168.23.201 win xp Outside Pc : 217.236.X.X I need two ports : 5631,5632 and i need forwarding it,from the firewall to my local maschine. I make a custom rule in : /etc/sysconfig/scripts/SuSEfirewall2-custom: iptables -A FORWARD -j ACCEPT -p tcp --dport 5631 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to 192.168.23.201:5631 iptables -A FORWARD -j ACCEPT -p tcp --dport 5632 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to 192.168.23.201:5632 The boot error message: Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.7a: unknown protocol `5631' specified Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.7a: unknown protocol `5632' specified Try `iptables -h' or 'iptables --help' for more information. What is the solution? Thanks a lot of your help. If it work, i will pay for all of you a beer :) Sorry for my english, and my long message. -------------------------------------------------------

1 0

Re: [suse-security] pcAnywhere-port forwarding
by Juan Erbes 11 Nov '03

11 Nov '03

See for custom rules: http://mailman.ds9a.nl/pipermail/lartc/2002q4/005488.html Mensaje citado por: root <root(a)katacnc.hu>: > Hi, > > I made this first time, but not work... > > Thanks Sebastian and Juan! > Sandor Herczegh > > 2003. november 11. 12.34 dátummal Juan Erbes ezt írta: > > ¿Is not better if configures the firewall with Yast? > > You need to open the ports 5631:5632, and You can make this with Yast in > > expert mode. > > > > Mensaje citado por: root <root(a)katacnc.hu>: > > > Sorry, my name... > > > ---------- Továbbított üzenet ---------- > > > > > > Subject: pcAnywhere-port forwarding > > > Date: 2003. november 11. 13.04 > > > From: root <root(a)katacnc.hu> > > > To: suse-security(a)suse.com > > > > > > Hi Guru\\\'s > > > > > > A beginner\\\'s big problem: > > > I\\\'m using SuSE 8.2 in the firewall. > > > eth0 192.168.23.80 > > > eth1 x.y.w.z > > > I configured the susefirewall2, the client can ping the firewall. > > > I need to enable to one outside client connect to my internal pc with > > > pcAnywhere > > > my pc: 192.168.23.201 win xp > > > Outside Pc : 217.236.X.X > > > I need two ports : 5631,5632 and i need forwarding it,from the firewall > > > to > > > > > > > my > > > > > > local maschine. > > > I make a custom rule in : /etc/sysconfig/scripts/SuSEfirewall2-custom: > > > iptables -A FORWARD -j ACCEPT -p tcp --dport 5631 > > > iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to > > > 192.168.23.201:5631 > > > > > > iptables -A FORWARD -j ACCEPT -p tcp --dport 5632 > > > iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5631 -j DNAT --to > > > 192.168.23.201:5632 > > > > > > > > > The boot error message: > > > Try `iptables -h\\\' or \\\'iptables --help\\\' for more information. > > > > > > iptables v1.2.7a: unknown protocol `5631\\\' specified > > > > > > Try `iptables -h\\\' or \\\'iptables --help\\\' for more information. > > > > > > iptables v1.2.7a: unknown protocol `5632\\\' specified > > > > > > Try `iptables -h\\\' or \\\'iptables --help\\\' for more information. > > > > > > What is the solution? > > > Thanks a lot of your help. > > > If it work, i will pay for all of you a beer :) > > > Sorry for my english, and my long message. > > > > > > ------------------------------------------------------- > > > > > > > > > -- > > > Check the headers for your unsubscription address > > > For additional commands, e-mail: suse-security-help(a)suse.com > > > Security-related bug reports go to security(a)suse.de, not here > > > > __________________________________ > > Registrate desde > > http://servicios.arnet.com.ar/registracion/registracion.asp?origenid=9 > y > > participá de todos los beneficios del Portal Arnet. > > > -- > Check the headers for your unsubscription address > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > > > -----------------------------------------------------

1 0