October 2004 - openSUSE Security - openSUSE Mailing Lists

Strange FTP logins
by Dominik Składanowski 11 Oct '04

11 Oct '04

Hello list. In LogWatch raport I found some succsessful logins to "anonymous" FTP account from different IP addresses. It is very strange because vsftpd.conf should reject this logins: anonymous_enable=NO Server is SuSE 8.2 Pro and vsftpd-1.1.3-37 Regards. -- ++++++++++++++++++++++++++++++++++++++++++ Dominik Składanowski e-mail: dominik.skladanowski(a)ch.pw.edu.pl ++++++++++++++++++++++++++++++++++++++++++

1 1

MonkeyShell: using XML-RPC for access to a remote shell
by Abe Usher 11 Oct '04

11 Oct '04

Security pundits have been warning about the dangers implicit with Web services for years. A good starting point for understanding the security issues related to Web services can be found at: http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci8… Of course to really understand the security risks posed by Web services, you need to understand the basics of Web services. Enter an application I wrote called "Monkey Shell." MonkeyShell is a simple open source Python application that uses extensible markup language remote procedure calls (XML-RPC) to execute commands through a remote system shell. I kept the code terse (less than 100 lines total) so that it can be studied easily. It is similar to netcat except instead of "shell shoveling" data through a raw TCP connection, it wraps data in XML and transports it over HTTP. MonkeyShell is freely available at: http://www.sharp-ideas.net/ Cheers, Abe Usher, CISSP

1 0

syslog-ng bug
by Peter Nixon 08 Oct '04

08 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Guys syslog-ng (tested on SuSE 9.1 pro) seems to have a bug. With the following defined destination, files and directories are created with the correct permissions but only files are created with the correct ownership. Directories are always created owned by group "root" destination hosts { file("/var/log/HOSTS/$HOST/$YEAR/$MONTH/$DAY/$FACILITY$YEAR$MONTH$DAY" owner(root) group(logview) perm(0640) dir_perm(0750) create_dirs(yes)); }; The syslog-ng documentation is at: http://www.balabit.com/products/syslog_ng/reference/x354.html#AEN357 It does not appear to mention any special "dir_group" option so I can only assume that I have the correct options. Does anyone have any ideas? - -- Viel Spa� Peter Nixon - nix(a)susesecurity.com SuSE Security FAQ Maintainer http://www.susesecurity.com/faq/ "If you think cryptography will solve the problem, then you don't understand cryptography and you don't understand your problem." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBZkNuAcdsUt9pJjwRAo0vAJ9n4QetlY9D5zsqfYq+HXvj9srsKQCgteR6 0z6KNV28to18vWI/Hr8HooQ= =8i6U -----END PGP SIGNATURE-----

1 0

mysqlhotcopy broken after latest mysql upgrade
by Kai Schaetzl 08 Oct '04

08 Oct '04

The latest security upgrade for mysql to mysql-4.0.15-67 (Suse 9.0) breaks mysqlhotcopy. ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mysql-4.0.15-67.i586_ en.info says it fixes a vulnerability in mysqlhotcopy, but it seems to break other functionality at the same time. Since then I get the following error on all machines with a simple command like "mysqlhotcopy -u $user -p $password -q $dbname $backuppath" String found where operator expected at /usr/bin/mysqlhotcopy line 631, near "my ($fh, $tmp)=tempfile('" (Might be a runaway multi-line '' string starting on line 629) (Missing semicolon on previous line?) Bareword found where operator expected at /usr/bin/mysqlhotcopy line 631, near "my ($fh, $tmp)=tempfile('mysqlhotcopy" (Do you need to predeclare my?) syntax error at /usr/bin/mysqlhotcopy line 631, near "my ($fh, $tmp)=tempfile('" Bad name after XXXXXX' at /usr/bin/mysqlhotcopy line 631. replacing the new file with an older one (I used the current one from Suse 8.2) fixes the problem. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org

1 0

ipsec routing problem
by Ralf Ronneburger 07 Oct '04

07 Oct '04

