June 2003 - openSUSE Security - openSUSE Mailing Lists

AW: [suse-security] Postfix errors[Scanned]
by Jörg Brandenburg 05 Jun '03

05 Jun '03

Hi Jeff, I use Postfix with Amavisd-new, SpamAssasin, Razor and DCC and it works great for me. You can find an excellent how-to at http://lawmonkey.org/anti-spam.html. This how-to is for OpenBSD but you can easy port it to Linux. You should read it before you start. I did it this way: cd /usr/local/src wget http://www.ijs.si/software/amavisd/amavisd-new-<version>.tar.gz tar xzvf amavisd-new-<version>.tar.gz cd amavisd-new-<version> useradd -o -g nogroup -u 65 -s /bin/false -c "Vscan account" -d /var/spool/vscan vscan mkdir /var/spool/vscan chown vscan:root /var/spool/vscan chmod 700 /var/spool/vscan cp amavisd /usr/sbin chown root:root /usr/sbin/amavisd chmod 755 /usr/sbin/amavisd cp amavisd.conf /etc/ chown vscan:root /etc/amavisd.conf chmod 600 /etc/amavisd.conf mkdir /var/spool/vscan/virusmails chown vscan:root /var/spool/vscan/virusmails chmod 700 /var/spool/vscan/virusmails mkdir /var/spool/vscan/amavis touch /var/spool/vscan/amavis/amavis.log chown -R vscan:root /var/spool/vscan/amavis chmod 700 /var/spool/vscan/amavis mkdir /var/spool/vscan/.spamassassin touch /var/spool/vscan/.spamassassin/user_prefs chown -R vscan:root /var/spool/vscan/.spamassassin edit the amavisd configuration-file (/etc/amavisd.conf): $MYHOME='/var/spool/vscan'; $MYDOMAIN='your-domain.name'; daemon_group='nogroup'; forward_method='127.0.0.1:10025'; notify_method=$forward_method; @bypass_virus_checks_acl=gw( . ); #This disables all virus checking code $LOGFILE="$MYHOME/amavis/amavis.log"; $QUARANTINEDIR='/var/spool/vscan/virusmails'; For a first test you can now start amavisd with /usr/sbin/amavisd debug and make a smtp-telnet-session to 127.0.0.1 10024 Postfix configuration: /etc/postfix/master.cf localhost:10025 inet n - y - - smtp -o content_filter= vscan unix - - y - 2 lmtp -o smtp_data_done_timeout=1200 -o disable_dns_lookups=yes /etc/postfix/main.cf content_filter=vscan:[127.0.0.1]:10024 For the configuration of spamassasin, razor and dcc you can use the how-to at lawmonkey.org -----Ursprüngliche Nachricht----- Von: Jeff Harris [mailto:linux@rallycentral.us] Gesendet: Mittwoch, 4. Juni 2003 21:43 An: suse-security(a)suse.com Betreff: Re: [suse-security] Postfix errors[Scanned] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Jun 2003, Jeff Harris wrote: > On Wed, 4 Jun 2003, Christopher Mahmood wrote: > > > * Jeff Harris (linux(a)rallycentral.us) [030604 12:17]: > > > > It looks like you didn't add rallycentral.us to $mydestination but > > it could be other things as well. Please send the output of > > /usr/sbin/postconf . > > > That was it exactly. For some reason, I thought I read something in the > main.cf that $mydomian would be prepended to $mydestination. The output of > /usr/sbin/postconf is pretty long. Is there anything in particular to > look for? And, should I be using main.cf or main.cf.SuSEconfig? > It's appears to be working now, since I sent this message to myself. For my next trick, spamassassin. Any tips before I break my machine again? <g> - -- Registered Linux user #304026. "lynx -source http://www.rallycentral.us/~linux/jharris.asc | gpg --import" or "gpg --keyserver pgp.mit.edu --recv-key BD23A31E" Key fingerprint = FB8C 3210 8DE1 78F4 6505 5918 0C34 BE94 BD23 A31E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQE+3kvVDDS+lL0jox4RAv8GAJ46vU+2jdehKjSvHRs/dNO4vASVuwCfTNdq JEXrUMU3zd/B1q/nDCtfYgo= =1Ecb -----END PGP SIGNATURE----- -- 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

