December 2004 - openSUSE Security - openSUSE Mailing Lists

Wine and ISDN
by Nihad Mujkanovic 15 Jan '05

15 Jan '05

NOW I AM REALLY PISSED OFF! At first I wanted to title this "DOS attack performed by SuSE" or "Sabotage performed by SuSE", but I managed it to cool down a bit, so I hopefully don't hit the wrong guy(s), but someone's got to be blamed and flamed, since this is a neverending story. I don't know if it's the team working on WINE or SuSE team compiling the packages for the distro, I assume it's both of them at the end. What they allow themselves is a pure sabotage and because it repeats in several distributions (I can remember at least the last 4-5) I can't believe that is an act of ignorance or a minor failure: I have never in my life had anything to do with ISDN and I don't have any hardware for this shit and I am even less interested in getting it, but SuSE is FORCING me to install ISDN packages, nevertheless. I ALWAYS deselect this crap and set it to "tabu", but the first time the system s allowed to automatically install a packet I happen to need (e.g. bttv in my case), it IGNORES any settings from installation time and installs all things I do not need: capi4linux, a bunch of isdn packages, formerly even "gnokii". Have you ever noticed that even if you deselect capi4linux, there are still packages required by it? Story background: I use wine sometimes and want it in my computer. Now, some brainless idiot(s) have set the package requirements so that you can't dodge, you'll get shot down anyway. Do they have something against smoothly running systems? Mine was OK, then I let the system automatically install packages needed for my TV card, and what happens? My computer hangs while trying to unload ISDN modules on reboot, and can't reboot any more!!! The only thing that helped was he reset button. After reboot, I saw there was a new entry in runlevel editor - you guess - "ISDN" and it was ON!!! I'm lucky this happened in my test machine and not in one of the servers I have running SuSE, but I am still VERY pissed off. What now? I don't believe that SuSE people are a bunch of idiots, because they have done many good things and hopefully will keep on doing them further. I don't believe it HAS to be this way, because other distributions don't do this to me/us. I don't believe they haven't noticed this, because this repeats for years, so what remains? Nothing I can think of but pure ignorance. This is not the only one thing that made me jump over to gentoo, but this is the only one that made me write this letter already three times ago, but every time till now I cooled down and trashed the mails. Now I won't. I have payed 90 EUR for the shit and I WANT IT WORKING PROPERLY! Don't you, wouldn't you, too? regards Dr. Nihad Mujkanovic Vienna, Austria

6 8

Will SuSE support stack smashing protection one day?
by Malte Gell 08 Jan '05

08 Jan '05

Hi there, I'm just playing a bit with IBM's SSP ( http://www.research.ibm.com/trl/projects/security/ssp/ ) and GCC 3.4.1. Since OpenBSD, Gentoo and others already ship with it, i wonder what do the SuSE security people think about SSP? Will SuSE support it in the future and if not, why? Is SSP really such an improvement as some say it is? regards Malte

16 32

"manually" updating PHP on Suse 9.1 (to PHP 4.3.10)
by Thomas Hochstein 05 Jan '05

05 Jan '05

I've got one or two questions egarding those still missing critical PHP updates. Suse 9.1, Apache2, mod_php 1. AFAIS, in Suse 9.1, most modules can be found in /usr/lib/php/extensions. Would it be sufficient to download PHP 4.3.10 from php.net, compile and install it into a different directory (--prefix), to get rid of the bugs? AFAIS, (un)serialize() and (un)pack() are part of the PHP core. 2. To "get back" to SuSe RPMs, is it sufficient to install the Suse apache2-mod_php-4 RPM as soon as it is available? (And perhaps to manually remove the install directoty from step 1 above). The RPM should overwrite /usr/lib/apache2-prefork/libphp4.so and all other newly installed files, I presume? Thanks for all comments - even if those questions *are* a little dumb, I fear. :) -thh

4 3

Failed attempts, block address
by MB 02 Jan '05

02 Jan '05

Hi list, Been getting a ton of attempts on my ssh/ftp connections as of late, first they started with the usual script kids trying the admin/guest/etc on the ssh connection, now i get people trying all sorts of stupid usernames with blank passwords on the ftp connection. 1. Is there a way to block an IP, either perm. or for set period of time for SSH attempts 2. Is there a simular way for VSFTP I'm sure i could block the address's manually, but i'd like it if it was automated? say for 6 attempts? Matt SuSE 9.1 --------------------------------- Do you Yahoo!? Yahoo! Mail - You care about security. So do we.

7 7

security settings in suse vs openbsd
by Cristian Del Carlo 30 Dec '04

30 Dec '04

Hi, i install in server web and firewall suse linux professional or openbsd. I find in openbsd some security settings and security applications very useful that i don't find in suse 9.1: 1) Apache in chroot by default Is possible to have in suse the possibility to chroot apache with an option in /etc/sysconfig/apache2 like dhcp or named? Now to have apache2 in chroot i use modsecurity ( that i must compile in to the system). 2) Systrace A very useful application is systrace, with this application is possible to execute the services with the possibilty to control the system calls. Is possible to use it in suse linux? Best regards, Cristian Del Carlo

3 2

RE: [suse-security] Will SuSE support stack smashing protection one day?
by James M. Patton 30 Dec '04

30 Dec '04

> Er, a vulnerablility that hasn't been discovered isn't a danger to anyone > and doesn't need protecting against! I'm not sure what you mean to say > here. I would sure hope that this is NOT the views of the Novell/SuSE team... > Not that many I suspect. SSP is unlikely to make a vulnerability > unexploitable, just harder to exploit. If I were penetration testing a > machine I knew to be using SSP I'd just craft my exploit accordingly. > Sometimes SSP/Stackguard/Stackshield/et al make it impossible to exploit a > vulnerability, but that is far from guaranteed. More likely the attacker > just needs to try harder. > > You appear to be under the impression that these sorts of tools offer > genuine protection. They don't. They sometimes downgrade a code execution > exploit into a denial of service (because the "protected" program will > still crash when its buffer is overflowed), but in general they just force > the attacker to work harder. But when dealing with script kiddies, any delay or difficulties you can cause very well may make the difference. In general, anything that one can do to increase the security of an information system under their control is a good thing. And any tools the vendors can provide us only helps to increase the security posture of our systems. Downgrading a local / remote compromise (or code execution exploit) to a denial of service is a great step forward. It could mean the difference of joe hacker crashing your system or having your shadow file - which would you prefer? I personally would prefer that my system be crashed than having to deal with a security incident.

5 4

RE: [suse-security] Will SuSE support stack smashing protection one day?
by James M. Patton 29 Dec '04

29 Dec '04

> Mail interface giving you shit huh ;) Yeah... freaking windoze for mail.. ugh. > Do you say that at work? From the addy I see Military, and I > know you guys have some Windows boxes somewhere, unless they > were finally taken out. scares me when the Army uses Windows.... > Or any other team who protects. I couldn't agree with you more on that. I admin Beowulf clusters, so my exposure to windows is pretty much only for e-mail and the like. However, I am very vocal about the security (or lack thereof) of windows. Nice thing about being a contractor ;) > And lose my uptime???????? That bastard better hope he > grabs the shadow file, at least that way I have one IP > in the logs instead of 300 a second. Then I can retaliate. > What's he going to do, say he was rooting me and I attacked > him ? Well, in our environment, data loss or a root compromise would be much worse than the cluster's head node being offline for a few minutes. I'd rather reboot a downed system than have to explain to the government folks why someone in Korea or another unfriendly has their data. Downtime is much easier to explain in many environments than a system compromise. And often the data which is on a system is far more important than maintaining a 99.999999999999% uptime.

