September 2006 - openSUSE Security - openSUSE Mailing Lists

SUSE Security Announcement: openssl security problems (SUSE-SA:2006:058)
by Marcus Meissner 15 Mar '07

15 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: openssl Announcement ID: SUSE-SA:2006:058 Date: Thu, 28 Sep 2006 18:00:00 +0000 Affected Products: Novell Linux Desktop 9 Novell Linux POS 9 Open Enterprise Server SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SuSE Linux Openexchange Server 4 SUSE LINUX Retail Solution 8 SuSE Linux School Server SuSE Linux Standard Server 8 SUSE SLED 10 SUSE SLES 10 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: remote denial of service Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-2937, CVE-2006-2940, CVE-2006-3738 CVE-2006-4343, VU#547300, VU#386964 Content of This Advisory: 1) Security Vulnerability Resolved: several security problems in openssl Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion Several security problems were found and fixed in the OpenSSL cryptographic library. CVE-2006-3738/VU#547300: A Google security audit found a buffer overflow condition within the SSL_get_shared_ciphers() function which has been fixed. CVE-2006-4343/VU#386964: The above Google security audit also found that the OpenSSL SSLv2 client code fails to properly check for NULL which could lead to a server program using openssl to crash. CVE-2006-2937: Fix mishandling of an error condition in parsing of certain invalid ASN1 structures, which could result in an infinite loop which consumes system memory. CVE-2006-2940: Certain types of public key can take disproportionate amounts of time to process. This could be used by an attacker in a denial of service attack to cause the remote side top spend an excessive amount of time in computation. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes None. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv <file.rpm> to apply the update, replacing <file.rpm> with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/openssl-0.9.8a-18.10.i586.… f5d7a08e60a52b7816cae88e9def7762 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/openssl-devel-0.9.8a-18.10… a583491fc985dff2f3f405776fa8554a SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/openssl-0.9.7g-2.10.i… 13d07a7a3b81fdef9ba68b0f0670f14c ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/openssl-devel-0.9.7g-… 1198085023a60d99ce90207b5498db45 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/openssl-0.9.7e-3.6.i58… 51606d0da43bc5c61562bb8d4679ca8b ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/openssl-devel-0.9.7e-3… c6a9122fec64b5a82f433c56b602f2b5 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/openssl-0.9.7d-25.6.i5… 96b59a2af5663ae1f780626da0b5756a ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/openssl-devel-0.9.7d-2… e33a86104b85919dda444b4a9901a10b Power PC Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/openssl-0.9.8a-18.10.ppc.rpm 8310266cd6da01baaf964ed8cac841c0 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/openssl-devel-0.9.8a-18.10.… 8ff4b94e685be05d00599ecc6cc939e7 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/openssl-0.9.7g-2.10.pp… 0678839057c3170dc84fab28b3dd202f ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/openssl-devel-0.9.7g-2… e86965c19538073b15c2131a04c20260 x86-64 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-0.9.8a-18.10.x86… 28dc138c088450b753fdd419c487023e ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-32bit-0.9.8a-18.… 651d62cab3c31d0bc3e18b91a4ba9ac3 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-devel-0.9.8a-18.… 2a3e98aca1aa613a58f09b39f12e84a4 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-devel-32bit-0.9.… 81bb446763424df4c18eac760e0ed80e SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-0.9.7g-2.10… 5a612bd7a6756e2926a3ef59a72fd197 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-32bit-0.9.7… 840e98707317d9cef51837a486541be7 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-devel-0.9.7… 46b1a289d445c5304001aba4417e73a9 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-devel-32bit… a4e2a59c151ff22ed683e115da8fce48 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-0.9.7e-3.6.x… 3bf35d8e03848aa87a662b93a8c14fe1 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-32bit-9.3-7.… 35ce818f05f655397c4b1b13ba3a93b3 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-devel-0.9.7e… dcfbcadb626de068028ac546f07ba685 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-devel-32bit-… da50170edc9a2596954c2453030494d6 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-0.9.7d-25.6.… 32ec53e71eefb0ebe893034ac2e552ac ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-32bit-9.2-20… 0b7706ce568832eb1b2e86bdd7cbe51d ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-devel-0.9.7d… c8671a7a77dcc5a08e2c19f9a6ff056c ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-devel-32bit-… 2bebb0fea9579ca5e659fca63c7beac0 Sources: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/openssl-0.9.8a-18.10.src.rpm 2613501ca4ea03f1a79548014b13ff67 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/openssl-0.9.7g-2.10.sr… c5b1ff892ff74af82ddbceaf757c6fb3 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/openssl-0.9.7e-3.6.src.… f62e34422fc77343fd15a1790e6ef8d8 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/openssl-0.9.7d-25.6.src… 8c451560ea55a3bec1b01f0b36943048 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: UnitedLinux 1.0 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SuSE Linux Openexchange Server 4 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… Open Enterprise Server http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… Novell Linux POS 9 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… Novell Linux Desktop 9 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SuSE Linux Enterprise Server 8 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SuSE Linux Standard Server 8 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SuSE Linux School Server http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SUSE LINUX Retail Solution 8 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SuSE Linux Desktop 1.0 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SUSE SLES 10 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SUSE SLED 10 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… SUSE SLES 9 http://support.novell.com/techcenter/psdb/16e2a93b390a1ceb86b0945a88a4d415.… ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify <file> replacing <file> with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made <DATE> using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team <security(a)suse.de>" where <DATE> is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. 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) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal 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, replacing <file.rpm> with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from build(a)suse.de with the key ID 9C800ACA. This key is automatically imported into the RPM database (on RPMv4-based distributions) and the gpg key ring of 'root' during installation. You can also find it on the first installation CD and at the end of this announcement. 2) If you need an alternative means of verification, use the md5sum command to verify the authenticity of the packages. Execute the command md5sum <filename.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 SUSE security announcement. Because the announcement containing the checksums is cryptographically signed (by security(a)suse.de) the checksums show proof of the authenticity of the package if the signature of the announcement is valid. Note that the md5 sums published in the SUSE Security Announcements are valid for the respective packages only. Newer versions of these packages cannot be verified. - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - General Linux and SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an e-mail 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 e-mail 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>. ===================================================================== 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, the clear text signature should show proof of the authenticity of the text. SUSE Linux Products GmbH provides 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.4.2 (GNU/Linux) mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBmQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCk YS3yEKeueNWc+z/0Kvff4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP +Y0PFPboMvKx0FXl/A0dM+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR 8xocQSVCFxcwvwCglVcOQliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U 8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0S cZqITuZC4CWxJa9GynBED3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEh ELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtB UVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOo AqajLfvkURHAeSsxXIoEmyW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1n KFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohi BBMRAgAiBQJA2AY+AhsDBQkObd+9BAsHAwIDFQIDAxYCAQIeAQIXgAAKCRCoTtro nIAKypCfAJ9RuZ6ZSV7QW4pTgTIxQ+ABPp0sIwCffG9bCNnrETPlgOn+dGEkAWeg KL+IRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lx yoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWn B/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDV wM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklLsnr35SJDZ6ram51/CWOnnaVh UzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF 5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3 D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGu zgpJt9IXSzyohEJB6XG5+D0BuQINBDnu9JIQCACEkdBN6Mxf5WvqDWkcMRy6wnrd 9DYJ8UUTmIT2iQf07tRUKJJ9v0JXfx2Z4d08IQSMNRaq4VgSe+PdYgIy0fbj23Vi a5/gO7fJEpD2hd2f+pMnOWvH2rOOIbeYfuhzAc6BQjAKtmgR0ERUTafTM9Wb6F13 CNZZNZfDqnFDP6L12w3z3F7FFXkz07Rs3AIto1ZfYZd4sCSpMr/0S5nLrHbIvGLp 271hhQBeRmmoGEKO2JRelGgUJ2CUzOdtwDIKT0LbCpvaP8PVnYF5IFoYJIWRHqlE t5ucTXstZy7vYjL6vTP4l5xs+LIOkNmPhqmfsgLzVo0UaLt80hOwc4NvDCOLAAMG B/9g+9V3ORzw4LvO1pwRYJqfDKUq/EJ0rNMMD4N8RLpZRhKHKJUm9nNHLbksnlZw rbSTM5LpC/U6sheLP+l0bLVoq0lmsCcUSyh+mY6PxWirLIWCn/IAZAGnXb6Zd6Tt IJlGG6pqUN8QxGJYQnonl0uTJKHJENbI9sWHQdcTtBMc34gorHFCo1Bcvpnc1LFL rWn7mfoGx6INQjf3HGQpMXAWuSBQhzkazY6vaWFpa8bBJ+gKbBuySWzNm3rFtT5H RKMWpO+M9bHp4d+puY0L1YwN1OMatcMMpcWnZpiWiR83oi32+xtWUY2U7Ae38mMa g8zFbpeqPQUsDv9V7CAJ1dbriEwEGBECAAwFAkDYBnoFCQ5t3+gACgkQqE7a6JyA CspnpgCfRbYwxT3iq+9l/PgNTUNTZOlof2oAn25y0eGi0371jap9kOV6uq71sUuO =ypVs - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBRRv66Xey5gA9JdPZAQL7fgf/WskObtJd6xDwy4d+F9TjeGy+K3Mi8iNC Meb8Chs08TaVuuuvp6+UwtUpek+zuMTimdUZdedF4Tc3xBjwQL6GmIvdh5Kr5vdA UZRnHUMWdD9ClKyc3KPKVHXrDGOmgytWVtaQdD4pSmrh6k7j5aE9Gsss1MSrI64u BefsTWYnoJ0OJ/iXFVIIh964A/6wBcFV6f0C9YWKMYjfylXPBTWlSBzhY69g722N kmgboFffBkxD37ILQSKygJrJ3N2fn6acN7pRylCEb+n0XWu5nPMf/xTWVVzH4f/I FS5jdzJc7gfb096tWsNoB48ULkLENIaauHZup1p6NCyt5/R3eLmgcQ== =TSxY -----END PGP SIGNATURE-----