Re: [suse-security] Postfix errors
by Jeff Harris 04 Jun '03

04 Jun '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Jun 2003, Jeff Harris wrote: > On Wed, 4 Jun 2003, Christopher Mahmood wrote: > > > * Jeff Harris (linux(a)rallycentral.us) [030604 12:17]: > > > > It looks like you didn't add rallycentral.us to $mydestination but > > it could be other things as well. Please send the output of > > /usr/sbin/postconf . > > > That was it exactly. For some reason, I thought I read something in the > main.cf that $mydomian would be prepended to $mydestination. The output of > /usr/sbin/postconf is pretty long. Is there anything in particular to > look for? And, should I be using main.cf or main.cf.SuSEconfig? > It's appears to be working now, since I sent this message to myself. For my next trick, spamassassin. Any tips before I break my machine again? <g> - -- Registered Linux user #304026. "lynx -source http://www.rallycentral.us/~linux/jharris.asc | gpg --import" or "gpg --keyserver pgp.mit.edu --recv-key BD23A31E" Key fingerprint = FB8C 3210 8DE1 78F4 6505 5918 0C34 BE94 BD23 A31E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQE+3kvVDDS+lL0jox4RAv8GAJ46vU+2jdehKjSvHRs/dNO4vASVuwCfTNdq JEXrUMU3zd/B1q/nDCtfYgo= =1Ecb -----END PGP SIGNATURE-----

1 0

Postfix errors
by Jeff Harris 04 Jun '03

04 Jun '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of days ago, someone said something like "why would you be using sendmail when postfix is much more secure and easier to set up." So, I decided last night, to remove sendmail and replace it with postfix. Now, as I'm sure the list admin is aware, I can't receive any mails. /var/log/mail quoth:" Jun 4 11:59:09 www postfix/smtpd[16893]: reject: RCPT from lists.suse.com[217.9.113.69]: 554 <linux(a)rallycentral.us>: Recipient address rejected: Relay access denied; from=<suse-security-return-18749-linux=rallycentral.us(a)suse.com> to=<linux(a)rallycentral.us>" If the person who wrote that would like to help me fix this issue, I would greatly appreciate it, and he would be my personal hero for at least the next week. Unfortunately, since I can't receive mail here, we'll have to take this off the list to another email: jeff(at)harris(dot)nu thanks, Jeff - -- Registered Linux user #304026. "lynx -source http://www.rallycentral.us/~linux/jharris.asc | gpg --import" or "gpg --keyserver pgp.mit.edu --recv-key BD23A31E" Key fingerprint = FB8C 3210 8DE1 78F4 6505 5918 0C34 BE94 BD23 A31E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQE+3kW1DDS+lL0jox4RAsv7AJ9l8QEVHwiycmeMQ5K/elTHQOddgwCggWgR h7+WaSvqMjJjYFZqeh5kNQ4= =jO/e -----END PGP SIGNATURE-----

2 1

Postfix relayhost
by Marcia Henke 04 Jun '03

04 Jun '03

Hi all !!!!! I'm using SuSE7.3, and postfix configuaration with "relayhost = srvmse.tsur.com.br" . I'm have problem in /var/log/mail : Jun 4 16:09:47 srvlnx postfix/pickup[10934]: 0A0488A09: uid=0 from=<root> Jun 4 16:09:47 srvlnx postfix/cleanup[11025]: 0A0488A09: message-id=<20030604190946.0A0488A09(a)srvlnx.tsur.local> Jun 4 16:09:47 srvlnx postfix/qmgr[10935]: 0A0488A09: from=<root(a)mail.tsur.com.br>, size=9855, nrcpt=1 (queue active) Jun 4 16:09:47 srvlnx postfix/smtp[11027]: 0A0488A09: to=<maykel(a)suryatec.com.br>, relay=srvmse.tsur.local[172.16.1.4], delay=1, stat us=sent (250 OK) Jun 4 16:10:01 srvlnx postfix/smtpd[11041]: connect from localhost[127.0.0.1] Jun 4 16:10:03 srvlnx postfix/pickup[10934]: 309268A09: uid=0 from=<root> Jun 4 16:10:03 srvlnx postfix/cleanup[11025]: 309268A09: message-id=<20030604191003.309268A09(a)srvlnx.tsur.local> Jun 4 16:10:03 srvlnx postfix/qmgr[10935]: 309268A09: from=<root(a)mail.tsur.com.br>, size=687, nrcpt=1 (queue active) Jun 4 16:10:03 srvlnx postfix/smtp[11027]: 309268A09: to=<root(a)mail.tsur.com.br>, relay=srvmse.tsur.local[172.16.1.4], delay=0, statu s=sent (250 OK) someone help me ????? Thanks Márcia :-)