1 0

Cyrus IMAP Backup Hints?
by Markus Feilner 28 Dec '04

28 Dec '04

Hello List, I have some questions concerning the backup of a cyrus imap server: Do you have any hints how to backup a Cyrus IMAP Server in general? I found two basic solutions, none of which seem perfect: a) stop the server, backup /var/lib/... AND THE CONFIG FILES, restart the server. b) make a snapshot of the filesystem (e.g. following the cyrus wiki) Solution b) seems a little much for a simple backup, but i don't want to stop my IMAP Server during the backup. So my questions are: Are there better solutions? There must be, hm? How long does Cyrus have to be down during backup? Do you have any experience? -- Mit freundlichen Grüßen Markus Feilner --------------------------- Bitte beachten Sie unsere neuen Adressdaten! Vielen Dank. --------------------------- Feilner IT Linux & GIS Linux Solutions, Training, Seminare und Workshops - auch Inhouse Beraiterweg 4 93047 Regensburg fon +49 941 9465243 fax +49 941 9465244 mobil + +49 170 3027092 mail mfeilner(a)feilner-it.net web http://www.feilner-it.net

3 5

PHP Update
by Stefan.Junge＠ssi-schaefer.de 28 Dec '04

28 Dec '04

Hello, I would like to update the php package on a old SuSe 7.3 box. Because there are no further updates available I decided to download the newest version 4.3.10. I have never updated php in these constellation. Is there a reason why I should not do this or could this be a problem? Thanks for any hints Stefan

3 2

Samba-LDAP-PAM question
by Mike Partyka 27 Dec '04

27 Dec '04

Hello, I am trying to follow IDEALx's "Samba3-LDAP PDC Howto" and am having difficulty with the PAM configuration portion of this because i am trying to install on SuSE Linux Enterprise Server 9 and SuSE does not use the pam_stack.so module so there is no catchall system-auth file to edit as the guide describes. Since there is not a system-auth file, i wonder would it be sufficient to do the necessary edit's to the /etc/pam.d/samba file? I know in some cases the /etc/pam.d/other file is used, when a specific config file for a service is not found in the /etc/pam.d directory. Can someone with a better understanding of the pam configuration, tell me which config files (lacking the system-auth file) in the /etc/pam.d directory are needed to make the overall setup work? And are the changes to these files the same as would have occured in the system-auth file? Mike Partyka Stonepath Logistics Systems Administrator (651)405-4300 Desk (651)208-5734 Cell (651)405-4342 Fax

2 1

WORM_SANTY.A and patch php
by Cristian Del Carlo 27 Dec '04

27 Dec '04

