July 2006 - openSUSE Security - openSUSE Mailing Lists

SPAM: AppArmor and vsftpd
by Miguel ALBUQUERQUE 18 Aug '06

18 Aug '06

I was just wondering how AppArmor and vsftpd will react if one enables the vsftpd option chroot_local_user=YES on /etc/vsftpd.conf Correct me if I am wrong, but as much as i understood, AA is for protecting data integrety as chroot jails for creating user confinement. In that case the combination of both will be a very good compromise in security vs performance or it's just a bit overkill ? Miguel Albuquerque Network Administrator DISCLAIMER - This message is intended for the use of the named person only. The information contained in this E-mail is confidential and any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited. This message does not represent a formal commitment by Codalis SA. Codalis SA is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

6 10

Impenetrable firewall - SuSE 9.2
by Keith Hopper 16 Aug '06

16 Aug '06

Greetings, I have a small home network of machines connected through the internal ethernet port of my SuSE linux server (192.168.42.xxx). The external ethernet port is connected to a LinkSys dsl modem (192.168.1.2 on the server to 192.168.1.1 - the modem). I have a fixed IP and the domain name asgard.org.nz to go with it - in the /etc/hosts file against the sever machine name srv too. I set up the firewall so that the local net could access the internet - but not vice versa. All has worked very well for months. By the way the HOSTNAME file appears to contain srv.asgard.org.nz correctly! Needing to publish a small web site now, I have set up apache 2.0.55 suitably configured - which works well on the local network. However, despite the fact that the host (called server.asgard.org.nz on the modem port) has the same name as the Apache ServerName and I appear to have the correct firewall settings as far as my reading of the config file and the examples tells me - ------- # 1 FW_QUICKMODE="no" #2 FW_DEV_EXT="eth-id-00:90:27:a7:d3:d2" #3 FW_DEV_INT="eth-id-00:50:8b:62:08:e6" #4 FW_DEV_DMZ="" #5 FW_ROUTE="yes" #6 FW_MASQUERADE="yes" #6a FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="0/0" #7 FW_PROTECT_FROM_INTERNAL="no" #8 FW_AUTOPROTECT_SERVICES="yes" #9 FW_SERVICES_EXT_TCP="5801 5901 domain http https" FW_SERVICES_EXT_UDP="domain isakmp" FW_SERVICES_EXT_IP="" FW_SERVICES_EXT_RPC="" FW_SERVICES_DMZ_TCP="http https 80" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_DMZ_RPC="" FW_SERVICES_INT_TCP="ftp http https 80" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="esp" FW_SERVICES_INT_RPC="mountd nfs nfs_acl ftp nlockmgr status" FW_SERVICES_DROP_EXT="" FW_SERVICES_REJECT_EXT="0/0,tcp,113" #9a FW_SERVICES_QUICK_TCP="" FW_SERVICES_QUICK_UDP="" FW_SERVICES_QUICK_IP="" #10 FW_TRUSTED_NETS="" #11 FW_ALLOW_INCOMING_HIGHPORTS_TCP="" FW_ALLOW_INCOMING_HIGHPORTS_UDP="" #13 FW_FORWARD="" #14 FW_FORWARD_MASQ="" #15 FW_REDIRECT="" #16 FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="no" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_LOG_LIMIT="" FW_LOG="" #17 FW_KERNEL_SECURITY="yes" #17a FW_ANTISPOOF="no" #18 FW_STOP_KEEP_ROUTING_STATE="no" #19 FW_ALLOW_PING_FW="yes" #19a FW_ALLOW_PING_DMZ="no" #19b FW_ALLOW_PING_EXT="yes" ## # END of /etc/sysconfig/SuSEfirewall2 ## # EXPERT OPTIONS - all others please don't change these! #20 FW_ALLOW_FW_TRACEROUTE="yes" #21 FW_ALLOW_FW_SOURCEQUENCH="yes" #22 FW_ALLOW_FW_BROADCAST="int" FW_IGNORE_FW_BROADCAST="no" #23 FW_ALLOW_CLASS_ROUTING="no" #25 FW_CUSTOMRULES="" #26 FW_REJECT="no" #27 FW_HTB_TUNE_DEV="" #28 FW_IPv6="" #28a FW_IPv6_REJECT_OUTGOING="yes" #29 FW_IPSEC_TRUST="int" -------------------------------- I cannot seem to get any local browser to access the web server with the external (srv.asgard.org.nz) IP address. I have tried external port scanners and they seem to see no open ports at all. Having spent two days getting nowhere - but learning a lot, I feel I need to humbly ask for help. It's probably something obvious to you experts - sorry, I don't see what might be wrong. Help, please! Keith Hopper -- Sky Development

11 15

password memory
by Ashley Gould 02 Aug '06

02 Aug '06

The managers are discussing password requirements. One desire is to disallow previously used passwords with memory of up to ten passwords used. Is there a sweet and simple way to implement this in SLES9/10? I don't see a pam module with this facility. -- -ashley Did you try poking at it with a stick?

16 27

Auditing System
by Thomas Jones 31 Jul '06

31 Jul '06

Hello all, I am under the impression that LAuS will not be ported forward to newer kernels --- 2.6.10+. Is this correct? Also, I understand that RedHat's auditing system has made it into the vanilla kernel. How does this affect the CC-EAL4+ certification? Essentially, the certification will not be valid in any extent past kernel 2.6.5 correct? I was hoping to acquire CC-EAL4+ equivalent security functions and measures within the 2.6.17 kernel. Has there been any precedence or discussion about this aspect of previous kernels from the SLES parentage moving forward to newer releases? Thanks. Thomas