6 6

Encrypted filesystem on loop file
by Carlos E. R. 01 Oct '06

01 Oct '06

Hi, I'm trying to create an encrypted filesystem via Yast partitioner in SuSE 10.1, using a file mounted via the loop device. I have done this before, in fact I have two such things created under 9.3 running; but I can't (couldn't) with 10.1, it is creating a plain non encrypted filesystem instead. Or so it seemed. Looking carefully again, after several runs, I noticed that it was mounting the filesystem as plain non encrypted, but it was in fact creating an encrypted one with the appropriate entry en /etc/cryptotab instead of in /etc/fstab - whereas in 9.3 it created then in /etc/fstab instead, and in 8.x they were created in /etc/cryptotab. This criteria change is very confusing. Perhaps Yast could ask where the user wanted to define it - feature request, perhaps? It's not only a config file difference; an encrypted filesystem defined in /etc/fstab can be mounted with the command mount, but one defined in /etc/cryptotab is mounted via the command "/etc/init.d/boot.crypto start", which is less comfortable for manual mount after boot (and it mounts all devices listed, even if already mounted). /etc/cryptotab sample line: /dev/loop3 /file3 /crypta3 ext3 twofish256 acl,user_xattr /etc/fstab, the equivalent sample line: /file3 /crypta3 ext3 noauto,acl,user_xattr,loop=/dev/loop3,encryption=twofish256 0 0 Both work with the same file, I tried. I'll stay with the second one. But in 9.3 the fstab line was instead (incompatible): /file2 /crypta2 ext3 noauto,acl,user_xattr,loop=/dev/loop2,encryption=twofish256,phash=sha512,itercountk=100 Comments? Also, how would I create the equivalent encrypted filesystem manually; docus, howtos? Tks. -- Cheers, Carlos Robinson

2 2

[suse-security] Deny access to file for all applications with apparmor?
by Boyan Tabakov 01 Oct '06

01 Oct '06

Hi, I was recently going through the manuals of apparmor. As far as I could understand you can create profiles for specific executables. I was wondering, however, is it possible to create a 'generic' profile that should be applied to ANY process started. Or, what I really want to accomplish, how can I deny access to specific file for ALL processes, except, let's say one or two? If I understand the concept right, this can't be done, but let me know if I am wrong, please! -- Blade hails you... Toll no bell for me father But let this suffering pass from me Send me no shepherd to heal my world But the Angel - the dream foretold --Nightwish

2 4

SuSEfirewall 2 - redirect ports on internal interface to DMZ
by Dirk Enrique Seiffert 30 Sep '06

30 Sep '06

I am moving a Mailserver from the internal network to the DMZ. This move should be invisible for the enduser. Lat but not least: Some hundred mail clients are configured to consult an IP, not a name: I can't solve the issue by configuring my DNS server. This is my configuration: 200.x.x.x (public IP) | SuSEfirewall-192.168.254.1--------192.168.254.2 MailServer | 192.168.0.249 | internal network I have to access the mailserver by an IP in the 192.168.0.0/24 range. External traffic I can easily redirect with FW_FORWARD_MASQ= to an IP in the DMZ. Internal traffic I can redirect to a local port on the firewall with FW_REDIRECT. Is it possible to redirect all traffic coming on the internal interface for 192.168.0.249 to 192.168.254.2 ? Any Custom rule? I was googling quite a while to, didn't find any rule doing a forward on the internal interface. Any idea is appreciated! Thanks Enrique -- Dirk Enrique Seiffert - Lintec S.A. Ed. Torre del Reloj - Of. 401 Plaza de los Coches, Centro Cartagena - Colombia http://www.lintecsa.com -- Este mensaje ha sido analizado por MailScanner en busca de viruses y otros contenidos peligrosos, y se considera que est limpio.

3 3

Suse 10.1 and update
by Cristian Del Carlo 29 Sep '06

29 Sep '06

Hi list, I tried to install a suse 10.1 as mail server. The installation was good by i was unable to update the system. "You" didn't find any update. What are the necessary condictions to work with zen management agent? Best regards, Cristian Del Carlo

4 3

Re: [suse-security] Re: SuSEfirewall 2 - redirect ports on internal interface to DMZ
by mail＠pv-consulting.com 28 Sep '06

28 Sep '06

Good day, I was recently fiddling around with this port forwarding issue myself. Using Susefirewall2 on a Suse 9.3 Pro allowed me to forward a port on my external IP to another port on a machine behind my firewall. However, using the same script on Novell OES (=SLES9) resulted in nothing. I then tried rinetd but dropped that again because it only forwards tcp ports, not udp. Anyway, would someone have any hints about this difference in behaviour between Suse Pro 9.3 and SLES9? Regards, Peter ____________________________ PV consulting Maria van Bourgondiëlaan 18 - B-8000 Brugge GSM +32 478 317 657 - fax +32 50 34 61 60 - skype peter.vynck e-mail mail(a)pv-consulting.com - http://www.pv-consulting.com -----"Ariel Guerrero" <ariel.guerrero(a)gmail.com> wrote: ----- To: "Dirk Schreiner" <Dirk.Schreiner(a)tria.de> From: "Ariel Guerrero" <ariel.guerrero(a)gmail.com> Date: 28/09/2006 00:30 cc: "Dirk Enrique Seiffert" <ds(a)caribenet.com>, suse-security(a)suse.com Subject: [suse-security] Re: SuSEfirewall 2 - redirect ports on internal interface to DMZ You could try with this rule. I'm not an expert in SuSEfirewall2.... FW_FORDWARD_MASQ="192.168.0.0/24,192.168.0.249,tcp,110,110,192.168.254.2/ 192.168.0.0/24,192.168.0.249,tcp,25,25,192.168.254.2" I use your configuration to make the example, and this is the syntax: <source network>.<ip to forward to>,<protocol>,<port>[redirect port,[destination ip]] I use it to redirect my local webserver and it work it. Sorry for my english, i'm Paraguayan.. Greetz 2006/9/27, Dirk Schreiner <Dirk.Schreiner(a)tria.de>: > Hi Dirk, > > checkout rinetd. > It should solve youre Problems. > > Dirk > > > Dirk Enrique Seiffert schrieb: > > I am moving a Mailserver from the internal network to the DMZ. This move > > should be invisible for the enduser. Lat but not least: Some hundred mail > > clients are configured to consult an IP, not a name: I can't solve the > > issue by configuring my DNS server. > > > > This is my configuration: > > > > > > 200.x.x.x (public IP) > > | > > SuSEfirewall-192.168.254.1--------192.168.254.2 MailServer > > | > > 192.168.0.249 > > | > > internal network > > > > > > I have to access the mailserver by an IP in the 192.168.0.0/24 range. > > External traffic I can easily redirect with FW_FORWARD_MASQ= to an IP in > > the DMZ. Internal traffic I can redirect to a local port on the firewall > > with FW_REDIRECT. > > > > Is it possible to redirect all traffic coming on the internal interface > > for 192.168.0.249 to 192.168.254.2 ? > > > > Any Custom rule? I was googling quite a while to, didn't find any rule > > doing a forward on the internal interface. > > > > Any idea is appreciated! > > > > Thanks > > > > Enrique > > > > > > > > -- > There are 10 sorts of people in this World. > Those who understand binary, and those who don`t. > > > > > > > > > > > > > > > > > > > > > > > TRIA IT-consulting GmbH > Joseph-Wild-Straße 20 > 81829 München > Germany > Tel: +49 (89) 92907-0 > Fax: +49 (89) 92907-100 > http://www.tria.de > > > Registergericht München HRB 113466 > USt.-IdNr. DE 180017238 Steuer-Nr. 802/40600 > Geschäftsführer: Rosa Igl > -------------------------------------------------------- > Nachricht von: Dirk.Schreiner(a)tria.de > Nachricht an: ds(a)caribenet.com, suse-security(a)suse.com > # Dateianhänge: 0 > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > 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 > > -- --------------------------------------------------------- Ing. Ariel Guerrero Mailto: ariel.guerrero(a)gmail.com Fone: +595 981 425040 Asunción - Paraguay -- 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

2 1

Re: [suse-security] 3 internet links thru firewall to windows PC
by B.Weber＠warwick.ac.uk 28 Sep '06

28 Sep '06

> i have 3 internet links. > > 2 coming through the same cisco router. > > and one other coming through a separate router. > > 1 link is purely reserved for surfing the web. > > while the other 2 links should be used to link to some > other organisation. The two links should be accessible > from one windows server inside the orgarnisation. > > my question is, > > how do i tell my SuSEFirewall to separate the traffic > for the 3 links, i want the windows server to sit > behind the firewall. probably in a DMZ. > but it's traffic should only pass through one of the > other 2 links. You can load additional custom rules into SuSEfirewall2 using the /etc/sysconfig/scripts/SuSEfirewall2-custom file, after enabling it in /etc/sysconfig/SuSEfirewall2. I'm not entirely sure if I understand your question correctly, but we had 3 internet connections in our house last year and did something like this (tried to simplify example so may have introduced errors. The methods for doing such things are described in full at lartc.org I suggest you read there. ------ INTERNALNIC=eth0 EXTERNALNICA=eth1 EXTERNALNICB=eth2 EXTERNALIP=0.0.0.0 #clean up for restart ip rule del fwmark 1 table interfacea.out ip rule del fwmark 2 table interfaceb.out #add rules to route packets marked with 1 with interfacea routing table #and packets marked with 2 with interfaceb routing table #you will need to have created these routing tables ip rule add fwmark 1 table interfacea.out ip rule add fwmark 2 table interfaceb.out #delete default route ip route del default #add default route through interfacea ip route add default via $externalipaddress dev $EXTERNALNICA table main #set default route for interfacea routing table through interfacea ip route del default table interfacea.out ip route add default via $EXTERNALIPA dev $EXTERNALNICA table interfacea.out #set default route for interfaceb routing table through interfaceb ip route del default table interfaceb.out ip route add default via $EXTERNALIPB dev $EXTERNALNICB table interfaceb.out #mark everything for connection 1 iptables -t mangle -A PREROUTING -i $INTERNALNIC -d 0/0 -j MARK --set-mark 1 #now mark stuff we want to go over connection2 #ssh iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp --dport 22 -j MARK --set-mark 2 #http(s) iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp --dport 80 -j MARK --set-mark 2 iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp --dport 443 -j MARK --set-mark 2 #irc iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp --dport 6667 -j MARK --set-mark 2 iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp --dport 6669 -j MARK --set-mark 2 #ssl iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp --dport 7070 -j MARK --set-mark 2 #freenode alternative port #put a specific machine on one connection iptables -A PREROUTING -i $INTERNALNIC -t mangle -p udp -s 192.168.0.30 -j MARK --set-mark 2 iptables -A PREROUTING -i $INTERNALNIC -t mangle -p tcp -s 192.168.0.30 -j MARK --set-mark 2

3 2

Re: [suse-security] 3 internet links thru firewall to windows PC
by polarizer 27 Sep '06

27 Sep '06

> how do i tell my SuSEFirewall to separate the traffic > for the 3 links This is usually not the job of Susefirewall, since it does not support source based routing. Check out "iproute2" to send outbound traffic over multiple links. An in depth howto is the "Linux Advanced Routing & Traffic Control" [1][2] polarizer's 2 cent [1] http://lartc.org/ [2] http://lartc.org/howto/lartc.iproute2.html

1 0

Re: [suse-security-announce] SUSE Security Announcement: Mozilla Firefox,Thunderbird, Seamonkey (SUSE-SA:2006:054)
by Stefan Tichy 26 Sep '06

26 Sep '06

Hi Marcus On Fri, Sep 22, 2006 at 03:02:16PM +0200, Marcus Meissner wrote: > x86 Platform: > SUSE LINUX 9.3: > ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/MozillaFirefox-1.5.0.7… > 746a56a6aa9402287d7c0f054989689c is there some debugging enabled in this browser version? Many messages written to stdout/stderr. There where none when using MozillaFirefox-1.5.0.6-1.4. -- Stefan Tichy ( s.list at pi4tel dot de )

11 19

3 internet links thru firewall to windows PC
by wpc 25 Sep '06

25 Sep '06

i have 3 internet links. 2 coming through the same cisco router. and one other coming through a separate router. 1 link is purely reserved for surfing the web. while the other 2 links should be used to link to some other organisation. The two links should be accessible from one windows server inside the orgarnisation. my question is, how do i tell my SuSEFirewall to separate the traffic for the 3 links, i want the windows server to sit behind the firewall. probably in a DMZ. but it's traffic should only pass through one of the other 2 links. Also the internet traffic from the workstations should only pass through the internet link. thanks "Who the heck is General Failure, and why is he reading my harddisk?" __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

rkhunter output
by Carl Hartung 22 Sep '06

22 Sep '06

Hi All, I've just installed rkhunter-1.2.7-16, updated it and scanned my 10.1 installation. It did a 'hidden file' check and alerted me to what appeared to be an old password lock file from May, which I deleted. It also said to "check /dev/.udev". Okay, I've "checked" and the directory is there... listed below. My question is this: What are these items and do they belong there? TIA & regards, Carl linux:/dev/.udev # l total 4 drwxr-xr-x 3 root root 80 2006-09-22 13:11 ./ drwxr-xr-x 12 root root 8160 2006-09-22 13:11 ../ drwxr-xr-x 2 root root 660 2006-09-22 09:40 db/ -rw-r--r-- 1 root root 5 2006-09-22 13:11 uevent_seqnum linux:/dev/.udev/db # l total 124 drwxr-xr-x 2 root root 660 2006-09-22 09:40 ./ drwxr-xr-x 3 root root 80 2006-09-22 13:11 ../ -rw-r--r-- 1 root root 212 2006-09-22 05:39 block@hda -rw-r--r-- 1 root root 385 2006-09-22 05:39 block@hda@hda1 -rw-r--r-- 1 root root 423 2006-09-22 05:39 block@hda@hda2 -rw-r--r-- 1 root root 423 2006-09-22 05:39 block@hda@hda3 -rw-r--r-- 1 root root 215 2006-09-22 05:39 block@hdb -rw-r--r-- 1 root root 333 2006-09-22 05:39 block@hdb@hdb1 -rw-r--r-- 1 root root 435 2006-09-22 05:39 block@hdb@hdb10 -rw-r--r-- 1 root root 435 2006-09-22 05:39 block@hdb@hdb11 -rw-r--r-- 1 root root 435 2006-09-22 05:39 block@hdb@hdb12 -rw-r--r-- 1 root root 428 2006-09-22 05:39 block@hdb@hdb2 -rw-r--r-- 1 root root 228 2006-09-22 05:39 block@hdb@hdb3 -rw-r--r-- 1 root root 376 2006-09-22 05:39 block@hdb@hdb5 -rw-r--r-- 1 root root 376 2006-09-22 05:39 block@hdb@hdb6 -rw-r--r-- 1 root root 432 2006-09-22 05:39 block@hdb@hdb7 -rw-r--r-- 1 root root 432 2006-09-22 05:39 block@hdb@hdb8 -rw-r--r-- 1 root root 432 2006-09-22 05:39 block@hdb@hdb9 -rw-r--r-- 1 root root 23 2006-09-22 05:39 class@input@input0@event0 -rw-r--r-- 1 root root 23 2006-09-22 05:39 class@input@input1@event1 -rw-r--r-- 1 root root 307 2006-09-22 05:39 class@input@input2@event2 -rw-r--r-- 1 root root 295 2006-09-22 05:39 class@input@input2@mouse0 -rw-r--r-- 1 root root 21 2006-09-22 05:39 class@input@mice -rw-r--r-- 1 root root 41 2006-09-22 05:39 class@misc@device-mapper -rw-r--r-- 1 root root 24 2006-09-22 05:39 class@sound@controlC0 -rw-r--r-- 1 root root 23 2006-09-22 05:39 class@sound@pcmC0D0c -rw-r--r-- 1 root root 23 2006-09-22 05:39 class@sound@pcmC0D0p -rw-r--r-- 1 root root 23 2006-09-22 05:39 class@sound@pcmC0D1p -rw-r--r-- 1 root root 18 2006-09-22 09:40 class@sound@seq -rw-r--r-- 1 root root 20 2006-09-22 05:39 class@sound@timer -rw-r--r-- 1 root root 26 2006-09-22 05:39 class@usb_device@usbdev1.1 -rw-r--r-- 1 root root 26 2006-09-22 05:39 class@usb_device@usbdev1.2 -rw-r--r-- 1 root root 28 2006-09-22 05:39 class@usb_device@usbdev2.1

1 1

Maintenance work at SUSE offices
by Marcus Meissner 22 Sep '06

22 Sep '06

Hi, Tomorrow, Saturday 23rd of September, our IS&T department will be doing elecritical reconfiguration work in our server rooms. This work will happen between 6am UTC and 11am UTC. This will affect: - The automated update mirror retrieval for SUSE Linux 9.2 up to 10.0. - @suse.com mailinglists (any mail will be queued and delivered later). - The old SUSE portal (portal.suse.de) Ciao, Marcus

1 0

SUSE Security Announcement: openssl,mozilla-nss RSA signature evasion (SUSE-SA:2006:055)
by Marcus Meissner 22 Sep '06

22 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: openssl,mozilla-nss Announcement ID: SUSE-SA:2006:055 Date: Fri, 22 Sep 2006 18:00:00 +0000 Affected Products: Novell Linux Desktop 9 Novell Linux POS 9 Open Enterprise Server SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SuSE Linux Openexchange Server 4 SUSE LINUX Retail Solution 8 SuSE Linux School Server SuSE Linux Standard Server 8 SUSE SLED 10 SUSE SLES 10 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: RSA signature evasion Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-4339, CVE-2006-4340, CVE-2006-4341 Content of This Advisory: 1) Security Vulnerability Resolved: RSA signature evasion Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion If an RSA key with exponent 3 is used it may be possible to forge a PKCS verify the certificate if they are not checking for excess data in the RSA exponentiation result of the signature. This problems affects various SSL implementations. This advisory covers the following implementations: - OpenSSL (CVE-2006-4339) - Mozilla NSS (CVE-2006-4340 and CVE-2006-4341) for SUSE Linux 10.0, 10.1 and SUSE Linux Enterprise 10. Implementations that are affected and still need to be updated: - gnutls in all distributions. - Mozilla NSS before SUSE Linux 10.0 and SUSE Linux Enterprise 10. The official openssl advisory is here: http://www.openssl.org/news/secadv_20060905.txt Some details of the actual technical problem can be found here: http://www.imc.org/ietf-openpgp/mail-archive/msg14307.html 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart running programs using SSL to verify PKCS signatures (web browsers, E-Mail clients, etc.) 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv <file.rpm> to apply the update, replacing <file.rpm> with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/mozilla-nss-3.11-21.7.i586… 2ca59cfa949741f970019250db6e7890 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/mozilla-nss-devel-3.11-21.… 5176d16fddcc9085c9c62633df1c1e7a ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/openssl-0.9.8a-18.7.i586.r… f3c5cb97da8acb6a4c4ef9434cb89e1a ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/openssl-devel-0.9.8a-18.7.… 20c03b69fb682e341fbcbd6e0b7fa08d SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/mozilla-nss-3.10-12.3… f1040a75792a24085ffeacaf4fdbbadb ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/mozilla-nss-devel-3.1… f666ce57dcedd14078d2289831658ec2 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/openssl-0.9.7g-2.8.i5… 2a2ec627749b0ebef913522777d6d10a ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/openssl-devel-0.9.7g-… 0889bf02be6b048e62109510b711debf SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/openssl-0.9.7e-3.4.i58… ef34f676b7c3279c368d044a35761e23 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/openssl-devel-0.9.7e-3… 2c0333c5ec9ba7b73c23c35bd8478668 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/openssl-0.9.7d-25.4.i5… e059156ac8c786f92915c66101c22cca ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/openssl-devel-0.9.7d-2… 163ce037ad79bbf3c53e4182a37c8b1a Power PC Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/mozilla-nss-3.11-21.7.ppc.r… 6b8a99c4f638adda50eda09925c11983 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/mozilla-nss-devel-3.11-21.7… 1e78438027cc3e92e7a65af293142280 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/openssl-0.9.8a-18.7.ppc.rpm a324d27cf6dfa4ceedcf83c1dcffb534 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/openssl-devel-0.9.8a-18.7.p… ab05376b3874aa893546a31630b503e8 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/mozilla-nss-3.10-12.3.… 420734304297e8e4f708d83843790ee4 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/mozilla-nss-devel-3.10… 530a0571a379a3b5965c7a16aac74c09 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/openssl-0.9.7g-2.8.ppc… 53a2702d6c99c2976730c4eca4f81fa2 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/openssl-devel-0.9.7g-2… ec29d438d00028c4c4937174fd378a49 x86-64 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/mozilla-nss-3.11-21.7.x8… 6fa083972df9ae919858f621b1aec930 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/mozilla-nss-32bit-3.11-2… 5ce7f14b2fd30384aa123dd6185f074e ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/mozilla-nss-devel-3.11-2… 2a4c684d4f59f64d4e25e18ea53f49c5 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-0.9.8a-18.7.x86_… 724ffd5c1123d162f19e3f9a929f2bc7 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-32bit-0.9.8a-18.… 7016abba594501c51de8f32e4051acec ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-devel-0.9.8a-18.… 96413d2dd6658ce9a08d777627e78b0a ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/openssl-devel-32bit-0.9.… d2af23fa3cabfb7a4458affcd4f24f89 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/mozilla-nss-3.10-12… f0e48cc8482ffa3d9f557caa8c495189 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/mozilla-nss-32bit-3… c5185e5f3ec998948e714231da384fae ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/mozilla-nss-devel-3… b872a76bded9ca5fea3a92ea6311a820 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-0.9.7g-2.8.… 4780f468291c749b082c18143319f7e0 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-32bit-0.9.7… a3203768a3736019ef975cfed314ddd3 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-devel-0.9.7… bc1f3b4a20b4d4a26e22c41700fa7c57 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/openssl-devel-32bit… 305646efe9293dc744744a9198c9d61b SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-0.9.7e-3.4.x… 0ee8251cc8d18e34683cffb9b836f6d2 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-32bit-9.3-7.… 01d8ecb0b20265fd547f2f6ce550ef30 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-devel-0.9.7e… e3e7086a44dfd719005b335c90b93dd0 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/openssl-devel-32bit-… 78b2ee77d6a84f3afded42aa048f77b1 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-0.9.7d-25.4.… 82bbf9b57187eae584eee9c748471266 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-32bit-9.2-20… 8a8ac0b203100e5ac137064760c5e285 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-devel-0.9.7d… 153d3ba8a9e7f1179d7495c643a46432 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/openssl-devel-32bit-… e0e8c2345d6a176e0b79fe1f5ec0b1eb Sources: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/mozilla-nss-3.11-21.7.src.r… 2d64292745510b79081aff63af3ae57c ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/openssl-0.9.8a-18.7.src.rpm a43b90f75865fbc3596084c35aac3585 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/mozilla-nss-3.10-12.3.… 205b16b750e3fdd4ba3c0b7a12627d6a ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/openssl-0.9.7g-2.8.src… 7949b6cbcd17092289949e85670e8330 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/openssl-0.9.7e-3.4.src.… a3fec9ffa1b2e15fedc51461d603e9c8 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/openssl-0.9.7d-25.4.src… f52a4666f358c6399137c6470c04355d Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: UnitedLinux 1.0 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SuSE Linux Openexchange Server 4 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… Open Enterprise Server http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… Novell Linux POS 9 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… Novell Linux Desktop 9 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SuSE Linux Enterprise Server 8 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SuSE Linux Standard Server 8 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SuSE Linux School Server http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SUSE LINUX Retail Solution 8 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SuSE Linux Desktop 1.0 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SUSE SLES 9 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… SUSE SLES 10 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… http://support.novell.com/techcenter/psdb/a9b0730b9578c91a3685d9913a531d37.… SUSE SLED 10 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.… http://support.novell.com/techcenter/psdb/a9b0730b9578c91a3685d9913a531d37.… ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify <file> replacing <file> with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made <DATE> using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team <security(a)suse.de>" where <DATE> is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. 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) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal 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, replacing <file.rpm> with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from build(a)suse.de with the key ID 9C800ACA. This key is automatically imported into the RPM database (on RPMv4-based distributions) and the gpg key ring of 'root' during installation. You can also find it on the first installation CD and at the end of this announcement. 2) If you need an alternative means of verification, use the md5sum command to verify the authenticity of the packages. Execute the command md5sum <filename.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 SUSE security announcement. Because the announcement containing the checksums is cryptographically signed (by security(a)suse.de) the checksums show proof of the authenticity of the package if the signature of the announcement is valid. Note that the md5 sums published in the SUSE Security Announcements are valid for the respective packages only. Newer versions of these packages cannot be verified. - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - General Linux and SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an e-mail 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 e-mail 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>. ===================================================================== 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, the clear text signature should show proof of the authenticity of the text. SUSE Linux Products GmbH provides 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.4.2 (GNU/Linux) mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBmQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCk YS3yEKeueNWc+z/0Kvff4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP +Y0PFPboMvKx0FXl/A0dM+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR 8xocQSVCFxcwvwCglVcOQliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U 8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0S cZqITuZC4CWxJa9GynBED3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEh ELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtB UVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOo AqajLfvkURHAeSsxXIoEmyW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1n KFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohi BBMRAgAiBQJA2AY+AhsDBQkObd+9BAsHAwIDFQIDAxYCAQIeAQIXgAAKCRCoTtro nIAKypCfAJ9RuZ6ZSV7QW4pTgTIxQ+ABPp0sIwCffG9bCNnrETPlgOn+dGEkAWeg KL+IRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lx yoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWn B/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDV wM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklLsnr35SJDZ6ram51/CWOnnaVh UzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF 5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3 D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGu zgpJt9IXSzyohEJB6XG5+D0BuQINBDnu9JIQCACEkdBN6Mxf5WvqDWkcMRy6wnrd 9DYJ8UUTmIT2iQf07tRUKJJ9v0JXfx2Z4d08IQSMNRaq4VgSe+PdYgIy0fbj23Vi a5/gO7fJEpD2hd2f+pMnOWvH2rOOIbeYfuhzAc6BQjAKtmgR0ERUTafTM9Wb6F13 CNZZNZfDqnFDP6L12w3z3F7FFXkz07Rs3AIto1ZfYZd4sCSpMr/0S5nLrHbIvGLp 271hhQBeRmmoGEKO2JRelGgUJ2CUzOdtwDIKT0LbCpvaP8PVnYF5IFoYJIWRHqlE t5ucTXstZy7vYjL6vTP4l5xs+LIOkNmPhqmfsgLzVo0UaLt80hOwc4NvDCOLAAMG B/9g+9V3ORzw4LvO1pwRYJqfDKUq/EJ0rNMMD4N8RLpZRhKHKJUm9nNHLbksnlZw rbSTM5LpC/U6sheLP+l0bLVoq0lmsCcUSyh+mY6PxWirLIWCn/IAZAGnXb6Zd6Tt IJlGG6pqUN8QxGJYQnonl0uTJKHJENbI9sWHQdcTtBMc34gorHFCo1Bcvpnc1LFL rWn7mfoGx6INQjf3HGQpMXAWuSBQhzkazY6vaWFpa8bBJ+gKbBuySWzNm3rFtT5H RKMWpO+M9bHp4d+puY0L1YwN1OMatcMMpcWnZpiWiR83oi32+xtWUY2U7Ae38mMa g8zFbpeqPQUsDv9V7CAJ1dbriEwEGBECAAwFAkDYBnoFCQ5t3+gACgkQqE7a6JyA CspnpgCfRbYwxT3iq+9l/PgNTUNTZOlof2oAn25y0eGi0371jap9kOV6uq71sUuO =ypVs - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBRRQAM3ey5gA9JdPZAQJJZQf9HiAwquQBJHoB/lOc6iVQj85iTlxXg5Rz srCTb7j0sYKNqn1bvoGHJYreYI3if2SU2ANH7Y3xgIaGt71R6254Yq5vEgEFralC ScK6LyWniJfn2CGFHewDndFAEjbyVTgcdo4kIeSrYLM/qsqRNBCqkSeLyDC9893l vjjebpKOfp2RSLZ695BFnI3qV/5GrRk14g8pRBlPewTrf82lxJuE9GEHI9laE9Yu WQciGGcS69yKuu+BG0tntIS5Gwrj+tOMpUKxebL19XlDPtA0Y2RGHT+KCwgkGXdT 64GckulBk13464q1OhZ8qjOmhWuhX2UwqfBmItXR7pHDuPvGD0z/+g== =Wjjp -----END PGP SIGNATURE-----

1 0

[Fwd: [suse-security-announce] Discontinued SUSE Linux Distribution: 9.2]
by Hubertus A. Haniel 22 Sep '06

22 Sep '06

Just as a bit of feedback for the guys at SuSE/Novell - It would have been nice to stretch this window a bit to wait till SuSE 10.2 ships. - I have always found the x.2 distributions the most stable ones and will not upgrade my 9.2 boxes till 10.2 ships. Best regards Hubba -------- Original Message -------- Subject: [suse-security-announce] Discontinued SUSE Linux Distribution: 9.2 Date: Thu, 7 Sep 2006 09:04:15 +0200 From: Marcus Meissner <meissner(a)suse.de> To: suse-security-announce(a)suse.com Dear suse-security-announce subscribers and SUSE Linux users, SUSE Security announces that SUSE Linux 9.2 will be discontinued soon. Having provided security-relevant fixes for more than two years, vulnerabilities found in SUSE Linux 9.2 after October 15th 2006 will not be fixed any more for this product. We expect to release the last updates around October 31st 2006. As a consequence, the SUSE Linux 9.2 distribution directory on our ftp server ftp.suse.com will be moved from /pub/suse/i386/9.2/ to the /pub/suse/discontinued/ directory tree structure to free space on our mirror sites. The 9.2 directory in the update tree /pub/suse/i386/update/9.2 will follow, as soon as all updates have been published. The discontinuation of SUSE Linux 9.2 enables us to focus on the SUSE Linux and openSUSE distributions of a newer release dates to ensure that our customers can continuously take advantage of the quality that they are used to with SUSE Linux products. This announcement holds true for SUSE Linux 9.2 only. As usual, SUSE will continue to provide update packages for the following products: SUSE Linux 9.3 SUSE Linux 10.0 and SUSE Linux 10.1 for a two-year period after the release of the respective distribution. Please note that the maintenance cycles of SUSE Linux Enterprise products and products based on the SUSE Linux Enterprise Server operating system are not affected by this announcement and have longer life cycles. To learn more about SUSE Linux business products, please visit http://www.novell.com/linux/suse/ . For a detailed list of the life cycles of our Enterprise Products please visit http://support.novell.com/lifecycle/ and http://support.novell.com/lifecycle/lcSearchResults.jsp?sl=suse If you have any questions regarding this announcement, please do not hesitate to contact SUSE Security at <security(a)suse.de>.

7 14

Possible to use LDAP from protected network to log in users to DMZ?
by Rikard Johnels 22 Sep '06

22 Sep '06

I am trying to set up a new and hopefully better network that we run today. I have a ADSL router/Firewall with DMZ and VPN capabilities. I also have a web/ftp server for both customers and company users that i want to put in the DMZ. And i would like the DMZ server to check its users against the LDAP server thats on the green protected LAN. All i want to do is have a centralized user handling system. Most of the users that use the WEB/FTP server are clients that doesnt have any LAN accounts But the ones coming in from the LAN, also has access to the DMZ for publishing their work. Nothing is to penetrate the firewall from neither red nor yellow network into the green one unless via VPN, and granted access via the LDAP server... Am i making any sense here? | [firewall]---------[DMZ] | |--------------[LDAP] | |--------------[USER] How would i go about this thing?? -- /Rikard ----------------------------------------------------------------------------- email : rikard.j(a)rikjoh.com web : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >

2 1

susefirewall2 & openvpn
by vbargsten 22 Sep '06

22 Sep '06

Hi suse-security, im running suse linux 9.3 and have newly installed openvpn. i added the tun0 device to my internal devices in the config of susefirewall2. everything works now correctly concerning opnevpn. i only have one problem left: the tun0 device is created when openvpn starts. so if the firwall has already been started, i have to restart it to make it work. so should i make openvpn start before susefirwall2 or should i call a restart of the firwall within the openvpn start script or are there other ideas? -- mfg vbargsten mailto:beer@freakmail.de

3 2

openssl vulnerability (CVE-2006-4339)
by Wolf, Josef 22 Sep '06

22 Sep '06

Hello! I wonder whether there are any plans to provide fixes for the openssl vulnerability described in http://www.heise.de/security/news/meldung/77783 and http://www.openssl.org/news/secadv_20060905.txt The fixes from upstream are available for more than two weeks now. In the meantime, there is even an exploit available: http://www.heise.de/security/news/meldung/78274

2 1

Re: [Discontinued SUSE Linux Distribution: 9.2]
by Keith Roberts 22 Sep '06

22 Sep '06

Maybe I'm missing something - but is it really two years ago since 9.2 was shipped? If the life cycle of each release lasts for two years, why can't SuSE release each upgrade on a 6 monthly cycle so we have a smooth transition between updates without any big gaps or overlaps? If ( (release_9_2 < release9_3) == six_months AND (release_9_3 < release10_0) == six_months AND (release_10_0 < release10_1) == six_months AND (release_10_1 < release10_2) == six_months AND ReleaseLifeTimeWithUpdates == two_years ) THEN CustomerSatisfaction = true ELSE CustomerSatisfaction = false Just my 2c. ------------------------------------------------------------ http://www.karsites.net http://www.raised-from-the-dead.org.uk This email address is challenge-response protected with http://www.tmda.net ------------------------------------------------------------ > Just as a bit of feedback for the guys at SuSE/Novell - It would have > been nice to stretch this window a bit to wait till SuSE 10.2 ships. - I > have always found the x.2 distributions the most stable ones and will > not upgrade my 9.2 boxes till 10.2 ships. > > Best regards > Hubba > Dear suse-security-announce subscribers and SUSE Linux users, > > > > SUSE Security announces that SUSE Linux 9.2 will be discontinued soon. > Having provided security-relevant fixes for more than two years, > vulnerabilities found in SUSE Linux 9.2 after October 15th 2006 will > not be fixed any more for this product. We expect to release the last > updates around October 31st 2006.

8 21

martians question...probably a silly one...but very confused
by Philip Warner 21 Sep '06

21 Sep '06

I've seen a lot about martian sources being from a 'wrong' subnet, and in that context can not see why I am getting lots of martian messages in my logs: Sep 21 22:29:49 ares kernel: martian source 203.8.195.10 from 203.8.195.20, on dev eth1 Sep 21 22:29:49 ares kernel: ll header: ff:ff:ff:ff:ff:ff:00:50:ba:39:10:22:08:06 where eth1 is configured as: eth1 Link encap:Ethernet HWaddr 00:50:BA:39:10:22 inet addr:203.8.195.20 Bcast:203.8.195.255 Mask:255.255.255.0 inet6 addr: fe80::250:baff:fe39:1022/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 collisions:0 txqueuelen:1000 and the routing has: 203.8.195.0/24 dev eth1 proto kernel scope link src 203.8.195.20 Admittedly, I'm no expert, but this looks like it should be OK: the martian 203.8.195.10 is on eth1's subnet, and the routing tables recognize where to send such packets...so any explanation or help would be appreciated. There are also 2 other ethernet devices, one to a 10.x.y/24 address range and the other to part of the same address range: eth2 Link encap:Ethernet HWaddr 00:01:80:5C:8B:35 inet addr:203.8.195.121 Bcast:203.8.195.121 Mask:255.255.255.255 (this interface should really be dropped, it's there for a legacy network that is now not used)...and when I drop eth2, I still get martians...so I assume it's not relevant.

