August 2004 - openSUSE Security - openSUSE Mailing Lists

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

Per user config for SpamAssassin with amavisd-new and cyrus-imapd
by David Huecking 26 Sep '04

26 Sep '04

Hi folks, maybe someone could give me a hint... I switched from: fetchmail->sendmail->sendmail.milter->Amavis->.forward->procmail->spamc(SpamAssasin)->INBOX which did global virus checking and per user spam checking with Bayes testing to fetchmail->postfix->amavisd-new->perl-spamassassin->cyrus-imapd which does global virus and global spam checking BUT NO PER USER spam checking, so without Bayes testing! :-( So the rate of unreconised spam did increase. I fiddled around with options in the /etc/mail/spamassassin/local.cf, but they were ignored because amavisd-new calls spamassin via perl interface and takes some SA parameters from the /etc/amavisd.conf (beginning with $sa_). I tried calling a SUIDed cyrus deliver (without SUID deliver hasn't got the right: deliver[3876]: connect(/var/lib/imap/socket/lmtp) failed: Permission denied) to user cyrus via .forward and a .procmailrc. The log said that lmtpd was called, but depending on the syntax of deliver in the .procmailrc the mail was delivered to the INBOX-file in /var/spool/mail or just vanished! One example for my .promailrc: :0 fw |/usr/bin/spamc -f |/usr/lib/cyrus/bin/deliver -e -a david -m user.david and the .forward: "|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #user" Could someone give me a hint using sieve or procmail for a per user SpamAssassin check? Thanks in advance. -- Eat, sleep and go running, David Huecking. Encrypted eMail welcome! GnuPG/ PGP-Key: 0x57809216. Fingerprint: 3DF2 CBE0 DFAA 4164 02C2 4E2A E005 8DF7 5780 9216

2 2

Re: [suse-security] harden_suse
by tfulton9909＠comcast.net 23 Sep '04

23 Sep '04

I was told that this was a resource for security questions to be answered. Could someone please help me. thanks Tom Fulton Novell San Jose, CA > On Mon, 09 Aug 2004 22:44:42 +0000, tfulton9909(a)comcast.net > wrote: > > Hello, > > What is that status of harden_suse in SLES 9 in light of Bastille being > released? > > thanks > > -- > 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 >

3 2

Metainformationen in Dokumenten als Sicherheitsrisiko- auch unter Linux?
by Axel.Krebs＠t-online.de 01 Sep '04

01 Sep '04

Hallo! Stieß vorhin auf http://www.metadatarisk.org/ Sind vergleichbare Sicherheitsrisiken in (unsichtbaren?) Metadaten auch in OO-Dokumenten bekannt? Weiß jemand was dazu? Danke erstmal, Axel -- Dr. A. Krebs <Axel.Krebs(a)T-Online.de>

4 3

Blocking a domain with SuseFirewall2
by Raphael Leplae 30 Aug '04

30 Aug '04

Hi, I've setup the SuseFirewall2 on my web server, allowing access just via http and ssh, that was very easy with the GUI. Now if I need to block a specific domain, let say *.123.123.123, is there a simple way to do it in /etc/sysconfig/SuSEfirewall2 ? I was expecting something like: FW_REJECT_IP="*.123.123.123" but nothing like that in the examples provided in /usr/share/doc/packages/SuSEfirewall2/ I guess there is a simple way to do it. Thanks in advance. Raphael -- ___________________________________________________________ Raphael Leplae, Ph.D. Research Scientist SCMBB - ULB Tel: +32 2 6505499 Blvd du Triomphe - CP 263 Fax: +32 2 6505425 1050 Brussels Belgium SCMBB Home Page http://www.scmbb.ulb.ac.be ACLAME - The Prokaryotic Mobilome http://aclame.ulb.ac.be ___________________________________________________________

5 6

Re: [suse-security] Blocking a domain with SuseFirewall2
by PW 30 Aug '04

30 Aug '04

If one knows how, yes, it's easy. Alas, SuSE's firewall documentation is not well documented in that aspect. Besides IPv6 problems, the firewall itself is configured out of the box to deny nearly all network traffic, which is not very practicable for a typical Web/LAN Server box, indeed. This firewall even requires custom rules to allow unlimited access from the internal network to external networks, such as the Internet, go figure. Here's the only way how to do it with SuSE firewall: 1. Open /etc/sysconfig/scripts/SuSEfirewall2-custom in a text editor 2. Seek to the section "fw_custom_before_antispoofing()" 3. Enter your custom firewall rules. I.e., block a specific address: iptables -I INPUT -s xxx.xxx.xxx.xxx -j DROP Philippe Wiede Raphael Leplae wrote: > Hi, > > I've setup the SuseFirewall2 on my web server, allowing access just via http and ssh, that was very easy with the GUI. > Now if I need to block a specific domain, let say *.123.123.123, is there a simple way to do it in /etc/sysconfig/SuSEfirewall2 ? > I was expecting something like: > FW_REJECT_IP="*.123.123.123" > but nothing like that in the examples provided in /usr/share/doc/packages/SuSEfirewall2/ > > I guess there is a simple way to do it. > Thanks in advance. > > Raphael

3 2

Re: [suse-security] Blocking a domain with SuseFirewall2
by b＠rry.co.za 30 Aug '04

30 Aug '04

Also, if you have set up FW_SERVICES_EXT_TCP="80" this expressley allows all connections, and so will be a conflicting rule. You need to take port 80 out of that string and create a trust rule in: - # 10.) # Which services should be accessible from trusted hosts/nets? # # Define trusted hosts/networks (doesnt matter if they are internal or # external) and the TCP and/or UDP services they are allowed to use. # Please note that a trusted host/net is *not* allowed to ping the firewall # until you set it to allow also icmp! # # Choice: leave FW_TRUSTED_NETS empty or any number of computers and/or # networks, seperated by a space. e.g. "172.20.1.1 172.20.0.0/16" # Optional, enter a protocol after a comma, e.g. "1.1.1.1,icmp" # Optional, enter a port after a protocol, e.g. "2.2.2.2,tcp,22" # FW_TRUSTED_NETS="" In other rules you can use ! to make an exception, can anyone confirm if that will work in this rule? -- Reader, suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself. -- Mark Twain

2 1

suse-linux-e
by ecobel 30 Aug '04

30 Aug '04

Sorry for this OT, but I do not receive mails from suse-linux-e anymore! Is there someone that can give any news? Thank you. ecobel

1 0

Re: [suse-security] Blocking a domain with SuseFirewall2
by b＠rry.co.za 30 Aug '04

30 Aug '04

One other thing, is your apache server on the same machine? I have had issue with blocking access before because of conflicting rules. I had a forwarder set up to direct traffic to my web server in the DMZ, set up a block on the firewall and found that the traffic was still being forwarded. I then had to alter my forwarding rule to forward only from designated ranges, so that my blocks would have effect. what do your log files say about the accepted sessions? -- You own a dog, but you can only feed a cat.

1 0

Re: [suse-security] Insecure temp file creation fix - peer review please
by Derek's Lists 29 Aug '04

29 Aug '04

On Saturday 28 August 2004 05:15, Christian Boltz wrote: > aka "symlink attack", i assume. Yup... :o) > > TDIR=${TMPDIR:-/tmp}/aview_$$ > > Insecure. $$ is guessable (or, worst case: for i in `seq 2 33000 ; do > ln -s /home/victim/Mail/inbox /tmp/aview_$i ; done - no more need to > guess ;-) > > Use mktemp instead: > > TDIR=`mktemp -d /tmp/aview.XXXXXXXXXX` || { > echo "unable to create temp dir" >&2; > exit 1; > } I avoided using mktemp because the aalib code runs on lots of different platforms. From what I've read, I can't be sure that mktemp is available on all of them. So....: > > trap clear 0 > > (umask 077 && mkdir $TDIR) || { > > echo "Unable to create temp directory $TDIR" > > exit 1 > > } > > mkfifo $FIFO || { > > echo "Unable to create FIFO $FIFO" > > exit 1 > > } > > These blocks are no longer needed because mktemp already creates the > temp dir and fifo. ...these blocks are needed! I think that's the platform independent, secure way to create a temporary directory, and if there's a nasty link in place it will fail. > > if anytopnm $1 >$FIFO 2>/dev/null ; then > > ^^ > Variables should be quoted: "$1" Good point! I only worried about the symlink issues (slaps own wrists)! > > while true; do > > echo "0 " > > done > > This is an endless loop just printing "0 " on your screen. Yeah, weird eh? I decided to only concentrate on the security aspects of the script. Presumably the original author felt good reason to fill the screen with 0s! > Yours, > > Christian Boltz Thanks, I've learnt more useful stuff... :o)

3 2

Whining... (Was Bad Quali....)
by b＠rry.co.za 29 Aug '04

29 Aug '04

The thing I don't get. The majority of people on this list have installed free software (I would love to see the amount of SuSE systems out there as a percentage of the amount SOLD by SuSE). While this is in the Open Source community no excuse for bad quality control, the overall service received from SuSE in unofficial support over the past 5 years has been nothing short of brilliant. A mistake has happened, been recognised, and guaranteed will be analysed to try and prevent the same mistake from happening again. Most kids fall off their bucycle at some point. They learn at that point that turning in the sand at high speed is a bad idea and don't do it again (unless the truck they are trying to avoid takes their eyes off the road for a moment). So all in all, SuSE keep it up, everyone else, shut up, I am getting to see this thread as SPAM in my security mailbox and am sure that while I am only adding to the problem now, hopefully you will all grow up and spend more time fixing your problems than whining because someone else isn't. -- Q: How many lawyers does it take to change a light bulb? A: You won't find a lawyer who can change a light bulb. Now, if you're looking for a lawyer to screw a light bulb...

8 12

Insecure temp file creation fix - peer review please
by Derek Fountain 29 Aug '04

29 Aug '04

A few days back I noticed that the /usr/bin/asciiview script from the aalib-1.4.0-275 package in SUSE-9.1 used insecure temp file creation. The exploit is trivial and allows an attacker to cause a victim to overwrite any of the victim's files. The project over at Sourceforge (http://aa-project.sourceforge.net) appears to be dead, having had no update for 3 years. Emails to the two maintainers (at least the email addresses found in the SUSE RPM information) came bouncing back. So I thought I'd fix the bug myself... :) Since the script is small, I can post it here - see below. Perhaps someone with a bit more experience at this sort of thing can have a look at it to see if I've done it properly? If my fix checks out I'll post it on the Sourceforge project page, although whether anything good will actually become of it is anyone's guess... #!/bin/bash # asciiview - an ascii art image browser script. Front end for aview/aaflip TDIR=${TMPDIR:-/tmp}/aview_$$ FIFO=$TDIR/aview$$.pgm clear() { kill $! 2>/dev/null rm -f $FIFO 2>/dev/null rmdir $TDIR 2>/dev/null } myconvert() { if anytopnm $1 >$FIFO 2>/dev/null ; then exit elif convert -colorspace gray $1 pgm:- 2>/dev/null ; then exit fi echo "Failed to convert file format to PNM by both convert and anytopnm" >&2 while true; do echo "0 " done } filenames="" options="" if [ "$1" = "" ]; then echo "$0 - an ascii art image/animation browser. To run this script you need aview, aaflip and NetPBM or ImageMagick. You may browse any graphics format supported by NetPBM or ImageMagick and .fli/.flc files. Usage: $0 [options] [filenames] type aview --help [enter] for list of options. " exit 1 fi while [ "$1" != "" ]; do case $1 in "-font" | "-driver" | "-kbddriver" | "-mousedriver" | "-*width" | "-*height" | "-bright" | "-contrast" | "-gamma" | "-random" | "-dimmul" | "-boldmul") options="$options $1 $2" shift shift ;; -*) options="$options $1" shift ;; *) filenames="$filenames $1" shift ;; esac done trap clear 0 (umask 077 && mkdir $TDIR) || { echo "Unable to create temp directory $TDIR" exit 1 } mkfifo $FIFO || { echo "Unable to create FIFO $FIFO" exit 1 } for name in $filenames ; do if test -r $name ; then case $name in *.fli | *.lfc | *.flic ) PATH="$PATH:." aaflip $options $name ;; *) myconvert $name >$FIFO & pid=$! PATH="$PATH:." aview $options $FIFO kill $pid 2>/dev/null esac else echo "$name could not be opened" fi done

3 2

Something broken in wvdial
by Carlos E. R. 29 Aug '04

29 Aug '04

Hi, Las mont I reported in SLE that I was getting the string "ovider" printed by the wvdial program when run on a terminal: --> Using interface ppp0 --> pppd: ovider --> pppd: ovider --> pppd: ovider --> Authentication (CHAP) started Then, after some kernel update, it changed to "Provider". Today, after I added a comment to /etc/wvdial.conf, it has changed to: --> pppd: Inherits --> pppd: Inherits Which is also a string contained in the wvdial.conf file, and I suppose, in the token space of the wvdial program. On a spanish Knoppix 3.4 live CD, the message is "espera", that is, "wait". That seems a quite more reasonable message. There is some weird string management there, an out of bounds or a not initialised pointer perhaps. Seems dangerous to me... the type of error that leads to a memory overflow and user user scalation or whatever it is called. That would be a security problem. Not to mention the speed limit of 2 Kb/s... but that is perhaps an unrelated problem. I forgot, this is SuSE 9.1. -- Cheers, Carlos Robinson

1 0

e-mail account does not exist
by Philippe Vogel 29 Aug '04

29 Aug '04

Hi! Can anyone remove following mail from the suse-security-list? suse-security(a)nl.corp.keenondots.net I got this several times: [...] suse-security on Sun, 29 Aug 2004 01:55:00 +0200 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <dc0.nl.corp.keenondots.net #5.1.1> [...] Subject: Re: AW: [suse-security] Very Slow Network-I need some help! From: "Philippe Vogel" <filiaap(a)freenet.de> Date: Sun, 29 Aug 2004 01:55:00 +0200 To: "suse-security" <suse-security(a)nl.corp.keenondots.net> content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C48D5A.6D16CB80" Message-ID: <5AD18AFA6BE20444903B38DC8907F6290A1841(a)dc0.nl.corp.keenondots.net> X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Thread-Topic: AW: [suse-security] Very Slow Network-I need some help! Thread-Index: AcSNWm3MrowclVL9QOiCJq2AX1lARw== List-Help: <mailto:suse-security-help@suse.com> List-Subscribe: <mailto:suse-security-subscribe@suse.com> List-Unsubscribe: <mailto:suse-security-unsubscribe-subscriptions=keenondots.com@suse.com> [...]

1 0

AW: [suse-security] Very Slow Network-I need some help!
by Rasp, Robert 28 Aug '04

28 Aug '04

Hello, How can squid run without a writeable file system ? Is there a hard drive in the firewall witch only is used by squid ? Slow Networks can be based on false DNS-Configurations CU Robert -----Ursprüngliche Nachricht----- Von: Paul Ikanza [mailto:PIkanza@newvision.co.ug] Gesendet: Freitag, 27. August 2004 13:45 An: suse-security(a)suse.com Betreff: [suse-security] Very Slow Network-I need some help! Hi Everyone, im running suse firewall on CD for my squid. It works in such a way that when the server boots, it actually boots from the cd-rom drive and picks some files from a floppy diskette (Which can be edited to suit one's need). It is therefore really secure in that a hacker would not write onto the CD-they can only go as far as maybe viewing the contents. I am however experiencing really slow network speeds as in really slow! I need ideas on how I can possibly troubleshoot that problem and if any one is actually using this procedure for a firewall, bring me upto speeed on it. Paul. o ~ o ~ o ~ o ~ o ~ o ~ o ~ o ~ o ~ o ~ o Julius Paul Ikanza Systems Administrator New Vision Printing & Publishing Company email: pikanza(a)newvision.co.ug -- 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

Very Slow Network-I need some help!
by Paul Ikanza 27 Aug '04

27 Aug '04

Hi Everyone, im running suse firewall on CD for my squid. It works in such a way that when the server boots, it actually boots from the cd-rom drive and picks some files from a floppy diskette (Which can be edited to suit one's need). It is therefore really secure in that a hacker would not write onto the CD-they can only go as far as maybe viewing the contents. I am however experiencing really slow network speeds as in really slow! I need ideas on how I can possibly troubleshoot that problem and if any one is actually using this procedure for a firewall, bring me upto speeed on it. Paul. o ~ o ~ o ~ o ~ o ~ o ~ o ~ o ~ o ~ o ~ o Julius Paul Ikanza Systems Administrator New Vision Printing & Publishing Company email: pikanza(a)newvision.co.ug

3 2

RE: [suse-security] Problem with SuSEfirewall2 on SuSE 9.0
by Laat-de, Geert-Jan 27 Aug '04

27 Aug '04

Ludwig, Thank you very much for your help, that solution worked like hell. Best regards, Geert-Jan > -----Original Message----- > From: Ludwig Nussel [mailto:ludwig.nussel@suse.de] > Sent: woensdag 25 augustus 2004 17:01 > To: suse-security(a)suse.com > Subject: Re: [suse-security] Problem with SuSEfirewall2 on SuSE 9.0 > > > Laat-de, Geert-Jan wrote: > > I've got a question with respect to SuSEfirewall2 on SuSE > 9.0. I'm upgrading > > my system coming from SuSE 6.3, on which I used the > SuSEfirewall package. > > Within the FW_MASQ_NETS I used to enter individual IP > addresses of local > > machines, e.g. FW_MASQ_NETS="192.168.0.13 192.168.0.15". > > > > When I use the same FW_MASQ_NETS in SuSEfirewall2 I get an > error message > > "Integer expression expected.". Is it at all possible to > use individual IP > > addresses ? And if so, How ? > > The error message is a bug. Just append /32 to each IP to make it > work. > > > This e-mail is for the intended recipient only. > > If you have received it by mistake please let us know by > reply and then > > delete it from your system; access, disclosure, copying, > distribution or > > reliance on any of it by anyone else is prohibited. > > If you as intended recipient have received this e-mail > incorrectly, please > > notify the sender (via e-mail) immediately. > > use gpg. > > cu > Ludwig > > -- > (o_ Ludwig Nussel > //\ SUSE LINUX AG, Development > V_/_ http://www.suse.de/ > > -- > 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 > This e-mail is for the intended recipient only. If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.

1 0

Old worm
by b＠rry.co.za 26 Aug '04

26 Aug '04

One of my servers is picking up huge volumes of requests for http://www.instituto.com.br/attackDoS.php?ver=01&task=newzad&first=1 This is a worm infection that somehow eluded the various anti virus solutions these people are running. It is hammering my squid proxy, even though the current zone for the domain points www.instituto.com.br to 127.0.0.1 I have created an explicit deny for the url, but the cache still has to deny the requests, so huge load on the cpu right now. The customers sysadmin is away and I cannot get there until probably tuesday (usually I only support the Linux servers), is there a way to block this with a reduced load so that the rest of my system can operate normally? P.S. I have no idea where this came from as the users are not permitted to download executables, scripts etc, and we have a comercial antivirus product that has successfully updated its pattern file every hour for the last 8 months. This also plugs into squid, so denying mime types via squid reduces the load but the anti-virus still checks things that go through (including activex and other scripts) -- After your lover has gone you will still have PEANUT BUTTER!

2 1

Re: [suse-security] Whining... (Was Bad Quali....)
by Michael Sim 26 Aug '04

26 Aug '04

Dear Barry, One cannot agree with you more, forcing staff to use gross language in order to please iTGeeks is beyond my comprehension. Mistakes are the ransom of success, on top of which I doubt very much that OpenSource soft if I'm not mistaken, as opposed to proprietary soft, has the same development budgets as BGs of this world have to throw at their softs. Give these guys a break & don't let them resort to gross language to satisfy iTGeeks' ego, it's bad for the corporate image. Regards Michael Sim SLI - MIS Central Team Phone: (32 0) 16 800 369 Fax: (32 0) 16 800 398 The information contained in this email is private and is solely for the use of the intended recipient(s). If you are not the intended recipient you have no entitlement to use the contents of this email. Views expressed in this email do not necessarily reflect SLi policies, does not guarantee that any attachments are free from viruses or other defects and accepts no liability for any losses resulting from infected email transmissions. Further information on SLi, services and products can be found at www.sylvania-lighting.com -----"b(a)rry.co.za" <b(a)rry.co.za> wrote: ----- To: suse-security(a)suse.com From: "b(a)rry.co.za" <b(a)rry.co.za> Date: 26/08/2004 11:59 Subject: [suse-security] Whining... (Was Bad Quali....) The thing I don't get. The majority of people on this list have installed free software (I would love to see the amount of SuSE systems out there as a percentage of the amount SOLD by SuSE). While this is in the Open Source community no excuse for bad quality control, the overall service received from SuSE in unofficial support over the past 5 years has been nothing short of brilliant. A mistake has happened, been recognised, and guaranteed will be analysed to try and prevent the same mistake from happening again. Most kids fall off their bucycle at some point. They learn at that point that turning in the sand at high speed is a bad idea and don't do it again (unless the truck they are trying to avoid takes their eyes off the road for a moment). So all in all, SuSE keep it up, everyone else, shut up, I am getting to see this thread as SPAM in my security mailbox and am sure that while I am only adding to the problem now, hopefully you will all grow up and spend more time fixing your problems than whining because someone else isn't. -- Q: How many lawyers does it take to change a light bulb? A: You won't find a lawyer who can change a light bulb. Now, if you're looking for a lawyer to screw a light bulb... -- 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

Bad quality of updates from SuSE ftp server
by Hubertus Haniel 26 Aug '04

26 Aug '04

On the FTP server is a mkinitrd-1.0-219.i586.rpm which actually contains mkinitrd-1.0-221 so to fix the nice graphical boot screen which was broken with mkinitrd-1.0-219 one has to remove the currently installed mkinitrd-1.0-219 and install it again from the FTP server to perform the update. Yesterday Yast tried to do the right thing as instructed by patches/mkinitrd-51598 but failed as it was looking for mkinitrd-1.0-221.i586.rpm which did not exist. Today this patch was marked as obsolete. The spamassassin update published today for 8.2 contains only spamassassin but no update for perl-spamassassin so I had to rebuild the source rpm to get both. I don't know about everybody else but I personally find the standard of SuSE updates has dropped since Novell have got the fingers in the pie. Best regards Hubba

18 31

Re: [suse-security] Bad quality of updates from SuSE ftp server
by Bill.Light＠kp.org 25 Aug '04

25 Aug '04

So back to the unanswered emails... Was any solution ever given, for someone that updated via YAST2, to get their machine to boot again after the wonderful kernel update ? "We F***ed up" is fine to say, but now...how do I get it working again, or does the old (without the required security) kernel need to be re-installed and the update lists ignored ? After the kernel update a pretty vanilla 9.1, adaptec 29160, 18G IBM disk, with a 1GHz Athlon won't even see the scsi disk! If I re-install from scratch it works, so I know the hardware is working. What gives ? - Bill

1 0

Re: [suse-security] Problem with SuSEfirewall2 on SuSE 9.0
by Armin Schoech 25 Aug '04

25 Aug '04

Hi ! > I've got a question with respect to SuSEfirewall2 on SuSE 9.0. I'm > upgrading my system coming from SuSE 6.3, on which I used the > SuSEfirewall package. Within the FW_MASQ_NETS I used to enter > individual IP addresses of local machines, e.g. > FW_MASQ_NETS=3D"192.168.0.13 192.168.0.15". > > When I use the same FW_MASQ_NETS in SuSEfirewall2 I get an error > message "Integer expression expected.". Is it at all possible to use > individual IP addresses ? And if so, How ? > --> I guess you should make them into small nets like this or: FW_MASQ_NETS="192.168.0.13/32 192.168.0.15/32". FW_MASQ_NETS="192.168.0.13/255.255.255.255 192.168.0.15/255.255.255.255". HTH, Armin -- Am Hasenberg 26 office: Institut fuer Atmosphaerenphysik D-18209 Bad Doberan Schloss-Strasse 6 Tel. ++49-(0)38203/42137 D-18225 Kuehlungsborn / GERMANY Email: schoech(a)iap-kborn.de Tel. +49-(0)38293-68-102 WWW: http://armins.cjb.net/ Fax. +49-(0)38293-68-50

1 0

Problem with SuSEfirewall2 on SuSE 9.0
by Laat-de, Geert-Jan 25 Aug '04

25 Aug '04

Hi, I've got a question with respect to SuSEfirewall2 on SuSE 9.0. I'm upgrading my system coming from SuSE 6.3, on which I used the SuSEfirewall package. Within the FW_MASQ_NETS I used to enter individual IP addresses of local machines, e.g. FW_MASQ_NETS="192.168.0.13 192.168.0.15". When I use the same FW_MASQ_NETS in SuSEfirewall2 I get an error message "Integer expression expected.". Is it at all possible to use individual IP addresses ? And if so, How ? I would like to use individual addresses as in this way I can fully control who gets internet access, and who doesn't. Best regards, Geert-Jan This e-mail is for the intended recipient only. If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.

2 1

RE: [suse-security] Bad quality of updates from SuSE ftp server
by Ness, Todd 25 Aug '04

25 Aug '04

Nice, might be a bit harsh, but, it is definitely to the point and concise. Try to have a good day. -----Original Message----- From: Marcus Meissner [mailto:meissner@suse.de] Sent: Wednesday, August 25, 2004 8:50 AM To: suse(a)rio.vg Cc: suse-security(a)suse.com Subject: Re: [suse-security] Bad quality of updates from SuSE ftp server On Wed, Aug 25, 2004 at 10:45:25AM -0400, suse(a)rio.vg wrote: > Quoting Marcus Meissner <meissner(a)suse.de>: > > > > We are sorry for any inconvience caused. We try to have the best quality > > for security updates, but unfortunately due to sheer mass of updates > > sometimes mistakes slip through our Quality Assurance. > > > > We have been and will be constantly improving our processes to avoid such > > mistakes in the future and are committed to provide the best service > > possible. > > > > Now I'm *REALLY* annoyed. This is suse-security, not your press release forum. > This sort of market-speak drivel only makes you look incompetent. Save the > "constantly improving our processes" and "commited to provide the best service" > for the suits. > > We're sysadmins here. We want results. If you want us to cut you some slack, > give us real information. Most of us are really laid back people. Talk to us > like professionals and we'll give you every chance. Just don't give us > marketing drivel. Ok, translated I want to say: "Yes, we fucked up. We try harder not to fuck up in the future." :) is this satisfyingly techy enough ? :) Fixed spamassassin updates are going out as I am writing this mail. Ciao, Marcus

1 0

Re: [suse-security] Don't install the spamassasin update!
by Michael Sim 25 Aug '04

25 Aug '04

Hi guys, What's the pb with SpamAssassin Regards Michael Sim SLI - MIS Central Team Phone: (32 0) 16 800 369 Fax: (32 0) 16 800 398 The information contained in this email is private and is solely for the use of the intended recipient(s). If you are not the intended recipient you have no entitlement to use the contents of this email. Views expressed in this email do not necessarily reflect SLi policies, does not guarantee that any attachments are free from viruses or other defects and accepts no liability for any losses resulting from infected email transmissions. Further information on SLi, services and products can be found at www.sylvania-lighting.com -----Marcus Meissner <meissner(a)suse.de> wrote: ----- To: list(a)nolog.org From: Marcus Meissner <meissner(a)suse.de> Date: 25/08/2004 10:57 cc: suse-security(a)suse.com Subject: Re: [suse-security] Don't install the spamassasin update! On Wed, Aug 25, 2004 at 10:50:24AM +0200, list(a)nolog.org wrote: > Hi, > > Marcus Meissner wrote: > >Wir arbeiten an diesem Problem und haben die Updates auf den Servern > >bis dahin deaktiviert. > > > >Ein neues Update wird heute im Laufe des Tages erscheinen. > > > >Ciao, Marcus > > since Marcus Meissner doesn't know or care that this is a list > where english is the common language, here my quick'n'dirty > translation: > > We're working on it and have deactivated the updates on the servers. > A new update will be released today. > > GTi > P.S.: Hey, don't you have a QA at SuSE? Are there some jobs you want to > offer? ;) I apologize. We are investigating why QA failed in this case. Ciao, Marcus

1 0

Don't install the spamassasin update!
by Markus Gaugusch 25 Aug '04

25 Aug '04

I ran fou4s and YOU (as extra-check to verify correctnes of fou4s) on several machines today and installed the spamassassin-update. Unfortunately, its companion perl-spamassassin is not updated! This will break spamassassin and it cannot startup any more. I urge everyone to postpone this update. Tested: * SuSE 8.1 (I had a self-prepared perl-spamassassin-2.64 there, which worked. I'm sure though, that the original 2.55 would not work) * SuSE 8.2 (error!) * SuSE 9.0 (error!) Markus Gaugusch

4 4

SUSE Security Announcement: qt3 (SUSE-SA:2004:027)
by Thomas Biege 19 Aug '04

19 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: qt3/qt3-non-mt/qt3-32bit/qt3-static Announcement-ID: SUSE-SA:2004:027 Date: Thursday, Aug 19th 2004 15:00 MEST Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Database Server, SUSE eMail Server III, 3.1 SUSE Linux Enterprise Server 8, 9 SUSE Linux Firewall on CD/Admin host SUSE Linux Connectivity Server SUSE Linux Office Server Vulnerability Type: remote system compromise Severity (1-10): 7 SUSE default package: yes Cross References: CAN-2004-0691 CAN-2004-0692 CAN-2004-0693 Content of this advisory: 1) security vulnerability resolved: - buffer overflow in image handling code problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - opera - acroread 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion The QT-library is an environment for GUI-programming and is used in various well-known projects, like KDE. Chris Evans found a heap overflow in the BMP image format parser (CAN-2004-0691) which can probably be abused by remote attackers to execute arbitrary code with the privileges of the user using a malformed image as input for a vulnerable QT-based application. Additionally a NULL dereference in the GIF parser (CAN-2004-0693) was found. This lead to more research by other people and revealed another NULL dereference in the XPM parser (CAN-2004-0692) found by Marcus Meissner, SuSE Security-Team. The last two bugs can be used to trigger a remote denial-of-service attack against QT-based applications. 2) solution/workaround A temporary workaround for this issue is not known. 3) special instructions and notes After applying the update make sure all QT-based applications are restarted. It would be best to re-login if you use KDE. 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.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/qt3-3.3.1-36.16.i586.r… ee1026d5b6a4a554d95ce9d3626d6bf7 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/qt3-non-mt-3.3.1-41.14… ea6c27890eb69d47b54786a727cb782f ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/qt3-static-3.3.1-41.14… b965364531163627f34b9a66e6d0b07e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/qt3-3.3.1-36.16.i586.p… e698670506097dff0f9e61b594bcfeb9 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/qt3-non-mt-3.3.1-41.14… e64be5421ff6f1451c2b2dc926f8f081 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/qt3-static-3.3.1-41.14… b891c79e3a96538b69417e1aba6e85c4 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/qt3-3.3.1-36.16.src.rpm 7d3b4859cca3548004d4dc0e2cb431a8 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/qt3-non-mt-3.3.1-41.14.… 1ebff5e543d7d36cd13670189fe50443 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/qt3-static-3.3.1-41.14.… a14a20c83eedde899af40a88cf60a14a SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/qt3-3.2.1-68.i586.rpm 975f35315d69a283355a9734edb323b1 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/qt3-non-mt-3.2.1-70.i5… 2256aa7e05a0d6f3a055dc915c6823a9 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/qt3-static-3.2.1-70.i5… df61777b0ce9dc097c794bcf3d236981 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/qt3-3.2.1-68.i586.patc… 26cb661048adf99b3633d633347043a7 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/qt3-non-mt-3.2.1-70.i5… f36dcd428c96ff5126817d0dfb130816 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/qt3-static-3.2.1-70.i5… 2bb28c8adac1b2db9a5c024c66095254 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/qt3-3.2.1-68.src.rpm 79e218f9442f1d466d962c1a8c192f6d ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/qt3-non-mt-3.2.1-70.src… df6ad6d300013d65cce5907bc4db2cce ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/qt3-static-3.2.1-70.src… 55a6d43b4e9cb67e3cff9efa6948e28d SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/qt3-3.1.1-118.i586.rpm cdd76473d916801409c2076b5d8cb46a ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/qt3-non-mt-3.1.1-125.i… 2cd5ce43cd92a32ad398c951678bfdd4 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/qt3-static-3.1.1-124.i… ec1dd1ddd3386ff6928c6fd865efcf31 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/qt3-3.1.1-118.i586.pat… cc95b4f40c3cafb77ecedbd99c820cad ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/qt3-non-mt-3.1.1-125.i… a114f7060501d6b5eab88ed7b97f5da1 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/qt3-static-3.1.1-124.i… 7da86919fd126713bb45fc30c8689b0b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/qt3-3.1.1-118.src.rpm 843966bca098ac9c4e14f07c4cbdfc31 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/qt3-non-mt-3.1.1-125.sr… ce74982f20ab42826681e6839a6c8985 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/qt3-static-3.1.1-124.sr… 31125b894ab4554760941b92d74d7b24 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/qt3-3.0.5-167.i586.rpm c9d7dc3a5670751d223c64b7e9fb9268 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/qt3-non-mt-3.0.5-231.i… fbab1881ad8cbbb9631a61592a86c271 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/qt3-static-3.0.5-159.i… 0e4950eebe57d7fa9994320c74382049 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/qt3-3.0.5-167.i586.pat… 5925050be240253a7c084ce981c85bc7 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/qt3-non-mt-3.0.5-231.i… 62e78b9496aeb0d0840f6a13d7e59785 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/qt3-static-3.0.5-159.i… 456b459f8c2ca4faaa0fabe3b334e570 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/qt3-non-mt-3.0.5-231.no… 53c739863f94725f0f9fb5f0a1b9e4fd ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/qt3-static-3.0.5-159.no… fe6b13ab4a056648b75597f2727e25d7 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/qt3-3.3.1-36.16.x8… 3524b344918baf5355c7c2e0725db323 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/qt3-non-mt-3.3.1-4… 6b0e942470d01229251e574dd9d4f96d ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/qt3-static-3.3.1-4… e9d953b5d043b290b3b1cff662f86946 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/qt3-3.3.1-36.16.x8… d4ad80cb52efb2d135f398e209c52632 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/qt3-non-mt-3.3.1-4… b84ad3c425ba10a37faa9bbba6a060c7 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/qt3-static-3.3.1-4… d53a5b337037a74589b11da4729bfa14 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/qt3-3.3.1-36.16.src.r… 68a890f08853c1cdc08788a9241d0cbf ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/qt3-non-mt-3.3.1-41.1… 937ee28b2e943d0c8dc0ffe618afb5b1 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/qt3-static-3.3.1-41.1… 95b1ba6fe5ef947376570de538578081 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/qt3-3.2.1-68.x86_6… b2110cb13ee350d616f6558fa719089e ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/qt3-non-mt-3.2.1-7… 2e43ea64c00a319d734dcba439a8b08e ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/qt3-static-3.2.1-7… 1856dbb6ac0a1936766f45bf4de4d1c3 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/qt3-3.2.1-68.x86_6… e358d84c5b3cb6633cc932d25f4ab7bf ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/qt3-non-mt-3.2.1-7… 6d7f993e6148b60eaa40dadc5c2b9919 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/qt3-static-3.2.1-7… 0717ffc7d31766e3cba63b5af84b338a source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/qt3-3.2.1-68.src.rpm 5091d4b48d52dae0efc4c50e1dffad19 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/qt3-non-mt-3.2.1-70.s… 24524c12c4315715a925e2d4dee12235 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/qt3-static-3.2.1-70.s… c0987ba79b084d5782441890a2a0dacf ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - opera The web-browser opera is affected by several security bugs. Due to the nature of this package we are not able to provide security updates in a timely manner and have to wait for binary packages to be published by "Opera Software". - acroread iDEFENSE reported a buffer overflow and insecure handling of shell meta-chars in acroread code. We depend on the release of a new binary package by Adobe. An update will be available as soon as possible. ______________________________________________________________________________ 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 (GNU/Linux) iQEVAwUBQSS29Xey5gA9JdPZAQFZAgf+KI1R99QGlkHl+CwMRMImn1KDhHAr2k/x T9ZYnk7uZv//DNhoRCnfD9J9hAaiUvHh8S2CHc+ET9o4MQkrSrM+kACus6RKF2t+ ffFZIjCG0xzdRGgvmIyLS+h3BPijMERtszg3tJrzbLAcd1NQjQb27ACjr8n+faQl L/V1cOFrpd6lJMW0lg8WvHcxe9wwHk9h+HqltHIGCSqIGFZD0Icjw4DqAT1aNoiG kswfOuumzm11I6op8oK5F7snQyb8AnEgrtK62yt2eB3hTgnUs/E5wNv5+xoMRuyI MNYVKSEQKft3gn8P6hyi9IwLyCZW9WAkyMmplwbosDWf+6vwMpij1Q== =Ik0W -----END PGP SIGNATURE-----

1 0

OT: ip_wccp.c
by Mark Tinka 19 Aug '04

19 Aug '04

hi all.. sorry for the slight OT, but i was wondering whether there are any security related issues with compiling and loading the ip_wccp.o module into the 2.6.5 kernel... also, i've been doing tests with this module, using the 2.6.5 kernel-source to build it.. loading doesn't yield any significant errors (except to say it isn't running under GPL), but it still won't work... and lastly, is there any chance that a precompiled ip_wccp.o module will be available in any upcoming kernel releases from SuSE?... again, sorry for the OT.. Mark. __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail

1 0

chkrootkit vs. 9.1 professional?
by Maxim A Belushkin 18 Aug '04

18 Aug '04

Yesterday I decided to run chkrootkit, and apart from the "top" and "find" commands being reported infected (which is ok afaik, everyone seems to have the same on any fresh installation), I realised the following was also reported: A) 5 "nscd" processes were hidden from the readdir and ps commands B) 1 suseplugger process was hidden from the readdir and ps commands Ok, I moved those files into a safe place for now, rebooted - and everything went fine until... I ran Yast2! y2base is reported hidden from the readdir and ps commands... Can someone advise me on this? Thanks! - Max -

9 9

John "the Ripper" Broken? SuSE 9.1
by Ann Hopkins 18 Aug '04

18 Aug '04

I think when SuSE fixed the version of "John" the password cracker, run by security-weekly and security-monthly, they broke "John." I checked manually, with a single word password list I know it broke before the patch, and now it passes. It also doesn't seem to use the /var/lib/john/john.log file to save every 600 seconds as stated in the /var/lib/john/john.ini file anymore. "John" does run, but it doesn't seem to come up with a result; it did before the patch. Has anyone else noticed this problem?

2 1

Firewall @ application level
by Christian (aka Neodaxus) 18 Aug '04

18 Aug '04

Hello, I'm looking for a free firewall at the application level for use with SuSE Linux. Maybe a firewall which also asks if a connection doesn't match the rules (like ZoneAlarm). Thanks, Christian

2 1

Susefirewall2 on 9.1 and emule
by John Lederer 17 Aug '04

17 Aug '04

I am afraid I am floundering with what should be a simple problem. I have a 9.1 box that operates as a firewall/router for a home network. Some of the workstaions are Windows XP. One of the windows XP staions wants to use emule. I have tried with and without masquerading, a midified /sbin/Susefirewall2 script, and an add on custom script. I have , in fact, gotten myself thorughly confused and tangled. Does anyone have an /etc/sysconfig/Susefirewall2 parameter script that works with emule that they would share? Many thanks, John Lederer ============================ Emule firewall requirments 1) /Local Port:/ 4662 /Remote Port:/ any /Protocol:/ TCP /Direction:/ incoming /Purpose:/ Client Port / Connections from other clients, Client to Client Source Exchange /Note:/ You can change this port in /Preferences -> Connection ->/ /Client Port/ This port has to be forwarded in a router. Changing this port in Preferences you must also change the forwarding in the router 2) /Local Port:/ any /Remote Port:/ 4662 /Protocol:/ TCP /Direction:/ outgoing /Purpose:/ Client Port / Connections to other clients, Client to Client Source Exchange /Note:/ 4662 is the default port, but other clients may have different settings. Change the /remote port/ to /any/ when configuring a firewall 3) /Local Port:/ 4672 /Remote Port:/ any /Protocol:/ UDP /Direction:/ incoming /Purpose:/ Clients source asking / extended eMule protocol, Queue Rating, File Reask Ping /Note:/ This port has to be forwarded in a router. Changing this port in Preferences you must also change the forwarding in the router. If you are not able to forward this port check the /disable/ box in /Preferences -> Connection -> UDP Port/ 4) /Local Port:/ any /Remote Port:/ 4672 /Protocol:/ UDP /Direction:/ outgoing /Purpose:/ Clients source asking / extended eMule protocol, Queue Rating, File Reask Ping /Note:/ 4672 is the default port, but other clients may have different settings. Change the /remote port/ to /any/ when configuring a firewall 5) /Local Port:/ any /Remote Port:/ 4661 /Protocol:/ TCP /Direction:/ outgoing /Purpose:/ Connection to server /Note:/ 4661 is the default port of a server. Many server use different ports. Configuring a firewall the /remote port/ again changes to /any/. 6) /Local Port:/ any /Remote Port:/ 4665 /Protocol:/ UDP /Direction:/ outgoing /Purpose:/ Source asking on servers /Note:/ Servers using the default port 4661 TCP (see #5) automatically set their port for source asking to 4665 UDP. If a server uses a different port in #5 the corresponding UDP port is set to [Connection Port + 4]. For firewalls the /remote port /here is /any./ 7) /Local Port:/ 4711 /Remote Port:/ any /Protocol:/ TCP /Direction:/ incoming /Purpose:/ Webserver /Note:/ This is the default port for the web interface. When using a router this port has to be forwarded or no connection to the webserver will be possible.

2 1

SUSE Security Announcement: rsync (SUSE-SA:2004:026)
by Thomas Biege 16 Aug '04

16 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: rsync Announcement-ID: SUSE-SA:2004:026 Date: Monday, Aug 16th 2004 16:00 MEST Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Database Server, SUSE eMail Server III, 3.1 SUSE Linux Enterprise Server 8, 9 SUSE Linux Firewall on CD/Admin host SUSE Linux Connectivity Server SUSE Linux Office Server Vulnerability Type: remote system compromise Severity (1-10): 2 SUSE default package: no Cross References: http://samba.org/rsync/#security_aug04 Content of this advisory: 1) security vulnerability resolved: - insufficient pathname sanitizing problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - KDE - mozilla/firefox - xine-lib - opera - acroread 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion The rsync-team released an advisory about a security problem in rsync. If rsync is running in daemon-mode and without a chroot environment it is possible for a remote attacker to trick rsyncd into creating an absolute pathname while sanitizing it. As a result it is possible to read/write from/to files outside the rsync directory. SUSE LINUX ships the rsync daemon with a chroot environment enabled by default, therefore the default setup is not vulnerable. 2) solution/workaround As a temporary workaround we suggest to keep the chroot-option of rsyncd enabled or to avoid the daemon-mode and use SSH as transport channel if possible. 3) special instructions and notes After applying the update, all instances of the rsyncd should be closed and the rsync daemon should be restarted. Please execute the following command as root: 'rcrsyncd 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. x86 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/rsync-2.6.2-8.9.i586.r… afa5b8894e2d1acff4b040e8ba515ae4 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/rsync-2.6.2-8.9.i586.p… c0bf6dcf573a9a4197da0977ea638f2a source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/rsync-2.6.2-8.9.src.rpm f31f409225560bd1ac1d5fb5f0d8c43e SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/rsync-2.6.2-26.i586.rpm 5d7be9a510a4a5fafccbc29c63b0dec8 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/rsync-2.6.2-26.i586.pa… 70809462c5d88bc8241b544100689efe source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/rsync-2.6.2-26.src.rpm f92d91816456f0e626ea1ee41ebe8b65 SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/rsync-2.6.2-26.i586.rpm 4f901dee110596bf2a48a24d8d094b71 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/rsync-2.6.2-26.i586.pa… c7260721ec51a569309cd4629a3a5ad1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/rsync-2.6.2-26.src.rpm fcd540a8e89c864b56cbad7d60696450 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/rsync-2.6.2-25.i586.rpm 193752687ef1d98a5ebec4ff471842b1 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/rsync-2.6.2-25.i586.pa… 9b6225e3bd2ff624f5f61bd6b033e8b8 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/rsync-2.6.2-25.src.rpm 0f649de8547008aa5e2a977ff209fca3 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/rsync-2.6.2-8.9.x8… 745a09fdbccc7ccfea9705f54a6825a3 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/rsync-2.6.2-8.9.x8… 725b10d1703f6ee41185564d08b151d3 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/rsync-2.6.2-8.9.src.r… 6145ed8346ebfd63863734b30fc3a8e9 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/rsync-2.6.2-26.x86… 20d3b3f8b3fde71ae1c3f0eed22feee0 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/rsync-2.6.2-26.x86… 9bc24b61361c74f37e4fd81e8e7faa98 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/rsync-2.6.2-26.src.rpm 599e9f0a19fd2890499c863cd0394598 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - KDE The KDE libs package contained two occurrences of insecure handling of temporary files in the mcoputils code (Thanks to Andrew Tuitt for reporting this to us) and in the dcopserver code. These two bugs can be exploited locally to remove and/or overwrite files with the privileges of the user running a vulnerable KDE application. A bug in the kdebase3 package allows the content of unrelated browser windows to be modified. This issue may be used to trick users into entering sensitive informations on a malicious web-site. New packages are available on our FTP servers. - mozilla/firefox We are currently testing new mozilla/firefox packages that include several fixes for security-related bugs. New packages are available on our FTP servers (for some products we have to delay the delivery of the update package). - xine-lib This update of xine fix' a buffer overflow in the vcd input source identifier. This buffer overflow is independent of the media format. The bug can be used to execute arbitrary commands. New packages are available on our FTP servers. - opera The web-browser opera is affected by several security bugs. Due to the nature of this package we are not able to provide security updates in a timely manner and have to wait for binary packages to be published by "Opera Software". - acroread iDEFENSE reported a buffer overflow and insecure handling of shell meta-chars in acroread code. We depend on the release of a new binary package by Adobe. An update will be available as soon as possible. ______________________________________________________________________________ 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 (GNU/Linux) iQEVAwUBQSDIVXey5gA9JdPZAQECNQf/VieGW0TuUNSEs10A/K2kPDJGzUpOPEs7 KzH0FGH0zT1+Ng9rV8nsez59+OOW0Wlff5BrxKEkz/yNhecNfcoGmg6wmyNPbvBC 4paP85Ft5vNHcy8uipVvOGCqutduNXeZzmYiQXASI9khyylDwwuc8WYYodsBPIbu qKcIm8odxLkRQuyWnTMyOp+JMXYKiLuWjnODHAMIKfsKgDvgzfPdY5Tks8P3bsgd kpNC4DT/dd8q0a0KyGse93tS79l3LeMzdiuFgCe/pC0HNU5In/hgWnGmJ7tonzeT 2mHfL2m7TAEjpfZZpbLD2PTMCQRRybj2tGmAVlSg7XW+kTc9Ff/wRg== =GgJC -----END PGP SIGNATURE-----

1 0

SSH login password guesses
by Sven 'Darkman' Michels 16 Aug '04

16 Aug '04

Hi there, we already had a small thread about this topic but only for some log entries and not the problem itself ;) As we probably all noticed there're a bunch of ssh connects every day which try to login as root, test, user, admin, guest and maybe others. Now i saw a scan with more then 5000 attempts to login to serval servers. I read a lot about this topic now but noone really knows whats going on. So i try to sum up the information i got, maybe you know a littlebit more than i or just have the same "problem" and want to know more about it ;) First of all, it seems that there multiple tools or scripts out trying these logins. The simplest one only try root:root and guest:guest as login. Later on a few more usernames where added: guest, test, user, admin (and maybe others). After that someone seems to add some dictionary support to the tools. Now it tries many passwords for the root user (no pass guesses for the other ones so far). If some box has such a weak/guessable password, some of the "crackers" installed stuff like rootkits (e.g. suckit) or DDoS flood scripts/IRC Bots and other "bad" stuff. Today we found such a server in our network. The password wasn't changed by the customer so it was guessable. But unlike other reports no rootkit etc. was installed. All we found was some "uname -r" that was done. Maybe because of a very recent kernel and some other stuff they didn't like this box very much. A few analyses had been done yet: http://dev.gentoo.org/~krispykringle/sshnotes.txt http://lists.netsys.com/pipermail/full-disclosure/2004-August/025330.html http://isc.sans.org/diary.php?date=2004-07-28 and many other postings on the well known lists like dev-shed, full-disclosure, bugtraq etc. Most of the attackers seem not to be very skilled like you'll see in some postings: they leaved bash_history files and did other stuff you'll notice if you take a closer look to your box. For ppl who want to protect themselves against such attacks: - disable rootlogin (PermitRootLogin no in sshd_config) - use secure passwords - maybe just use ssh keys - don't use guessable accounts - put sshd on a different port then 22 (will only help for such "normal" scans, not if someone want to break *your* box.) - use features like hosts.allow/deny or iptables to allow ssh just for a couple of hosts (maybe isn't useable for ppl with nonstatic ips, but you still can limit ssh access to your isp, or use a vpn ;) Hope i didn't forget anything. If someone knows more about this topic, please let us know ;) Regards, Sven

2 1

Latest kernel still hangs?
by suse＠tremor.com 16 Aug '04

16 Aug '04

I really don't have the ability to test the latest kernel on my servers due to location, but the last update prior to the latest one (2.6.5-95 I believe) caused my servers to hang on boot, mainly after try to access the transaction logs on my filesystems. Has anyone tried the latest kernel update on a system that hung before? For noting, my servers are newer DL320 G2 series, with the latest BIOS, with ReiserFS as the filesystem.

4 5

Samba Updates SuSe 9.1 Professional
by dannowwillis＠att.net 16 Aug '04

16 Aug '04

The June Samba update (going from 3.02 to 3.04) for SuSe Professional 9.1 brought my Samba server to its knees. I had to revert back to 3.02. Has anyone running a Samba server as a member server of an NT 4 domain successfully applied the latest patches to Samba 3.05? I like to be current on patches, but once bitten, twice shy... Thanks, Dan Willis

1 0

nmap broken again in 9.1 ?
by David Uvalle 16 Aug '04

16 Aug '04

Hi Im trying to run nmap as root to use some features i need but it doesnt scan anything, as user it scan normally am on suse 9.1, with kernel 2.6.5-7.104-default have all the patches from Yast/Online Update until today, maybe the last kernel upgrade broke something i dont know Thanks for your help guys -- */*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* David Uvalle Zepeda Chief Security Officer. Radikal Systems S.A de C.V. http://www.radikalsystems.com

7 13

Re: [suse-security] So, is Suse working on a fix for the mysqld problem?
by Hans-Peter Winkler 15 Aug '04

15 Aug '04

Hello, > > If so, will you bring out a new 8.0 kernel as well, even if 8.0 has > > reached its EOL? > > > The latter. There are some few packages in the queue for 8.0, but they > are just waiting for their publication date and have been ready for > quite some time... > It should be possible, however, to run an 8.1 kernel on an 8.0 system - > and the 8.1 kernel is an extremely reliable one. I haven't seen a crash > so far. has anyone tried the 8.1 kernel update on an 8.0 system yet? I am too affected by the bug in the kernel. Or is there any specific date for the "some few packages in the queue for 8.0" to be released (including an updated kernel)? Rgds hpwi -- NEU: WLAN-Router f�r 0,- EUR* - auch f�r DSL-Wechsler! GMX DSL = superg�nstig & kabellos http://www.gmx.net/de/go/dsl

1 0

PROTO_IPSEC_ESP SA not found (maybe expired)
by mailinglists 14 Aug '04

14 Aug '04

Hi I've changed from redhat 9 SuperFreeSwan 1.99.8 to suse 9.1 FreeSwan 2.05. With a few changes done on ipsec.conf it all should have worked fine. I can start conns, the freeswan deamon negotiates all its SAs with the other sides. And I can ping the other sides. But I fail to get any other communication through any tunnel. I never have seen before the "PROTO_IPSEC_ESP SA(0x79b5f800) not found (maybe expired)" error message. As a matter of fact I recompiled the kernel with ESP, IPCOMP and IPIP compiled into the kernel not just added as modules. This dropped a number error messages at the initial Freeswan start-up. However it did not change the situation. Then I dropped the SuSE FreeSwan daemon and installed newest StrongSwan 2.1.5 release. No change. So problem probably not deriving from FreeSwan. I can ping, the rtt is normal. But I don't get neither UDP nor TCP nor traceroute through any tunnel. Does anybody know a work around (please don't say change distro). Philipp

1 0

Static NAT w/ iptables problem
by Markus Trümper 13 Aug '04

13 Aug '04

Hello, I'm trying to set up a firewall to do static NAT between two networks: internal network 192.168.1.0/24 server 192.168.1.3 | LAN_IF 192.168.1.7 Firewall EXT_IF 10.80.137.1, 10.80.137.10 | DMZ 10.80.137.0/24 'server' should be reachable from the DMZ by talking to 10.80.137.1. That address has no other purpose. My rules so far don't work. I can not reach 'server' by talking to x.x.x.1 on the external IF of the Firewall. Any idea why? ------------------------------------------------ ifconfig eth1 add 10.80.137.1 echo "Clearing current rules ..." iptables -F iptables -X iptables -t nat -F iptables -t nat -X iptables -t mangle -F iptables -t mangle -X # LAN: 192.168.1.0/24 LAN_IF=eth0 # EXT: 10.80.137.0/24 EXT_IF=eth1 # 'server': EXT_DS=10.80.137.1 DS=192.168.1.195 IPTABLES=/sbin/iptables # (Connections originating from the DMZ) $IPTABLES -t nat -A PREROUTING -d $EXT_DS -i $EXT_IF -j DNAT --to-destination $DS $IPTABLES -A FORWARD -p all -i $EXT_IF -o $LAN_IF -d $DS -m state --state NEW -j ACCEPT $IPTABLES -A FORWARD -t filter -i $EXT_IF -m state --state ESTABLISHED,RELATED -j ACCEPT # (Connections originating from internal) $IPTABLES -t nat -A POSTROUTING -s $EXT_DS -o $EXT_IF -j SNAT --to-source $DS $IPTABLES -A FORWARD -t filter -i $LAN_IF -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT ------------------------------------------------ Thanks in advance Markus --------------------------------------------------------------------------------- | Dipl. Inform. Markus Trümper | | | | Daewoo Automobile Deutschland GmbH | | email: m.truemper(a)daewoo-automobile.de | Lindenstraße 110 | | www: http://www.daewoo-automobile.de | 28755 Bremen | | Telefon: +49 (0)421 668-4138 | Germany | | Fax: +49 (0)421 668-4192 | | ---------------------------------------------------------------------------------

1 0

Re: [suse-security] So, is Suse working on a fix for the mysqld problem?
by Marcus Meissner 13 Aug '04

13 Aug '04

On Thu, Aug 12, 2004 at 04:31:38PM +0200, Kai Schaetzl wrote: > Marcus Meissner wrote on Thu, 12 Aug 2004 13:55:16 +0200: > > The 9.0 kernel we released yesterday does not contain the fix due to a small > > technical problem here. > That explains my observations. > > All others kernels did contain the bugfix. > I can confirm that. > > > We will try to push out the fixed 9.0 kernel as soon as possible. > > Will this be a new (241) kernel or still only a replacement for 238? A kernel with a newer release larger than 238 definitely. Most likely 243. Ciao, Marcus

2 3

So, is Suse working on a fix for the mysqld problem?
by Kai Schaetzl 12 Aug '04

12 Aug '04

Unfortunately, I didn't read that thread until now and updated all of our machines to kernel 2.4.21-238 yesterday and hit the mysql problem already discussed on the weekend. Since then the thread has been quiet. So, is Suse working on a fix for this? After all, mysqld processes maxing out is a *serious* problem, the systems are effectively DoSing themselves. I urge Suse to issue a new announcement that warns about this problem, so vendors are warned and can consider halting on the upgrade. What I know so far is: - it seems all 2.4.21-238 (no matter, if Athlon, Intel or smp) on all newer Suse systems (we have 8.1 and 9.0 at the moment) are affected (maybe only 32bit, we don't have any 64bit). All systems run with latest standard Suse programs. - each time a mysql connection is closed that mysqld process goes <defunct> and stays forever until killed with "killall -9 mysqld", it's sufficient to "mysql -pxxx" and just quit, so it is surely not a problem of corrupted databases or specific programs - mysql-max does *not* seem to be affected - I have one system (Suse 9.0) with normal mysqld which doesn't seem to be affected. I don't know why. But all other 9.0 systems are affected. 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

6 15

SUSE Security Announcement: gaim (SUSE-SA:2004:025)
by Thomas Biege 12 Aug '04

12 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: gaim Announcement-ID: SUSE-SA:2004:025 Date: Thursday, Aug 12th 2004 12:00 MEST Affected products: 9.1 Vulnerability Type: remote code execution Severity (1-10): 6 SUSE default package: No Cross References: CAN-2004-0500 Content of this advisory: 1) security vulnerability resolved: - buffer overflow in gaim problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - KDE - mozilla/firefox - ethereal - arts 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Gaim is an instant messaging client which supports a wide range of protocols. Sebastian Krahmer of the SuSE Security Team discovered various remotely exploitable buffer overflows in the MSN-protocol parsing functions during a code review of the MSN protocol handling code. Remote attackers can execute arbitrary code as the user running the gaim client. The vulnerable code exists in SUSE Linux 9.1 only. 2) solution/workaround There is no known workaround. 3) special instructions and notes Before applying the update, all instances of the gaim client should be closed. 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.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/gaim-0.75-79.2.i586.rpm 860321d82ba69b52420f20a79d85e1cf patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/gaim-0.75-79.2.i586.pa… 4f1fc5407a2edf9483103cf1e4c9667b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/gaim-0.75-79.2.src.rpm 3944443b7a6739d24737eca93cc48e98 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/gaim-0.75-79.2.x86… d6cf6e00d46bf3098f4b3a384e14b27f patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/gaim-0.75-79.2.x86… 35aa894e1a3f51fa4e210d0d01bfdd17 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/gaim-0.75-79.2.src.rpm 02e49732c72aec9d928a01491bca68fd ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - KDE The KDE libs package contained two occureneces of insecure handling of temporary files in the mcoputils code (Thanks to Andrew Tuitt for reporting this to us) and in the dcopserver code. These two bugs can be exploited locally to remove and/or overwrite files with the privileges of the user running a vulnerable KDE application. A bug in the kdebase3 package allows the content of unrelated browser windows to be modified. This issue may be used to trick users into entering sensitive informations on a malicious web-site. New packages will be available soon. - mozilla/firefox We are currently testing new mozilla/firefox packages that include several fixes for security-related bugs. New packages will be available soon. - ethereal It may be possible to make Ethereal crash or run arbitrary code by injecting a malformed packet or by convincing someone to read a malformed packet trace file. (CAN-2004-0633, CAN-2004-0634, CAN-2004-0635) New packages are available at our FTP servers. - arts This update removes an inconsistency in the comparsion of credentials while creating temporary files. This flaw can be exploited locally in conjunction with setuid Arts applications. (very unlikely) ______________________________________________________________________________ 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 (GNU/Linux) iQEVAwUBQRtg6Hey5gA9JdPZAQHLzQf/XkHTl/qHDMtyNluHXvyuVSJhqPWmZhEr FgkBtCtbmb4ni4vMpfWYhF6QSxARdRtDWT8ejhMcheswMgCQkOJCo95ecLOfXYLs V8aR/cyZMgQX0i9ph2ZZkuwcNDGBAGV6GBN3B6AcjL1db5xXPDeI1LLmqkQnWOdr FLptFIPwMsmmx40/W5ICg5xlO5GtQE94aW+zB1qLYdAHFs1mFM1o8GMHllbzZiqf wW/ZqJK2eFeg3Lq9H7s6ZHBtsMbEFPv+UNzCQexQviTiDBv98FvBDakdyORrTnaS 6JYfdLjeZqBmESdgVBeRvcgR+96TwTByaDkZK0lckOG7lHBaNbP5gw== =j6iP -----END PGP SIGNATURE-----

1 0

How to allow fragmented packets through SuSEfirewall2
by Simon Oliver 12 Aug '04

12 Aug '04

My goal here is to allow NFS/NIS traffic through the SuSE Firewall on a 9.1 system. > I did find a useful resource at > http://www.lowth.com/LinWiz/nfs_help.html > but it is a little out of date (SuSE 7.3). This recommends > tying down nfsd (and associated services) to specific ports > so that less holes need to be opened in the firewall. > > Tying down the ports seems quite messy according to the > guide, and I'm worried that an automatic update could > overwrite one of the altered files and cause something to > stop working. I decided to read through the sysconfig files and init.d scripts in order to work out the best way to open holes in the firewall for NFS and NIS. At this point I noticed that in 9.1 SuSE don't provide any mechanism to assign static ports to rpc services such as rpc.mountd. Instead they simply scan the ports (rpcinfo -p) to build a service-to-port mapping and dynamically add firewall rules for the ports associated with selected services (FW_SERVICES_EXT_RPC in /etc/sysconfig/SuSEfirewall2). This is not only a more elegant solution but also solves the problem where an rpc service has no mechanism for binding to a specific port. Well done SuSE! But I now have another problem, due to my lack of experience with configuring SuSEfirewall2... It is my understanding that as well as opening the appropriate rpc ports and port 111 in the firewall, it is also necessary to allow fragmented through. Under RHEL I do this by adding a rule to the start of the INPUT chain: iptables -I INPUT -f -j ACCEPT. However, I'm not how to accomplish this with SuSEfirewall2. I've looked through /etc/sysconfig/SuSEfirewall2 and can't see any easy was to allow fragmented packets through. I've scanned /sbin/SuSEfirewall2 and can't find any reference to fragmented packets there either. I guess I have to create a custom rule via the file specified by FW_CUSTOMRULES - but how to do that? So I have two questions: - If SuSE recognise the need to open up rpc ports for NFS why do they not provide the functionality to allow packet fragments through? - Can anyone help me solve this problem right now? Thanks -- Simon Oliver

2 2

completed automatic online updates
by Kurt R. Rahlfs 12 Aug '04

12 Aug '04

I am using the automatic yast online update. It's output shows an "I" before some of the updates. The "I" could be for the english work "install." Are these updates that have been applied to my system? Or is there further work for me to do? TIA, KurtRR -- Kurt R. Rahlfs affinity Computer Masters, LLC 721 South Mustang Road Yukon, OK 73099-6778 http://www.affinityCM.com 405.350.6984

2 1

Re: ArGoSoft Mailing List Server
by Roman Drahtmueller 12 Aug '04

12 Aug '04

On Thu, 12 Aug 2004 postmaster(a)elliscomp.com wrote: > From: postmaster(a)elliscomp.com > To: draht(a)suse.de > Date: Thu, 12 Aug 2004 04:06:41 +0200 (CEST) > Subject: ArGoSoft Mailing List Server > > Command > > > > > not understood. > > Please send mail to postmaster(a)elliscomp.com, containing word HELP as the first non-blank line for the list of available commands. > > ArGoSoft Mailing List Server > *zap* R.

1 0

sorry for this test
by Kurt R. Rahlfs 12 Aug '04

12 Aug '04

will it bouce now?

2 1

reiserfs strange behavior
by Uwe Debacher 12 Aug '04

12 Aug '04

Hi, I have a strange problem with reiserfs and SuSE 9.1. There seem to be pairs of filenames which are not different in the same directory. An example is nb3001/mm3001: /tmp> mkdir nb3001 /tmp> mkdir mm3001 mkdir: kann Verzeichnis „mm3001“ nicht anlegen: Die Datei existiert bereits /tmp> rm -r mm3001 > ls nb3001 /bin/ls: nb3001: Datei oder Verzeichnis nicht gefunden This problem exists on any reiserfs partition an any of my SuSE 9.1 systems. If I change to ext3 everything is OK. Even reiserfs on SuSE 9.0 ist OK. No matter whether you create files ore directories. ls always shows the created file, but rm, chown, ... may use both! Some other pairs are bb3001/am3001 gb3001/fm3001 mb4001/lm4001. Any hint where the problem or better the solution is? Best Uwe

8 13

Hardware dependency - Is SuSE working on it ...
by Bill.Light＠kp.org 11 Aug '04

11 Aug '04

I had to rebuild after the last kernel update - will this "new and improved" mysql fix kernel also be unavailable if you want the machine to ever re-boot again ? Is SuSE going to address the issues from the last "wonderful" experience ? ================= From Monday ================= EXT2 - AMD 1Ghz Athlon with 512Mb memory - just "ate it" with Kernel update. I decided to try "standard" YAST2 update and took the kernel selection, now it won't even find the disk (IBM 18G connected to Adaptec 29160) pretty vanilla if you ask me. Pretty "secure" kernel if it won't boot. There's nobody that's hacking this box now... Is there a way to get the security part of the update without the wonderful disk destruction ?

1 0

harden_suse
by tfulton9909＠comcast.net 11 Aug '04

11 Aug '04

Hello, What is that status of harden_suse in SLES 9 in light of Bastille being released? thanks

2 1

SELinux
by Jarosław Nozderko 10 Aug '04

10 Aug '04

Hi, what is the status/plans (if any) of SELinux integration in SUSE (both enterprise and standard) ? Thanks for any information, Jarek

1 0

Recent Sun Java Security Alert
by Oliver Schwabedissen 10 Aug '04

10 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Sun recently published a Java security alert (http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert/57613) The problem occurs in SDK and JRE from v1.4.0 up to 1.4.2_04. Will there be a fix from SuSE for the J2RE delivered with eg. SuSE 9.1 Pro (java2-jre-1.4.2-129) or will one have to install the JRE 1.4.2_05 or later from http://java.sun.com/j2se/ (which installs to a different location)? - -- Ciao, Oliver GPG Public Key available at http://www.keyserver.net Key fingerprint = CD75 B140 3EAB 859B A904 C4EC BE86 FAC5 8566 5CEF -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBGFXVvob6xYVmXO8RAtGcAJ44rzQi18rMpjeDU5DH/Uq5Bd7YWACbB9yf eOe0MDwSHybyl5OGkOntM8s= =a8M4 -----END PGP SIGNATURE-----

1 0

Re: [suse-security] Latest kernel still hangs?
by Bill.Light＠kp.org 09 Aug '04

09 Aug '04

EXT2 - AMD 1Ghz Athlon with 512Mb memory - just "ate it" with Kernel update. I decided to try "standard" YAST2 update and took the kernel selection, now it won't even find the disk (IBM 18G connected to Adaptec 29160) pretty vanilla if you ask me. Pretty "secure" kernel if it won't boot. There's nobody that's hacking this box now... Is there a way to get the security part of the update without the wonderful disk destruction ? ============================================== I have had this hang on two HP DL320 G2 servers. On one server, I actually reinstalled the system with ext3 and it still hung on boot, although at a different point. I can't quite recall when it happened with ext3. During the testing I had mounted the filesystem and unmounted as you stated and it didn't help, unfortunately. These machines are only about 6 months to 1 year old. > Hello guys, > that bug if it's bug appear onl;y when you have > someting in transaction jornal file to be replyed over > reiserfs filesystem, in that file are normally somting > when the system didn't reboot or shutdown clear. > Anyway I upgarded so many machines and only one hangs. > How to fix it. > Just boot from installation CD or LiveCD and mount the > filesystem, them unmout it and reboot the system and > everything works fine ;-) > > Best Regards > --- suse(a)tremor.com wrote: > >> I really don't have the ability to test the latest >> kernel on my servers >> due to location, but the last update prior to the >> latest one (2.6.5-95 I >> believe) caused my servers to hang on boot, mainly >> after try to access the >> transaction logs on my filesystems. >> >> Has anyone tried the latest kernel update on a >> system that hung before? >> >> For noting, my servers are newer DL320 G2 series, >> with the latest BIOS, >> with ReiserFS as the filesystem. >> >> --

1 0

SLES8, heimdal: "KDC policy rejects request"
by Helge Bahmann 09 Aug '04

09 Aug '04

Hello, after the latest security update for heimdal (heimdal-0.4e-401) on an SLES 8 server, pam_krb5 (and, for that matter, all gssapi-based services) stopped working throughouht the kerberos realm; reverting back to an older version of heimdal makes the problem go away Symptoms: - it is still possible to get tgt tickets (e.g. using kinit) - it *appears* to be not possible to get any service tickets at all relevant log generated from pam_krb5: Aug 9 13:19:13 f100 sshd[7120]: (pam_krb5) pam_krb5_verify_tgt: krb5_mk_req: KDC policy rejects request Aug 9 13:19:13 f100 sshd[7120]: (pam_krb5) pam_krb5_verify_tgt: Authentication failure The same message ("KDC policy rejects request") is logged in the kdc log; it is also logged for any attempt to use services via GSSAPI (e.g. LDAP) I found a posting on the web that seems related (bottom of the page): http://www.emsl.pnl.gov/ops/comphelp/ssh/faq.html It hints that this may have something to do with the "renewable" flag of host and service principals; can anyone explain to me what this means, why this change of behaviour in heimdal was necessary, and what I should do? I can find no mention of "renewable" in the heimdal docs, or how to configure it Best regards -- Helge Bahmann <hcb(a)chaoticmind.net> /| \__ The past: Smart users in front of dumb terminals /_|____\ _/\ | __) $ ./configure \\ \|__/__| checking whether build environment is sane... yes \\/___/ | checking for AIX... no (we already did this) |

1 0

SUSE Security Announcement: kernel (SUSE-SA:2004:024)
by Thomas Biege 09 Aug '04

09 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2004:024 Date: Monday, Aug 9th 2004 08:50 MEST Affected products: 8.0, 8.1, 8.2, 9.0, 9.1 SUSE Linux Database Server, SUSE eMail Server III, 3.1 SUSE Linux Enterprise Server 7, 8, 9 SUSE Linux Firewall on CD/Admin host SUSE Linux Connectivity Server SUSE Linux Office Server Vulnerability Type: local privilege escalation Severity (1-10): 6 SUSE default package: yes Cross References: CAN-2004-0415 Content of this advisory: 1) security vulnerability resolved: - race condition in file offset pointer handling problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - gaim - mozilla/firebird 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Paul Starzetz from iSEC informed us about a race condition in the 64bit file offset handling code of the kernel. The file offset pointer (f_pos) is changed during reading, writing, and seeking through a file to point to the current position in a file. The Linux kernel offers a 32bit and a 64bit API. Unfortunately the value conversion between this two APIs as well as the access to the f_pos pointer is defective. These bugs can be abused (mostly with entries in /proc) by a local attacker to gain access to uninitialized kernel memory which may contain sensitive information (root password and alike). Additionally a bug in the implementation of chown(2) for updating inode times, and a denial-of-service condition that can occur while handling signals was fixed. (Please note that the latter patch can cause problems by leaving zombie processes. We are working on a fix.) 2) solution/workaround The is no workaround known for this problem. Please install the update package for the kernel on your system. 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. Note: The update packages for the SuSE Linux Enterprise Server 7 (SLES7) are being tested at the moment and will be published as soon as possible. **** 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 chipsets 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.0/images/ 8.1/rpm/i586 8.2/rpm/i586 9.0/rpm/i586 9.1/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.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-bigsmp-2.6.5-7.… 7c85b0457972f99ea4ac84a4c14aa11d ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-default-2.6.5-7… 7eba8c73098e79b3e4e003c233d63d1e ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-syms-2.6.5-7.10… 2f0c3582356994a238460a1ddd11364b ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-smp-2.6.5-7.104… b8c993646b760d585391b0bae6e7473e ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-source-2.6.5-7.… 634d50a5b5aa4b2866536e66b18befeb source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-bigsmp-2.6.5-7.1… 0289c1840b5d5da713feb85c2b8f2fef ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-default-2.6.5-7.… ab48b1fb238850d2576b7836b700f34c ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-syms-2.6.5-7.104… e882ffca04f84c9c2d4a9d8bb7fbd46f ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-smp-2.6.5-7.104.… b673c013e8d3e59c1cad61e68ac5b2db ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-source-2.6.5-7.1… db2833d74a093e81cecab6a878cceeb8 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-238.i5… 32afadf0bc5720c3b6908e8d1930cf5a ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-238.i58… 2f0b04a5a541dc7e968e34cb673212a0 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_um-2.4.21-238.i586.r… 0de617af99feef4eebcb6acd26e43ec2 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp4G-2.4.21-238.i58… 4a34622f783ef3cf83e48663a0608983 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-2… fabd2effa2e9cd91dac78f1fbee39542 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-238.i586.… 1a33701036c2881de95b870fae0b42bb ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-238.i58… 2f0b04a5a541dc7e968e34cb673212a0 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-238.i5… 32afadf0bc5720c3b6908e8d1930cf5a source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-238.src… 432376a5c73031fd92e3b7a5400e74a1 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-238.src.… 480c2a0ae1a4ef8db0013b7486ba3204 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_um-2.4.21-238.src.rpm ca1ce8b2b232595dc64ec16894bbbd91 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp4G-2.4.21-238.src.… b8a177a4baeb45b356ba4ae3949bbd6b ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-23… 8dff6fb225cad06f4235b260c78297e6 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-238.src.rpm 1ce273d733825abd2013424b85ceb1a5 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-238.src.… 480c2a0ae1a4ef8db0013b7486ba3204 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-238.src… 432376a5c73031fd92e3b7a5400e74a1 SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-118.i5… 58742cc74f8b1306497f7a4e854e0349 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-118.i58… cfa736f8d0331decc43c710ce3e251a9 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… a1a73c62e658f3fdceb581a1195d6cf0 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-118.i586.… d33e298380bb61ef06596d1e42bd2211 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-118.i586… bfa8c23ef57a2219275ddbadf83f94df ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-118.i58… cfa736f8d0331decc43c710ce3e251a9 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-118.i5… 58742cc74f8b1306497f7a4e854e0349 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-118.src… 346198e849036593f1c7398624204b80 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-118.src.… 23e10cd0d53d4eaf4a903bce50c27edc ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.Su… 7996319a61e107e03be85aeff8401b2f ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-118.src.rpm 8e1e2c7b114a2377e270110d143127fd ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-118.src.r… c05d264136ab3008d2c0202097af5a51 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-118.src.… 23e10cd0d53d4eaf4a903bce50c27edc ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-118.src… 346198e849036593f1c7398624204b80 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-238.i5… c87fb98e0efc1875da70b87e053abd12 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-238.i58… e266534b5894394a80b704fc69039d85 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-2… 99d48777da013e06775ede24378301fc ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_smp-2.4.21-238.i586.… 40f9309e12736e355f0625a9bb1419a7 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_psmp-2.4.21-238.i586… 47143e6181adcc0b273b82168e6bd444 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-238.i58… e266534b5894394a80b704fc69039d85 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-238.i5… c87fb98e0efc1875da70b87e053abd12 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-238.src… e20c53d0fdb984f13b328694ade10891 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-238.src.… fa9cb58e89460b09834c4b27658e12d6 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kernel-source-2.4.21-23… 9efc389dda80050045ca0177c1d878ae ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_smp-2.4.21-238.src.rpm 54f5e3706bb34d3cf4056aaca2be60b1 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_psmp-2.4.21-238.src.r… 1fb22ced69456c133518926bbb24e5ed ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-238.src.… fa9cb58e89460b09834c4b27658e12d6 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-238.src… e20c53d0fdb984f13b328694ade10891 SUSE Linux 8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_deflt-2.4.18-310.i386.… e08cff6d3391365f1afb099e20a3fe61 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_i386-2.4.18-310.i386.r… 77b7a525ca02d0310dacc6532111051b ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/kernel-source-2.4.18.SuSE-31… 4d4eba0c559f137b4be6ec8f9a528632 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_smp-2.4.18-310.i386.rpm e5c3e41729c02ac28ac9232b146aa4e4 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_psmp-2.4.18-310.i386.r… 8a2e5b5bbf1bde4533ae984b60f1ad82 ftp://ftp.suse.com/pub/suse/i386/update/8.0/images/k_deflt-2.4.18-310.i386.… e08cff6d3391365f1afb099e20a3fe61 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_deflt-2.4.18-310.src.rpm 09be0e0f30a27ad5af8b3480a091f6a1 ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_i386-2.4.18-310.src.rpm 7c2a1722f899702ae3b9a08c42c8db4c ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/kernel-source-2.4.18.SuSE-3… b47d6b6b14f417902a038325072d63f1 ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_smp-2.4.18-310.src.rpm 170b51b1b1d04b72d8d12439a5ade0f1 ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_psmp-2.4.18-310.src.rpm 98d8e61a495663a6d6a70e27503826d4 ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/k_deflt-2.4.18-310.src.rpm 09be0e0f30a27ad5af8b3480a091f6a1 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-source-2.6.… db50c10aef8f142bf9183fe053dcac90 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-source-2.6.5-7… 91a4d3f953489314a2eaa7b738969232 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-238… 3229ea33080c16fec96627a927fd45de ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… 951dc563493357551df1aca30093a85a ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-238.x… 51952cafbba877ecafaa3e350168e924 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-238… 3229ea33080c16fec96627a927fd45de source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-238.sr… 72d16b1d90ae62bf00e711328582be43 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… cb9543e58aa4eb4bcc8b9f8fff796959 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-238.src.… e66e38362ad27dca08691c546df003f8 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-238.sr… 72d16b1d90ae62bf00e711328582be43 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - gaim The SuSE Security Team discovers various remotely exploitable buffer overflows in the MSN-protocol parsing functions of gaim. The only affected product is SUSE LINUX 9.1. New packages will be available soon. (CAN-2004-0500) - mozilla/firebird We are currently testing new mozilla/firebirds packages that include several fixes for security-related bugs. New packages will be available soon. ______________________________________________________________________________ 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 (GNU/Linux) iQEUAwUBQRczY3ey5gA9JdPZAQFrewf4hHJuaQ/X52NHgc0KR4qv4iI37SPz2RCj 5A4xrC818nDL8/UO7Tocjn4V4PWzU+bdkm/o/+Zgc1jwpqFKXeWBf9xpfBcm79Xc gZirYzIVEVEcPPTowFPKutlA5z2YIroeiC8XD8n5w7gCx0DwD/qgIP34gevw4h5l iVI7ao+XOBFtSheipOkhbyVDUSYT491roGDOqVrN1kEAFTHiCeGYyB8fjQsROAk4 uotjb2GLxiLMzE5+3voNUUUr2bzJUzfzunWDJmxIzp0iG8GmjJhjZmN1KHiuZv+c r49vM/wnZjTSAbxikB5MrnNeifA5GvFs20LvWPFGGaVqA47roKCF =akkg -----END PGP SIGNATURE-----

5 4

SSH attacks - why different messages
by Juergen.Mell＠t-online.de 09 Aug '04

09 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi List, in the last days I see an increasing number of attacks against our SSH system. Up to now the attackers do not seem to have any success, but I am wondering about one thing: I have set up a list of users which are allowed to use the SSH daemon with the AllowUsers command in sshd_config. Now I get different messages from SSHD although none of the user names the attacker is trying is in the AllowUsers list: Aug 7 22:47:17 akira sshd[5512]: User test not allowed because not listed in AllowUsers Aug 7 22:47:17 akira sshd[5514]: User guest not allowed because not listed in AllowUsers Aug 7 22:47:18 akira sshd[5516]: Illegal user admin from www.xxx.yyy.zzz Aug 7 22:47:20 akira sshd[5520]: Illegal user user from www.xxx.yyy.zzz Aug 7 22:47:21 akira sshd[5522]: User root not allowed because not listed in AllowUsers Why are 'admin' and 'user' handled differently than 'test'. None of these users exist on my system ('guest' and 'root' are available). And none of these five is in AllowUsers. Can anybody shed some light on this? Thanks! Jürgen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFBFUpjtMrl3JEeRvwRAuBTAKClf/i9qgAUNzuwsEhYiNLipvPs/ACg8sEu VYZO+DJ7KM6E42A+Ow8uGKU= =sYpw -----END PGP SIGNATURE-----

3 3

RE: [suse-security] SuSE 8.0 patch update : problem with mod_ssl- 2.8.7-120.i386.patch .rpm
by Theytaz Antoine 09 Aug '04

09 Aug '04

Thanks a lot for the information ! and it works :) Antoine -----Message d'origine----- De : Kevin Ivory [mailto:Ivory@SerNet.de] Envoyé : vendredi 6 août 2004 18:00 À : Theytaz Antoine Objet : Re: [suse-security] SuSE 8.0 patch update : problem with mod_ssl-2.8.7-120.i386.patch .rpm On 2004-08-05 10:40, Theytaz Antoine wrote: > I have exactly this problem. Armin, did you get any answer ? > ... > Date: Tue, 27 Jul 2004 08:11:28 +0000 (GMT) > From: Armin Schoech <schoech(a)iap-kborn.de> > Message-ID: <Pine.LNX.4.58.0407270808170.3318(a)pcramnan.iap-kborn.de> > Subject: [suse-security] Problem with mod_ssl-2.8.7-120.i386.patch.rpm > ... > I have a problem with the newest mod_ssl Patches on my SuSE 8.0 boxes. > The error messsage ist: > > > error: failed dependencies: > apache = 1.3.23-152 is needed by mod_ssl-2.8.7-120 > > > But there is no apache-1.3.23-152.i386.rpm on the SuSE FTP server. The > latest patch for apache is apache-1.3.23-150.i386.rpm. There is only a > apache-1.3.23-152.src.rpm but no pre-compiled rpm. > > > Is anyone having the same problem ? Can I just force the update with > "--nodeps" option ? --nodeps is okay. I wrote to security(a)suse.de and got a personal mail as answer. Kevin -- _ | Kevin Ivory | Tel: +49-551-3700000 |_ |\ | | Service Network GmbH | Fax: +49-551-3700009 ._|ER | \|ET | Bahnhofsallee 1b | mailto:Ivory@SerNet.de Service Network | 37081 Goettingen | http://www.SerNet.de/

1 0

suse-security
by Carlos E. R. 09 Aug '04

09 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm getting an error message when the script /usr/lib/secchk/security-weekly.sh runs, claiming that 'john.ini' does not exist - and it does. I tried to reinstall both john and seccheck packages, same error. This is SuSE 9.1 Ideas? |Date: Mon, 2 Aug 2004 01:30:52 +0200 (CEST) |From: Cron Daemon <root(a)nimrodel.valinor> |To: root(a)nimrodel.valinor |Subject: Cron <root@nimrodel> test -x /usr/lib/secchk/security-control.sh && | /usr/lib/secchk/security-control.sh weekly & | |fopen: john.ini: No such file or directory | - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFBDgsLtTMYHG2NR9URAgU2AJ9MNPVfFhcu2z6EPunOBm/MzMIjiQCcCRLw Kk0Pol326cv6fGX5uck4zqA= =rJaq -----END PGP SIGNATURE-----

2 3

many mysqld zombies after latest kernel update
by Olivier Mueller 08 Aug '04

08 Aug '04

Hello, After installing the latest kernel update (from 6.Aug) and rebooting, I'm now getting hunderds of mysqld zombies (defunct) one some servers. I don't really see why yet... the only thing which changed was the kernel... The mysqld is a self-compiled one. The services are still working fine, but that is still a bit disturbing... Anybody noticed the same thing? regards, Olivier -- _______________________________________________________ Olivier Müller - PGP key ID: 0x0E84D2EA - Switzerland E-Mail: http://omx.ch/mail/ - AIM/iChat: swix3k

5 11

32 or 64 bit?
by root 07 Aug '04

07 Aug '04

I was under the impression that SuSe9.1Pro was a 64 bit OS. I did an install on an AMD64, on an Asus K8V. Before install begins, I get a warning about This is not 64 bit software. Be kind in your answers I am pretty new, and really hope this isn't classified as a dumb question. Phil

2 1

SUSE loop_fish2 keylength ?
by szh＠dgap.mipt.ru 06 Aug '04

06 Aug '04

Hello I am wondering what keylength does SUSE loop_fish2 use ? Suse losetup setups 20+20=40 bytes of loopinfo.lo_encrypt_key data, sets keylength = 20 and passes to kernel loop_fish2 it seems work only with 128, 192, 256 bits keys. Can somebody please clarify : Which length loop_fish2 uses ? and How is it derived from lo_encrypt_key ?

1 0

Kernel vulnerability?
by Frank Steiner 06 Aug '04

06 Aug '04

Hi, are the SuSE kernels affected by this? http://isec.pl/vulnerabilities/isec-0016-procleaks.txt It seems that this issue (if it is one) is more or less ignored on the LKML. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049

3 2

pam_unix2 ldap limiting host access
by rian bogle 05 Aug '04

05 Aug '04

How can one go about limiting access to hosts by ldap users with suse pam_ldap and nss_ldap. It appears as though pam_unix2 actually uses nss_ldap and thus ignores the traditional pam_check_host_attr for pam_ldap in ldap.conf. In my network, we have multiple suse workstations and servers who authenticate to an ldap server and mount a remote home dir. I would like to limit access of users to certain and specific hosts by using the host dn in my ldap db. Thanks, Rian -- ******************************************************** * Rian Bogle * * Computer Programmer / IT Specialist * * Flagstaff Field Center * * US Geological Survey * * (928) 556 7212 * * * * "Unix is user friendly, * * its just particular about who its friends are...." * * * ********************************************************

1 0

administrativa: unsubscribed amazon addresses
by Roman Drahtmueller 05 Aug '04

05 Aug '04

FYI: ---------- Forwarded message ---------- From: Roman Drahtmueller <suse-security-owner(a)suse.com> To: all amazon subscribers <suse-security-owner(a)suse.com> Cc: abuse(a)amazon.com Date: Thu, 5 Aug 2004 13:01:18 +0200 (MEST) Subject: your subscription Dear subscriber on suse-security(a)suse.com, due to some complaints of other list members, all subscribers using amazon domains in their subscription email address are being removed from the list, effective immediately. The complaints refer to unsolicited email sent to addresses that appear actively on the list, and that stem from amazon.co.uk or amazon.com domains. We consider this reason enough to unsubscribe you from the list. If you feel that your unsubscription from suse-security(a)suse.com happened in error, then please let us know, and feel free to re-subscribe to the list. If you are the reason why we are unsubscribing all amazon email addresses from our list, then please stay off the list. Thank you, Roman Drahtmüller, SUSE Security. -- - - | Roman Drahtmüller <draht(a)suse.de> // The mistakes you regret the most in | Novell - SUSE Linux AG - Security // your life are the ones you didn't | Nürnberg, Germany // commit when you had the chance. (HR) | - -

3 2

SuSE 8.0 patch update : problem with mod_ssl-2.8.7-120.i386.patch .rpm
by Theytaz Antoine 05 Aug '04

05 Aug '04

hello all, I have exactly this problem. Armin, did you get any answer ? Thanks, Antoine ---------------------------------------------------------------------------- ----------------- Date: Tue, 27 Jul 2004 08:11:28 +0000 (GMT) From: Armin Schoech <schoech(a)iap-kborn.de> Message-ID: <Pine.LNX.4.58.0407270808170.3318(a)pcramnan.iap-kborn.de> Subject: [suse-security] Problem with mod_ssl-2.8.7-120.i386.patch.rpm Hi ! I have a problem with the newest mod_ssl Patches on my SuSE 8.0 boxes. The error messsage ist: error: failed dependencies: apache = 1.3.23-152 is needed by mod_ssl-2.8.7-120 But there is no apache-1.3.23-152.i386.rpm on the SuSE FTP server. The latest patch for apache is apache-1.3.23-150.i386.rpm. There is only a apache-1.3.23-152.src.rpm but no pre-compiled rpm. Is anyone having the same problem ? Can I just force the update with "--nodeps" option ? Armin

1 0

SUSE Security Announcement: libpng (SUSE-SA:2004:023)
by Thomas Biege 05 Aug '04

05 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: libpng Announcement-ID: SUSE-SA:2004:023 Date: Wednesday, Aug 4th 2004 16:00 MEST Affected products: 8.0, 8.1, 8.2, 9.0, 9.1 SUSE Linux Database Server, SUSE eMail Server III, 3.1 SUSE Linux Enterprise Server 7, 8, 9 SUSE Linux Firewall on CD/Admin host SUSE Linux Connectivity Server SUSE Linux Office Server Vulnerability Type: remote system compromise Severity (1-10): 9 SUSE default package: yes Cross References: VU#388984 VU#236656 VU#160448 VU#477512 VU#817368 VU#286464 CAN-2004-0597 CAN-2004-0598 CAN-2004-0599 Content of this advisory: 1) security vulnerability resolved: - stack based buffer overflows - NULL pointer dereference - integer overflows problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - mod_ssl - lha - gfxboot - liby2util - pure-ftpd - neon - pavuk - sox - gaim - kernel 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Several different security vulnerabilities were found in the PNG library which is used by applications to support the PNG image format. A remote attacker is able to execute arbitrary code by triggering a buffer overflow due to the incorrect handling of the length of transparency chunk data and in other pathes of image processing. (VU#388984, VU#817368, CAN-2004-0597) A special PNG image can be used to cause an application crashing due to NULL pointer dereference in the function png_handle_iCPP() (and other locations). (VU#236656, CAN-2004-0598) Integer overflows were found in png_handle_sPLT(), png_read_png() functions and other locations. These bugs may at least crash an application. (VU#160448, VU#477512, VU#286464, CAN-2004-0599) Many thanks to Chris Evans who reported issues to us and other vendors. 3) special instructions and notes Various applications use libpng either dynamically linked, statically linked, or by linking a copy of libpng included in the application's source distribution. In the first case you have to restart the affected application. In the other cases we will release updates for these packages if the vulnerable libpng code is called with input from an untrusted source. 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.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libpng-1.2.5-182.7.i58… 0e89a04a0a50a49f756795bbd319e1dd patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/libpng-1.2.5-182.7.i58… dc7270f4c0c728c3ba7252d0a551e437 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/libpng-1.2.5-182.7.src.… bb8d8000a010d92747dda1b0908d41aa SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libpng-1.2.5-191.i586.… 5b34c70a715cd34bb0e5879063dcf63b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/libpng-1.2.5-191.i586.… 6c192934eae546bc1f2c9b7980c848f0 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/libpng-1.2.5-191.src.rpm c740a8c8c6188470512c91ec8e9e70a9 SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libpng-1.2.5-191.i586.… 64d76d67104123317c4a66a0721072e8 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/libpng-1.2.5-191.i586.… 372b2eae57ff3ff90ad1250e8a2d3a91 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/libpng-1.2.5-191.src.rpm 16dde1bf26f8c9c006ccad4779d138d7 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libpng-1.2.4-115.i586.… 88dc17c0edccfcd65fea3539379de370 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/libpng-1.2.4-115.i586.… 24d8632e5454e46ce4623c5a672a3d5d source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/libpng-1.2.4-115.src.rpm e3086525ee914ddc5dc0c7da7ab96a25 SUSE Linux 8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/gra1/libpng-2.1.0.12-169.i386.r… 09b22a2fab61b1018ce73e2965777123 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/gra1/libpng-2.1.0.12-169.i386.p… 097de7e1c11106390128b6996041fe3c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/libpng-2.1.0.12-169.src.rpm 9e1da14f139fc4dcf481cdf836397da7 x86-64 Platform: SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libpng-1.2.5-182.7… c6c0f425059cf94803952530f0e9ba02 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/libpng-1.2.5-182.7… 01814d5c445560c6bcca0f1d9221e5be source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/libpng-1.2.5-182.7.sr… 27c4236b2ca11a760b3028c5058db7cf SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libpng-1.2.5-191.x… 5e8c7dcfe20c386150c4129bb549569f patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/libpng-1.2.5-191.x… 4fc9a5a29f5c813b32b9dee230250b17 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/libpng-1.2.5-191.src.… 526c0048344f1aa467903b1a8bce3506 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: - mod_ssl A remotely exploitable format string bug has been found in the logging function of mod_ssl. New packages are available at our FTP servers. - lha A source code review of lha was conducted by the SuSE Security-Team to fix all possible buffer overflows. New packages are available at our FTP servers. - gfxboot/bootsplash-theme-SuSE/bootsplash-theme-SuSE-Home A bug in gfxboot on SUSE LINUX 9.1 caused the lilo boot password to be shown in cleartext while typing. The standard boot loader is grub. New packages are available at our FTP servers. - liby2util File names of patch files are no longer passed to gpg via the system() call. Since those file names are not protected by a digital signature, an attacker could previously manage to implant shell code. New packages are available at our FTP servers. - pure-ftpd This update fixes a possible DoS attack because of a bug in the accept_client function handling the setup of new connections. New packages are available at our FTP servers. - neon This update adds a missing filter for control characters. New packages are available at our FTP servers. - pavuk This update fixes several buffer overflows in pavuk's digest authentication support. Thanks to Matthew Murphy for reporting this issue to us. New packages are available at our FTP servers. - sox Several buffer overflows in the 'sox' and 'play' have been fixed that can be exploited by playing specially crafted .wav files. (CAN-2004-0557) New packages are available at our FTP servers. - gaim The SuSE Security Team discovers various remotely exploitable buffer overflows in the MSN-protocol parsing functions of gaim. The only affected product is SUSE LINUX 9.1. New packages will be available soon. (CAN-2004-0500) - kernel Paul Starzetz from iSEC informed us about a race condition in the 64bit file offset handling code of the kernel. New kernels for SUSE LINUX Enterprise Server 9 are available from the maintenance-web. The updates for the SUSE LINUX 9.1 kernels are available from our FTP servers. Kernel update packages for older SUSE LINUX distributions will be available in the next few days and will be announced with a dedicated advisory. ______________________________________________________________________________ 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 (GNU/Linux) iQEVAwUBQRD6oHey5gA9JdPZAQH0sQf/Y8TYYttWr44JA29vuduY6dZg4HkCujEh tMjOLSxJ2MfvLkbY5dGdjpwx5ih4it57jt0IeWfcjQ3CeQOA/3z6xRYwlQ0QgzXD YOaGdq1W30FDBfphZUvBvBrWbzJpETFEcb36PEMSncedpx4a7Hmz3GbDiAPoMMke /ykL9NG5ooSvmf09LreXPl5xD+mbT9qxX0Mw0nSixmyMKTJBnqub+Sa03lnmq0Ud c+R5UaG9ncB3MZfLK4YlZVygpIPn6+ezoEQ4KUvI91ESNdvoqozHNhf//37TzRLL noVNSAouV1R1aEeFGxjtHVatnlWdv/NTekxW5rcs2ENQ1bDT/TPVQw== =ossK -----END PGP SIGNATURE-----

2 2

Fwd: [suse-security] reiserfs strange behavior
by melissad＠speakeasy.net 03 Aug '04

03 Aug '04

Per the source for Reiser or to get an answer, go to the Reiser Site at http://namesys.com or reiser(a)namesys.com I quit using Reiser as my successive SuSE release updates would not recognize the volumes and could not mount them. I would have to go to the Reiser Site, obtain the version that SuSE was using, then load and compile, then rebuild the file system. I just went to Ext3 --- not as criticism of Reiser. neither Reiser nor I could fathom why SuSE's installation would not provide a bridge for allowing for updating the Reiser file system with an upgrade. The folks at namesys.com, the owners of Reiser, are great and helpful. melissa > -----Original Message----- > From: Guido Tschakert [mailto:guido.tschakert@src-gmbh.de] > Sent: Tuesday, August 3, 2004 01:53 PM > To: suse-security(a)suse.com > Subject: Re: [suse-security] reiserfs strange behavior > > Hello, > > > > You may even try the following pairs > > bb3001/am3001 > > gb3001/fm3001 > > mb4001/lm4001 > > mb4002/lm4002 > > ma4001/ll4001 > > td3001/so3001 > > ma4001/ll4001 > > > > I found these files becaus this is my system for user accounts. Among my > > 1300 usernames I found about 10 pairs with this kind of clash! > > > I also can confirm the problem (didn't test the hole bunch written above :-) > Is anybody here knowing the sourcecode of reiserfs (At the moment I > don't have installed the source nor I have the time to look through). I > wonder if this names are reserved in some way by reiserfs, so you can't > use'm. > I also tried to find a correaltion between the pairs mentioned above, > but I didn't see anything :-( > > But will this be the only ones? > > > I fear there are more of this kind. Why should it be only 7 pairs, you > found by chance. > > Somebody here who can test it on another Kernel < 2.6.5 > In Kernel 2.4.x (no I did not test all of them :-) I didn't found the > problem. I could imagine that it is a problem of kernel 2.6.x + reiserfs. > > guido > > Best > > Uwe > > > > > > > > > > > > > > > -- > Check the headers for your unsubscription address > For additional commands, e-mail: suse-security-help(a)suse.com > Security-related bug reports go to security(a)suse.de, not here > >

1 0

Re: [suse-security] suse-security
by Carlos E. R. 03 Aug '04

03 Aug '04

El 2004-08-02 a las 16:13 -0000, suse(a)karsites.net escribió: > have the file or directory permisisons been changed somehow? No, they are those made by the rpm - I touched nothing. I had 8.2, it worked. Upgraded to 9.1, it stopped working. Reinstall afected packages, no change. -- Saludos Carlos Robinson

1 0

network performance problems with SuSEfirewall2 and multiple interfaces
by Ralf Ronneburger 03 Aug '04

03 Aug '04

Hi everyone, I've a machine with 3 real and 15 virtual interfaces under SuSE 9.0 with SuSEfirewall2. Resulting from this I've also a lot of iptable-rules (iptables-save | wc -l gives me 1068 lines). After some weeks the machine slows down network-traffic, although everything else seems to run quite well (low CPU-load, low memory-usage), so I have to reboot it (restarting SuSEfirewall2 does not help). I wounder if anybody else has experienced something similar, if anything of that kind is known and if anybody has an idea, where the problem may lay. Greetings, Ralf

3 3

SuSEfirewall2 and added iptables rule question
by guus 03 Aug '04

03 Aug '04

Hello list users, I am using SuSE 9.1 prof. And its doing quite nice on my server. Although I have a security related question. Is there somebody who can give me a hint on how to add iptables rules to the SuSEfirwall2 setup. I haven been trying severall things before posting to this list, for example: - adding the rule directly from the prompt using the iptables -A command. - usung the webmin firewall configuration tool, added the rule and made it run at startup. - put the rule in the startup script SuSEfirewall2 using the folowing: FW_CUSTOMRULES="/etc/sysconfig/scripts/SuSEfirewall2-custom" where the called script includes: fw_custom_before_denyall() { iptables -A input_ext -m state -s 80.0.0.0/0 -d 10.0.1.253 -i eth1 --state NEW,ESTABLISHED,RELATED,INVALID -j DROP true } Nevertheless when I execute the iptables -L command the rule seems not to be added to the filtering table. Only the other rules, generated by the firewall are there. I realy like to get this running, so if yoy could help then please do. Your help will be much appreciated. Thank you in advance. Guus Bill -------------------------------------------------------

2 1

hw compatibilty
by Emiliano Sutil 02 Aug '04

02 Aug '04

Hello, I want to know if is there any problem to install a Suse 9.1 on this mainboard: http://es.asus.com/products/mb/socket939/a8v-d/overview.htm Thanks Emiliano Sutil

2 1

Re: [suse-security] Martian source
by m3047＠inwa.net 02 Aug '04

02 Aug '04

We get these from the phones which are part of an ethernet/IP phone system when they come in over an IPSec tunnel with a separate subnet at the other end and are trying to contact the switch. The local tunnel endpoint is not running on the default gateway (and no way to set routes on idiot phone switch), so there is a route on the default gateway machine to send the packets to the machine with the tunnel endpoint (certainly not an optimal network configuration, but it works for everything else). The box with the VPN endpoint then drops the martian packets (could turn that off, I suppose). The expedient course of action was to change the default route on the phone switch so that it points to the VPN gateway, and then they're not considered "martian". So far that hasn't broken anything else; I suppose if it does we'll have to add a route to the VPN box so that it redirects "normal" traffic to the default gateway.. :-\ -- Fred Morris fredm3047(a)inwa.net (I-ACK)

1 0

Martian source
by Paolo Santancini 02 Aug '04

02 Aug '04

Hi all, anybody can give me information about the kernel message called "martian source" written in "/var/log/messages"??? What does it mean? Thank Bye Paolo

4 3

RE: [SLE] yast update not working with Novell Border manager authentication?
by g.lams＠itcilo.org 02 Aug '04

02 Aug '04

In fact, it's what our novell administrator has done, i.e create an access rule that allows the IP address of that machine to the site it needs to reach. Then check the "autnehticate only when user attempts to access restricted site" and put that rule on top of the others. It works for our servers but several users, including myself, have problems navigating a few sites including hotmail, yahoo Gael "Jesse Pretorius" <preycor(a)myrealbox.com> wrote on 02/08/2004 15.42.33: > > Authentication has been implemented on our Novell BorderManager proxy > > servers > > I've setup the proxy in yast providing username and password but before > > being giving me the list of updates, there is the following error: > > BorderManager's login page is proprietary in a way that does not provide an > authentication request in a way that YaST expects it. > > AFAIK the only way around it would be to set the NBM to allow your server's > IP address to go through without requiring authentication. > >

1 0

Unsubscribtion
by Vibeke & John Petersen 02 Aug '04

02 Aug '04

Please, unsubscribe me NOW! Thanks.

3 2

Re: [suse-security] yast update not working with Novell Border manager authentication?
by Juan Erbes 02 Aug '04

02 Aug '04

Mensaje citado por: g.lams(a)itcilo.org: > Hi All, > > Authentication has been implemented on our Novell BorderManager proxy > servers: this way, the desktops, when they do\'nt authenticate on our > novell network, need to provide username and password before navigating in > > > Internet > But since this modification, my SuSe servers are not able to fetch a > list > of security updates, and obviously download them. > > I\'ve setup the proxy in yast providing username and password but before > being giving me the list of updates, there is the following error: > \"signature check for patch info files failed.Cannot load patch > information. \" > > And when I click on details, it gives the following message: > Path:<HTML><HEAD><TITLE>Novell/i386/update/9.0/patches/<HTML><HEAD><TITLE>N> ovell > BorderManager</TITLE></HEAD><BODY>The document > has moved <A > HREF=\"https:/172.16.11.1:444/BM-Login/?%22http:/ftp.uni-kl.de/pub/linux/s> use/<HTML><HEAD><TITLE>Novell/i386/upd > ate/9.0/patches/directory.3%22\">here.</A></BODY></HTML> > > It seems that, even if I provide a username and password, the > BorderManager is redirecting my linux server to the authentication page > (172.16.11.1 corresponds to one of the border manager server) > I have tehe same problem, but I\'m working in. You must to install ncpfs, and the Novel client for linux http://novelclient.sourceforge.net/ Read the faq and howto from this site. I need to probe the Client Trust (with wine), for complete the autentication in the Border Manager. __________________________________ Registrate desde http://servicios.arnet.com.ar/registracion/registracion.asp?origenid=9 y participá de todos los beneficios del Portal Arnet.

1 0

yast update not working with Novell Border manager authentication?
by g.lams＠itcilo.org 02 Aug '04

02 Aug '04

Hi All, Authentication has been implemented on our Novell BorderManager proxy servers: this way, the desktops, when they do'nt authenticate on our novell network, need to provide username and password before navigating in Internet But since this modification, my SuSe servers are not able to fetch a list of security updates, and obviously download them. I've setup the proxy in yast providing username and password but before being giving me the list of updates, there is the following error: "signature check for patch info files failed.Cannot load patch information. " And when I click on details, it gives the following message: Path:<HTML><HEAD><TITLE>Novell/i386/update/9.0/patches/<HTML><HEAD><TITLE>Novell BorderManager</TITLE></HEAD><BODY>The document has moved <A HREF="https:/172.16.11.1:444/BM-Login/?%22http:/ftp.uni-kl.de/pub/linux/suse/<HTML><HEAD><TITLE>Novell/i386/upd ate/9.0/patches/directory.3%22">here.</A></BODY></HTML> It seems that, even if I provide a username and password, the BorderManager is redirecting my linux server to the authentication page (172.16.11.1 corresponds to one of the border manager server) Any help would be appreciated Gaël

1 0

password recovery
by Lyle Giese 02 Aug '04

02 Aug '04

I have been using suse for a bit now, having used RH previously. One feature that I seem not to see or maybe it's just not there. In RH, there was a way to recover the root password. As I am an independant consultant, I can just imagine getting to a client's site and they don't remember/know the root password. Is there a way/method to recover/reset the root password in suse? Thanks, Lyle

17 30