Hi, i am waiting for the patch for php ( the update has been released the 14-Dec http://www.php.net/ChangeLog-4.php#4.3.10) because there is a lot of security issues. I know that there is a worm that can use this problem and defeces a web server http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_SANTY.A. Why so much time to release the patch for suse 9.X ? Best regards, Cristian Del Carlo delcarlo(a)osratoscana.it Tel. 0583 424700 Fax 0583 424750 http://www.osratoscana.it Il testo e gli eventuali documenti trasmessi contengono informazioni riservate al destinatario indicato. La seguente e-mail è confidenziale e la sua riservatezza è tutelata legalmente dal Decreto Legislativo 196 del 30/06/2003 (Codice di tutela della privacy). La lettura, copia o altro uso non autorizzato o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere, immediatamente, alla sua distruzione.

4 4

Re: [suse-security] WORM_SANTY.A and patch php
by Marcus Meissner 27 Dec '04

27 Dec '04

On Mon, Dec 27, 2004 at 11:50:52AM +0100, Mailings wrote: > Not that I'm accusing anybody of anything here, but can somebody please > explain who is telling the truth here? The phpBB site is stating that the > problem is PHP. As I've already upgraded to the 4.3.10 version of PHP (I > install Apache and PHP myself from the source), I'm assuming that I'm safe. The trendmicro link the original poster refered to explicitly states phpBB at fault. check: http://sourceforge.net/project/shownotes.php?group_id=7885&release_id=283691 There definitely is a PHP vulnerability, but the Santy.A worm does not use it, it uses the phpBB vulnerability in phpBB version prior to phpBB 2.0.11. Ciao, Marcus

1 0

Re: SUSE Security Announcement: various kernel problems (SUSE-SA:2004:044)
by Marcus Meissner 24 Dec '04

24 Dec '04

Hi folks, Like some of you noted the 9.2 kernels RPMs are not there anymore, even though they are listed in the advisory. This is due us receiving reports where the Yast Online Update updating this kernel made the machine fail to boot. The reason is that a script is no longer creating the vmlinuz and initrd symlinks as is required for successful booting. We are preparing updated fixed packages for this problem and will be releasing them hopefully within the next day(s). Sorry for the inconvience, Marcus Meissner, Team Lead SUSE Security

1 2

Detection of DoS Attacks on Webserver
by Markus Roth 23 Dec '04

23 Dec '04

Hi! I'm currently doing my diploma work. its about detecting HTTP-DoS Attacks on web servers. it tries to detect this attacks based on statistical anomalies of the requests. it looks at the request rate (with an exponential moving average), the period in which a client is active, the time distribution of the requests (chi square), the return status of the web server and the distribution of the URI's hit. till now, it looks pretty promising but one very important factor is unaccounted, the coast of a single request! what i like to do is calculating a coast for each request, so that request that charge the CPU more or demand lots of bandwidth, have a higher suspicious level. the hole analysis process is done on the logfile of a web server. to train the system old logfiles are feed. after that the system switches to live mode and watches the access logfile (like tail -f) for changes and tries to detect attacks in "real time" (with the possibility to block them via an apache module or the firewall (time based rule)). some companies in switzerland sponsored their logfiles to develop the system. the bad thing, non of this logfiles contains the time to handle the requests! now my question, is somebody willing to give me some log data in combined format but with the time to handle a request. apache2 would log this with the "%D" parameter in microseconds. logfiles with about 100'000 - x'000'000 requests would be optimal. you can anonimize your logdata with http://sourceforge.net/projects/anonlog/ if you like or have to. an other thing which would be very interesting is if somebody has logfiles where script kiddies tried to bring down a web server with lots of requests to cpu intensive dynamic pages or got attacked in an other way. if you think i'm running in the wrong direction with this project or have other things on your mind which i should consider, please let my know! regards markus roth

7 14

SUSE Security Announcement: samba (SUSE-SA:2004:045)
by krahmer＠suse.de 23 Dec '04

23 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: samba Announcement-ID: SUSE-SA:2004:045 Date: Wednesday, Dec 22st 2004 14:30 MEST Affected products: 8.1, 8.2, 9.0, 9.1, 9.2 SUSE Linux Desktop 1.0 SUSE Linux Enterprise Server 8, 9 Novell Linux Desktop 9 Vulnerability Type: remote privilege escalation Severity (1-10): 9 SUSE default package: no Cross References: CAN-2004-1154 Content of this advisory: 1) security vulnerability resolved: - several integer overflows problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - none 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion The Samba developers informed us about several potential integer overflow issues in the Samba 2 and Samba 3 code. This update adds constraints to the Samba server code which protects it from using values from untrusted sources as operands in arithmetic operations to determine heap memory space needed to copy data. Without these limitations a remote attacker may be able to overflow the heap memory of the process and to overwrite vital information structures which can be abused to execute arbitrary code. 2) solution/workaround There is no workaround known. Please install the new packages provided on our FTP servers. 3) special instructions and notes Please make sure that all running instances of smbd which were started before the update were terminated. Run the following command as root: /usr/sbin/rcsmb try-restart 4) package location and checksums 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 for installation from the maintenance web. x86 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/samba-3.0.9-2.1.5.i586… 31d6dce3c460010b98a105a234fdfc29 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/samba-client-3.0.9-2.1… 5970e5495401201fd17bf72d42806756 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/samba-vscan-0.3.5-11.7… 076bbc4a366e9294ea00e4ce6df5d92c ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libsmbclient-3.0.9-2.1… 94519e295e8c2bb70b6d11381be7ce4b ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libsmbclient-devel-3.0… 9385c5f9ff0b727db2bd0ac8d5d71d0b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/samba-3.0.9-2.1.5.i586… d73986ed6e5d65c293e5ecba075bf380 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/samba-client-3.0.9-2.1… 5817596556919012df4a9c5b64f096d3 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/samba-vscan-0.3.5-11.7… e712e8b43540e0471c118463637208ce ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libsmbclient-3.0.9-2.1… dfaea082943a41c2e70628c661cb3f41 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libsmbclient-devel-3.0… 03d7db3fbc15a7a9662bf2f491ebd10d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/samba-3.0.9-2.1.5.src.r… cb7ae8682eb81165ac85fb240476aad8 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-2.2.8a-230.i586.… ee2fb1cc077f3a042f4dbc283e595059 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-client-2.2.8a-23… f4a3e0b3301d331f69d2f68aaf023923 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-vscan-0.3.2a-283… cfa30b9837ddf28f9473e3a30c502977 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libsmbclient-2.2.8a-23… 80bf72a472af1f4e0740620d0a11efcd ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libsmbclient-devel-2.2… 6d3017a019779c6bab77d4420fd9d25a patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-2.2.8a-230.i586.… 95a6d02fe783c624c9c91863731fa725 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-client-2.2.8a-23… 4fc881c60bbd642fe45bc1bf45dcab66 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-vscan-0.3.2a-283… 51474087fae63e6990a405a47659dbca ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libsmbclient-2.2.8a-23… 49fb1785f3b2482c82188456288f00c9 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libsmbclient-devel-2.2… 0178214fa88081ff7a81cf45212474a3 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/samba-2.2.8a-230.src.rpm 4379b75dd8a56c30b7692f98d2e5ce1f SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.8a-230.i586.… 61357920f6867471d7620bbc89f7c5ac ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-client-2.2.8a-23… ae6be84a1cd10cc3e9a3b35ffc655202 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-vscan-0.3.2a-283… f0a8b417898c72a9f01bc8a585edca50 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libsmbclient-2.2.8a-23… 6f9a7fcb1a312e69a1180d830b7c20f9 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libsmbclient-devel-2.2… 1655622d433a92cc681933b8789cb626 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.8a-230.i586.… fc0f1995b339155671e1e815197d9207 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-client-2.2.8a-23… 548e87b48b1860ef0cca5d7b4f515ad2 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-vscan-0.3.2a-283… a0bed64f240cb05661ee2940d3674495 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libsmbclient-2.2.8a-23… f3d8ce4cfa47c2339ddd667542f86aaf ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libsmbclient-devel-2.2… d4f5f688b670c3622a4cfa946ff2b213 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/samba-2.2.8a-230.src.rpm 716200e217b2ace1d7408c05b19a6aa2 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.8a-230.i586.… e18ca12ea203e0088678d6d8ce250a78 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-client-2.2.8a-23… 24b7a5fadadc6db6347f4748cef1b0fd ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-vscan-0.3.2a-283… e5e1f125cd181b4a19422bb6f3b55c3f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.8a-230.i586.… 1945bf0bf7ff7d2c81568e5bc09a52fe ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-client-2.2.8a-23… 5383658a41c122daef14dfa2c5b55784 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-vscan-0.3.2a-283… 6fb046905637c3a6af3f12fec3f0b292 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/samba-2.2.8a-230.src.rpm c56bd7063220447f67e716aba72d0892 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/samba-3.0.9-2.1.5.… 953d948cad88670011ae7a3ed2118762 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/samba-client-3.0.9… 85199d04b3d15e6c1dd58ab544a1e510 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/samba-vscan-0.3.5-… 3509a79794efd0f0f63872bd3007b0fc ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libsmbclient-3.0.9… b22487852b695b8b60490be0a455c289 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libsmbclient-devel… 942fbf53d0b646aca7ab260090dcbf8e patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/samba-3.0.9-2.1.5.… 2864fcaad4c8d7068edd876af3ec2bae ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/samba-client-3.0.9… ec5764c99de3f9c56d8ac340d9d1643a ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/samba-vscan-0.3.5-… d324917057e9a2a2bde0931bc73c7bc7 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libsmbclient-3.0.9… 731cc0be9fd9b716dd7f35d21909ae4b ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libsmbclient-devel… d1e2effe2b1354b9024c7a89c6387442 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/samba-3.0.9-2.1.5.src… 40da40f8ff9f1db087eac4d7b620a35d SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-2.2.8a-230.x… 1c22bc894586a1c9c5e9d44deaa2ba4a ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-client-2.2.8… 0d0217165b53d305d7c798d9b5e32ff3 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-vscan-0.3.2a… ef3a6e86f61846f4205ebe022c9664e1 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libsmbclient-2.2.8… 855242455eb372013af4d011d2bcf594 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libsmbclient-devel… fd83b22302546721730c33b18771e527 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-2.2.8a-230.x… f73247663792f7da9bfbd8509bd17d98 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-client-2.2.8… 6540338d9ea046f15a8008a3dfb992c4 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-vscan-0.3.2a… 8fe413f93cba0007e1121110b42bf0ed ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libsmbclient-2.2.8… d074f8dfde22f1b4f4e853e8cd09a808 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libsmbclient-devel… ab366f5de0559174c665dfc4113dce35 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/samba-2.2.8a-230.src.… 371b70146d4b1bbb9795b29b2276e36a ______________________________________________________________________________ 5) pending vulnerabilities in SUSE Distributions and Workarounds: Please have a look at: http://www.suse.de/de/security/2004_04_sr.html ______________________________________________________________________________ 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 recommend against subscribing to security lists that cause the e-mail 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 file name of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled 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.7 (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+ 3J2KRWSOhpAMsnMxtPbBiEYEExECAAYFAkGJG+YACgkQGsiRhDTRlzm8CQCg14Wz vg6j45e/r1oyt9EaHhleSacAnA+2dArk1I3xt49Z5rdnhqheF//9mQGiBDnu9IER BACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff4JctBsgs47tj miI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0dM+HFrruCgBlW t6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcOQliHu8jwRQHx lRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifr ZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBED3+D2t1V/f8l 0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1 krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoEmyW/xC1sBbDk DUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25p bmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkDwmcABAsKAwQD FQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6dNfnwI2PAsgCg jH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzO AKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUD BRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4 fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklL snr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMn snT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/ xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmp U661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0EExECAB0FAjxq qTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1fAJ9dR7saz2KP NwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0EOe70khAIAISR 0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/HZnh3TwhBIw1 FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44ht5h+6HMBzoFC MAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPTtGzcAi2jVl9h l3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM523AMgpPQtsK m9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q2Y+GqZ+yAvNW jRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8QnSs0wwPg3xE ullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWawJxRLKH6Zjo/F aKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ1sj2xYdB1xO0 ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCHORrNjq9pYWlr xsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1wwylxadmmJaJ HzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQYEQIADAUCOe70 kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol0JdGwACeKTtt geVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAKCRCoTtronIAK yofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3coSPihn1+OBNw= =Fv2n - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iQEVAwUBQcmDM3ey5gA9JdPZAQHqoAf+L57lmJfGIFHA70nR51rqt0w/c+3U/ARx jV/W2jPABqzgJ5kUi+YX51qI3haNLRWHYpmZr4VgMazHcsiVhCRpBgCRhxKnwdCz 40i+yCQOrok8aW6f8T8S+ATm/dri4FHrsWT/pjDL1Jj+fPOBtkQg3J4Hl1Lnz0UK a5MEMQpnzbZd8H9CN9mqbW0R5OZe12khvIcxuBdiuRwhcRqbusW5Q1Dxa+978wrb /BrAh/yz8/pFLJjG2kYgvqK/tDLHBFH+D0/1EQOQRO/sdgYHZ8hefI4lEkPDgzWR jyUXvpHK/q7CghTcRzejFzmxOU2NPSFwwRCoKwBT4UVowvAMiFu6Lw== =oLMK -----END PGP SIGNATURE-----