1 0

Improvements to seccheck
by Michael James 21 Sep '06

21 Sep '06

Who is looking after seccheck these days? The header says: Daily security check v2.0 by Marc Heuse <marc(a)suse.de> But I sent an email to him and it bounced. Has he moved on? Here's what I am suggesting: The seccheck scripts provide some interesting reading for the systems administrator, pointers for tightening things etc. But I get pages of false positives from the writeable, executable, and suid parts of the script. You see some partitions on my disks contain regular rsync-ed backups of other machines, including machines not under my control. To protect my machine, backup partitions are mounted noexec,nosuid. When your scripts get the list of mounts they take no account of this. Would it be an improvement to split your $MNT list into 3? Say: $MNT_WRITE $MNT_EXEC $MNT_SUID This would allow the find to only be fired into the branches of the filesystem where the permissions matter. I'd be happy to work out and suggest some patches, but if you think it better left simple, I won't bother you... michaelj -- Michael James michael.james(a)csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166

2 1

Re: [suse-security] PGP key server
by HG 10 Sep '06

10 Sep '06

Hi! On 9/8/06, Kim Johansen - WebDeal AS <kim(a)webdeal.no> wrote: > Hi, > > I would probably upload all public keys to pgp.mit.edu, or set up a own > pgp server for internal use. For internal use I do not think I need a key server, more for the customers and 3rd parties that need to communicate using encryption. As somebody said, there doesn't seem to be any PGP servers easily available for SUSE. So it'll be quite a jub to get it up and running - if I'll even find one. So, I guess the route will be the public PGP servers. I'm thinking of setting up one "company master key" that I'll use to sign everybody's keys. I think I should upload that key to the key servers. Right? Anything to consider there? The users can then either upload their keys or not. -- HG.