1 0

SuSE Security Announcement: glibc (SuSE-SA:2003:027)
by Thomas Biege 04 Jun '03

04 Jun '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: glibc Announcement-ID: SuSE-SA:2003:027 Date: Monday, May 26th 2003 16:12 MET Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7, SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: remote system compromise Severity (1-10): 6 SuSE default package: yes Cross References: CAN-2003-0028 Content of this advisory: 1) security vulnerability resolved: integer overflow in XDR code problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - ethereal - XFree4 - vnc - bitchx - lv 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Another integer overflow was found in glibc' XDR code. This bug is equal to the one described in advisory SuSE-SA:2002:031. The overflow occurs in the function xdrmem_getbytes() and can be used by external attackers to execute arbitrary code. There is no temporary workaround for this security problem other than disabling all RPC based server and client programs. The permanent solution is to update the glibc packages with the update packages listed below. Notes, Special installation instructions: * PRECAUTIONS The shared libraries package of the glibc is the most sensitive part of a running Linux system, and modifications to it should be handled with special care. During the update of the shlibs/glibc package, runtime-linking the shared libraries is likely to fail for processes that execute a new binary with the execve(2) system call. Therefore, we recommend to bring a system to single user mode ("init S") to perform the package update. If this is not applicable for operational reasons, a system receiving the update should be kept as quiet as possible (no shell scripts of any kind, no cron jobs, no incoming email). * After performing the update, you should run the following command on your system: /sbin/ldconfig ldconfig will rebuild the runtime linker cache. If you use YOU (Yast2 Online Update), the ldconfig command will be executed automatically at the end of the update. The shared libraries that were installed on the system before the update have been removed from the filesystem, but they are still in use by the running applications. Therefore, the disk-space as well as the memory will not be freed until the last process that uses these files exits. We recommend to reboot the system to workaround this problem. Listed below you find the URLs for the update packages for the SuSE Linux products. We only list the packages that are relevant for the security 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/i686/glibc-2.2.5-177.i686.r… 1cf549fa52427710c7dc3316fc5df4a6 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i686/glibc-2.2.5-177.i686.p… f87601fd71edf54928104581684dae8f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/a1/glibc-2.2.5-177.i386.rpm da51402d30c37dd5dc6d5444c37f4dc3 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/a1/glibc-2.2.5-177.i386.patch.r… 0b5ea57d89c31d923cfb56cb1f951bac source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/glibc-2.2.5-177.src.rpm 6fecec2ed42fb792b6e9cb2a5602fe23 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/a1/glibc-2.2.4-78.i386.rpm 11cc1ceb173b18fc82d8500b1528663e source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/glibc-2.2.4-78.src.rpm 38527e5f75d94c016659c71028c37c52 SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/a1/glibc-2.2.2-68.i386.rpm 82f4c3ee8ba0cf3feef5e0ba7321a230 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/glibc-2.2.2-68.src.rpm 34114134cb51d706989c45306f4fdde3 SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/glibc-2.2-26.i386.rpm ffe7c422727ee98b8191facbbf40b9d7 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/glibc-2.2-26.src.rpm 1c5b778ff60a82f03e412239b907671b Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/a1/glibc-2.2.4-46.sparc.rpm dc577491e13344411462603b6fe83d3f source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/glibc-2.2.4-46.src.rpm 0a0a5dd6ee76e6b0ef866b500d6537b2 AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/a1/glibc-2.2-34.alpha.rpm d250c254668e02b9f23341903f2f3a5e source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/glibc-2.2-34.src.rpm d89b4a1ff27227a085e516b48ccdb1cf PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/a1/glibc-2.2.4-69.ppc.rpm 5bf4edf432c996b3e38ef085122e1e8 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - ethereal Several one-byte buffer overflows and integer overflows are fixed. These bugs lead to remote denial-of-service or even remote code execution. New packages are available on our FTP servers. - XFree4 A buffer overflow in the Xlib code can be triggered while handling the environment variable XLOCALEDIR. The X version affected is 4.2.0 (SuSE Linux 8.0 and 8.1). New packages are available on our FTP servers. - vnc VNC (Virtual Network Computing) uses a weak cookie generation process which can be exploited by an attacker to bypass authentication. New packages are available on our FTP servers. - bitchx Several buffer overflows got fixed that can be exploited remotely by a malicious IRC servers. New packages are available on our FTP servers. - lv lv reads config files from the current directory without verifying the ownership. If lv is called in world-writeable directories like /tmp it can be tricked into executing commands by putting a malicious config- file there. New 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) iQEVAwUBPtNwVney5gA9JdPZAQGgRwf+Jb5OmG6zuqPPAE9nf31SVOUXKY1aO+D0 eHqEM/7VbSaCQ2TAx28mYfyek1NaGudwyqDBGxyVYrrlwz0z9jkGRP/GUY4h2mBk vff5xnlzSbvetFCnoHtR/RqXXRPvnDe3GDgeJXoPpZtRYnDb/Rw/4UOKnIyev7QP iw8yupuYGEQt6yDHwMatSJAHOT3QOmYbsqy6N8GcQ2KwttaVWmHw8bm5eoJKrAAM HR0YjLAu371ZO4pfV4r3Vl2HhaQ+r+/tm4VHnySqA5YdDyM1QiX1AEi5RXqD3L0U ERYYwSc/h/jG6aqKcqAurFIdoGUqAvzevJv0quQAYRWNwbik8jzv8g== =BUi3 -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de> SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | gpg --import" Key fingerprint = 7254 B15D B3C4 943F 485E 0BBD 8ECC D7CB C200 A213 -- Das erste Opfer einer Schlacht ist immer der Schlachtplan.

