March 2006 - openSUSE Security - openSUSE Mailing Lists

Bug with login.defs: DEFAULT_HOME no
by Ashley Gould 13 Mar '06

13 Mar '06

Hi list, SLES9 i386 sp3 pwdutils-2.6.4-2.25 I'm trying to prevent user login when no home directory, but setting 'DEFAULT_HOME no' in /etc/login.defs doesn't seem to have any affect: hvxen-0c:~ # grep DEFAULT_HOME /etc/login.defs hvxen-0c:~ # mv /home/slim/ /home/notslim agould@isis:~/ucop/notes/installion> ssh slim@hvxen-0c Password: Could not chdir to home directory /home/slim: No such file or directory slim@hvxen-0c:/> Is there a bug in pwdutils? or a missing pam config? -- -ashley Did you try poking at it with a stick?

3 4

"SSLRequire false" has no effect and allows access to directories 9.3 & 10.0
by Thomas K 13 Mar '06

13 Mar '06

============================================ "SSLRequire false" has no effect and allows access to directories. SSLRequire ALWAYS allows access regardless of expression in the back. ============================================ SuSE Linux 10.0 and 9.3 *binary* packages only! SuSE 10.0 broken module: f712b436b294d1f6088f458c266a691a /usr/lib/apache2-prefork/mod_ssl.so 1. Loading the module /usr/lib/apache2-prefork/mod_ssl.so into a fresh-built 2.0.54 breaks SSLRequire 2. Loading a fresh built httpd-2.0.54/modules/ssl/.libs/mod_ssl.so into SuSE's httpd2 of the same version fails: undefined symbol: X509_free 3. Compiled sources from SuSE 9.3 apache2-2.0.53-9.src.rpm do NOT show this symptom (even with tls-upgrade patch)!! 4. Compiled sources from apache.org (2.0.54, 2.0.55) do not show this symptom: they correctly reject access with a user certificate and log the reject. (My tests used a user certificate.) linux:~ # httpd2 -v Server version: Apache/2.0.54 Server built: Feb 1 2006 18:13:06 linux:~ # httpd2 -f /etc/apache2/test2.conf Syntax error on line 23 of /etc/apache2/test2.conf: Cannot load /root/gnu/httpd-2.0.54/modules/ssl/.libs/mod_ssl.so into server: /root/gnu/httpd-2.0.54/modules/ssl/.libs/mod_ssl.so: undefined symbol: X509_free httpd2 -V -D APACHE_MPM_DIR="server/mpm/prefork" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D HTTPD_ROOT="/srv/www" -D SUEXEC_BIN="/usr/sbin/suexec2" -D DEFAULT_PIDLOG="/var/run/httpd2.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_LOCKFILE="/var/run/accept.lock" -D DEFAULT_ERRORLOG="/var/log/apache2/error_log" -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types" -D SERVER_CONFIG_FILE="/etc/apache2/httpd.conf" ## APACHE TEST CONF: # jEdit:mode=apacheconf: # Template for a VirtualHost with SSL #This file loads the default modules from SuSE 10.0 (Apache 2.0.54) into Apache 2.0.55 #SSLRequire fails to work the error seems to be within /usr/lib/apache2-prefork/mod_ssl.so #req for http2 SuSE #LoadModule setenvif_module /usr/lib/apache2-prefork/mod_setenvif.so #LoadModule log_config_module /usr/lib/apache2-prefork/mod_log_config.so #LoadModule alias_module /usr/lib/apache2-prefork/mod_alias.so #LoadModule access_module /usr/lib/apache2-prefork/mod_access.so #LoadModule dir_module /usr/lib/apache2-prefork/mod_dir.so #BAAAAAAD guy: #LoadModule ssl_module /usr/lib/apache2-prefork/mod_ssl.so #Original module from src.rpm package SuSE 9.3 (correct reject of SSLRequire false) #Patched with /usr/src/packages/SOURCES/httpd-2.0.53-tls-upgrade.patch (correct reject) #LoadModule ssl_module /root/gnu/httpd-2.0.53/modules/ssl/.libs/mod_ssl.so #GOOD: #LoadModule ssl_module /root/gnu/httpd-2.0.55/modules/ssl/.libs/mod_ssl.so LoadModule ssl_module /root/gnu/httpd-2.0.54/modules/ssl/.libs/mod_ssl.so LoadModule dav_module /usr/lib/apache2-prefork/mod_dav.so LoadModule dav_fs_module /usr/lib/apache2-prefork/mod_dav_fs.so LoadModule php4_module /usr/lib/apache2-prefork/libphp4.so User wwwrun Listen 443 <VirtualHost _default_:443> DocumentRoot "/srv/www/htdocs" ServerName localhost:443 ServerAdmin "bla" ErrorLog /tmp/err # /var/log/apache2/error_log #TransferLog /tmp/acc #/var/log/apache2/access_log # A normal format + SSL extension CustomLog /tmp/acc "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %{SSL_PROTOCOL}x %{SSL_CIPHER}x %{CLIENTCERT}x \"%{ERRSTR}x\" %v" SSLEngine on LogLevel info SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite ALL:!NULL:!aNULL:!eNULL:!ADH:!EXPORT56:!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM SSLCertificateFile /etc/apache2/ssl.crt/server.crt SSLCertificateKeyFile /etc/apache2/ssl.key/server.key SSLCertificateChainFile /etc/apache2/ssl.crt/ca.crt SSLCACertificatePath /etc/apache2/ssl.crt #SSLCARevocationPath /etc/apache2/ssl.crl SSLVerifyClient require SSLVerifyDepth 1 SetEnvIf User-Agent ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 ########################################### ########## START DIRECTORY CONFIG ######### ########################################### SSLUserName SSL_CLIENT_S_DN_Email #SSLOptions +FakeBasicAuth <Directory "/srv/www/htdocs"> Options Indexes SSLOptions +StrictRequire SSLRequireSSL SSLRequire false </Directory> Alias /gallery "/srv/www/gallery" <Directory "/srv/www/gallery"> Options Indexes AllowOverride AuthConfig Limit Order allow,deny Allow from all DAV On SSLOptions +StrictRequire SSLRequire false # AuthType Basic # AuthName swarco # AuthUserFile /srv/www/.htpasswd # AuthGroupFile /srv/www/.htgroups # <LimitExcept GET> # Require valid-user # </LimitExcept> php_admin_value open_basedir /srv/www/gallery </Directory> </VirtualHost> _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