4 6

PGP key server
by HG 08 Sep '06

08 Sep '06

Hello! A small company of 25-35 people needs to set up PGP for everybody. The server solution that is offered by PGP corp is too expensive route, so the individual route has been desided to take. But still some key management or at least distribution is needed. Question is: how should the public keys be distributed to the world? 1) Upload them all to the web-server? 2) Upload the "master" key to the web-server and then just have everybody email their keys to 3rd parties (who can verify the keys as they are signed with the master)? 3) Set up a own key server using SUSE obviously? 4) Just upload all the keys to some public key sever? Which? What would you recommend? -- HG.

4 3

SuSEfirewall2 and VPN
by Christian Wittmer 04 Sep '06

04 Sep '06

Hi list-users, trying to setup SuSEfirewall2 (SuSE 9.3) to work with IPSEC, but with no success. tunnel is up, but packets who should go through tunnel did not go through. Any help would be appreciated. Here some info about my config: I'm using DSL with fixed IP. VARS from SuSEfirewall2: FW_DEV_EXT="ppp0" FW_DEV_INT="eth0 eth1" # eth0 192.168.101.0/24 FW_MASQ_NETS="192.168.101.0/24 172.16.17.0/29 0/0,!192.168.2.0/24" FW_SERVICES_EXT_UDP="37 53 123 500 873 922 2401 4500" FW_SERVICES_EXT_IP="esp" FW_FORWARD="\ 172.16.17.0/29,192.168.101.0/24,ICMP \ 192.168.101.0/24,172.16.17.0/29,ICMP \ 172.16.17.0/29,192.168.101.220,tcp,19226 \ 192.168.101.220,172.16.17.0/29,tcp,19226 \ 192.168.101.0/24,192.168.2.0/24,,,ipsec \ 192.168.2.0/24,192.168.101.0/24,,,ipsec \ 192.168.101.0/24,192.168.68.0/24,,,ipsec \ 192.168.68.0/24,192.168.101.0/24,,,ipsec" FW_IPSEC_TRUST="no" ################## hades:/etc/sysconfig # iptables -L -n -t nat Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- 192.168.101.0/24 0.0.0.0/0 MASQUERADE all -- 172.16.17.0/29 0.0.0.0/0 MASQUERADE all -- 0.0.0.0/0 !192.168.2.0/24 Chain OUTPUT (policy ACCEPT) target prot opt source destination ################## hades:/etc/sysconfig # setkey -D xxx.xxx.xxx.188 xxx.xxx.xxx.138 esp mode=tunnel spi=3117414419(0xb9cff813) reqid=16385(0x00004001) E: 3des-cbc 334fec87 9c497e97 2ee43f9b d70dfe2a 65ae72e0 cb08c64b A: hmac-md5 177d6696 9e1143ec 102ec467 f2e8d9bf seq=0x00000000 replay=32 flags=0x00000000 state=mature created: Sep 4 18:29:37 2006 current: Sep 4 21:36:02 2006 diff: 11185(s) hard: 0(s) soft: 0(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=1 pid=28506 refcnt=0 xxx.xxx.xxx.138 xxx.xxx.xxx.188 esp mode=tunnel spi=2811047203(0xa78d2d23) reqid=16385(0x00004001) E: 3des-cbc 47767294 28a98de2 34a641be e1606fcc 16837566 ----------------------------------------- Diese E-Mail wurde durch SquirrelMail versandt "Webmail for nuts!" ----------------------------------------- Bereitgestellt fuer Kunden von Scorpio IT http://www.scorpio-it.net

1 0