2 1

PAM cracklib and credits
by Jason Monroe "JC" 22 Dec '04

22 Dec '04

Hello All, I have SUSE enterprise 9 and I seem to have run up against a brick wall. All of the services /etc/pam.d/* call pwcheck and the global configuration for pwcheck is /etc/security/pam_pwcheck.conf. Pwcheck calls cracklib, however, the way that pwcheck calls cracklib there doesn't seem to be a way to send arguments to cracklib. I want to make use of: dcredit=N ucredit=N lcredit=N ocredit=N arguments to cracklib as to meet a password complexity requirement that we have. Do any of you know of a way to give these options to pwcheck either by magic or a different version of (pam / pwcheck) or the like. Since I'm really only interested in passwd, sshd, and su throwing a cracklib reference into those /etc/pam.d/ files would also be sufficient, but my experience there hasn't born any fruit. Any suggestions? Thanks, JC

1 0

Web Content Filter
by Stefan.Junge＠ssi-schaefer.de 22 Dec '04

22 Dec '04

Hi, I´m searching for a good web content filter. At the moment there is as squid proxy, but we need a little bit more. Any suggestions for a good product? (It could be a commercial product) Thanks Stefan GnuPG Fingerprint 970E C83D 1B68 E668 12C5 FFF8 643A 3610 A5F6 6B18

3 2

SUSE Security Announcement: kernel local privilege escalation (SUSE-SA:2004:046)
by Marcus Meissner 22 Dec '04

22 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2004:046 Date: Wednesday, Dec 22nd 2004 16:00 MEST Affected products: 9.0 / AMD64 SUSE Linux Enterprise Server 8 / AMD64 Vulnerability Type: local privilege escalation Severity (1-10): 8 SUSE default package: yes Cross References: CAN-2004-1144 Content of this advisory: 1) security vulnerability resolved: - local root exploit in 2.4 AMD64 kernel problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - see SUSE Security Summary 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Due to missing argument checking in the 32 bit compatibility system call handler in the 2.4 Linux Kernel on the AMD64 platform a local attacker can gain root access using a simple program. This issue was found and fixed by Petr Vandrovec and has been assigned the Mitre CVE ID CAN-2004-1144. This is a 2.4 Kernel and AMD64 specific problem, other architectures and the 2.6 Kernel are not affected. 2) solution/workaround There is no workaround, please install the supplied kernels. 3) special instructions and notes SPECIAL INSTALL INSTRUCTIONS: ============================== The following paragraphs will guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, the steps outlined in a particular paragraph may or may not be applicable to your situation. Therefore, please make sure to read through all of the steps below before attempting any of these procedures. All of the commands that need to be executed are required to be run as the superuser (root). Each step relies on the steps before it to complete successfully. **** Step 1: Determine the needed kernel type Please use the following command to find the kernel type that is installed on your system: rpm -qf /boot/vmlinuz Following are the possible kernel types (disregard the version and build number following the name separated by the "-" character) k_deflt # default kernel, good for most systems. k_i386 # kernel for older processors and chip sets k_athlon # kernel made specifically for AMD Athlon(tm) family processors k_psmp # kernel for Pentium-I dual processor systems k_smp # kernel for SMP systems (Pentium-II and above) k_smp4G # kernel for SMP systems which supports a maximum of 4G of RAM kernel-64k-pagesize kernel-bigsmp kernel-default kernel-smp **** Step 2: Download the package for your system Please download the kernel RPM package for your distribution with the name as indicated by Step 1. The list of all kernel rpm packages is appended below. Note: The kernel-source package does not contain a binary kernel in bootable form. Instead, it contains the sources that the binary kernel rpm packages are created from. It can be used by administrators who have decided to build their own kernel. Since the kernel-source.rpm is an installable (compiled) package that contains sources for the linux kernel, it is not the source RPM for the kernel RPM binary packages. The kernel RPM binary packages for the distributions can be found at the locations below ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64. After downloading the kernel RPM package for your system, you should verify the authenticity of the kernel rpm package using the methods as listed in section 3) of each SUSE Security Announcement. **** Step 3: Installing your kernel rpm package Install the rpm package that you have downloaded in Steps 3 or 4 with the command rpm -Uhv --nodeps --force <K_FILE.RPM> where <K_FILE.RPM> is the name of the rpm package that you downloaded. Warning: After performing this step, your system will likely not be able to boot if the following steps have not been fully followed. If you run SUSE LINUX 8.1 and haven't applied the kernel update (SUSE-SA:2003:034), AND you are using the freeswan package, you also need to update the freeswan rpm as a dependency as offered by YOU (YaST Online Update). The package can be downloaded from ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/ **** Step 4: configuring and creating the initrd The initrd is a ramdisk that is loaded into the memory of your system together with the kernel boot image by the bootloader. The kernel uses the content of this ramdisk to execute commands that must be run before the kernel can mount its actual root filesystem. It is usually used to initialize SCSI drivers or NIC drivers for diskless operation. The variable INITRD_MODULES in /etc/sysconfig/kernel determines which kernel modules will be loaded in the initrd before the kernel has mounted its actual root filesystem. The variable should contain your SCSI adapter (if any) or filesystem driver modules. With the installation of the new kernel, the initrd has to be re-packed with the update kernel modules. Please run the command mk_initrd as root to create a new init ramdisk (initrd) for your system. On SuSE Linux 8.1 and later, this is done automatically when the RPM is installed. **** Step 5: bootloader If you run a SUSE LINUX 8.x, SLES8, or SUSE LINUX 9.x system, there are two options: Depending on your software configuration, you have either the lilo bootloader or the grub bootloader installed and initialized on your system. The grub bootloader does not require any further actions to be performed after the new kernel images have been moved in place by the rpm Update command. If you have a lilo bootloader installed and initialized, then the lilo program must be run as root. Use the command grep LOADER_TYPE /etc/sysconfig/bootloader to find out which boot loader is configured. If it is lilo, then you must run the lilo command as root. If grub is listed, then your system does not require any bootloader initialization. Warning: An improperly installed bootloader may render your system unbootable. **** Step 6: reboot If all of the steps above have been successfully completed on your system, then the new kernel including the kernel modules and the initrd should be ready to boot. The system needs to be rebooted for the changes to become active. Please make sure that all steps have completed, then reboot using the command shutdown -r now or init 6 Your system should now shut down and reboot with the new kernel. 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. x86-64 Platform: SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-268… 585c7dd47f8e6f9e60ae4eed5fbb21fe ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-268.x… 44b0c5e8beae0d1b60b85f0f1406a4f9 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… 000194dc37b15a93c8b0313288c9c879 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-268.sr… 3f0a9d938251f2d72fce0ccc979c19a1 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-268.src.… 33b072ab6ef6333f42bda07a5de7e658 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… 772c469c0907594d6396918a5d4c91f6 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: See the SUSE Security Summary Report for more information. ______________________________________________________________________________ 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.7 (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+ 3J2KRWSOhpAMsnMxtPbBiEYEExECAAYFAkGJG+YACgkQGsiRhDTRlzm8CQCg14Wz vg6j45e/r1oyt9EaHhleSacAnA+2dArk1I3xt49Z5rdnhqheF//9mQGiBDnu9IER BACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff4JctBsgs47tj miI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0dM+HFrruCgBlW t6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcOQliHu8jwRQHx lRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifr ZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBED3+D2t1V/f8l 0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1 krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoEmyW/xC1sBbDk DUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25p bmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkDwmcABAsKAwQD FQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6dNfnwI2PAsgCg jH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzO AKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUD BRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4 fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklL snr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMn snT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/ xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmp U661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0EExECAB0FAjxq qTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1fAJ9dR7saz2KP NwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0EOe70khAIAISR 0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/HZnh3TwhBIw1 FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44ht5h+6HMBzoFC MAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPTtGzcAi2jVl9h l3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM523AMgpPQtsK m9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q2Y+GqZ+yAvNW jRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8QnSs0wwPg3xE ullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWawJxRLKH6Zjo/F aKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ1sj2xYdB1xO0 ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCHORrNjq9pYWlr xsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1wwylxadmmJaJ HzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQYEQIADAUCOe70 kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol0JdGwACeKTtt geVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAKCRCoTtronIAK yofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3coSPihn1+OBNw= =Fv2n - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQcmLyHey5gA9JdPZAQE1fwf9G0r2SfPkxcKfahP7PtA53M4+zuh+lIPT NYVU1Pl7oOOCqSH6d7dk5BLMqUWN41cCzpXW2cYTtIY5WYD+RsbRooF1wotxY8nz iSPZ5ZujLPNcC2X8KNo3iqh0rz6JwRUJwJjsWcyQTIHfPoXd4SwOJUG/NFUeFl+T zN+3nfKe6+t7iwXbgQ1qRTuLE2kK8J7qw/+4sx5nDsefYq8HqJtf6kz7w7x+ZBCL Twtn0mnxPbbZElvr2PDJHMPP/Ul3/Cuv0wDmtzfQ9Oxinew9sNTqmz8AcFSrqm69 appLDLdEJkaNyYxIymqo2+Oeom9D/SUfV4COpQdLbOH4cBvmoLlKBQ== =sIxH -----END PGP SIGNATURE-----

1 0

Re: [suse-security] SUSE Security Announcement: various kernel problems (SUSE-SA:2004:044)
by Kyek, Andreas, VF-DE 22 Dec '04

22 Dec '04

Markus meissner wrote: [...] [...] > > x86 Platform: > > SUSE Linux 9.2: > > ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-so > urce-2.6.8-24.8.i586.rpm > 8dc5b70f5fdef7c0437372d2811bcb02 > > ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-de > fault-2.6.8-24.8.i586.rpm > 134c37732850c86ef872c97171c81ede [...] Where are they? I do not find any packages for 9.2; neither on gwdg.de nor directly on ftp.suse.com. Andreas

4 3

mod_dav module in Apache 2.0.50
by Ray Carlino 22 Dec '04

22 Dec '04

CAN-2004-0809 Since I can't find anything on the new site maybe someone can answer where I can find where this has been addressed in 9.2? Thanks -- Ray

1 0

EXTERN -> SSH ON FIREWALL
by Patrick Holzinger 22 Dec '04

22 Dec '04

Hello members, i has a problem with the access of external - > SSH on the Firewall can communicate someone to me the suitable rule (ipchain). thx Patrick

1 0

RE: [suse-security] Web Content Filter
by Theytaz Antoine 22 Dec '04

22 Dec '04

I know "Websense Enterprise", seem to be really really efficient... for Windows, Linux (Redhat only ?) and Solaris Does anybody has this installed under SuSE ? Antoine -----Message d'origine----- De : Stefan.Junge(a)ssi-schaefer.de [mailto:Stefan.Junge@ssi-schaefer.de] Envoyé : mercredi 22 décembre 2004 08:27 À : suse-security(a)suse.com Objet : [suse-security] Web Content Filter Hi, I´m searching for a good web content filter. At the moment there is as squid proxy, but we need a little bit more. Any suggestions for a good product? (It could be a commercial product) Thanks Stefan GnuPG Fingerprint 970E C83D 1B68 E668 12C5 FFF8 643A 3610 A5F6 6B18 -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

2 1

PHP patches
by Jim Clausing 22 Dec '04

22 Dec '04

Any idea when the PHP patches are going to be available. The Santy thing this morning only exploits phpBB, so if you're not running that you are okay for the moment, but exploit code for the unserialize() vuln has been around for at least 4 days, so I suspect someone will turn that into a worm pretty quick. -- Jim Clausing GCFA, GCIA, CISSP, CCSA

2 1

SUSE Security Announcement: various kernel problems (SUSE-SA:2004:044)
by Marcus Meissner 21 Dec '04

21 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2004:044 Date: Tuesday, Dec 21st 2004 18:00 MEST Affected products: SUSE Linux 8.1, 8.2, 9.0, 9.1, 9.2 SUSE Linux Enterprise Server 8, 9 SUSE Linux Desktop 1.0 Novell Linux Desktop 9 Vulnerability Type: local privilege escalation remote denial of service local denial of service Severity (1-10): 9 SUSE default package: yes Cross References: CAN-2004-1068 CAN-2004-1016 CAN-2004-1137 CAN-2004-1151 Content of this advisory: 1) security vulnerability resolved: - several vulnerabilities in the linux kernel problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - problem with smbfs in earlier update - see SUSE Security Summary Report 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Linux kernel Several vulnerabilities have been found and fixed in the Linux kernel. Paul Starzetz reported that the missing serialization in unix_dgram_recvmsg() which was added to kernel 2.4.28 can be used by a local attacker to gain elevated privileges (root access). This issue is tracked by the Mitre CVE ID CAN-2004-1068. Paul Starzetz and Georgi Guninski reported independently that bad argument handling and bad integer arithmetics in the IPv4 sendmsg handling of control messages could lead to a local attacker crashing the machine. This problem was fixed by Herbert Xu and is tracked by the Mitre CVE ID CAN-2004-1016. Georgi Guninski reported a memory leak in the IP option handling of the IPv4 sendmsg call. Paul Starzetz found bad handling in the kernel IGMP code, which could lead to a local attacker being able to crash the machine. This problem was fixed by Chris Wright and is tracked by the Mitre CVE ID CAN-2004-1137. Olaf Kirch found and fixed a problem in the RPC handling in the kernel of SUSE Linux 9.1, 9.2, and SUSE Linux Enterprise Server 9 which could lead to a remote attacker crashing the machine. A local denial of service problem in the aio_free_ring system call could allow a local attacker to crash the machine. A problem in the memory management handling of ELF executables could lead to a local attacker crashing the machine with a handcrafted ELF binary. (This is a VMA overlap problem and not related to earlier ELF problems.) A buffer overflow in the system call handling in the 32bit system call emulation on AMD64 / Intel EM64T systems was fixed. It is not thought to be exploitable. A memory leak in the ip_conntrack_ftp firewalling module was fixed in the 2.6 kernels. Various UML security issues in the SUSE Linux 9.2 UML setup were fixed. Additionally some non-security bugs were fixed in the released kernels: SUSE Linux Enterprise Server 8 and SUSE Linux 8.1: - A memory leak in addition / removal of SCSI target devices was fixed. - A race condition in SCSI I/O accounting which could lead to erroneous reports on SCSI disk I/O was fixed. - S390: Patches from IBM have been installed in the S/390 architecture, both for 32 and 64bit. Refer to the maintenance information mail for the full change log. - The "memfrac" and "lower_zone_reserve" kernel parameters had no effect since they were used before kernel command line parsing. - PowerPC: Missing synchronization that could lead to processes hanging in signal delivery was added. SUSE Linux Enterprise Server 9 and SUSE Linux 9.1: - A vfree() was called with interrupts disabled in the SCSI generic device handling, which could lead to a hanging machine. - A race condition between a file unlink and umount could lead to a machine crash. - Fixed a small memory leak in bio_copy_user(). - cdrecord -scanbus could crash the kernel when using the "gdth" SCSI driver. - Allow reading from zero page (/dev/zero) using O_DIRECT/rawio. - Fixed some LSB issues in the fcntl compatibility handling. - The st (SCSI tape) driver did not pass on generic SCSI ioctl commands to the SCSI mid layer. SUSE Linux 9.2: - The kernel installation routines did not call depmod for the modules in the -nongpl RPMs, so they could not be loaded. This lead to non working USB modem drivers and similar. This problem was fixed. - A Problem with mounting iPods over FireWire was fixed. - A data corruption problem in the megaraid driver was fixed. - A pageattr overflow condition in the memory subsystem and missing TLB flush if multiple pages were passed were fixed. - Allow reading from zeropage with O_DIRECT/rawio. - Do not restart the system on ACPI events after power down. (Make it no longer start on opening the lid of just shutdown laptops for instance.) - New memory imbalance handling handling by Andrea leading to better Out Of Memory (OOM) handling was added. 2) solution/workaround Please install the fixed packages, there is no workaround. 3) special instructions and notes SPECIAL INSTALL INSTRUCTIONS: ============================== The following paragraphs will guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, the steps outlined in a particular paragraph may or may not be applicable to your situation. Therefore, please make sure to read through all of the steps below before attempting any of these procedures. All of the commands that need to be executed are required to be run as the superuser (root). Each step relies on the steps before it to complete successfully. **** Step 1: Determine the needed kernel type Please use the following command to find the kernel type that is installed on your system: rpm -qf /boot/vmlinuz Following are the possible kernel types (disregard the version and build number following the name separated by the "-" character) k_deflt # default kernel, good for most systems. k_i386 # kernel for older processors and chip sets k_athlon # kernel made specifically for AMD Athlon(tm) family processors k_psmp # kernel for Pentium-I dual processor systems k_smp # kernel for SMP systems (Pentium-II and above) k_smp4G # kernel for SMP systems which supports a maximum of 4G of RAM kernel-64k-pagesize kernel-bigsmp kernel-default kernel-smp **** Step 2: Download the package for your system Please download the kernel RPM package for your distribution with the name as indicated by Step 1. The list of all kernel rpm packages is appended below. Note: The kernel-source package does not contain a binary kernel in bootable form. Instead, it contains the sources that the binary kernel rpm packages are created from. It can be used by administrators who have decided to build their own kernel. Since the kernel-source.rpm is an installable (compiled) package that contains sources for the linux kernel, it is not the source RPM for the kernel RPM binary packages. The kernel RPM binary packages for the distributions can be found at the locations below ftp://ftp.suse.com/pub/suse/i386/update/. 8.1/rpm/i586 8.2/rpm/i586 9.0/rpm/i586 9.1/rpm/i586 9.2/rpm/i586 After downloading the kernel RPM package for your system, you should verify the authenticity of the kernel rpm package using the methods as listed in section 3) of each SUSE Security Announcement. **** Step 3: Installing your kernel rpm package Install the rpm package that you have downloaded in Steps 3 or 4 with the command rpm -Uhv --nodeps --force <K_FILE.RPM> where <K_FILE.RPM> is the name of the rpm package that you downloaded. Warning: After performing this step, your system will likely not be able to boot if the following steps have not been fully followed. If you run SUSE LINUX 8.1 and haven't applied the kernel update (SUSE-SA:2003:034), AND you are using the freeswan package, you also need to update the freeswan rpm as a dependency as offered by YOU (YaST Online Update). The package can be downloaded from ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/ **** Step 4: configuring and creating the initrd The initrd is a ramdisk that is loaded into the memory of your system together with the kernel boot image by the bootloader. The kernel uses the content of this ramdisk to execute commands that must be run before the kernel can mount its actual root filesystem. It is usually used to initialize SCSI drivers or NIC drivers for diskless operation. The variable INITRD_MODULES in /etc/sysconfig/kernel determines which kernel modules will be loaded in the initrd before the kernel has mounted its actual root filesystem. The variable should contain your SCSI adapter (if any) or filesystem driver modules. With the installation of the new kernel, the initrd has to be re-packed with the update kernel modules. Please run the command mk_initrd as root to create a new init ramdisk (initrd) for your system. On SuSE Linux 8.1 and later, this is done automatically when the RPM is installed. **** Step 5: bootloader If you run a SUSE LINUX 8.x, SLES8, or SUSE LINUX 9.x system, there are two options: Depending on your software configuration, you have either the lilo bootloader or the grub bootloader installed and initialized on your system. The grub bootloader does not require any further actions to be performed after the new kernel images have been moved in place by the rpm Update command. If you have a lilo bootloader installed and initialized, then the lilo program must be run as root. Use the command grep LOADER_TYPE /etc/sysconfig/bootloader to find out which boot loader is configured. If it is lilo, then you must run the lilo command as root. If grub is listed, then your system does not require any bootloader initialization. Warning: An improperly installed bootloader may render your system unbootable. **** Step 6: reboot If all of the steps above have been successfully completed on your system, then the new kernel including the kernel modules and the initrd should be ready to boot. The system needs to be rebooted for the changes to become active. Please make sure that all steps have completed, then reboot using the command shutdown -r now or init 6 Your system should now shut down and reboot with the new kernel. 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. x86 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-source-2.6.8-24… 8dc5b70f5fdef7c0437372d2811bcb02 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-default-2.6.8-2… 134c37732850c86ef872c97171c81ede ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-smp-2.6.8-24.8.… f552ef1f49675a4e8dc8f71ad7829ed1 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-bigsmp-2.6.8-24… ea2be2b3152a5b6d362636cc29534007 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-default-nongpl-… f5af05e9e7ec387fe1ce755b8f53a022 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-smp-nongpl-2.6.… 94e01d31f7cdda2a2ae00377613ad625 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-bigsmp-nongpl-2… f3437bd22be65df11df36b9722f15fa7 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/um-host-kernel-2.6.8-2… 772e6200300a11d137383e51486cd159 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/um-host-install-initrd… 00eba31f6adc46309c4be34ddd477d1a patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/um-host-kernel-2.6.8-2… 00d6b04af9b54eaff147d7267d66ae08 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/um-host-install-initrd… 2de74bf6f185d1c732412945147c4914 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-source-2.6.8-24.… bc9e4a08ba429884716d9e1768ca7391 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-default-2.6.8-24… 0cbc4714154be7df7a18fda4c5ca595b ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-smp-2.6.8-24.8.n… 451d4c51a5d4083b4e663913bb53e622 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-bigsmp-2.6.8-24.… 292bc1aab35f113099765e01f5c87b8e ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-default-2.6.8-24… 0cbc4714154be7df7a18fda4c5ca595b ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-smp-2.6.8-24.8.n… 451d4c51a5d4083b4e663913bb53e622 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-bigsmp-2.6.8-24.… 292bc1aab35f113099765e01f5c87b8e ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-um-2.6.8-24.8.no… 32aeaea2ff952d83cfd2cf94b1358d33 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/um-host-install-initrd-… bc079272affb6c4a444ff0eed5668c58 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-source-2.6.5-7.… b5905fea74dd7c6b43896506c28a23d7 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-default-2.6.5-7… 35fd6f0047d3666f6402b07175c69ce2 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-smp-2.6.5-7.111… 0a41cb4c8a9325b15ffee9407af62e08 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-bigsmp-2.6.5-7.… 4cc0c401f76b7d5109dfbd7e2775c83f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-source-2.6.5-7.1… cbfd74fdb9bb2c9017f281a7ffe3ea0c ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-default-2.6.5-7.… 11708c86166aff33fe48157d998139a3 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-smp-2.6.5-7.111.… 5989481ab5506a2a8ee539b172fd3a3e ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-bigsmp-2.6.5-7.1… 25e8246b9d18d6bac0087ccd16012c8b SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-2… 3fabe8709c6f108985e6db14d8eddd68 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-266.i58… d7d5f9d018ed62aa4785046128509de7 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-266.i586.… 151eec47b73e0aab0376a8d4dd108607 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-266.i5… ea1f74c173b2fac8bc5a335de2304e3f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-26… 06dea7c190f66312cee81b9d59f6b968 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-266.src.… 63b4cdc0ef1549057931da01b3ebc1a3 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-266.src.rpm 1636bcd52054dd60493def485fa00576 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-266.src… 0f2ab3b06dc3be82a31317cece16ad7b SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… 1baebbe7215434dec73aeaec61b68579 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-127.i58… 500299c75a582d4ac4fb9d9d56e6ce9d ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-127.i586.… 6cee78e7216c8fa9b07a5b78c7a0b774 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-127.i5… e15fe145d9d62977f89f3647d43d6692 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-127.i586… a88e3cd46a56f49f4846d151a05d4430 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.Su… bd4ba934e3ce4dec888fcaf26e5dec38 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-127.src.… c1e43e827b7d2db8d0a189daf33c3eee ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-127.src.rpm 3871dac3965594d5e368fd91f56f07cb ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-127.src… 74d66b02ab0cadb0cc6709068f30e7e5 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-127.src.r… 318b66cbf216317af917bc8e7cc28fea SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-2… 496f775186fb745b86e7545e9f13e7bd ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-266.i58… 174fd559a0378e35aa11fb2d93a2684b ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_smp-2.4.21-266.i586.… add6505218c8f6929d79305ee7343727 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-266.i5… 3cc4344755df9721d20d717a0ff2ecc4 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_psmp-2.4.21-266.i586… a2b0cb0c0181f4dc5a072e21789dc585 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kernel-source-2.4.21-26… 40d6ed2f4c77f2225bed7a5dd7f8e346 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-266.src.… 70e9a1131849f3d98c8d5009915abb52 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_smp-2.4.21-266.src.rpm b7eb4f46bd06cab9aa1ad7c97264c96c ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-266.src… 66879d8b6ffff23e44895bbfa6c1c644 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_psmp-2.4.21-266.src.r… ade3afd2816ba005650b82de9dc1da7b x86-64 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-source-2.6.… dca3907a9c0e31ea7fd3cb13f6d7a2c7 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-default-2.6… 22d4f74fe29eae1acb8a4dacbed16c26 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-smp-2.6.8-2… b38935409955a9f7e427532f1a9a110e ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-default-non… a4196f62b128a4d59106b6e4fb91a89d ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-smp-nongpl-… 7ab6d19efe01324674c3ff0f06740d99 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-source-2.6.8-2… bc9e4a08ba429884716d9e1768ca7391 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-default-2.6.8-… 0cbc4714154be7df7a18fda4c5ca595b ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-smp-2.6.8-24.8… 451d4c51a5d4083b4e663913bb53e622 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-default-2.6.8-… 0cbc4714154be7df7a18fda4c5ca595b ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-smp-2.6.8-24.8… 451d4c51a5d4083b4e663913bb53e622 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-source-2.6.… 9eaf681cb5ce3d0bca96dc93c2cbbe4d ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-default-2.6… 1be1de01f36069168846ca611a9c493a ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-smp-2.6.5-7… 905182441a3e0dfc19d241249f0bcd43 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-source-2.6.5-7… 07caa57a7b036cc4e22f73744f0378f3 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-default-2.6.5-… 15b023f310014e3327dde1a0bcf746c1 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-smp-2.6.5-7.11… 10c39d732cbafaeabb21f64aab518602 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… 981d7abbc9dd7774c724a3aec2508db1 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-266… 47e4ec4f93d49abc0459a058526c1fb6 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-266.x… 03b0c0787d0a818634b11d4bbc533a38 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_numa-2.4.21-149.… 8877a1ca2ea3cb393aa96be727ca362e source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… 326f9c08d5f92ccc3bca476977b745d6 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-266.sr… ab01bf0aa3117ce642cc2eedebbba41b ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-266.src.… 714b10cc3466776599cab8237223165f ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_numa-2.4.21-149.src… 52c705df37ed9e44bb2943af318d8500 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: Please see our Security Summary Report. - problem with smbfs in the previous kernel update We received reports of smbfs being broken by our last kernel update (released on Dec 1st, SUSE-SA:2004:042). This apparently only affects the smbfs filesystem on 2.6 kernels, so SUSE Linux 9.1, 9.2, SUSE Linux Enterprise Server 9 and Novell Linux Desktop 9. This problem is unfortunately not yet fixed in this security update, we will be releasing fixed packages in the begin of next year. As workaround please change to use the cifs filesystem if possible, which replaces smbfs in the 2.6 kernel series. ______________________________________________________________________________ 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.7 (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+ 3J2KRWSOhpAMsnMxtPbBiEYEExECAAYFAkGJG+YACgkQGsiRhDTRlzm8CQCg14Wz vg6j45e/r1oyt9EaHhleSacAnA+2dArk1I3xt49Z5rdnhqheF//9mQGiBDnu9IER BACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff4JctBsgs47tj miI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0dM+HFrruCgBlW t6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcOQliHu8jwRQHx lRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifr ZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBED3+D2t1V/f8l 0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1 krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoEmyW/xC1sBbDk DUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25p bmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkDwmcABAsKAwQD FQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6dNfnwI2PAsgCg jH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzO AKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUD BRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4 fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklL snr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMn snT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/ xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmp U661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0EExECAB0FAjxq qTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1fAJ9dR7saz2KP NwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0EOe70khAIAISR 0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/HZnh3TwhBIw1 FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44ht5h+6HMBzoFC MAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPTtGzcAi2jVl9h l3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM523AMgpPQtsK m9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q2Y+GqZ+yAvNW jRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8QnSs0wwPg3xE ullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWawJxRLKH6Zjo/F aKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ1sj2xYdB1xO0 ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCHORrNjq9pYWlr xsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1wwylxadmmJaJ HzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQYEQIADAUCOe70 kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol0JdGwACeKTtt geVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAKCRCoTtronIAK yofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3coSPihn1+OBNw= =Fv2n - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQch6Z3ey5gA9JdPZAQH3HQgAnuu2f4XzU4J5LhAWoUOsnBEARd6UJP3c WCruYVbFFQHnEJylqwyJSrFLZ1/vWcVUIE6eEP5DDXmZqo4Yrbq/auNoZs7/35rZ XJo7PPEVoPnyyvqH5a4Do0+mVkdHotxC6vltuEnryQO4X0ti5FVR7fOTLbBW/khW QfbzoCTTS9yXA/mVTd3APZqsPpRdBdL3uLYBdkQ92+25TS+EKPRgo0xdvdxFaNsR KmSMH1O+ki0xTRTrB//0WajHRS9WvyzrLhZJ8/pY1Q/4sWWwX/BJuXvTEscXDr15 QpLZFn5ASbhUV9qiPgQem8Bvx5zI1MwesE8BGUSvUWw8eAZGoH301g== =BemR -----END PGP SIGNATURE-----

1 0

Re: Warning about accessing / attacking phising and spoofing sites
by suse＠karsites.net 19 Dec '04

19 Dec '04

Yes I agree - the same applies to visiting know hackers sites, to see what they are up to. I picked something up by downloading a document, or possibly clicking on the 'about this site' button, on a well known hackers site. Obviously a bobby-trapped link somewhere, and as I was the one that initiated the connection, it got through my firewall as an established or related connection. (If you want the URL of the hackers site, please email me off list and request it). No I'm NOT a hacker, I was just curious to know what their latest Linux exploits were. I noticed that after visiting the hackers site, whenever I connected to the net, there was activity on my modem, and some IP packets were being sent to two IP's in Australia. The IP's actually resolved to an IT firms website in Aus. I had to do a fresh installation to cure the problem. So my advice would be, use a dedicated machine, with it's own single connection and dynamic IP address to the internet, if you want to go poking around hackers or phishers sites. That way, if your machine gets infected, you can reformat your hard drive, and do a fresh O/S installation, which should hopefully wipe out any viruses your machine may have picked up. Alternatively, use a low capacity HDD, that you can afford to bin if it gets infected. Whatever you do, don't try this on a machine that is networked, or you could end up infecting all machines on the entire network. Just my 2 pence worth. Kind Regards - Keith Roberts http://www.karsites.net/ On Sun, 19 Dec 2004, Amir Herzberg wrote: --snip-- > You both probably meant this as a joke, but just for safety, let me warn > anybody against doing this, or entering phishing sites `just for fun`. > Since we're doing research on secure user-interface extensions to > browsers to prevent web spoofing and phishing, I've been looking at many > phishing and spoofing web sites (see article at > http://www.cs.biu.ac.il/~herzbea//Papers/ecommerce/spoofing.htm or > extension for Mozilla/FireFox at http://trustbar.mozdev.org) However, > this should be done very carefully (read: from a specially protected, > not sensitive machine), since many of these sites try (also) to use > different browser vulnerabilities to break into machines. While I am > sure you are all trying to maintain your browsers and OS updated and > configured securely, there is always the risk of some exploit you were > not aware of. So, I suggest you don't visit these pages `just for fun`.

1 0