1 0

SUSE Security Announcement: gpg signature checking problems (SUSE-SA:2006:014)
by Marcus Meissner 12 Mar '06

12 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: gpg Announcement ID: SUSE-SA:2006:014 Date: Fri, 10 Mar 2006 18:00:00 +0000 Affected Products: SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: remote code execution Severity (1-10): 9 SUSE Default Package: yes Cross-References: CVE-2006-0049 Content of This Advisory: 1) Security Vulnerability Resolved: gpg signature verification problem 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 The GNU Privacy Guard (GPG) allows crafting a message which could check out correct using "--verify", but would extract a different, potentially malicious content when using "-o --batch". The reason for this is that a .gpg or .asc file can contain multiple plain text and signature streams and the handling of these streams was only possible when correctly following the gpg state. The gpg "--verify" option has been changed to be way more strict than before and fail on files with multiple signatures/blocks to mitigate the problem of doing the common --verify checks and -o extraction. This problem could be used by an attacker to remotely execute code by using handcrafted YaST Online Patch files put onto a compromised YOU mirror server and waiting for the user to run YOU. This problem is tracked by the Mitre CVE ID CVE-2006-0049. This is a different issue than the gpg signature checking problem for which we released updates a week ago, tracked by SUSE-SA:2006:013 / CVE-2006-0455. 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.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/gpg-1.4.2-5.4.i586.rpm 17f4db7313fb81477d491cd1de3b4a7c SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/gpg-1.4.0-4.4.i586.rpm 781a1f6ee507960c3b7f5ab7b09aae01 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/gpg-1.2.5-3.6.i586.rpm 0ac37c5097314b9d65fe3c00552991ba SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/gpg-1.2.4-68.13.i586.r… 2436ccc119ac1af98928536d2b968a3a Power PC Platform: SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/gpg-1.4.2-5.4.ppc.rpm 7da97d12baf4aa28e307affa9ccaa2ad x86-64 Platform: SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/gpg-1.4.2-5.4.x86_6… 490728e89c6564ac1e0b679012a89a42 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/gpg-1.4.0-4.4.x86_64… f258e8971ef2eb171907bbc426e15893 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/gpg-1.2.5-3.6.x86_64… 3e59895b7bed858997bdbc49aece5644 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/gpg-1.2.4-68.13.x8… 6369420f068f5d935bbc01f4798f2f20 Sources: SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/gpg-1.4.2-5.4.src.rpm a4ee567384c8744bafc59c19ed89669e SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/gpg-1.4.0-4.4.src.rpm 2d392b6698c4a9bb5f2b54aa51b53405 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/gpg-1.2.5-3.6.src.rpm 1cb53598e1a3c6d31aefc69c2ea18f37 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/gpg-1.2.4-68.13.src.rpm 91f82734783f307bf64a1728dbcddd79 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/gpg-1.2.4-68.13.src.r… 117ec3bfb057b88b637355db64c74723 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/a78b647fae6fd03… ______________________________________________________________________________ 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.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBRBG0h3ey5gA9JdPZAQIHLAf/eLWLO1jJ+6TGVJF08VsdT3AvwXEjE1yW O+5PzsDeNl/VrQIaJrtlwW5IykM/GsMRsclJO+ZkGY1YZ0J+PVluY+q2NibyYsRT XowCg3DnVExDIh1l7bf4Dtpq3gwsV1GQFwwZRYj8XEOa8Oesaj/wYNmn1Q6F1P5Z MLR05ZsZLPPPSZfTcYmV5+yZtkylCEcq9JacDapd8FMsJRBiFlGeyo+uzS4uQ52b ErD85wZmhfzo8i4IWcDRijzjmV4nIC85KLfNOAZfTUh0rcmn5YU3pIvR0wI90po0 kodEch1z+5K7MoKxH0ecejY3wegpdIBLuy2XgqB6msBdtkolHHICYg== =OfkL -----END PGP SIGNATURE-----

