October 2002 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement: hylafax (SuSE-SA:2002:035)
by Thomas Biege 07 Oct '02

07 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: hylafax Announcement-ID: SuSE-SA:2002:035 Date: Friday, Oct 4th 2002 10:30 MEST Affected products: 7.0, 7.1, 7.2, 7.3, 8.0 SuSE Linux Connectivity Server SuSE Linux Enterprise Server SuSE Linux Office Server Vulnerability Type: remote privilege escalation Severity (1-10): 4 SuSE default package: no Cross References: CAN-2002-1050 Content of this advisory: 1) security vulnerability resolved: - format string bug in logging code for TSI - buffer overflow in faxgetty while handling image data 2) pending vulnerabilities, solutions, workarounds: - glibc - ghostview/kghostview - fetchmail - kdelibs - ethereal 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information HylaFAX is a client-server architecture for receiving and sending facsimiles. The logging function of faxgetty prior version 4.1.3 was vulnerable to a format string bug when handling the TSI value of a received facsimile. This bug could easily be used to trigger a denial-of-service attack or to execute arbitrary code remotely. Another bug in faxgetty, a buffer overflow, can be abused by a remote attacker by sending a large line of image data to execute arbitrary commands too. Several format string bugs in local helper applications were fixed too. These bugs can not be exploited to gain higher privileges on a system running SuSE Linux because of the absence of setuid bits. The hylafax package is not installed by default. A temporary fix is not known. 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. i386 Intel Platform: SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/hylafax-4.1-285.i386.patch.r… 3115ebdb9e65027f35809463c5e6ae7e SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/hylafax-4.1-285.i386.rpm 07b0f2d015b0fd83c5bb9be548e7b8fb source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/hylafax-4.1-285.src.rpm 8231586e2de356c737ef3d6f9d17c0ea SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n3/hylafax-4.1-284.i386.rpm de51bda21cc9ee1a4dd3cd06ccccf71e source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/hylafax-4.1-284.src.rpm aac2ecddf06934f286960f52f2e7670e SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n3/hylafax-4.1beta2-376.i386.rpm 275c73b0b192da9c883cfebf6638604e source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/hylafax-4.1beta2-376.src.rpm b8698144b8bb859d880659fcf01eb020 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n3/hylafax-4.1beta2-375.i386.rpm c322bc9007191e3692341b5702b29200 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/hylafax-4.1beta2-375.src.rpm 4d76cd426565e411941b4aaebf6ad761 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n2/hylafax-4.1beta2-373.i386.rpm fa7399ce161a44dbad630928cd6b3b84 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/hylafax-4.1beta2-373.src.rpm 0ac9d8b33b75f29b55a5750f17a65b93 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n3/hylafax-4.1-112.sparc.rpm 1cabb4113f858df010d305fa576c5a02 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/hylafax-4.1-112.src.rpm a5ddaee97231c423e04fb71b757532a3 SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n3/hylafax-4.1beta2-218.sparc.… 1449e568071f5fb6080efebb8f2a7a2b source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/hylafax-4.1beta2-218.src.r… bf8c780206da51bc548e9fd4264b9bfc SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n2/hylafax-4.1beta2-218.sparc.… bb265465ea8b84ca31b5c954266daf1d source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/hylafax-4.1beta2-218.src.r… b5bcae601fe056f399fc8696aa156529 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n3/hylafax-4.1beta2-245.alpha.rpm 45d0fd7061f10e4bef9e57c42a9b160d source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/hylafax-4.1beta2-245.src.rpm baf364ec3636077fe8f810edeb111572 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n2/hylafax-4.1beta2-244.alpha.rpm 856e96ce4a165b74e70ebc9ef3201672 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/hylafax-4.1beta2-244.src.rpm f68e2260aa36d4d218a3f3589333ea0e PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n3/hylafax-4.1-189.ppc.rpm 79846b9ae0f75f8ed9b17fed07ba6263 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/hylafax-4.1-189.src.rpm 98a123cf18cb6b34ffd9018a76ad161f SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n3/hylafax-4.1beta2-218.ppc.rpm 2bfe866f1bd1d93307449de95d84d6c2 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/hylafax-4.1beta2-218.src.rpm 972c605bd3a9cc15bbbc5aa188dfc864 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n2/hylafax-4.1beta2-217.ppc.rpm 00b1ae1c91235ecceb287ffe7aced175 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/hylafax-4.1beta2-217.src.rpm e905325a032854fb653cf458e0db8942 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - glibc Client applications which use res_search/res_nsreach and/or res_query()/ res_nquery() of libresolv could trigger a DNS decoding error, a SEGV or leak information by reading beyond the end of a too small 'answer' buffer. The update packages are being built and tested. We will publish a security announcement as soon as they are ready. - ghostview/kghostview Bufferoverflows have recently been discovered in these packages. They allow attackers to execute arbitrary code with the privileges of the user viewing special crafted documents created by the attacker. New packgaes will soon be available on our ftp servers. - fetchmail Fetchmail contains remotely exploitable overflows in the mail header parsing functions. In depth discussion of these problems can be found at http://security.e-matters.de/advisories/032002.html. New packages will soon be available on our ftp servers. - kdelibs KDE's SSL implementation fails to check the trust chain in SSL certificates. This bug allows faking valid SSL certificates. New KDE packages will be available soon to fix this and other bugs. - ethereal Several potential security issues have been discovered in ethereal 0.9.4. After this package is tested succesfuly it will be relased. ______________________________________________________________________________ 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: 2.6.3in Charset: noconv iQEVAwUBPZ2QC3ey5gA9JdPZAQES0gf/Un5d3SHgL+xDlFaseqLg6t7NHa1d4KRw ZM8eqLE+ClFpfq+o/Rf97DqAaQZYrvUYzleOUUcvci2BLevCFMbqBsRxBc0FvU7G lvxgJkjslnlBxjAgkvXp/DmEcYN3sVH/4f8eLtq+cUb4AwU01elI7mThE6l3n6P6 Xq2q4NdWnw1RAXmsgfjNkRuX5gNUgULRUYFFlQF/ycKleoml/DQCH7dBet9tBQQP jem58hBq2cnQmTG2GyFFs0fsb81PCfxk0LrrxveKoMHR/cgH/y2sOBCu01bEzBBe HhpZPhgOcO1CxijXuEufaPbufXN5d/L2gHJpQK54L7Oc6n8zsDLXmg== =7yxm -----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 | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- Cold silence has a tendency to atrophy any sense of compassion - Maynard James Keenan

1 0

Re: [suse-security] strange seccheck output - cracked?
by Thomas Lamy 07 Oct '02

07 Oct '02