Hi everyone, I have a box (SuSE 9.1) with 3 network-cards (eth0 for internal, eth1 for dmz, eth2 for internet), that is to be client to a ipsec-vpn. But when I try to connect to the vpn-server (217.0.1.1) I get the following errors: Oct 7 11:28:29 vpn_clnt pluto[21240]: "VPN_Server": route-client output: RTNETLINK answers: Network is unreachable Oct 7 11:28:29 vpn_clnt pluto[21240]: "VPN_Server": route-client output: /usr/lib/ipsec/_updown: `ip route add 192.168.0.0/24 via 217.0.1.1 dev eth2' failed Oct 7 11:28:29 vpn_clnt pluto[21240]: "VPN_Server": route-client command exited with status 2 Oct 7 11:28:29 vpn_clnt ipsec__plutorun: 003 "VPN_Server": route-client command exited with status 2 Oct 7 11:28:29 vpn_clnt ipsec__plutorun: 025 "VPN_Server": could not route Oct 7 11:28:29 vpn_clnt ipsec__plutorun: ...could not route conn "VPN_Server" Oct 7 11:28:29 vpn_clnt pluto[21240]: "VPN_Server" #1: initiating Main Mode Oct 7 11:28:29 vpn_clnt ipsec__plutorun: 104 "VPN_Server" #1: STATE_MAIN_I1: initiate Oct 7 11:28:29 vpn_clnt ipsec__plutorun: ...could not start conn "VPN_Server" Oct 7 11:28:29 vpn_clnt pluto[21240]: "VPN_Server" #1: Informational Exchange message must be encrypted The network is reachable for sure, as I connect to the box remote and as the isakmp-packeges get to the vpn-server and the other way around. ipsec.conf looks like this: config setup interfaces="ipsec0=eth2" # Debug-logging controls: "none" for (almost) none, "all" for lots. #klipsdebug=all #plutodebug=all # Certificate Revocation List handling #crlcheckinterval=600 #strictcrlpolicy=yes # Change rp_filter setting, default = 0 (switch off) #rp_filter=%unchanged # Switch on NAT-Traversal (if patch is installed) #nat_traversal=yes # default settings for connections conn %default # Default: %forever (try forever) #keyingtries=3 # Sig keys (default: %dnsondemand) leftrsasigkey=%cert rightrsasigkey=%cert # Lifetimes, defaults are 1h/8hrs #ikelifetime=20m #keylife=1h #rekeymargin=8m # OE policy groups are disabled by default conn block auto=ignore conn clear auto=ignore conn private auto=ignore conn private-or-clear auto=ignore conn clear-or-private auto=ignore conn packetdefault auto=ignore #conn OEself # auto=ignore # Add connections here. conn VPN_Server left=217.0.0.49 leftcert=clientCert.pem leftsubnet=10.0.0.0/24 right=217.0.1.1 rightcert=serverCert.pem rightsubnet=192.168.0.0/24 auto=start Might one reason for the problem be the overlapping interfaces for eth1 and eth2 (eth1 has 217.0.0.51/255.255.255.248, eth2 has 217.0.0.49/255.255.255.0 but actually is only connected via direct link to .50, static routes for machines in the dmz are set via eth1)? The network is reachable for sure, as I connect to the box remote and as the isakmp-packeges get to the vpn-server and the other way around. Thanks and greetings, Ralf

2 3

Problems with SuSE 9.1 - some issues aren't fixed for ages
by Philippe Vogel 07 Oct '04

07 Oct '04

Hello! There are several errors reguarding SuSE 9.1. I would better call them children <http://dict.leo.org/?p=14/p..&search=children>'s <http://dict.leo.org/?p=14/p..&search=s> disease <http://dict.leo.org/?p=14/p..&search=disease>. For users with much linux-practise it will not be a too big problem to solve them, for beginners it is an unsolveable issue and there are damn no support-pages on the SuSE homepage reguarding this issues. For this here are the issues I had and my olutions for this. @SuSE: Why are this well-known problems not fixed within a hotfix? 1) Issue: Coldplug uses by default kernelmodule hw_random which is unable to be loaded e.g. with intel-chipset motherboards. At bootup /etc/init.d/network starts magically SuSEfirewall, but SuSEfirewall should start right after networkinitialization as it can be found in init-scripts. With some networkcards this makes problems, sometimes cards refuse to work after a while or you get driver errors in /var/log/warn: Oct 6 06:25:01 tux-box kernel: NETDEV WATCHDOG: eth0: transmit timed out Oct 6 06:25:01 tux-box kernel: eth0: 21140 transmit timed out, status fc670045, SIA fffffff0 ffffffff 1c09fdc0 fffffec8, resetting... Unfortunately i don't like that. There is no security if there is no answering networkcard. O.K. I would call this bock hack-secure, because there is no network accessible. Hotfix: add hw_random to the file /etc/hotplug/blacklist PLZ fix this dear SuSE-Team!!! 2) Issue: Some services start and stop like they want. O.K. you say this is not security-related, but what happens if your desired service doesn't start because of this issue? Hotfix: Edit /etc/init.d/SERVICE and add the services to start before here: # Requires-Start: SERVICE(LIST)_TO_START_BEFORE yast/system/runleveleditor -> add and remove services and write config. Here you should know, what to do. The next reboot all will do fine. 3) Issue: Networkinitialization is confusing because of missing aliases to the apropriate network cards. If you are planning a firewall, router or gateway you maybe want to know which card is which and without beeing David Copperfield foreseeing which card will boot next time as eth0. SuSE 9.1 with kernel 2.6 uses eth-id instead of eth-aliases in /etc/modules.conf which is empty now (and the system will not care a lot what's inside an empty compatibility-file afaik maybe sooner or later in 9.2). If you use a managed switch with learning function or a license-server you need to have the right order assigned to the cards. If you use eth-id instead of ethx in SuSEfirewall all will work well, except a licenseserver, because as every user is evil the security-solution providers only allow bindings to eth0 for licenserver ehernet-id's. Hotfix: /etc/modprobe.conf.local alias eth0 MODULENAME alias eth1 MODULENAME1 Or using nameif and editing /etc/init.d/network (in the case of same cards) [...] case "$ACTION" in start) echo Setting up network interfaces: date +%s > $NETWORK_RUNFILE # Change begin if [ -e /etc/mactab ] ; then /bin/sleep 1 /sbin/nameif fi # Change end for IFACE in ${INTERFACE:- $LO [...] Edit /etc/mactab # # /etc/mactab # eth0 00:11:22:33:EA:A3 eth1 00:11:22:34:26:26 After the next reboot the cards have the right order as desired and setup in Yast. PLZ dear SuSE-Team fix this as well!!! 4) Issue: Some services can be started chroot, but all others are not offered to be started localhost only or bind to a specific Interface or IP. Hotfix: This binds Samba to 192.168.0.1 and the connected subnet: Edit /etc/samba/smb.conf and restart samba and all related services (nmb, winbind ...) [global] [...] interfaces = 192.168.0.1/255.255.255.0 socket address = 192.168.0.1 bind interfaces only = yes allow hosts = 192.168.0.0/255.255.255.0 [...] This binds mysql to locahost and makes it inaccessbile for external attacks except local exploits from errorous scripts: /etc/init.d/mysql before: $SAFE_MYSQLD \ --user=$mysql_daemon_user \ --pid-file=$pid_file \ --socket=$socket \ --datadir=$datadir &>/dev/null & after: $SAFE_MYSQLD \ --user=$mysql_daemon_user \ --pid-file=$pid_file \ --socket=$socket \ --bind-address=127.0.0.1 \ --datadir=$datadir &>/dev/null & 6) Issue: Winbind loggs the loggs full with errors because of using winbind after installing winbind with samba 3. Hotfix: Edit /etc/securety/pam_unix2.conf before: auth: call_modules=winbind nullok account: call_modules=winbind password: md5 nullok session: none after: auth: nullok account: password: md5 nullok session: none Use different authentification within smba or edit your /etc/pam.d/samba appropriate. As default Samba uses unix-auth, but you can change this and find a better solution. 7) Issue: SSH allows root to login but imo nobody wants to have this. Hotfix: Edit /etc/ssh/sshd_config and restart sshd: PermitRootLogin no 8) Issue: Limiting rights of users is not really setup secure within SuSE. Hotfix: - give www/ftp/samba-users only /bin/false - give admins /bin/bash - edit /etc/limits.conf to your needs to limit users acl's on systemlevel This should be set per default after choosing network services or serverservices packages within Yast (minimal system & no X). 9) Issue: Postfixconfiguration is a mess when using cyrus + imap + sasl-auth/smtp-auth or any other non-standard-setups. Hotfix: Drop the config and forget everything Yast and SuSEconfig is doing, instead read this: http://postfix.state-of-mind.de/patrick.koetter/smtpauth/index.html For many other issues reguarding postfix: http://www.stahl.bau.tu-bs.de/~hildeb/postfix/ 10) Errors within SuSE aren't fixed over many many distributions. There are much more children <http://dict.leo.org/?p=14/p..&search=children>'s <http://dict.leo.org/?p=14/p..&search=s> disease <http://dict.leo.org/?p=14/p..&search=disease>s in SuSE and everytime they aren't fixed, only a small remark on a support-page is written. Issue: Problem XY happens because of not enough testing SuSE's reaction: Look at the support-pages. O.K. I find a solution overytime, but isn't it more easy to implement the fixes as updates? I think you ow us this, because buying SuSE and every updated Distribution cost more, than an everage Windows distribution within their time of support. 11) Commonly used software works well, other more complex setups and their provided software works only after doing a handjob to the configs. O.K. it is easy to say this, but all bulletting boards are full of questions but less in qualified answers. This wouldn't be if there was more whise thinking within Yast and SuSEconfig. SuSEconfig always drops my handedited stuff so I disabled it by default. Linux is linux not depending on the distribution only depending on where the files are. Reguards Philippe

8 10

SUSE Security Announcement: samba (SUSE-SA:2004:035)
by Thomas Biege 07 Oct '04

07 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: samba Announcement-ID: SUSE-SA:2004:035 Date: Tuesday, Oct 5th 2004 16:53:01 MEST Affected products: 8.1, 8.2, 9.0 SUSE Linux Enterprise Server 8 SUSE Linux Desktop 1.0 Vulnerability Type: remote file disclosure Severity (1-10): 6 SUSE default package: Yes Cross References: CAN-2004-0815 Content of this advisory: 1) security vulnerability resolved: - Samba file access problem problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - opera - kernel - mozilla 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion The Samba server, which allows to share files and resources via the SMB/CIFS protocol, contains a bug in the sanitation code of path names which allows remote attackers to access files outside of the defined share. In order to access these files, they must be readable by the account used for the SMB session. CAN-2004-0815 has been assigned to this issue. 2) solution/workaround As a temporary workaround you can set the wide links = no option in smb.conf and restart the samba server. However an update is recommended nevertheless. 3) special instructions and notes After successfully updating the samba package, you need to issue the following command as root: rcsmb restart 4) package location and checksums Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-2.2.8a-226.i586.… eb71869029b35d2a97d55e26514524db patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-2.2.8a-226.i586.… 48bb3e455079fcfdf4ad2baa28f28557 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/samba-2.2.8a-226.src.rpm d162ea5a39b14ee16ae1c6d5df9211bb SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.8a-225.i586.… 79b0514a827bdd782e6d3f62bb92fb85 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.8a-225.i586.… a50dd448212245d51e9ac59ae50514e8 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/samba-2.2.8a-225.src.rpm 25d488678b607b3c67612ee065abd77a SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.8a-224.i586.… 93d0fb2502f30593548dbe2f41ec8948 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.8a-224.i586.… da5b107fb71c5daf5972b6e0aaca4f5c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/samba-2.2.8a-224.src.rpm e0b9f9af6c5348cb9840b5d98a1c59dc x86-64 Platform: SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-2.2.8a-226.x… 0f1c94aa23653b0cf9b318646d9153af patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-2.2.8a-226.x… 569974c359702c263b0968ce8fb9810f source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/samba-2.2.8a-226.src.… 75c1a01d03af42835809691840eaa331 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - opera New opera packages are available on our ftp servers, fixing CAN-2004-0691, CAN-2004-0597, CAN-2004-0598, CAN-2004-0599 and CAN-2004-0746. - kernel Update kernels for the kNFSd problem for SLES 8 and SL 8.1 have been released. - mozilla We are in the process of releasing updates for mozilla (and related browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718, CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759, CAN-2004-0760, CAN-2004-0761, CAN-2004-0762, CAN-2004-0763, CAN-2004-0764 and CAN-2004-0765. We will give you concrete details in a separate mozilla advisory when the updates are available. ______________________________________________________________________________ 6) standard appendix: authenticity verification, additional information - Package authenticity verification: SUSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SUSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de) the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an un-installed rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SUSE in rpm packages for SUSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SUSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SUSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)suse.de> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SUSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iQEVAwUBQWK1Q3ey5gA9JdPZAQG2XAf/brEQk2j1Eh3S7Q3r9jnNHM/0oJ6rfish wS/GcWazRcIV7I8JnUqspDU9zYamS2oB8Vu977yTFc+nhTryvpWsbJDnQIjtYE52 bEMMFW6gYTzUqG2U31mWKaqtpuFJJNuA3Lu0HgsxaQJ5F7qjVcsBOwX5PqCARMFp KIcGJi8BtLsQ36x2ZWOXKG6p8jXxx8kSVln7T6e1T0v4tVURA6BaEkE4Dh0ZoKh1 V+lYw0QipbBIByWnY/rT4T1tvZE9NUG3JSHe0olyvDekmm/WzoHLIqOe2cKfR77a nNb+cA81JW7JJk10NWKY4hzUX9oLCN8/mAvl40nvCHX+9YHldeM3Ag== =LbT6 -----END PGP SIGNATURE-----

2 1

Re: [suse-security] Problems with SuSE 9.1 - some issues aren't fixed for ages [Incident: 041007-000114]
by Philippe Vogel 06 Oct '04

06 Oct '04

This time in ToFu and html :) Could someone kick this user from the list: paradise(a)custhelp.com I get this "funny and I don't care a lot about it" from him: Paradise Support schrieb: > Your question has been received. You should expect a response from us > within 4 business days. > > To update this question by e-mail, please reply to this message. > Because your reply will be processed automatically, you MUST enter > your reply in the space below. Text entered into any other part of > this message will be discarded. > > [===> Please enter your reply below this line <===] > > [===> Please enter your reply above this line <===] > > To update your question from our support site, click here. > <https://paradise.custhelp.com/cgi-bin/paradise.cfg/php/enduser/acct_login.p…> > > > Alternatively, you may call us Customer Services 0800 467 272, option > 1 between 10am and 9pm Helpdesk 0508 888 800 > > > * Discussion Thread* > * Customer (Philippe Vogel)* 07/10/2004 06.26 AM > > My Mail [...] > Philippe P.S.: Signing up to this list doesn't mean you can treat everybody with ads for you most famous website! This is not the platform for this kind of ads.

1 0

SUSE Security Announcement: mozilla (SUSE-SA:2004:036)
by krahmer＠suse.de 06 Oct '04

06 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: mozilla Announcement-ID: SUSE-SA:2004:036 Date: Wednesday, Oct 6th 14:36:39 MEST 2004 Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Enterprise Server 8, 9 SUSE Linux Desktop 1.0 Vulnerability Type: various vulnerabilities Severity (1-10): 5 SUSE default package: yes Cross References: http://www.mozilla.org/security/ Content of this advisory: 1) security vulnerability resolved: - various vulnerabilities problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - openmotif 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion During the last months a number of security problems have been fixed in Mozilla and Mozilla based brwosers. These include: - CAN-2004-0718: content in unrelated windows could be modified - CAN-2004-0722: integer overflow in the SOAPParameter object constructor - CAN-2004-0757: heap-based buffer overflow in the SendUidl of POP3 code - CAN-2004-0758: denial-of-service with malicious SSL certificates - CAN-2004-0759: read files via JavaScript - CAN-2004-0760: MIME code handles %00 incorrectly - CAN-2004-0761: spoofing of security lock icon - CAN-2004-0762: manipulation of XPInstall Security dialog box - CAN-2004-0763: spoofing of SSL certificates by using redirects and JavaScript - CAN-2004-0764: hijacking the user interface via the "chrome" flag and XML User Interface Language (XUL) files - CAN-2004-0765: spoofing SSL certificates due to incorrecting comparsion of hostnames - CAN-2004-0902: Several heap based buffer overflows in Mozilla Browsers. - CAN-2004-0903: Stack-based buffer overflow in the writeGroup function in vcard handling. - CAN-2004-0904: Overflow in BMP bitmap decoding. - CAN-2004-0905: Crossdomain scripting and possible code execution by javascript drag and drop. - CAN-2004-0906: XPI Installer sets insecure permissions, allowing local users to overwrite files of the user. - CAN-2004-0908: Allow untrusted javascript code to read and write to the clipboard. - CAN-2004-0909: Allow remote attackers to trick the user into performing dangerous operations by modifying security relevant dialog boxes. 2) solution/workaround Since there is no workaround, we recommend an update in any case if you use the mozilla browser. 3) special instructions and notes After successfully updating the package(s) you need to close all instances of the web browser and restart it again. 4) package location and checksums Due to the large amount of updated packages and dependencies we do not provide MD5-sums this time. The updates are cryptographically signed and are available for download via the Yast Online Update. ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - openmotif The XPM security problems within openmotif have been fixed. New packages are available on our ftp servers. ______________________________________________________________________________ 6) standard appendix: authenticity verification, additional information - Package authenticity verification: SUSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SUSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de) the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an un-installed rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SUSE in rpm packages for SUSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SUSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SUSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)suse.de> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SUSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQWPsxHey5gA9JdPZAQGMcwf/TCYBxw1SszOxykVCoBjSOP9/afp2f8S/ Zkf7rh+dti+C/JcqVpzNhu8C9TRsECoTWCqsV6m7+VIak1REUW0Tc6EwR43yDqUc 1G9VPbYX7+T5Wv6mE2zU7VGKqBXSYQPHqFCX5/Q+gR099QNxpWT/1QxmTefPuy/p wKwqIaBz0OISxFs20bR3ZS9Lwr0Uu5V9SFwn9I0qiDb0fwzRxmGTzVFura8k87oH l5ww/EKb2bgFqsu5aHanAQWsWg6S9K8l+Y6Jah72EXzPcy1QT6UBkHdj9zk2f8+f 6ENyU1qpTG2A4ZKWOWCUWl2uQ4kYZtdBX+4EP3ryM5V5xszxACQdpQ== =S9Fr -----END PGP SIGNATURE-----

1 0

Commercial exploit ?
by Dan Am 05 Oct '04

05 Oct '04

Hi list, I received the mail below just after posting to suse-security. Well, how's THAT for a scam ? Some joint giving a commercial Auto-Reply to all list postings. Or am I missing something ? Anyone else seen this ? Regards Dan Am Tuesday 05 October 2004 13:26 schrieb Paradise Support: >Subject: [suse-security] Getting SELINUX going on 9.1 [Incident: >041005-000868] > Your question has been received. You should expect a response from us > within 4 business days. > > > To update this question by email, please reply to this message. > Because your reply will be processed automatically, you MUST enter > your reply in the space below. Text entered into any other part of > this message will be discarded. > > [===> Please enter your reply below this line <===] > > [===> Please enter your reply above this line <===] > > To update your question from our support site, click on the following > link or paste it into your Web browser. > > Alternatively, you may call us > Customer Services 0800 467 272, option 1 between 10am and 9pm > Helpdesk 0508 888 800 > https://paradise.custhelp.com/cgi-bin/paradise.cfg/php/enduser/acct_login.p >hp?p_userid=suse(a)dertext.de&p_next_page=myq_upd.php&p_iid=285190&p_created=1 >096975586 > > > Discussion Thread > --------------------------------------------------------------- > Customer (Dan Am) - 05/10/2004 11.26 PM > [Sorry for crossposting, but not much seems to be happening on the > suse-selinux list. Interested anyone ?] > > Hello List, > > being quite willing to dig into an unknown application I have managed to > get Selinux going with the Sourceforge Tutorial, ready to explore. Here are > my questions/observations so far: > 1. Even in permissive mode insertion of the pam_selinux session modules > make login impossible, "no chown of tty possible". Hmmmm.... > 2. Proceeding are quite tedious. Are there scripts/frontends available ? > Maybe in SLES 9 ? > 3. Is there any Policy available for 9.1 ? I am getting quite a lot of > "avc denied" in the log, which would make the system unusable in "enforce" > mode, not so ? > (2 & 3: While all this is fun, I am not one to reinvent the wheel, either) > 4. Any other howto's/Docu for SuSE, apart from nsa.gov ? > Well, I hope I don't get to much flamefor this and looking forward to your > answers. > > Regards > Dan > > -- > buddha 2.6.4-54.5-default 9:05am an 19:31, 1 Benutzer, -- buddha 2.6.4-54.5-default 9:05am an 19:31, 1 Benutzer,

2 1