2 1

Upgrading SLES9 Susefirewall2 to SuSE9.3
by Michael James 31 Jul '06

31 Jul '06

Susefirewall2 fills my logs with reports of dropped packets as a stupid windows network monitor tries to talk SNMP. I've asked them to stop, but often "fixing the internet" is not the easiest way to resolve problems. The SLES9 version of Susefirewall2 lacks the parameter "FW_SERVICES_DROP_EXT="0/0,tcp,161" # Packets to silently reject without log message. So as I've done so often, I upgraded the SLES9 RPM. rpm -Fvh SuSEfirewall2-3.3-18.noarch.rpm Pulled a copy of /etc/sysconfig/Susefirewall2 across from my 9.3 workstation and customised it. Rebooted and it seems to work fine. I'll give it a week and upgrade all the production boxes. Just wanted to share that, (and see if anyone knew why not...) 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.

3 4

SUSE Security Announcement: apache,apache2 mod_rewrite problem (SUSE-SA:2006:043)
by Marcus Meissner 29 Jul '06

29 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: apache,apache2 Announcement ID: SUSE-SA:2006:043 Date: Fri, 28 Jul 2006 17:00:00 +0000 Affected Products: SLE SDK 10 SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE SLES 10 SUSE SLES 9 Vulnerability Type: remote denial of service Severity (1-10): 6 SUSE Default Package: yes Cross-References: CVE-2005-3352, CVE-2006-3747 Content of This Advisory: 1) Security Vulnerability Resolved: Apache off by one security 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 following security problem was fixed in the Apache and Apache 2 web servers: mod_rewrite: Fix an off-by-one security problem in the ldap scheme handling. For some RewriteRules this could lead to a pointer being written out of bounds. Depending on stack alignment this could be used to potentially execute code. The mod_rewrite module is not enabled per default in our packages. This problem is tracked by the Mitre CVE ID CVE-2006-3747. A more detailed description of this problem is available in: http://www.apache.org/dist/httpd/Announcement2.0.html For SUSE Linux 10.0, 10.1 and SUSE Linux Enterprise 10 additionally a old bug was fixed that we missed to forward port to the Apache 2.2 packages: mod_imap: Fixes a cross-site-scripting bug in the imagemap module. This issue is tracked by the Mitre CVE ID CVE-2005-3352. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart all running instances of Apache after the update. 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/apache2-2.2.0-21.7.i586.rpm 124342d5311b318586d91d12117bdd2a ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/apache2-prefork-2.2.0-21.7… 4a73ae89777943f4127743f817f0a0a5 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/apache2-worker-2.2.0-21.7.… 1905af7f606986f1818ebed5bd3382d5 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/apache2-2.0.54-10.5.i… adf6c8665b9f0f36c6a7720a8f1bfad1 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/apache2-prefork-2.0.5… 1cbcec6896dc46504140177b48ca014d ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/apache2-worker-2.0.54… f721e397c518cc6160886a1296e5a109 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/apache2-2.0.53-9.12.i5… e6ae2ee1353c1f1c31c0595b60d18137 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/apache2-prefork-2.0.53… cb02c5f97671d2ab0a64215ed9987c2f ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/apache2-worker-2.0.53-… b8872991cf54d99659e60d860d0c44e8 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/apache2-2.0.50-7.14.i5… 9365d403839e7c0740aae1e2f1b6cdfc ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/apache2-prefork-2.0.50… 97d506d68996f80ffaaaa6494a127f7c ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/apache2-worker-2.0.50-… f649e8eb98d43d6a44231f0c7453c9b2 Power PC Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/apache2-2.2.0-21.7.ppc.rpm 133b02c7a3a52a2bf144ece351ba00a1 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/apache2-prefork-2.2.0-21.7.… 099056b7a0f634ff1daf583ce2163839 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/apache2-worker-2.2.0-21.7.p… a22ae78408cedfea6d66362509d3c721 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/apache2-2.0.54-10.5.pp… 16a119e6dab8e972a992ef37bd9973aa ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/apache2-prefork-2.0.54… fcb8c3ca92f1b9a39791f51aad5b8907 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/apache2-worker-2.0.54-… 0f5dff953aea37964958bc0ed8932412 x86-64 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/apache2-2.2.0-21.7.x86_6… 3ab36db089d7f3d60a7114820970afdd ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/apache2-prefork-2.2.0-21… b7e9bc09fe9684292acf0e7ed0218b14 ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/apache2-worker-2.2.0-21.… b6b1ab1c03073f7f2acc07a0231ea532 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/apache2-2.0.54-10.5… 17c4bdc7577446bf45335ba58ebb3513 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/apache2-prefork-2.0… d55a93a86ae6b5bf037ee336d4307133 ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/apache2-worker-2.0.… e64fc86d3337913db0c22ffde3519a36 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/apache2-2.0.53-9.12.… d4996884e49ef11d27c97340efb6f079 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/apache2-prefork-2.0.… 5b599e78e59c7b59dc199777fe2c4eea ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/apache2-worker-2.0.5… 09f0f1dc18761a8a902f2dc5ab166883 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/apache2-2.0.50-7.14.… 595101ab05dfe5117ddab1d1f1463a28 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/apache2-prefork-2.0.… 112fe5dd14b66a4fbb82c3c5178bef69 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/apache2-worker-2.0.5… 7c07b8b400e6ed13a4707c3ebe1eed3a Sources: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/apache2-2.2.0-21.7.src.rpm 493d11cc099e975bc0974611cf936816 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/apache2-2.0.54-10.5.sr… b83da64c6ad0b76d7a3a8bf909d61d39 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/apache2-2.0.53-9.12.src… 5d4c85c7f60ea5c73df0fba7d92bec35 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/apache2-2.0.50-7.14.src… 2c4e95c0ebe9bee49dec733cbdeb42d3 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: SUSE SLES 10 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/90eac595ae9e6c7… SLE SDK 10 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/90eac595ae9e6c7… SUSE SLES 9 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/90eac595ae9e6c7… http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/5d0c08a7586a4b9… ______________________________________________________________________________ 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) iQEVAwUBRModD3ey5gA9JdPZAQId4Af/VhoqcRf1+yjri2+3kTMoB6mI638eGzWB Cp95ERRylsDcrhwvqOtESGC78FMN6bGSMgtTOzakhVVDr2Rn2eKjYmHJU4E6W3da UD9nOA3YDWVqHZDxH3XOhbvg7HtQ/44IMBC15Ob8P/vH6IarTLh1CA4ZOop+FClk 183vo2+i8BosBJGSsBGE6dCEQdqm1wGLo33/WYD+9Q3S3Hr8Yl5lZjfr0UEiVzKg t60XhsFdUpS+kXQZlS3axdYaCPi86joji8nWo6ncgeL+VcBtyELHHRdpY2hFO5yU hpAZRRJ/dOASX2MsaOV33v1yYtUEq0jaDxOTDOdUYf4Hz7I8MT01uQ== =beMF -----END PGP SIGNATURE-----