> -----Ursprüngliche Nachricht----- > Von: Maik Holtkamp [mailto:holtkamp@medical-city.de] > Gesendet: Montag, 7. Oktober 2002 11:10 > An: 'suse-security(a)suse.com' > Betreff: [suse-security] strange seccheck output - cracked? > > > Hi, > > after a long weekend I found this seccheck output in my inbox: > > ---cut--- > The following programs have got a different md5 checksum since last > week: > + ++ /var/lib/secchk/data/rpm-md5.new Sun Oct 6 23:13:52 2002 > + SM5....T /usr/share/groff > + S.5....T /usr/share/info/gzip.info.gz > + SM5....T /usr/lib/kbd > + SM5....T /sbin/conf.d/SuSEconfig.pam > + S.5....T /usr/share/doc/packages/pam/modules/README.pam_unix > [....] > + SM5....T /usr/share/zoneinfo > > The following devices were added: > + ++ /var/lib/secchk/data/devices.new Sun Oct 6 23:15:02 2002 > + brw-rw---- root disk 49, 79 > /usr/lib/locale/es_DO/LC_MESSAGES > + brw-rw---- root disk 49, 77 > /usr/lib/locale/mr_IN.utf8/LC_CTYPE/LC_TELEPHONE > + brw-rw---- root disk 49, 78 > /usr/lib/locale/mr_IN.utf8/LC_CTYPE/LC_TIME > ---schnapp--- > > The box is running SuSE 7.1 and masquerading our small LAN on an > isdn multilink (ibod) DOD dial-up. > > ---schnapp--- > > [....] > > I checked the logs, but did not found anything suspicious. The files > mentioned above are corrupted. Files in /etc/init.d/gpm or idedma, > however, they are no longer executable. Even more strange > /usr/src/linux-2.2.19.SuSE is a binary,too, and in this case it is > world executable. > > -- > Maik Hi, I'm pretty sure you were not hacked, but there's either a direct problem with your disk (flopped bits), an indirect disk problem (faulty cables), or some other problem that caused data corruption on your disk. Had this problem some time ago (from time to time) with SuSE 7.0 on a Compaq Deskpro w/ 10 Gig Maxtor HD. Went away when I upgraded to 7.3 with a 2.4 kernel, so it were maybe driver issues or timing problems. Thomas

1 0

DNS - Changing the owner to named
by Edward Cheadle 07 Oct '02

07 Oct '02

I would like to run named to run under the user named. The default setting seems to run as root. I have been reading security books and they all suggest this change. In my Redhat distribution I change the init script and it works. In the named script found in /etc/init.d the named process is started by startproc. The startproc man page says to start the process with the -u and -g switch. It does run as a different user, but then named seems not to work. The named process is running, but it does not respond to queries. I can't tell at the moment if it is because startproc starts it as a user process, that is to say it does not start up as root, or what is going on. I am going to investigate it further, I just want to know if I was on the right track or if there is somewhere in the manuals that describe starting named with a user other than root and I just haven't found it. thanks edward

4 3

strange seccheck output - cracked?
by Maik Holtkamp 07 Oct '02

07 Oct '02