3 5

SUSE Security Announcement: gpg,liby2util signature checking problems (SUSE-SA:2006:013)
by Marcus Meissner 09 Mar '06

09 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: gpg,liby2util Announcement ID: SUSE-SA:2006:013 Date: Wed, 01 Mar 2006 11:00:00 +0000 Affected Products: SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SUSE LINUX Enterprise Server 9 UnitedLinux 1.0 Open Enterprise Server 1 Novell Linux Desktop 9 Vulnerability Type: remote code execution Severity (1-10): 9 SUSE Default Package: yes Cross-References: CVE-2006-0455, CVE-2006-0803 Content of This Advisory: 1) Security Vulnerability Resolved: gpg signature checking problems 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 This is a reissue of SUSE-SA:2006:009, after we found out that also gpg version < 1.4.x are affected by the signature checking problem of CVE-2006-0455. With certain handcraft-able signatures GPG was returning a 0 (valid signature) when used on command-line with option --verify. This could make automated checkers, like for instance the patch file verification checker of the YaST Online Update, pass malicious patch files as correct and allow remote code execution. This is tracked by the Mitre CVE ID CVE-2006-0455. Also, the YaST Online Update script signature verification had used a feature which was not meant to be used for signature verification, making it possible to supply any kind of script which would be considered correct. This would also allow code execution. This issue is tracked by the Mitre CVE ID CVE-2006-0803. Both attacks require an attacker either manipulating a YaST Online Update mirror or manipulating the network traffic between the mirror and your machine. 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.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/liby2util-2.12.9-0.4.… 91697f9207b20931d669f9f6d085b816 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/liby2util-devel-2.12.… c6815c8ff1cc695f91cf9c1ba6960554 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/liby2util-2.11.7-0.3.i… a321ab146d07c50cc69a91352ac28bf7 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/liby2util-devel-2.11.7… 1215bcf8f061079dbe05b93b1d611818 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/gpg-1.2.5-3.4.i586.rpm 3df19ea2069732c17da1b150d76fdba1 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/liby2util-2.10.7-0.3.i… ab21dd4a8f561abba2cd5b25e3076e41 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/liby2util-devel-2.10.7… e1b45fbf2b326e7a4d06d1fa23100415 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/gpg-1.2.4-68.10.i586.r… 5ea37344f72e28ff06f40976081e6499 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/liby2util-2.9.27-0.7.i… dcdaf21f345b2d4ffa55a78c74625633 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/liby2util-devel-2.9.27… 18624f647f80b9e39a8c910c90d60c87 Power PC Platform: SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/liby2util-2.12.9-0.4.p… 584b0cc0fadc160148b98976cbb9abb8 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/liby2util-devel-2.12.9… dcc926d75e15cda7c83e6ab110defd1f x86-64 Platform: SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/liby2util-2.12.9-0.… 712892d9238ad5ae230837f89528a4c1 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/liby2util-devel-2.1… ea0e06b186f3ffe7df066888b69e64fe SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/liby2util-2.11.7-0.3… 7cd1425a429b4637b34aa675d4eeaa85 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/liby2util-devel-2.11… 8d27157261b70a5bb51ab643d8dd1fe8 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/gpg-1.2.5-3.4.x86_64… 9e0fb9977027d7b95006ac6405a1befc ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/liby2util-2.10.7-0.3… b33ebf6703546c56ec10eea205e4fbd8 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/liby2util-devel-2.10… 6b385cd9d0902eeede67267933248404 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/gpg-1.2.4-68.10.x8… d05a99f75d4089a56b2f21c2b7aca67a ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/liby2util-2.9.27-0… d1c2276f502d6ad34940d1f2b907890d ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/liby2util-devel-2.… d74648e8c92952b1c9fdb4796f3d360e Sources: SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/liby2util-2.12.9-0.4.s… e1f57563afd30bb0252494a010d3c0c0 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/liby2util-2.11.7-0.3.sr… 2663aecb5e77147aca6881bd92e570bb SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/gpg-1.2.5-3.4.src.rpm 9415d5fefce7c12bd381d03255ec02f1 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/liby2util-2.10.7-0.3.sr… 9e6d935a4c540a5de5ff2681ee8281f1 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/gpg-1.2.4-68.10.src.rpm 4147426d68077823fa808905e10478bf ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/liby2util-2.9.27-0.7.sr… f4d1da1c13fd712999a87f7736eec2eb ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/gpg-1.2.4-68.10.src.r… c3ee5b82f7bb056082b3402d59b1eaed ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/liby2util-2.9.27-0.7.… 3dc3eea2b078aa1222875ad8abd09260 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/3b6c0c5ac07d0c8… http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/76efde003272170… ______________________________________________________________________________ 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.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBRAVnv3ey5gA9JdPZAQJS9QgAmqyv5V9kk8R7pPRp3J5lofrzIa1Hd0EM do6w9ycwunqiNltOLAi7tuD5K/4OhofmZH1WD6UAFhJ35YMePVkM1HWouR2ubxFM 1fOzPoMZDw8QDeQ8PZX43OV11e7hc16FZYWOnuzKDrS2pO4riaRgTRFrvhmuFX9Q IFJkx2nyAd5uvdMcJQP25jLdiB6Au7wluJ753E0rPTb9OMHPgE/q7Hvdl36B3zE3 yC/BYR8/nf5l7z6Zfbh5mE5yR6OHtsmrNcFoC4G/GpUy+Qe8+d3sdLi5Bn5i7FBE 8CMiwulX2X9fphywIP1kaWXVQJ+nQ2JdabZU7rGyQlb2Mn2TWpIEGQ== =FVL4 -----END PGP SIGNATURE-----