2 2

Updates of ClamAV
by Joachim Schoenberg 28 Jul '06

28 Jul '06

Hello list, the latest version of ClamAV is approx. four weeks out now. Does anybody know if it will give updates from Suse like it gave for the versions before? Joe -- ---------------------------------------------------------------- Joachim Schoenberg PHONE: +49 30 20377 374 Paul-Drude-Institut fuer FAX: +49 30 20377 201 Festkoerperelektronik Berlin ----------------------------------------------------------------

5 6

How to not allowing YoU to update the kernel?
by Beck, Odd Arne 28 Jul '06

28 Jul '06

Hello guys! I've been trying to find a manual for YaST (YoU) but haven't found the answers.. Hope you're not killing me for raising this question in this group, but it is somehow security related, at least for my part :-) As I have installed a program that requires the server to have a "stable" kernel version I would like YoU to NOT update the kernel unless I say so. If the kernel is updated I have to recompile the beforementioned program in order for it to work... (...in case of an emergency/uncontrolled reboot) I've taken a look at YoU and found the kernel in the list and kinda "locked" it (there's a symbol of a lock next to it and it says Protected - Do Not Modify). I wonder if this is the correct procedure for not having an uncontrolled kernel update. Best regards. Odd Arne Beck -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 2

Bug in nfsd from kernel 2.6.16.21-0.13
by Marco Munderloh 26 Jul '06

26 Jul '06

Hello, I discovered a bug in the nfs daemon delivered with the kernel update to kernel 2.6.16.21-0.13. When accessing a large amount of files over an nfs export from a machine with SuSE 10.1 and kernel 2.6.16.21-0.13, stale NFS handles occur. After a short period (3-5s) the files are accessible again. "grep -R hello" * triggers the bug for example. My configuration: SuSE 10.1 with kernel 2.6.16.21-0.13, NFS export of an XFS filesystem mounted on different clients with autofs (UDP and TCP). Degrading back the kernel to 2.6.16.13-4 and all works fine again. Regards, Marco

5 6

Re: [suse-security] SPAM: AppArmor and vsftpd
by Miguel ALBUQUERQUE 26 Jul '06

26 Jul '06

Thank you ! Miguel Albuquerque Network Administrator DISCLAIMER - This message is intended for the use of the named person only. The information contained in this E-mail is confidential and any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited. This message does not represent a formal commitment by Codalis SA. Codalis SA is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Richard Ibbotson <richard(a)sheflug.co.uk> 26.07.2006 15:09 To "Miguel ALBUQUERQUE" <miguel.albuquerque(a)codalis.ch> cc Subject Re: [suse-security] SPAM: AppArmor and vsftpd Miguel You might be interested in reading my non-technical write up of AppArmor and Crispin Cowan... http://www.sheflug.co.uk/docs.html "Linux User & Developer magazine issue 63" -- Richard www.sheflug.co.uk

1 0

Command line version of You
by Bob Vickers 26 Jul '06

26 Jul '06

Since upgrading to 10.1 I have found applying security updates has become an extremely hit-and-miss process which takes much longer than it did under SuSE 9.3. I would be very grateful if someone could answer two questions: (1) What is the simplest way of applying security updates from the command-line? Something equivalent to online_update security (2) How do you configure it to use a local mirror instead of the far-off Austrian mirror that the Setup process likes to configure? I have looked at the rug man page and frankly don't understand it (the only bit I do understand turns out to be a lie: it says the only command you need is 'rug update'). I'm not interested in catalogues and services etc, I just want to install security updates. Regards, Bob Vickers ============================================================== Bob Vickers Dept of Computer Science, Royal Holloway, University of London

5 6

Re: Command line version of You
by Markus Gaugusch 25 Jul '06

25 Jul '06

On Jul 25, Bob Vickers <bobv(a)cs.rhul.ac.uk> wrote: > Since upgrading to 10.1 I have found applying security updates has become > an extremely hit-and-miss process which takes much longer than it did > under SuSE 9.3. I would be very grateful if someone could answer two > questions: Hi, You might want to try the beta version of fou4s available from http://fou4s.gaugusch.at/ You need to use the "--nopatch" option to disable patch RPMs until you have installed the "rpm" update package which enables them. The final version will hopefully do this automatically ;) > (1) What is the simplest way of applying security updates from the > command-line? Something equivalent to > online_update security fou4s -uis (fou4s --update --install --security) -- you only need to use --update once a day or so, it fetches the update descriptions. All other operations are local (except for downloading of course). Use the -v option to see update descriptions. > (2) How do you configure it to use a local mirror instead of the far-off > Austrian mirror that the Setup process likes to configure? fou4s --server -w Markus -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(at)gaugusch.at X Against HTML Mail / \

1 0

SuseFirewall2: Problem accessing from internal to external + port forward.
by Acute - Sebastien Flory 25 Jul '06

25 Jul '06

Hello, I have a problem maybe one of you could help me fix.. I have a webserver running on a internal ip, the router/fw forward the port 80 of the external ip to this internal webserver. Everything works fine in theses scenario: - access from internet to external ip (port is fwd, webserver answer) - access from intranet to internal ip of the webserver But it doesn't work when the internal network wants to access the external ip. I have browse this list archive and found that adding a custom rules would help. iptables -A INPUT -i eth0 -s 10.25.0.0/24 -d xxx.aaa.yyy.jjj -j ACCEPT Actually, it helps, but instead of using the port forward, the router/ fw answer by itself. I believe this is because of the order of something but I'm no expert in theses things so I would be reallly really happy if someone could help me resolve my issue.. Thanks a lot, Sebastien

1 0

AW: [suse-security] Command line version of You
by dag Danczul Georg 25 Jul '06

25 Jul '06

Hi, it takes also much longer then 10.0 and I will use 10.0 as production dist. My system uses ftp.chg.ru/pub/Linux/SuSE/suse/update/10.1/ It seems you has chanched a bad way... regards, georg danczul -----Ursprüngliche Nachricht----- Von: Bob Vickers [mailto:bobv@cs.rhul.ac.uk] Gesendet: Dienstag, 25. Juli 2006 10:55 An: SuSE-Security Betreff: [suse-security] Command line version of You Since upgrading to 10.1 I have found applying security updates has become an extremely hit-and-miss process which takes much longer than it did under SuSE 9.3. I would be very grateful if someone could answer two questions: (1) What is the simplest way of applying security updates from the command-line? Something equivalent to online_update security (2) How do you configure it to use a local mirror instead of the far-off Austrian mirror that the Setup process likes to configure? I have looked at the rug man page and frankly don't understand it (the only bit I do understand turns out to be a lie: it says the only command you need is 'rug update'). I'm not interested in catalogues and services etc, I just want to install security updates. Regards, Bob Vickers ============================================================== Bob Vickers Dept of Computer Science, Royal Holloway, University of London -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

1 0

susefirewall2 problem (SuSE 10.1)
by Carlos E. R. 25 Jul '06

25 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I start the computer or run SuSEfirewall2 I get some weird errors: nimrodel:~ # SuSEfirewall2 SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: Firewall customary rules loaded from /etc/sysconfig/scripts/SuSEfirewall2-custom SuSEfirewall2: batch committing... iptables-batch v1.3.5: host/network `##' not found Try `iptables-batch -h' or 'iptables-batch --help' for more information. SuSEfirewall2: Error: iptables-batch failed, re-running using iptables iptables v1.3.5: host/network `##' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `##' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `Type:' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `Type:' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `string' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `string' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `##' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `##' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `Default:' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.3.5: host/network `Default:' not found Try `iptables -h' or 'iptables --help' for more information. SuSEfirewall2: Firewall rules successfully set nimrodel:~ # rcSuSEfirewall2 status Checking the status of SuSEfirewall2 running nimrodel:~ # I worry about the "not found" errors. How do I find out what is the exact problem? A bug of mine or of SuSE? It does not report the problematic file or line. The configuration is the same I had with 9.3, and it worked with no errors, AFAIK. I'm also getting some strange errors, maybe non related: Jul 23 13:13:16 nimrodel kernel: SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.12 DST=134.76.11.100 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=61663 DF PROTO=TCP SPT=24438 DPT=80 WINDOW=2184 RES=0x00 ACK FIN URGP=0 OPT (0101080A0002D56B70A5E356) Jul 23 13:13:18 nimrodel kernel: SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.12 DST=134.76.11.100 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=61664 DF PROTO=TCP SPT=24438 DPT=80 WINDOW=2184 RES=0x00 ACK FIN URGP=0 OPT (0101080A0002D6D370A5E356) Jul 23 13:13:21 nimrodel kernel: SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.12 DST=134.76.11.100 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=61665 DF PROTO=TCP SPT=24438 DPT=80 WINDOW=2184 RES=0x00 ACK FIN URGP=0 OPT (0101080A0002D9A370A5E356) Jul 23 13:13:38 nimrodel kernel: SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.12 DST=134.76.11.100 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=61667 DF PROTO=TCP SPT=24438 DPT=80 WINDOW=2184 RES=0x00 ACK FIN URGP=0 OPT (0101080A0002EA8370A5E356) The remote IP is ftp.gwdg.de. They occur when starting or closing YOU. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEw1rMtTMYHG2NR9URAn9aAJ9aFh4mvEVf4RQHr3kqkEAYAb7IPwCfVTJj /qdeTyTRV3vOgjmnC93TcoQ= =ENV8 -----END PGP SIGNATURE-----

4 8

Statefull packet inspection in SuSEfirewall2
by pronco＠conae.gov.ar 25 Jul '06

25 Jul '06

Hi, Is it there any way to configure stateful packet inspection rules in SuSEfirewall2 for masquerade networks? When I configure a rule in FW_MASQ_NETS in order to allow traffic from the outside to the DMZ, I also have to configure a rule for responses. Example: Incoming traffic to my web server in a DMZ with private addresses FW_FORWARD_MASQ="0/0,192.168.1.5,tcp,80 I also need to set up the following rules in order to let responses out FW_MASQ_NETS="192.168.1.5/32,0/0,tcp,1024:65535" This rule permits not only established sessions, but additionally it allows my web server to establish connections to the outside world. Dont know why the FW_FORWARD rules are stateful as I want, but FW_MASQ_NETS ones dont. Any suggestion? Is it possible to math the SYN, ACK and FIN TCP bits with SuSEfirewall2? Thanks in advance. Pablo Ronco

4 5

Please cancel my e-mails
by sharpjoe＠charter.net 25 Jul '06

25 Jul '06

15 18

SPAM: Please unsubscribe
by Ash Thakrar 24 Jul '06

24 Jul '06

Ash Thakrar ash(a)largedesign.com

4 3

[SLE] postfix and apparmour
by Carlos E. R. 24 Jul '06

24 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I post this here so that the maintainer of apparmour sees it and corrects what I think are bugs. When I installed 10.1 I had to add some rules to apparmour or postfix mail delivery with amavis would fail. These are my modifications I did then: /etc/apparmor.d/usr.lib.postfix.qmgr: /{var/spool/postfix/,}private/smtp-amavis w, /{var/spool/postfix/,}public/flush w, /etc/apparmor.d/usr.lib.postfix.smtpd: /{var/spool/postfix,}/pid/inet.localhost rw, /{var/spool/postfix,}/pid/inet.localhost:10025 rw, /etc/apparmor.d/usr.lib.postfix.master: /usr/lib/postfix/lmtp px, These modifications petain to these log entries: Jul 5 13:03:05 nimrodel postfix/smtpd[5615]: fatal: open lock file pid/inet.localhost:10025: cannot open file: Operation not permit Jul 5 13:03:06 nimrodel postfix/master[22973]: warning: process /usr/lib/postfix/smtpd pid 5615 exit status 1 Jul 5 13:10:35 nimrodel postfix/master[5908]: warning: /usr/lib/postfix/lmtp: bad command startup -- throttling Jul 5 13:11:35 nimrodel master[5985]: fatal: master_spawn: exec /usr/lib/postfix/lmtp: Operation not permitted I don't know if the correct procedure is to modify those files directly, but that's what I did and it works. Now, I have another problem. Today I had some hundred emails being downloaded, and the command mailq took a long time before failing to complete. I saw this log entry: Jul 21 20:00:46 nimrodel postfix/showq[18412]: fatal: open incoming 564677F01D: Operation not permitted Jul 21 20:00:47 nimrodel postfix/master[4587]: warning: process /usr/lib/postfix/showq pid 18412 exit status 1 Jul 21 20:00:47 nimrodel postfix/master[4587]: warning: /usr/lib/postfix/showq: bad command startup -- throttling Then I looked at /var/log/audit/audit.log, and sure, there was a problem: type=APPARMOR msg=audit(1153504846.751:1344): REJECTING r access to /var/spool/postfix/incoming/564677F01D (showq(18412) profile /usr/lib/postfix/showq active /usr/lib/postfix/showq) So I go to /etc/apparmor.d/usr.lib.postfix.showq, and see this: /{var/spool/postfix/,}incoming r, /{var/spool/postfix/,}incoming/[0-9A-F] r, /{var/spool/postfix/,}incoming/[0-9A-F]/[0-9A-F] r, /{var/spool/postfix/,}incoming/[0-9A-F]/[0-9A-F]/* r, /{var/spool/postfix/,}incoming/[0-9A-F]/[0-9A-F]* r, /{var/spool/postfix/,}incoming/[0-0A-F]* r, Now, the question: Should the last line be: /{var/spool/postfix/,}incoming/[0-9A-F]* r, instead? Notice that it is very dificult for me to test this: not till I get another mail with certain ID will it work or fail. Is this a bug? Should all those modifications be included by SuSE in a patch? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEwhhXtTMYHG2NR9URAoGvAJ9ioB5ah2O2hrEYzfXQyFj3jnpSeQCeMbQP 6UYW04xk07bjBY2vOtCs0Oc= =6nKD -----END PGP SIGNATURE-----

3 5

SLES10 Security Certification
by shashi 24 Jul '06

24 Jul '06

Hi As AppArmor will implement a type of MAC in SLES10, is Novell has submitted (or) going to achieve EAL4+ LSPP ? As SLES9 already certified for EAL4+ CAPP, i didn't heared SLES10 about this. Thanks & Regards, Shashi Kanth

3 4

Fwd: Kerberos Auth in Suse 9.2
by Ciro Iriarte 24 Jul '06

24 Jul '06

---------- Forwarded message ---------- From: Ciro Iriarte <cyruspy(a)gmail.com> Date: 20-jul-2006 0:07 Subject: Kerberos Auth in Suse 9.2 To: SLE <suse-linux-e(a)suse.com> I'm having a "missing file" error when i'm trying to auth an ssh client, getting a ticket with kinit works, but it seems pam_krb5 is broken, anybody have seen this? Jul 19 23:57:10 asusis-ope1 sshd[17944]: pam_unix2: dlopen("/lib/security/pam_use_krb5.so") failed: /lib/security/pam_use_krb5.so: cannot open shared object file: No such file or directory Jul 19 23:57:10 asusis-ope1 sshd[17944]: pam_krb5: unable to determine uid/gid for user Jul 19 23:57:10 asusis-ope1 sshd[17944]: pam_krb5: authentication fails for `iriartec' Jul 19 23:57:10 asusis-ope1 sshd[17944]: pam_krb5: pam_sm_authenticate returning 10 (User not known to the underlying authentication module) Ciro

1 0

YOU fails to update libzypp (rug)
by Carlos E. R. 23 Jul '06

23 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 YOU wanted to update libzypp, package rug-7.1.1.0-18.9 to rug-7.1.1.0-18.24. It run, then said that it needed to restart, then it reported a bunch of files to update, which were _instantly_ updated. I wasn't satisfied (so fast? no time to download anything!), so I closed Yast manually and tried a second time: it wanted to update rug again! I went this loop three times. The command rpm reported I had only the old version installed. Yast did not complain of any error, though, but it failed. Finally, I downloaded manually rug-7.1.1.0-18.24.i586.rpm and installed it with rpm --upgrade, which worked flawlessly; then I fired up Yast which this time is updating a bunch of things (nearly 800 Mb!), including a kernel update. 792Mb... how are modem users going to cope? No delta.rpm support in yast... :-( By the way, I find the current behaviour of yast, downloading a package, then installing it, downloading the next, installing it, worse than the previous behaviour of downloading everything in one operation. At least, being the install so slow now, it could continue downloading the next package while it installs the previous one at the same time. Linux is multitasking, right? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEw1VDtTMYHG2NR9URAiXhAJ9/LBPsVw5UGFbgjyPlHv/umiciLgCaAsHQ wKvIj7n0m34BYTRVAI8d3lk= =mH9+ -----END PGP SIGNATURE-----

4 7

Re: [suse-security-announce] SUSE Linux 9.1 is done
by Fred Morris 22 Jul '06

22 Jul '06

Marcus, The stats, as a quality metric, are interesting... intentional or not. By the way keep up the good^H^H^H^Hexcellent work! On Friday 21 July 2006 07:54, Marcus Meissner wrote: >[...] > Here is a small summary over the YOU patches we released > for SUSE Linux 9.1: >[...]

1 0

Apparmor and chroot
by Michael James 20 Jul '06

20 Jul '06

Should we get rid of the old chroot jails and trust to apparmor? They are both basically trying to avoid unforseen and unwanted access to the filesystem. eg: The default profile for postfix fails because it doesn't bestow "chroot" privileges to smtpd. Once bestowed, there are problems because the chrooted daemon wants to get to /default/some-file and doesn't know it's actually talking about /var/spool/postfix/default Neither does apparmor 8^( Is the best practise way to tell postfix NOT to chroot? There are ways of breaking out of chroot jails aren't there? Has apparmor been coded to secure the known techniques? It's more versatile, is it more secure? How much of a performance hit? Thanks for any discussion of this, michaelj PS: RTFM replies welcome; as long as they give links to the FM. -- 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.

2 1

workround for kernel bug CVE-2006-2451
by Bob Vickers 14 Jul '06

14 Jul '06

I have just seen the message from Marcus about the local root exploit in Linux kernel (CVE-2006-2451). He doesn't give a workround, but I imagine that putting * hard core 0 in /etc/security/limits.conf would be pretty effective (although it doesn't catch people already logged on). Is that correct? Bob

2 1

apache2 Strange Logs HASH(0xead1b0) etc.
by Dirk Enrique Seiffert 13 Jul '06

13 Jul '06

Hello, on one Apache2 webserver we get strange logs: The originating IP reverse lookup points to internetidentity.com - Googling about this company says they they provide anti-phishing filters to Microsoft. The file they are going for is an phishing-site, placed frequently in unpatched horde instalations. What do the HASH(***) entries in the error logs mean? 209.147.127.222 - - [12/Jul/2006:18:11:53 -0500] "GET /horde/.../www.alaskausa.org/ultrabranch.alaskausa.org/services-activatevisa-init-wait.htm HTTP/1.1" 404 1025 "-" "HASH(0xead1b0), HASH(0xed5c50), HASH(0xed11a0), HASH(0xee8e60), HASH(0xeb2e10), HASH(0xec1600), HASH(0xed3b90), HASH(0xed5ce0), HASH(0xeac910), HASH(0xed0f70), HASH(0xeadf00), HASH(0xee8ef0), HASH(0xea2b10), HASH(0xead190), HASH(0xee86a0), HASH(0xee8a50), HASH(0xed7280), HASH(0xed5cc0), HASH(0xedd640), HASH(0xeb53f0), HASH(0xed3960), HASH(0xede590), HASH(0xed5fa0), HASH(0xed14e0), HASH(0xeb2e20), HASH(0xead580), HASH(0xeb4cf0), HASH(0xea6760), HASH(0xec98d0), HASH(0xe84640), HASH(0xed65d0), HASH(0xe988b0), HASH(0xed6050), HASH(0xe896a0), HASH(0xed0c90), HASH(0xea4e10), HASH(0xec9790), HASH(0xec9850), HASH(0xec98a0), HASH(0xec9c00), HASH(0xec9ac0), HASH(0xec9970), HASH(0xec4a60), HASH(0xeca0c0), HASH(0xee8fb0), HASH(0xee8fe0), HASH(0xee9010), HASH(0xee9040), HASH(0xee9070), HASH(0xee90a0), HASH(0xee90d0), HASH(0xee9100), HASH(0xee9130), HASH(0xee9160), HASH(0xee9190), HASH(0xee91c0), HASH(0xee91f0), HASH(0xee9220), HASH(0xee9250), HASH(0xee9280), HASH(0xee92b0), HASH(0xee92e0), HASH(0xee9310), HASH(0xee9340), HASH(0xee9370), HASH(0xee93a0), HASH(0xee93d0), HASH(0xee9400), HASH(0xee9430), HASH(0xee9460), HASH(0xee9490)" Thanks a lot 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 2

SUSE Security Announcement: acroread remote code execution (SUSE-SA:2006:041)
by Marcus Meissner 04 Jul '06

04 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: acroread Announcement ID: SUSE-SA:2006:041 Date: Tue, 04 Jul 2006 14:00:00 +0000 Affected Products: SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE SLES 9 Vulnerability Type: unknown Severity (1-10): 8 SUSE Default Package: yes Cross-References: CVE-2006-3093 Content of This Advisory: 1) Security Vulnerability Resolved: Acroread security upgrade to 7.0.8 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 Various unspecified security problems have been fixed in Acrobat Reader version 7.0.8. Adobe does not provide detailed information about the nature of the security problems. Therefore, it is necessary to assume that remote code execution is possible. Adobe does not provide update packages for Acroread that are compatible with some of our releases from the past. Therefore, updates are missing (and might not be provided) for the products listed as follows. As a solution to Adobe acroread security problems on older products we suggest removal of the package from exposed systems and to use the longer maintained open source PDF viewers. - SUSE Linux Enterprise Server 9, Open Enterprise Server, Novell Linux POS 9 Acrobat Reader 7.0.8 has a new requirement on GTK+ 2.4 libraries (previously GTK+ 2.2). Since the above products contain only GTK+ 2.2, the Acrobat Reader 7.0.8 provided by Adobe is currently not functional. We have postponed the updates and wait for Adobe to clarify this problem. - SUSE Linux Enterprise Server 8, SUSE Linux Enterprise Desktop 1 These versions only support Acrobat Reader 5 and could not be upgraded for Acrobat Reader 7 due to glibc and GTK+ requirements. We discontinued security support for Acrobat Reader on those products some time ago already. This issue is tracked by the Mitre CVE ID CVE-2006-3093. 2) Solution or Work-Around Please install the update packages. You can also use the open source PDF viewer replacements, as for instance xpdf, kpdf, evince, gpdf or similar programs. 3) Special Instructions and Notes Please close and restart all running instances of acroread after the update. 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/acroread-7.0.8-0.4.i586.rpm 0a439b3541fec2329b55f3b9b3bc4858 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/acroread-7.0.8-1.1.i5… 76d13f4fd89e25549a363ae443cbab04 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/acroread-7.0.8-1.1.i58… 953a36fb273d1245a122ea9a0774fcc2 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/acroread-7.0.8-1.1.i58… 4691f003b517f23bad4b923f24f45133 Sources: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/acroread-7.0.8-0.4.nosrc.rpm cdf32850c4a770fe4458df7e78fd0dbe SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/acroread-7.0.8-1.1.nos… 76eb5e155e370109b0d55226e8b94895 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/acroread-7.0.8-1.1.src.… e55b674570116b348ba7091f2b8b906e SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/acroread-7.0.8-1.1.src.… 97fdaba08621d339fdfde9b94db62a70 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: SUSE SLES 9 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/4bcb737ce757116… ______________________________________________________________________________ 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) iQEVAwUBRKpxEHey5gA9JdPZAQJTzgf+IGvAswMRbi25ToZgdF9GmfsWckV/MR2Z GNbKHarDKWJtpNrrhL/YQ9F/EDcZxKyYErZ3J7H3WMRIrutri7e064k019Ln2J6q F1PQNE2Yv9OROF/5cSuZg1hA5ZEm37QslnSL6YQxV1hfj6zaacpqgXI+WLMg+1mz le49xi3X9VygDt0pGgi7gLGHwEAAMNgZwSKxS1oO/piz3BcsWZcPK5/MCGEnBclz /VNanZQhkZM/sbUQxikgQSVg2zfw8vDrjfANJ/hDRYRe4B4is93I9ZF7n7JoDyPD 97Ri1agGBDeiYy2TzEq8Ta0MNeKEIGMnPtJLxGoXhlS6Wmh+uuORig== =5yN7 -----END PGP SIGNATURE-----

1 0

SUSE Security Announcement: kdebase3-kdm information disclosure (SUSE-SA:2006:039)
by Marcus Meissner 03 Jul '06

03 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: kdebase3-kdm Announcement ID: SUSE-SA:2006:039 Date: Mon, 03 Jul 2006 16:00:00 +0000 Affected Products: Novell Linux Desktop 9 SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SUSE SLES 9 Vulnerability Type: local privilege escalation Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-2449 Content of This Advisory: 1) Security Vulnerability Resolved: KDM local information exposure 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 KDE Display Manager KDM stores the type of the previously used session in the user's home directory. By using a symlink a local attacker could trick kdm into also storing content of files that are normally not accessible by users, like for instance /etc/shadow. This problem is tracked by Mitre CVE ID CVE-2006-2449 and was found by Ludwig Nussel of the SUSE Security Team. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please restart all running instances of kdm after the update. 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/kdebase3-kdm-3.5.1-69.23.i… 6b51aa1795da71a71119cf6aa6820153 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/kdebase3-kdm-3.4.2-27… 5b36c9bc7cee1cdde72d7ad70860d596 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/kdebase3-kdm-3.4.0-28.… f5a7cc054bf5223057e36aeef4bb2e55 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kdebase3-kdm-3.3.0-29.… e3b919080e181d5854526410675e116e SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kdebase3-kdm-3.2.1-68.… 247b449b8b6142ff9ee413acbd4efc57 Power PC Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/kdebase3-kdm-3.5.1-69.23.pp… 6db4614fe15867245801e17c72e9c8bd SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/kdebase3-kdm-3.4.2-27.… 6366c0536eb41220bd1686513fe6e2c1 x86-64 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/kdebase3-kdm-3.5.1-69.23… 6c31f10bd18a53f585a1cc6ac45ccbe4 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/kdebase3-kdm-3.4.2-… f606da7a6561ec09fbbb70a467da1790 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/kdebase3-kdm-3.4.0-2… fece9cedbe4033094c62124d85fe37cd SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kdebase3-kdm-3.3.0-2… 421cfc9dcacc8d1a59009cc849182297 SUSE LINUX 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kdebase3-kdm-3.2.1… 3456c10099c7c075ef2653e750f0ad72 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: Novell Linux Desktop 9 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/c43d8bdde8ba418… SUSE SLES 9 http://support.novell.com/cgi-bin/search/searchtid.cgi?psdb/292ea0b25bd919e… ______________________________________________________________________________ 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) iQEVAwUBRKkhr3ey5gA9JdPZAQJwGAf+J5wt1zWBdHvVTXWeqfh0rfSznNNiLSPz D7S5JTXG+SG2vKUiF/Vi/CeD5W86CrT3MpHQyVNxrK9P12L5b08Fm5U5hhMwub7V SJNWC79agPuFMNh0wNqSOhqsfMB/vSwGSdLQ3TnQLHIdAyredmXu0wE52v2BfjPW HxuOVBRl5Cp4yFwMxWfmTfvqwNIyWdjF7HLzu0xtmYLZw4Mh09MvfnrzyhC3TxNO fTzxs38Eki2EYdrIIHknnA02GNVLCMDblms4+9q5gAe+tlrVHnS91FJ3zO/qkSZD 4Q6YhosCsnjFZLHTWtZI7dNBlQE9JbEblXs0JdvwFbi9o992lYOh5g== =wahD -----END PGP SIGNATURE-----

1 0

SUSE Security Announcement: Opera 9.0 security upgrade (SUSE-SA:2006:038)
by Marcus Meissner 03 Jul '06

03 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: opera Announcement ID: SUSE-SA:2006:038 Date: Mon, 03 Jul 2006 16:00:00 +0000 Affected Products: SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 Vulnerability Type: remote code execution Severity (1-10): 6 SUSE Default Package: no Cross-References: CVE-2006-3198, CVE-2006-3331 Content of This Advisory: 1) Security Vulnerability Resolved: Opera security upgrade to version 9.0 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 web browser Opera has been upgraded to version 9.0 to add lots of new features, and to fix the following security problem: - CVE-2006-3198: An integer overflow vulnerability exists in the Opera Web Browser due to the improper handling of JPEG files. If excessively large height and width values are specified in certain fields of a JPEG file, an integer overflow may cause Opera to allocate insufficient memory for the image. This will lead to a buffer overflow when the image is loaded into memory, which can be exploited to execute arbitrary code. - CVE-2006-3331: Opera did not reset the SSL security bar after displaying a download dialog from an SSL-enabled website, which allows remote attackers to spoof a trusted SSL certificate from an untrusted website and facilitates phishing attacks. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart all running instances of Opera after the update. 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/opera-9.0-1.3.i586.rpm dbe4f7ebdc8cf6c136f353be8e548954 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/opera-9.0-1.3.i586.rpm dc16c7c133a5d9a479552b8940735bbd SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/opera-9.0-1.3.i586.rpm 1eada48d9a4ccba242d9d8ec92872065 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/opera-9.0-1.4.i586.rpm 03715655bbc24e45645937fde9c9927a Power PC Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/opera-9.0-1.3.ppc.rpm ff66785910294364e7c0d043b48889dc x86-64 Platform: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/opera-9.0-1.3.x86_64.rpm a4e2435b110a28d29650998a2f08eb22 SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/opera-9.0-1.3.x86_6… 94af3ffd12a53616ecd3b7ec572279f5 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/opera-9.0-1.3.x86_64… 4f55ed7caeaa590436c8ad0344a24353 SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/opera-9.0-1.4.x86_64… e03753b7a7a0448a66073f2d83c8f2d4 Sources: SUSE LINUX 10.1: ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/opera-9.0-1.3.nosrc.rpm 7f74b7b8d4756a99070f0c9c566ef81d SUSE LINUX 10.0: ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/opera-9.0-1.3.nosrc.rpm e984adc5a788c1ad8d7fcced4a29e237 SUSE LINUX 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/opera-9.0-1.3.nosrc.rpm efcf570644020fbb33be81a647fe478f SUSE LINUX 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/opera-9.0-1.4.nosrc.rpm 0c1d68b31fcbd9d45a10805d2a3cc1fd Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: ______________________________________________________________________________ 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) iQEVAwUBRKkeKXey5gA9JdPZAQLRGwf/YCDkTd3lnkrJDH1ZsEiAjeekee96EPfz 5FQcTRPivrCikSSUzXHLBXBnaGi9Q/it0SqXnPs/hdePr3QxY7IOWKLrePS05bAY qGR0eCWRpnvG7v7Q8vVrNnzvop44UMJXqq48KBLj29ACsr6SMjML8UNLKUWchgPV s0ExrtounnErvRxrlaqg/M18or8vMb8JmEQvFUJgUSP6rDbNu6lIo4KE925ZF8C7 De2KzIHTmF/ulLv+1OhtyvsGmJtPQE/vcf0DFp0VbBzT2LWq3FKP46mNJ8gGJjiY 1UEamXhiUEeywTzfJ7cTiqfLYFFsYfpf/YMc+2CPTHCFzqPcXhxilw== =EXm9 -----END PGP SIGNATURE-----

1 0