Hi, after a long weekend I found this seccheck output in my inbox: ---cut--- The following programs have got a different md5 checksum since last week: + ++ /var/lib/secchk/data/rpm-md5.new Sun Oct 6 23:13:52 2002 + SM5....T /usr/share/groff + S.5....T /usr/share/info/gzip.info.gz + SM5....T /usr/lib/kbd + SM5....T /sbin/conf.d/SuSEconfig.pam + S.5....T /usr/share/doc/packages/pam/modules/README.pam_unix + S.5....T /usr/share/doc/packages/pam/modules/README.pam_warn + SM5....T /sbin/conf.d/SuSEconfig.perl + SM5....T /usr/lib/perl5/5.6.0/i586-linux + S.5....T /usr/share/terminfo/x/xterm-xi + S.5....T /usr/share/terminfo/x/xterm1 + S.5....T /usr/share/terminfo/x/xtermc + SM5....T /usr/share/terminfo/x/xterms + S.5....T /usr/share/terminfo/x/xterms-sun + SM5....T /usr/share/terminfo/x/xwsh + SM5....T /usr/share/terminfo/z/z19 + S.5....T /usr/share/terminfo/z/z29a + SM5....T /usr/share/terminfo/z/z29a-kc-bc + S.5....T /usr/share/terminfo/z/z29a-kc-uc + S.5....T /usr/share/terminfo/z/z29a-nkc-bc + S.5....T /usr/share/terminfo/z/z29a-nkc-uc + SM5....T /usr/share/terminfo/z/z29b + SM5....T /usr/share/terminfo/z/z30 + S.5....T /usr/share/terminfo/z/z340 + S.5....T /usr/share/terminfo/z/z340-nam + S.5....T /usr/share/terminfo/z/z39-a + SM5....T /usr/share/terminfo/z/z39a + SM5....T /usr/share/terminfo/z/z8001 + S.5....T /usr/share/terminfo/z/zen50 + SM5....T /usr/share/terminfo/z/zen8001 + SM5....T /usr/share/terminfo/z/zenith + SM5....T /usr/share/terminfo/z/zenith29 + SM5....T /usr/share/terminfo/z/zenith39-a + SM5....T /usr/share/terminfo/z/zenith39-ansi + SM5....T /usr/share/terminfo/z/zt-1 + S.5....T /usr/share/terminfo/z/ztx + SM5....T /usr/share/terminfo/z/ztx-1-a + SM5....T /usr/share/terminfo/z/ztx11 + S.5....T /usr/include/curses.h + SM5....T /usr/bin/setfdprm + SM5...GT /usr/bin/wall + SM5....T /usr/bin/whereis + S.5....T /usr/share/locale/nl/LC_MESSAGES/util-linux.mo + SM5....T c /etc/init.d/idedma - S.5....T c /etc/init.d/gpm + SM5....T c /etc/init.d/gpm + SM5....T /usr/share/locale/sl/LC_MESSAGES/popt.mo + S.5....T /usr/share/locale/tr/LC_MESSAGES/popt.mo + SM5....T /etc/init.d/dhclient + S.5....T /usr/share/info/textutils.info.gz + S.5....T /usr/share/locale/nl/LC_MESSAGES/textutils.mo + SM5....T /usr/bin/c++filt + SM5....T /usr/bin/cc + SM5....T /usr/bin/cpp + SM5....T /usr/bin/gcc + SM5....T /usr/bin/gcov + SM5....T /usr/bin/protoize + SM5....T /usr/bin/unprotoize - S.5....T /var/spool/atjobs/.SEQ + SM5....T c /etc/init.d/at + SM5..UGT /var/spool/atjobs/.SEQ + SM5....T /usr/bin/ld + SM5....T /usr/bin/nm + SM5....T /usr/bin/objcopy + SM5....T /usr/bin/objdump + SM5....T /usr/bin/ranlib + SM5....T /usr/bin/readelf + SM5....T /usr/bin/size + SM5....T /usr/bin/strings + SM5....T /usr/bin/strip + SM5....T c /etc/init.d/sshd + S.5....T /usr/share/locale/nl/LC_MESSAGES/wget.mo + SM5....T c /etc/init.d/argus + SM5....T /etc/init.d/scanlogd + SM5....T c /etc/init.d/i4l + SM5....T c /etc/init.d/i4l_hardware + SM5....T c /etc/init.d/sendmail - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/sys_timer.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/trident.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/trident.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/trix.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/tuning.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/uart401.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/uart6850.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/ulaw.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/v_midi.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/v_midi.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/via82cxxx_audio.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/vidc.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/vidc.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/vidc_fill.S - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/vidc_synth.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/vwsnd.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/waveartist.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/waveartist.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/wavfront.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/wf_midi.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/ymfpci.c - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/ymfpci.h - S.5....T /usr/src/linux-2.2.19.SuSE/drivers/sound/ymfpci_image.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/apm.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/autofs/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/binfmt/misc.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/3w/xxxx/raid.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/aec62xx.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/ali15x3.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/cmd640/enhanced.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/cmd64x.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/cs5530.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/idefloppy.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/loop.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/sd.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/blk/dev/sr.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/bsd/disklabel.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/bsd/process/acct.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/chr/dev/osst.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/chr/dev/sg.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/chr/dev/st.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/configlang/english.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/configlang/german.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/dummy/module.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/eexpress/pro100.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/experimental.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/fat/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/filter.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/firewall.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/idedma/pci/experimental.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/idepci/share/irq.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/inet/rarp.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/ip/advanced/router.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/ip/alias.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/ip/multicast.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/ip/pnp.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/joliet.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/kmod.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/m486.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/m686.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/mac/partition.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/magic/sysrq.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/minix/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/msdos/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/mtrr.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/net/sched.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/netlink.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/nfs/v3.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/nls.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/nvram.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/paride/parport.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/ppscsi.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/proc/config.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/quota.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/reiserfs/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/rtc.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/7000fasst.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/aacraid.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/acard.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/advansys.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/aha152x.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/aha1542.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/aha1740.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/aic7xxx.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/aic7xxx/old.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/am53c974.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/buslogic.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/constants.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/cpqfcts.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/dc390t.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/dpt/i2o.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/dtc3280.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/eata.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/eata/dma.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/eata/pio.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/future/domain.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/gdth.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/generic/ncr5380.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/in2000.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/inia100.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/initio.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ips.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/logging.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/megaraid.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/multi/lun.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c406a.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c7xx.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c8xx.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c8xx/default/tag s.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c8xx/iomapped.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c8xx/max/tags.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c8xx/pqs/pds.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ncr53c8xx/sync.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/pas16.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/pci2000.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/pci2220i.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/psi240i.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/qlogic/1280.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/qlogic/fas.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/qlogic/fc.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/qlogic/isp.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/qlogic/qla2x00.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/seagate.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/sim710.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/sym53c416.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/sym53c8xx.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/t128.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/u14/34f.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/scsi/ultrastor.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/serial/console.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/serial/extended.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/serial/nonstandard.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/smd/disklabel.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/solaris/x86/partition.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/syn/cookies.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/umsdos/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/vfat/fs.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/video/select.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/x86/good/apic.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/config/x86/tsc.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/linux/autoconf.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/linux/compile.h - S.5....T /usr/src/linux-2.2.19.SuSE/include/linux/config_data.h + S.5....T /usr/share/man/allman/man2/sysctl.2.gz + S.5....T /usr/share/man/allman/man2/sysfs.2.gz + S.5....T /usr/share/man/allman/man2/sysinfo.2.gz + S.5....T /usr/share/man/allman/man2/syslog.2.gz + S.5....T /usr/share/man/allman/man2/time.2.gz + S.5....T /usr/share/man/allman/man2/times.2.gz + S.5....T /usr/share/man/allman/man2/trecv.2.gz + S.5....T /usr/share/man/allman/man2/truncate.2.gz + S.5....T /usr/share/man/allman/man2/tsend.2.gz + S.5....T /usr/share/man/allman/man2/umask.2.gz + S.5....T /usr/share/man/allman/man2/uname.2.gz + S.5....T /usr/share/man/allman/man2/unimplemented.2.gz + S.5....T /usr/share/man/allman/man2/unlink.2.gz + S.5....T /usr/share/man/allman/man2/uselib.2.gz + S.5....T /usr/share/man/allman/man2/ustat.2.gz + S.5....T /usr/share/man/allman/man2/utime.2.gz + S.5....T /usr/share/man/allman/man2/utimes.2.gz + S.5....T /usr/share/man/allman/man2/vfork.2.gz + S.5....T /usr/share/man/allman/man2/vhangup.2.gz + S.5....T /usr/share/man/allman/man2/vm86.2.gz + S.5....T /usr/share/man/allman/man2/wait.2.gz + S.5....T /usr/share/man/allman/man2/wait3.2.gz + S.5....T /usr/share/man/allman/man2/waitpid.2.gz + S.5....T /usr/share/man/allman/man2/writev.2.gz + SM5....T /usr/share/man/allman/man6 + SM5....T /usr/share/man/allman/man7 + SM5....T /usr/share/man/allman/man8 + SM5....T /usr/share/man/allman/man9 + SM5....T /usr/share/man/allman/mann + SM5....T /usr/src/linux-2.2.19.SuSE + SM5....T /usr/bin/rvim + SM5....T /usr/bin/vi + SM5....T /usr/bin/view + SM5....T /usr/bin/vimtutor + SM5....T /usr/bin/xxd + SM5....T /usr/share/vim/vim57/macros/hanoi + SM5....T /usr/share/vim/vim57/macros/life + SM5....T /usr/share/vim/vim57/syntax + SM5....T /usr/bin/sprof + SM5....T /usr/bin/tzselect + SM5....T /usr/bin/xtrace + S.5....T /usr/lib/locale/af_ZA/LC_NAME + S.5....T /usr/lib/locale/af_ZA/LC_NUMERIC + S.5....T /usr/lib/locale/af_ZA/LC_PAPER + S.5....T /usr/lib/locale/af_ZA/LC_TELEPHONE + S.5....T /usr/lib/locale/af_ZA/LC_TIME + SM5....T /usr/lib/locale/ar_BH + S.5....T /usr/lib/locale/ar_IQ/LC_COLLATE + S.5....T /usr/lib/locale/ar_IQ/LC_CTYPE + S.5....T /usr/lib/locale/ar_IQ/LC_IDENTIFICATION + S.5....T /usr/lib/locale/ar_IQ/LC_MEASUREMENT + S.5....T /usr/lib/locale/ar_IQ/LC_MONETARY + S.5....T /usr/lib/locale/ar_IQ/LC_NAME + S.5....T /usr/lib/locale/ar_IQ/LC_TELEPHONE + SM5....T /usr/lib/locale/ar_MA/LC_MESSAGES + SM5....T /usr/lib/locale/ar_OM + SM5....T /usr/lib/locale/ar_QA + SM5....T /usr/lib/locale/ar_SY/LC_MESSAGES + SM5....T /usr/lib/locale/ar_TN + SM5....T /usr/lib/locale/ar_YE + SM5....T /usr/lib/locale/bg_BG/LC_MESSAGES + SM5....T /usr/lib/locale/ca_ES + SM5..U.T /usr/lib/locale/ca_ES@euro + SM5....T /usr/lib/locale/de_AT/LC_MESSAGES + SM5....T /usr/lib/locale/de_AT@euro + SM5....T /usr/lib/locale/de_BE + SM5....T /usr/lib/locale/de_CH/LC_MESSAGES + SM5....T /usr/lib/locale/de_DE + S.5....T /usr/lib/locale/de_DE.utf8/LC_ADDRESS + S.5....T /usr/lib/locale/de_DE.utf8/LC_COLLATE + S.5....T /usr/lib/locale/de_DE.utf8/LC_IDENTIFICATION + S.5....T /usr/lib/locale/de_DE.utf8/LC_MEASUREMENT + S.5....T /usr/lib/locale/de_DE.utf8/LC_MESSAGES/SYS_LC_MESSAGES + S.5....T /usr/lib/locale/de_DE.utf8/LC_MONETARY + S.5....T /usr/lib/locale/de_DE.utf8/LC_NAME + S.5....T /usr/lib/locale/de_DE.utf8/LC_NUMERIC + S.5....T /usr/lib/locale/de_DE.utf8/LC_PAPER + S.5....T /usr/lib/locale/de_DE.utf8/LC_TELEPHONE + S.5....T /usr/lib/locale/de_DE.utf8/LC_TIME + SM5....T /usr/lib/locale/de_DE@euro/LC_MESSAGES + SM5....T /usr/lib/locale/de_LU + SM5....T /usr/lib/locale/de_LU@euro + SM5....T /usr/lib/locale/en_AU/LC_MESSAGES + SM5....T /usr/lib/locale/en_BW + SM5....T /usr/lib/locale/en_CA/LC_MESSAGES + SM5....T /usr/lib/locale/en_DK + S.5....T /usr/lib/locale/en_GB/LC_MONETARY + S.5....T /usr/lib/locale/en_GB/LC_NAME + S.5....T /usr/lib/locale/en_GB/LC_NUMERIC + S.5....T /usr/lib/locale/en_GB/LC_TELEPHONE + S.5....T /usr/lib/locale/en_GB/LC_TIME + SM5....T /usr/lib/locale/en_IE/LC_MESSAGES + SM5....T /usr/lib/locale/en_IE@euro + SM5....T /usr/lib/locale/en_NZ + SM5....T /usr/lib/locale/en_US + SM5....T /usr/lib/locale/en_US.utf8 + SM5....T /usr/lib/locale/en_ZA/LC_MESSAGES + SM5....T /usr/lib/locale/en_ZW + SM5....T /usr/lib/locale/es_AR/LC_MESSAGES + SM5....T /usr/lib/locale/es_BO + SM5....T /usr/lib/locale/es_CL + SM5....T /usr/lib/locale/es_CR/LC_MESSAGES + SM5....T /usr/lib/locale/es_EC + SM5....T /usr/lib/locale/es_ES + SM5....T /usr/lib/locale/es_HN/LC_MESSAGES + SM5....T /usr/lib/locale/es_MX + SM5....T /usr/lib/locale/es_NI + SM5....T /usr/lib/locale/es_PA + SM5....T /usr/lib/locale/es_PR/LC_MESSAGES + SM5....T /usr/lib/locale/es_PY/LC_MESSAGES + SM5....T /usr/lib/locale/es_SV + SM5....T /usr/lib/locale/es_US + SM5....T /usr/lib/locale/es_UY + SM5....T /usr/lib/locale/eu_ES/LC_MESSAGES + SM5....T /usr/lib/locale/eu_ES@euro + SM5....T /usr/lib/locale/fa_IR.utf8 + S.5....T /usr/lib/locale/fi_FI/LC_MESSAGES/SYS_LC_MESSAGES + S.5....T /usr/lib/locale/fi_FI@euro/LC_ADDRESS + S.5....T /usr/lib/locale/fi_FI@euro/LC_COLLATE + S.5....T /usr/lib/locale/fi_FI@euro/LC_CTYPE + S.5....T /usr/lib/locale/fi_FI@euro/LC_IDENTIFICATION + S.5....T /usr/lib/locale/fi_FI@euro/LC_MEASUREMENT + S.5....T /usr/lib/locale/fi_FI@euro/LC_MESSAGES/SYS_LC_MESSAGES + S.5....T /usr/lib/locale/fi_FI@euro/LC_MONETARY + S.5....T /usr/lib/locale/fi_FI@euro/LC_NAME + S.5....T /usr/lib/locale/fi_FI@euro/LC_NUMERIC + S.5....T /usr/lib/locale/fi_FI@euro/LC_PAPER + S.5....T /usr/lib/locale/fi_FI@euro/LC_TELEPHONE + S.5....T /usr/lib/locale/fi_FI@euro/LC_TIME + SM5....T /usr/lib/locale/fr_BE + SM5....T /usr/lib/locale/fr_CA/LC_MESSAGES + SM5....T /usr/lib/locale/fr_CH + SM5....T /usr/lib/locale/fr_FR/LC_MESSAGES + SM5....T /usr/lib/locale/fr_LU + SM5....T /usr/lib/locale/ga_IE/LC_MESSAGES + SM5....T /usr/lib/locale/ga_IE@euro + SM5....T /usr/lib/locale/he_IL + SM5....T /usr/lib/locale/id_ID + SM5....T /usr/lib/locale/it_CH/LC_MESSAGES + SM5....T /usr/lib/locale/it_IT + SM5....T /usr/lib/locale/it_IT@euro + SM5....T /usr/lib/locale/iw_IL + SM5....T /usr/lib/locale/ko_KR.euckr/LC_MESSAGES + SM5....T /usr/lib/locale/ko_KR.utf8 + SM5....T /usr/lib/locale/kw_GB + SM5....T /usr/lib/locale/lt_LT + SM5....T /usr/lib/locale/lv_LV/LC_MESSAGES + SM5....T /usr/lib/locale/mk_MK/LC_MESSAGES + S.5....T /usr/lib/locale/mr_IN.utf8/LC_ADDRESS + S.5....T /usr/lib/locale/mr_IN.utf8/LC_COLLATE + S.5....T /usr/lib/locale/mr_IN.utf8/LC_IDENTIFICATION + S.5....T /usr/lib/locale/mr_IN.utf8/LC_MEASUREMENT + SM5....T /usr/lib/locale/mr_IN.utf8/LC_MESSAGES + S.5....T /usr/lib/locale/mr_IN.utf8/LC_MONETARY + S.5....T /usr/lib/locale/mr_IN.utf8/LC_NAME + S.5....T /usr/lib/locale/mr_IN.utf8/LC_NUMERIC + S.5....T /usr/lib/locale/mr_IN.utf8/LC_PAPER + S.5....T /usr/lib/locale/mr_IN.utf8/LC_TELEPHONE + S.5....T /usr/lib/locale/mr_IN.utf8/LC_TIME + SM5....T /usr/lib/locale/mt_MT + SM5....T /usr/lib/locale/nl_BE@euro/LC_MESSAGES + SM5....T /usr/lib/locale/nl_NL + SM5....T /usr/lib/locale/nl_NL@euro/LC_MESSAGES + SM5....T /usr/lib/locale/nn_NO/LC_MESSAGES + SM5....T /usr/lib/locale/no_NO + SM5....T /usr/lib/locale/pl_PL + S.5....T /usr/lib/locale/pt_BR/LC_MESSAGES/SYS_LC_MESSAGES + S.5....T /usr/lib/locale/pt_PT@euro/LC_COLLATE + S.5....T /usr/lib/locale/pt_PT@euro/LC_IDENTIFICATION + SM5....T /usr/lib/locale/pt_PT@euro/LC_MESSAGES + S.5....T /usr/lib/locale/pt_PT@euro/LC_MONETARY + S.5....T /usr/lib/locale/pt_PT@euro/LC_NAME + S.5....T /usr/lib/locale/pt_PT@euro/LC_NUMERIC + S.5....T /usr/lib/locale/pt_PT@euro/LC_PAPER + S.5....T /usr/lib/locale/pt_PT@euro/LC_TELEPHONE + S.5....T /usr/lib/locale/pt_PT@euro/LC_TIME + SM5....T /usr/lib/locale/ru_RU.koi8r/LC_MESSAGES + SM5....T /usr/lib/locale/ru_RU.utf8 + SM5....T /usr/lib/locale/ru_UA/LC_MESSAGES + SM5....T /usr/lib/locale/sl_SI + SM5....T /usr/lib/locale/sv_FI + SM5....T /usr/lib/locale/sv_SE + SM5....T /usr/lib/locale/uk_UA/LC_MESSAGES + SM5....T /usr/lib/locale/vi_VN.utf8 + SM5....T /usr/lib/locale/zh_CN + SM5....T /usr/lib/locale/zh_CN.utf8 + SM5....T /usr/lib/locale/zh_TW + SM5....T /usr/lib/locale/zh_TW.utf8 + S.5....T /usr/share/locale/it/LC_MESSAGES/libc.mo + S.5....T /usr/share/locale/nl/LC_MESSAGES/libc.mo + SM5....T /usr/lib/zoneinfo + SM5....T /usr/share/zoneinfo The following devices were added: + ++ /var/lib/secchk/data/devices.new Sun Oct 6 23:15:02 2002 + brw-rw---- root disk 49, 79 /usr/lib/locale/es_DO/LC_MESSAGES + brw-rw---- root disk 49, 77 /usr/lib/locale/mr_IN.utf8/LC_CTYPE/LC_TELEPHONE + brw-rw---- root disk 49, 78 /usr/lib/locale/mr_IN.utf8/LC_CTYPE/LC_TIME ---schnapp--- The box is running SuSE 7.1 and masquerading our small LAN on an isdn multilink (ibod) DOD dial-up. netstat -tulpen shows: ---cut--- tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 30 2152897 14411/wwwoffled tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 30 2152896 14411/wwwoffled tcp 0 0 10.0.0.5:53 0.0.0.0:* LISTEN 0 2054547 28677/named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 0 2054545 28677/named tcp 0 0 0.0.0.0:6050 0.0.0.0:* LISTEN 0 1171726 27331/ibod tcp 0 0 0.0.0.0:20011 0.0.0.0:* LISTEN 0 1171577 27132/isdnlog tcp 0 0 :::22 :::* LISTEN 0 1171609 27231/sshd udp 0 0 0.0.0.0:2105 0.0.0.0:* 0 2054548 28677/named udp 0 0 10.0.0.5:53 0.0.0.0:* 0 2054546 28677/named udp 0 0 127.0.0.1:53 0.0.0.0:* 0 2054544 28677/named udp 0 0 0.0.0.0:67 0.0.0.0:* 0 1171701 27317/dhcpd ---schnapp--- ports < 1024 are closed by ipchains for external use. 8080,8081,6050 and 20011, too. Just 2105 udp is open. Chkrootkit did not claim anything except /usr/lib/perl5/5.6.0/i586-linux/.pcklist, however I think this is quite common. I checked the logs, but did not found anything suspicious. The files mentioned above are corrupted. Files in /etc/init.d/gpm or idedma, however, they are no longer executable. Even more strange /usr/src/linux-2.2.19.SuSE is a binary,too, and in this case it is world executable. I hoped dial-up gives some extra security, so I break some basic sec rules (compiler on the box etc.) but it seems that this was a personal error :(. However, since the logs did not show anything suspicious, I am not totaly sure, that it was a break in or some mad running script :(. Any idea on this topic greatly appreciated. TIA BTW: Sorry, for this long mail, since I am not sure what will be of assistance I prefered not to cut the logs. -- Maik

1 0

AW: [suse-security] only start one application uner X with autologin
by Ulrich Roth 07 Oct '02

07 Oct '02

Hello Martin, > I want to run a minimal linux-system and X with only one > application - started from an interactive shellscript - > running on an old pentium 200MHz. > No DisplayMgr, no WindowMgr, Hmm, is it possible to run X without GUI? AFAIK you can run Xvfb from the package "xextra" if you don't want X on your computer. Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth(a)impact.de

1 0

Two nameservers?
by Ingo Doerrie 07 Oct '02

07 Oct '02

Hello! Can anybody tell me a) why I should use two nameservers on a Firewall to protect the internal? Does this make sense? b) how to configure this on a SuSE 8.0 machine? Thank you in advance. -- Freundliche Grüße kind regards Ingo