5 5

SuSE 7.1 Mirror
by Drew J. Como 04 Jun '03

04 Jun '03

All, Good Day! Does anyone know of a mirror that is still offering the 7.1 packages for download? I know that SuSE still offers the updates, but the package that I need was never updated. Thanks :-) ============================================ Drew J. Como Phone: 631-434-6600 Systems Administrator Fax: 631-434-7800 dcomo(a)bascom.com Web: www.bascom.com BASCOM Global Internet Services, Inc. -------------------------------------------- "When quality is the goal, winning is guaranteed."

2 2

RE: [suse-security] have I been invaded?
by Peer Stefan 04 Jun '03

04 Jun '03

Hi Richard, > From: Richard [mailto:ratcheson@earthlink.net] [skip ssh1/ssh2 config] > > Thanks John, I made that change. Do you have any idea why my default > route has that strange destination? I went through Yast and > by all that > I can see it should not be that but should be the IP of my > isp unless I > am completely wrong. As I recall, it used to be the IP (24.233.51.9) > that I get when the network is started. I did a whois on the name and > got that it was available. Strange!!! > ra The fqdn (fully qualified domain name) of the mentioned ip-address is 'user-0ceico9.cable.mindspring.com'. Since 'route' has only a certain amount of characters available for each entry it just cuts the name after 'user-0ceico9.ca'. So nothing to worry there :o) If you don't want to use name-resolving with 'route', try 'route -n'. Try 'dig' or 'host' the next time to resolve an ip-address, 'whois' shows information about the regristration of a domain, not the hostname. regards, Stefan

3 2

What is difference between /etc/pam.d/passwd and the "password" of /etc/pam.d/sshd?
by Jeongmo Jeong 04 Jun '03

04 Jun '03