5 11

ip-down.local does not run anymore/ SuSE 10.0
by David Huecking 08 Mar '06

08 Mar '06

Hi! I discovered that from February 24. 2006 the call ip-down.local and the scripts in /etc/ppp/ip-down.d from /etc/ppp/ip-down (symbolic link to /etc/ip-up) did not run anymore on my SuSE 10.0 box running as a router for a DSL-connection to the internet. But till now I had no time to look after that. ...now I tracked it down to the following: In /etc/ppp/ip-down in the case-statement case "$BASENAME" in the choice ip-down) the call to the function start_firewall does not return! Tracked further down into this function I found that the call to the external program /sbin/SuSEfirewall2 start does not return anymore when ip-down is run with its basename "ip-down". But It does return if "/etc/ppp/ip-up" is called... I worked around that for me that way that I put the call to start_firewall after the calls to ip-down.local and ip-down.d/* So does someone use the .local-function in ip-down and has (or has not) similar problems? TIA. -- Eat, sleep and go running, David Hücking. ;-> Encrypted eMail welcome! GnuPG/ PGP-Key: 0x57809216. Fingerprint: 3DF2 CBE0 DFAA 4164 02C2 4E2A E005 8DF7 5780 9216

1 0

Creating non-root perl owner to run CPAN
by Michael James 07 Mar '06

07 Mar '06

There are a number of Linux language packages that are self-extending such as Perl, python, and R, For example, installing the BioConductor package is easiest from within R, just run R, source a URL to download the script, then run the function thus created. Lots happens, and hey presto, a new R library! Traditionally everything is owned and maintained by root, but being a sysadmin (paid professional paranoid) I created a user "rowner" and group "rusers" and "chown -R" the R base directory "/usr/lib/R" Now I su to rowner before doing the above, and the system is isolated from any malicious code somewhere in R's contributed package libraries. So much for a language I don't know (or like or trust). What about the language I do know, love and trust, Perl? Su to root, set dependencies to "follow", run CPAN, "install Bundle::Evil::RootKit" and go have a cup of coffee... There's an awful lot of libraries and contributors... Do I trust them all? Historically I've effectively said, "Of course! Anyone who hacks Perl has to be a good-guy!" Well history aside, maybe it's not such a good idea; what do people think of using the R strategy for all self extending languages? michaelj -- Michael James michael.james(a)csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 No matter how much you pay for software, you always get less than you hoped. Unless you pay nothing, then you get more.

1 0

Re: [suse-security-announce] SUSE Security Summary Report SUSE-SR:2006:005
by Frank Steiner 06 Mar '06

06 Mar '06

Hi, Marcus Meissner wrote > - metamail buffer overflow > > A buffer overflow was found in metamail. This bug could be exploited > remotely to execute arbitrary code by handcrafting specific > boundary tags. > > This issue is tracked by the Mitre CVE ID CVE-2006-0709 and affects > all SUSE Linux products containing metamail. an update for 9.1 is missing at ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/ (16:12:00 +000) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 1

Re: [suse-security] Intrusion spyware malware key stroke detection
by Martin 03 Mar '06

03 Mar '06

Follow up: > 1. Make up 2 obscure search terms that you *never* would use. 2. Enter one of them into google. 3. Go visit the resulting web sites. 4. See if you get spam. 5. Enter the other search term into google 6. Do *not* visit any of the resulting web sites. > 7. See if you get spam. I did this. Results are nothing relevant. . Martin

2 1

SuSE & Good Security
by Ahmed Shaban 02 Mar '06

02 Mar '06

Hello everyone I have small Q How can I Make Good Security on my SuSE 9.3 Machine ? I update it day by day I installed ClamAV and using KlamAV and scaning every time and the Firewall is enabled I wish to make security to defence myself from hackers thanks

2 1

RE: [suse-security] APT & RPM signatures
by Carlos E. R. 02 Mar '06

02 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2006-03-02 a las 08:38 -0000, Administrator escribió: > > You forgot to email to the list. > > Corrected. Somehow, this one did not make to the list, unknown reason. Anyway, I'll email to list with private copy to you, so that others can contribute. >>> Suffice to say that I have 2 sig keys missing, IDs 8750d2c4 and >>> 2e80fbc2. I can't find rpmkey rpms for them. I have found the keys >>> and downloaded them. They load into Kgpg on the SuSE box without >>> complaint. RPM ignores them after import - key IDs not listed in 'rpm >>> -qa gpg-pubkey*'. Errors continue. Can't do apt dist-upgrade without >>> turning off sig checking. Bad. >>> :-{ >> >> >> Suposedly, you have to import them with: >> >> rpm --import public-key-file.asc >> >> as root. I don't think Kgpg will inport them to the proper place > > I tried rpm --import. It didn't have any noticeable effect, nor did it > produce any errors. I don't know what to try next ... Then, the only thing you can try is (according to the man page): rpm -qa gpg-pubkey* that should list all signatures available - it seems that all of them are of that pattern and get listed that way, there doen't seem to be a specific command to list only signatures regardless of pattern. Funny. Then, rpm -qi gpg-pubkey-db42a60e would give details about that key. With: rpm --checksig package.rpm you check all digests signatures contained in package.rpm. Finally, you can try to remove the signature, in case it is badly imported: rpm -e gpg-pubkey-db42a60e More than that, I simply do not know. I assume you have updated your system recently with YOU, there has been a patch correcting a "nasty" bug (IMHO) related to signature checking of rpms. Broken database perhaps? Try --rebuilddb then... - -- Saludos Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEBsqatTMYHG2NR9URArF/AJ9nMG6ISku/BiHEzFynZsZ7WlJ45gCeLD6X +bW2+9sLIr+OWzCTO+2BltI= =5ZNA -----END PGP SIGNATURE-----

3 3