1 0

general question about pachtes
by Jens Hoja 06 Oct '02

06 Oct '02

Hi everyone, i guess this is an newbie question: Wenn I patch a software like openssl does the version of the software change. The original version of openssl I had was openssl 0.9.6.c (this is the vulnerable version), but after a patch everything works fine (someone said in this newsgroup): >>if the latest rpm on suse update is the -80 then you're safe :) So the message in your logfile just show you that someone try to exploit the hole. But the version stays the same. Is this correct Mit freundlichem Gruß Jens Hoja

2 1

Problems with SuSEfirewall2 under 8.1
by Daniel Schulz 06 Oct '02

06 Oct '02

Hi everybody, I installed SuSE 8.1 yesterday and configurated the Firewall under /etc/sysconfig/SuSEfirewall2. But when I now try to run the Firewall following error occurs: nessaja:/etc/sysconfig # SuSEfirewall2 /sbin/SuSEfirewall2: line 696: test: 192.168.1.0/24: integer expression expected iptables v1.2.7a: host/network `ppp0' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.7a: Maximum prefix length 29 for --log-prefix Try `iptables -h' or 'iptables --help' for more information.. Thanks in advance. Daniel Schulz

2 3

[suse-security] wrong entries in btmp - hacked?
by Fritz Berger 06 Oct '02