Hello, I'm very sorry for my poor english. I know PAM(Password Authentication Module), but I don't know the difference /etc/pam.d/passwd and the "password" of each file in /etc/pam.d/sshd, /etc/pam.d/login..etc /etc/pam.d/passwd also have the word, "passwd" I'm very confused, Please explain what the difference is... Thanks in advance~ From Japan.

2 1

AW: [suse-security] snort & logsurfer
by mailinglists 03 Jun '03

03 Jun '03

Hi > > oehm, did not find that -F Parameter in > man sendmail ;-(( Oh, it's there. man sendmail: -F full_name Set the sender full name. This is used only with messages that have no From: message header. > $1 is the line with the Error-Message, right? right. > If yes, then try the following: > > "echo $1 | mail -s Security_Alert ALERT(a)domain.com" skipping... > if this works, try: > > "echo $1 | mail -s \"Security_Alert: $1\" ALERT(a)domain.com" hey, no bad idea. effect is that the alert is displayed in the subject textfield, not in the body. the echo $1 didn't work. Logsurfer printed the matching logs to shell. Thanks a lot. Philipp > > > -----Original Message----- > > From: mailinglists [mailto:mailinglists@belfin.ch] > > Sent: Tuesday, June 03, 2003 7:24 AM > > To: Dirk Schreiner; suse-security(a)suse.com > > Subject: AW: [suse-security] snort & logsurfer > > > > > > > > > > > Blind shot: > > > > ...missed, unfortunately :-( > > > > > '(.*snort:.*)' - - - 0 report "/usr/lib/sendmail -F > ALERT(a)domain.com > > > psnizek \"security alert: $1\"" "$1" > > > > I tried that. Result is the string gets tokenized and every > > token becomes part of the receiver's email address, such as: > > security(a)domain.com > > alert(a)domain.com > > . > > . > > . > > snort(a)domain.com > > and later > > psnizek(a)domain.com > > > > Besides of that the mail body still is empty. > > > > Philipp > > > > > Dirk > > > > > > > > > > -----Original Message----- > > > > From: mailinglists [mailto:mailinglists@belfin.ch] > > > > Sent: Monday, June 02, 2003 9:57 PM > > > > To: suse-security(a)suse.com > > > > Subject: [suse-security] snort & logsurfer > > > > > > > > > > > > Hi > > > > > > > > I'm trying to build up an email alerting system with snort 2 > > > > and logsurfer 1.5. Basically it's working; I get the emails > > > > from the snort box when snort acction occurs in the messages > > > > log. Problem is, the mail bodies are empty. > > > > > > > > That's the logsurfer command: > > > > > > > > '(.*snort:.*)' - - - 0 report "/usr/lib/sendmail -F > > > > ALERT(a)domain.com psnizek "security alert: $1"" "$1" > > > > > > > > > > > > please, can anybody help? > > > > > > > > thanks a lot & kind regards, > > > > > > > > Philipp > > > > > > > > -- > > > > 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 > > > > > > > > > > > > > > > > > > > > -- > > > 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 > > > > > > > > > > >

3 2

PHP 4.2.2-215 session failure
by Toni Zeitler 03 Jun '03

03 Jun '03

Hello... The new security-fixed PHP version 4.2.2-215 seems not to work properly any more. It was fixed a litte bit too much, I believe. This small session test script runs without problems in the older version 4.2.2-168, the latest version does not save sessions any more (tested by simply up-/downdating with rpm): <?php session_start(); print($counter); $counter++; session_register("counter"); ?> Might I have done something wrong or is the latest version simply broken? If it is, when can we expect a new release? Bye, Toni ********************* Hallo... Die neue Security-gefixte PHP-Version 4.2.2-215 funktioniert anscheinend nicht mehr richtig. Da wurde zuviel gefixt, glaub ich. Dieses Mini-Session-Test-Skript geht mit der Vorläuferversion 4.2.2-168 problemlos, mit der neuen speichert er keine Sessions mehr (getestet ganz einfach durch up-/downdaten mit rpm): <?php session_start(); print($counter); $counter++; session_register("counter"); ?> Also... hab ich evtl. was falsch gemacht oder ist die neue Version einfach kaputt? Wann ist denn im letzteren Fall Abhilfe zu erwarten? Ciao, Toni

2 2