06 Oct '02

Hi List! Is there a known bug in any program that leaves following entries between the correct ones in the btmp-file (viewed with last): H******* ****H******* H*******H******* Sun Apr 7 02:20 - down (10408+15:09 H******* ****H******* H*******H**** Thu Jan 1 01:00 - down (11948+19:50 *7 ****H******* Thu Jan 1 01:00 - down (11946+16:48 ...or am I hacked??? I'm running SuSE 8.0 Prof with all relevant security patches installed. Thank you for answers! Fritz

2 1

Missing 7.3 glibc i386 updates
by Leppo von Arenfels 05 Oct '02

05 Oct '02

Does anybody know why, not any 7.3 glibc and related RPM like tomezone is up on ftp.gwdg.de/*/i386/update/7.3/ anymore? Lost links stem from Aug., 30th, 17:58 CEST If they are withdrawn, why? Greetings, Leppo.

2 1

nur Anwendung unter X starten
by Martin.Probst＠gmx.at 04 Oct '02

04 Oct '02

Hallo Liste, ich möchte auf einem alten Arbeitsplatz-PC (Pentium 200MHz) eine minimales Linux-System installieren und genau eine X-Anwendung (Citrix-ICA Client) aus einem interaktiven shellskript starten. Es soll nur X also kein Display- oder Fenstermanager laufen. Auch soll der Benutzer nicht wissen als welcher Linux-User er angemeldet ist, schon gar nicht soll er mit einer Linux-Anmeldung konfrontiert werden. d.h. es sollte das System eine Art autologin durchführen. Meinen Frage: - Hat jemand Erfahrung mit Derartigem, auch was die Sicherheit des Systems betrifft ? DANKE Martin p.s. o.a. shellscript soll nur den gewünschten Citrix-Server des Users abfragen und dann die entsprechende Verbindung starten - dort gibt es dann ein Domänen-login. -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Günstige DSL- & Modem/ISDN-Tarife!

2 1

only start one application uner X with autologin
by Martin.Probst＠gmx.at 04 Oct '02

04 Oct '02

Sorry, I forgot that this is an english list :-/ OK, try again: Hi list, I want to run a minimal linux-system and X with only one application - started from an interactive shellscript - running on an old pentium 200MHz. No DisplayMgr, no WindowMgr, the shellscript asks the user for the desired Citrix-Metaframe-Server and then starts an ICA-Client-Session to this server. The user should not see any linux-login nor should he have to know his linux-username. this assumes something like autologin ... has anybody any ideas how to securely perform such things ? Thanks in advance Martin -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Günstige DSL- & Modem/ISDN-Tarife!

1 0

Off topic
by John Andersen 04 Oct '02

04 Oct '02

I know this is the wrong group... but I don't know the correct one. My Suse 8.1 Pro boxed set walked in the door and I was wondering if anyone else had problems installing from the DVD...? It reads it, and boots but can't find any packages to install. -- _________________________________________________ No I Don't Yahoo! And I'm getting pretty sick of being asked if I do. _________________________________________________ John Andersen / Juneau Alaska

3 2

DPT=3185 and DPT=53163
by David Huecking 03 Oct '02

03 Oct '02

Hello list, here are two SuSE i386 8.0 Pro boxes sending a bunch of packets to the standard-gateway when the machines are booted. The destination ports of the packets are first 3185 and then 53163. The sending is repeated some times and then the PCs are quiet. I noticed that behaviour because the packets are dropped by the NAT firewall everytime. What could that be? - I didn't find any suspicious processes. The only hint I found was that the SuSE Meta PPP Daemon (smpppd) is using port 53163 and 3185, but according /sbin/chkconfig smpppd is turned off! There is also no link in a rc-directory and no process. And another box also running SuSE 8.0 with installed smpppd does not show that behaviour. -- Eat, sleep and go running, David Huecking. Encrypted eMail welcome! GnuPG/ PGP-Fingerprint: 3DF2 CBE0 DFAA 4164 02C2 4E2A E005 8DF7 5780 9216

1 0

tar and unzip vulnerabilities
by Michael Salmon 03 Oct '02

03 Oct '02

RH has released updates for tar and unzip: Description: The unzip and tar utilities are used for manipulating archives, which are multiple files stored inside of a single file. A directory traversal vulnerability in unzip version 5.42 and earlier, as well as GNU tar 1.13.19 and earlier, allows attackers to overwrite arbitrary files during archive extraction via a ".." (dot dot) in an extracted filename. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2001-1267 and CAN-2001-1268 to this issue. In addition, unzip version 5.42 and earlier also allows attackers to overwrite arbitrary files during archive extraction via filenames in the archive that begin with the "/" (slash) character. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2001-1269 to this issue. During testing of the fix to GNU tar, it was discovered that GNU tar 1.13.25 was still vulnerable to a modified version of the same problem. Red Hat has provided a patch to tar 1.3.25 to correct this problem. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2002-0399 to this issue. It doesn't seem much of a problem unless you are running as root and don't look check the contents first. I thought that I'd ask to see if there was anything in the pipeline though. /Michael -- This space intentionally left non-blank.

2 1

initiate personal firewall and apply config files
by Susan Buczak 03 Oct '02

03 Oct '02

3 items; how does one go about initiating the personal-firewall the first time for suse8.0? Yast2 will start configuration for suseFirewall2 but there isn't any source help for initiating the personal firewall. calling it from /sbin does nothing. Second, I need to configure certain /etc files, for instance I want only certain local users in access.conf. When I make the changes the system doesn't recognize that the files have been changed. Likewise I tried setting su to group wheel for admin only and chmod to 4750 so only wheel can use it, and on reboot it allows everyone to attempt login again, it reset itself. thanks, Susan

5 4

Fou4s 0.7.3
by Markus Gaugusch 02 Oct '02

02 Oct '02

After installing SuSE 8.1 tonight, I had to find out, that fou4s didn't work with it. So, here's a new version :-) http://fou4s.gaugusch.at/ It's a branch of 0.7.2, so no business features yet. Self-update should work even on 8.1. fou4s -i --checkfou4s Markus PS: 8.1 install went great, except for not installing in graphics mode after CD1, but this was because I didn't downgrade the NVidia drivers and the installed ones had no kernel module for the new kernel. -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(a)gaugusch.at X Against HTML Mail / \

1 0

SSL and KDE 3.03
by Doug Glenn 02 Oct '02

02 Oct '02

When are the patches to Konquerer 3.03 going to be posted to fix the SSL vunerability? I note you can get it via the KDELNKs section, but it does not show up via YOU Regards, Doug

2 2

SuSE Security Announcement: heimdal (SuSE-SA:2002:034)
by Sebastian Krahmer 02 Oct '02

02 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: heimdal Announcement-ID: SuSE-SA:2002:034 Date: Mon Sep 30 17:00:00 CEST 2002 Affected products: SuSE Linux 7.2, 7.3, 8.0, SuSE eMail Server, SuSE Linux Connectivity Server, SuSE Linux Enterprise Server 7, SuSE Linux Office Server Vulnerability Type: remote command execution Severity (1-10): 8 SuSE default package: Yes Cross References: http://www.pdc.kth.se/heimdal Content of this advisory: 1) security vulnerability resolved: Various overflows in heimdal. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - ghostview/kghostview - fetchmail 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The Heimdal package is a free Kerberos implementation offering flexible authentication mechanisms based on the Kerberos 5 and Kerberos 4 scheme. The SuSE Security Team has reviewed critical parts of the Heimdal package such as the kadmind and kdc server. While doing so several possible buffer overflows and other bugs have been uncovered and fixed. Remote attackers can probably gain remote root access on unpatched systems. Since these services run usually on authentication servers we consider these bugs to be very serious. An update is strongly recommended if you are using the Heimdal package. 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. To be sure the update takes effect you have to restart the services which belong to the heimdal package. As root execute the command /etc/rc.d/kdc restart If you are running other Kerberos based services such as hpropd make sure you also restart them as well. i386 Intel Platform: SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/d4/heimdal-devel-0.4e-191.i386.… 9dcb318864c2ad7c8bb11a51b0c1e12a ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/heimdal-lib-0.4e-191.i386.… 7971b5a482b0f8521c0a8bd07182be36 ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/heimdal-0.4e-191.i386.rpm fb6792204a9ec58f69a9dc7b4bcbed59 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/heimdal-0.4e-191.src.rpm 976383f4b7eeabcfc48ab4360a14586f SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/heimdal-0.4d-132.i386.rpm d2f174640a8d3b976eef3ff3afb642ee ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec2/heimdal-devel-0.4d-132.i38… fad86035d9b94aa50a9225c9e40618da source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/heimdal-0.4d-132.src.rpm 5d3afb07af86563e5eff5f0fad6113d4 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/heimdal-lib-0.3e-83.i386.r… 7a5f3f3e1c16481b6dea589bedd7ee44 ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/heimdal-0.3e-83.i386.rpm f94d2a88a2100b2b28496b1a8f3030c4 ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec2/heimdal-devel-0.3e-83.i386… d4fa5f75cb1d422fe439a276fdfe8aca source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/heimdal-0.3e-83.src.rpm a42a3535e0bd5966eb8b9d017213dfb5 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/heimdal-lib-0.4d-67.sparc… c50802492db0e8728d666f3b38b7ca5e ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/heimdal-0.4d-67.sparc.rpm 595d21ca05b8c886c0887189bb76487d ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec2/heimdal-devel-0.4d-67.spa… 1dfe9d49c83303ddf3490497dffce7fa source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/heimdal-0.4d-67.src.rpm 7c61896ca257f79656e35bc59e1de734 PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/heimdal-lib-0.4d-113.ppc.rpm e905e8c468b9eddef6b8a785d5241914 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/heimdal-0.4d-113.ppc.rpm 7b816aa786118e481be811be6974177f ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec2/heimdal-devel-0.4d-113.ppc.… 100f9fbe35d82dcf02aed98aa70103b8 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/heimdal-0.4d-113.src.rpm 24467d712a359516ae60462c56dc97df ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - ghostview/kghostview Bufferoverflows have recently been discovered in these packages. They allow attackers to execute arbitrary code with the privileges of the user viewing special crafted documents created by the attacker. New packgaes will soon be available on our ftp servers. - fetchmail Fetchmail contains remotely exploitable overflows in the mail header parsing functions. In depth discussion of these problems can be found at http://security.e-matters.de/advisories/032002.html. New packages will soon be 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: 2.6.3in Charset: noconv iQEVAwUBPZhp63ey5gA9JdPZAQGBSAf+PjBSNoZVnkySDmBABDYI3QFbezFDgZ7y 0cpd3jtDBDgr7nyki2H3kUIpk0TW8JqfKrq4psnwDS3minbrxy6iS08iC/CFDj1m 3n+pdGxrcSfGbiYQke4Pn7fiUwCyv2DVeLCoI/b0dik38JOMDNvXp0Rjv2/2uEZJ itc3QV1ocxTx3Q064DAsU3Ll7W9THjGd47eRz6QVott01eBjlDZTaw9gtVvyN99T ooQArj5yhoErRXTkc/V1ttz2MahmvxeB7ohxyMl/26UQ2BWVk71T4mqo1vWEmzv1 59+7cbnjUzIw4iq5G99xkWEVgSgaiFwc8q0BrcwE6KNPhmXAngEq6w== =yeEG -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

4 4

forcing connection (newbie question)?
by Mario Ohnewald 02 Oct '02

02 Oct '02

Hello! I work in a tiny company and we have a SuSEfirewall, wich i can not access or influence, cause its set up by a 3rd Person. LINUX_HOME FIREWALL LINUX_WORK ------------> | Traffic from LINUX_WORK to external is allowed. I´m root on LINUX_HOME and LINUX_WORK. Can i somehow force a ssh connection from LINUX_WORK to LINUX_HOME (the other way is not possible due to the firewall) so that i can connect from HOME to WORK? I guess its not possbile, but worth to ask ;) Cheers, Mario

3 4

RE: [suse-security] VPN server setup for windows clients
by Reckhard, Tobias 02 Oct '02

02 Oct '02

Re > I have been running a non-routing dual-homed host as a firewall for a > while now with SuSEfirewall and all required services proxied > with Squid, > SuSE ftp-proxy, etc. OK, I've understood that. :-) > I thought I would have a go at setting up a VPN > server for windows '98 machine to connect up through the > internet and, on > a first reading through the documentation, it appears that I have to > allow IP packets to be routed through the machine, i.e. with > masquerading, rather than redirected. > > Is this correct? If so the job changes in nature. This is correct, at least for IPSec using FreeS/WAN. However, you typically don't use masquerading in IPSec VPNs and it can cause serious problems. If you're contemplating to use PPTP, which doesn't seem entirely unlikely, seeing as you've got Win98 machines, I'm not sure, I haven't dealt with that daemon yet myself (and don't plan to, as I normally advise people to steer clear of PPTP, at least the MS implementation). Cheers Tobias

1 0

Apache/mod_ssl Worm
by Raul Horacio Lapitzondo 02 Oct '02

02 Oct '02

What is this ? In the Apache Log appear the next error: mod_ssl: SSL handshake failed (server lapi.hn.org:443, client xxx.xxx.xxx.xxx) (OpenSSL library error follows) OpenSSL: error:1406B458:lib(20):func(107):reason(1112) I have SuSE 8.0 whith: mod_ssl-2.8.7-105 openssl-0.9.6c-80 Apache/1.3.23 (Unix) Any suggestion?

3 3

SuSE Security Announcement: glibc (SuSE-SA:2002:031)
by Roman Drahtmueller 02 Oct '02

02 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: glibc Announcement-ID: SuSE-SA:2002:031 Date: Friday, Aug 30th 2002 19:00 MEST Affected products: 7.0, 7.1, 7.2, 7.3, 8.0 SuSE Linux Database Server, SuSE eMail Server III, SuSE Linux Enterprise Server, SuSE Linux Firewall on CD SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: local/remote privilege escalation Severity (1-10): 6 SuSE default package: yes Cross References: CAN-2002-0391, CERT CA-2002-25 Content of this advisory: 1) security vulnerability resolved: glibc problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - ethereal 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information An integer overflow has been discovered in the xdr_array() function, contained in the Sun Microsystems RPC/XDR library, which is part of the glibc library package on all SuSE products. This overflow allows a remote attacker to overflow a buffer, leading to remote execution of arbitrary code supplied by the attacker. 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: * The update packages for the SuSE Linux distributions 7.0 and 7.1 have not been built yet. The packages for these distributions will be published in approximately two weeks (mid September) from now. * The names of both the source RPM as well as the binary RPM (sub-) packages have changed between different SuSE Linux products. Overview: dist | source-RPM | shared libs | static libs,header| profiling ----------------------------------------------------------------------- 7.0 libc shlibs libc libd all SuSE products after and including SuSE Linux 7.1 glibc glibc glibc-devel glibc-profile Find out which of the four packages are installed on your system according to the package names in the table. Use the command rpm -q name_of_package to query the package database for each name. If you have your package list, download the packages that you need from the URLs as listed below. Verify their integrity and authenticity following the guidelines as described in section 3) of this security announcement. * 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 diskspace 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.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/a1/glibc-2.2.5-123.i386.rpm 57bb8eb5e4355539f01ee9dc2e1b790e ftp://ftp.suse.com/pub/suse/i386/update/8.0/d2/glibc-devel-2.2.5-123.i386.r… cf1a18510a8e78914500c10cc9b79bf0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/glibc-profile-2.2.5-123.i386… a03333bb8a0bd77def78b633d790fdb2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/glibc-2.2.5-123.src.rpm 5ca1e41a5ab22282b0cd0ecc5c286093 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/a1/glibc-2.2.4-75.i386.rpm b6c392faf66f4a3e23f9f8ba70166496 ftp://ftp.suse.com/pub/suse/i386/update/7.3/d1/glibc-devel-2.2.4-75.i386.rpm f4616d3ddcaef2847b113f2ac7a86866 ftp://ftp.suse.com/pub/suse/i386/update/7.3/d2/glibc-profile-2.2.4-75.i386.… a8d5377fc289837c5b9d7902785ea1fe source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/glibc-2.2.4-75.src.rpm 646af6d0e99f54fd03eb0ec99449df36 SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/a1/glibc-2.2.2-64.i386.rpm 1408ad17ef2bc543cb9ff42cb2813f99 ftp://ftp.suse.com/pub/suse/i386/update/7.2/d1/glibc-devel-2.2.2-64.i386.rpm 283d808402eed8f0f4a8ae2b64b91e17 ftp://ftp.suse.com/pub/suse/i386/update/7.2/d2/glibc-profile-2.2.2-64.i386.… d23a61431b924e5c2e09861463f5489d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/glibc-2.2.2-64.src.rpm 9019bbfd6a6952bb154bdcf7cd8d37d3 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/a1/glibc-2.2.4-43.sparc.rpm df6be3f3b427f4ca6cd27b12dbf16fc8 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/d1/glibc-devel-2.2.4-43.sparc.… f90e87513d996235cb2711286371dfae ftp://ftp.suse.com/pub/suse/sparc/update/7.3/d2/glibc-profile-2.2.4-43.spar… bc659d5181c4d571950821a978fa6ab2 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/glibc-2.2.4-43.src.rpm 846403d32700d8173e10932517926fc3 AXP Alpha Platform: - no new packages - PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/a1/glibc-2.2.4-63.ppc.rpm 2294e4d4777954e7d7c85b6a4e5c8ef7 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d1/glibc-devel-2.2.4-63.ppc.rpm f68b4b421cd5af4e62a80e9a2c803bd6 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d2/glibc-profile-2.2.4-63.ppc.rpm 0f837c5c1e4bac59e73a0d23b0d88187 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/glibc-2.2.4-63.src.rpm fdef49ff7f4ec9546f1e9d8bd46e8fa9 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - ethereal Multiple overflows and other security related problems have been found in ethereal, a network traffic analyzer program. We have provided update packages on our ftp server that upgrade the ethereal package to the latest version 0.9.6. A backport of the security fixes to the versions supplied in the released SuSE Linux products does not seem feasible. We will not release an own announcement for this specific problem. - postgresql A buffer overflow has been found in the postgresql database management system. We are about to prepare update packages for this vulnerability. - openldap2 Andrew McCall reported a problem within the openldap2 package which could lead to a denial of service attack against the slapd server. This problem has been fixed. New openldap2 packages will soon be available. ______________________________________________________________________________ 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----- Roman Drahtmüller, SuSE Security. - -- - - | Roman Drahtmüller <draht(a)suse.de> // "You don't need eyes to see, | SuSE Linux AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPW+lVney5gA9JdPZAQF0cQf/bLrFDn0vzfXuT+LZ+lME3R438/PM9IOU XfUKz8rKJk14pkHMHxI6MCxzQnNS41jajE9XkG6i4z89bGy5+8cXShl6Jl+woVWN iwCJC8U1BgMKXHq3ns5c0+YzQpD7f7YQSUUXoCLoARNYMS/A8b4FHmX942uurjKg u4VKCe4nV0VY9ydn8hHtb+AtA/2FEkuK2J7b5jeh80UeC0ZzysahawB8zyOmaOYm ip1ji2YmuKzsVcVd1Wy7gQUkUmzTIxGX7XB4UaAJY99NeXkeBapRgDKRgNVdj06a QVu1Yh/0jA4XptOIUlBdwYLUPckRR0EV3xeYl6kmb/V7cDJesvGHRw== =g3B7 -----END PGP SIGNATURE-----

5 10

Problem compiling dazuko with SuSE 8.0
by Claus-Peter Fröhlich 01 Oct '02

01 Oct '02

I'm a newbie to linux and have got a problem compiling dazuko 1.1.0 with my SuSE Linux 8.0 pro. I've installed the kernel-source-rpm (2.4.18-4GB) and made a symbolic link so that dazuko can find the kernel sources. Afterwards I configured a kernel and made the dependencies. Compiling the dazuko module didn't produce a error, but trying to integrate the module using the insmod command produces an error, that the specified IRQ or IO-adress isn't valid.

2 2

Re: [suse-security] LDAP, Novell and Squid
by GentooRulez 01 Oct '02

01 Oct '02

> In a private LAN we have NT- and Win2k- Workstations with > Novell-Netware-Clients, getting their IP-Addresses via DHCP. > > On a Suse-7.2-Linux-Box runs Squid, which is the one and only host > of the private LAN allowed to cross the Firewall with http-related > requests. > > A Netware-Server with LDAP installed, translates NDS-Attributes of > our choice to LDAP. > > According to our Policies only some of our users are allowed to surf > the net. > > To enable these "privileged" users, we put them into a certain > NDS-group. On the squidhost every 15 Minutes runs a perlscript, which > asks the LDAP Server for a list of IP-Adresses, where members of this > group are currently logged in. This list is than formatted as an > Client-Adress-ACL for squid. > > Hence users have to authenticate themselves only once to the > Netware-Server and get enabled or not - independent of their current > IP-Adresses - iff they are members of this privileged group. This is even better then social engineering (ok, maybe its exactly that). Ask for a mouse and get the whole elephant. The only thing i missed was a short excerpt from some of your logs with your ip's in it :O), so would i've to check it for myself. > Dr. H. Rosner > Stadtverwaltung Jena > Hauptamt / Datenverarbeitung A paranioc user :O) Think about ! Michael

2 1