October 2003 - openSUSE Security - openSUSE Mailing Lists

explicitly allow fragmented packets in ipsec environment - unset the DF bit
by mailinglists 03 Oct '03

03 Oct '03

Hi I've stumbled over something that appears to be a bit strange to me. I can send 15 Kbyte (I haven't tried larger packets yet but I'm sure they will go through the tunnel as well) pings to the other end of an ipsec (freeswan-freeswan) tunnel. Checking my fragmented packets the DF bit is not set. The other end of the tunnel, however, can "only" send 1500 Byte pings to me. Those packets have the DF bit set. I wonder how it is possible to unset the DF bit in an IP implementation. Or is there a difference between the various linux distributions? My ipsec box is a redhat while the firewall box right behind it is a SuSE box. I also checked the /proc filesystem for an option to disable the DF bit, but could not find anything. Thanks for any suggestions, Philipp

2 1

Mail missplaced or lost
by David Soltero-Lugo 03 Oct '03

03 Oct '03

I have a system running SuSE 7.3 with all updates, and I noticed that the old mail (readed) was moving to the Trash folder or there was another new folder instead with the old mail. I don't know when the problem started but it is happening on multiple accounts, if not in all. I am using imapd and sendmail? is someone else seen something like this? thanks David

1 0

Re: [suse-security] Solved: How to apply IPSec NAT-Traversal Patch to SuSE8.2-Kernel ?
by J J 02 Oct '03

02 Oct '03

Apologies to Andreas and Elmar, evidently I didn't read Andreas' posting properly before I replied! :) Obviously avoiding recompiling your kernel will make life far simpler for you and it sounds like you don't need to recompile to get NAT-traversal running. The only reasons I can see that you might are (i) to enable the possibility of debugging with ipsec klipsdebug --all and (ii) for intellectual satisfaction/training/certainty! If you did want to pursue recompiling the kernel... Given that reiserfs.o is being built, my suggestions about configuration aren't applicable anymore! I have seen the effect you describe before: where an unchanged configuration still shows a change in .config - it seems to be harmless. Things like new comments, or sections that don't do anything (because an option is not switched on higher up) but are still being written. It's not too surprising if you look at how each file gets written. zcat /proc/config.gz is effectively an output from the kernel itself of saved config information so will be minimal. make xconfig is a complex tcl/tk script. If you want to progress this any further then we will probably need the exact error message, word for word, letter for letter that you're getting in the boot process with the new kernel, and exactly at what point in the boot process it occurs, what message lines do you see just before it. Does it occur absolutely immediately (like when the kernel starts) or a bit later, during the startup scripts? My guess is that it's pretty early. If you are going to abandon the new kernel build then that's cool and I wish you luck with freeswan - it's a first-rate product but can be tricky without kernel debug IMHO! All the best, Carl >From: Elmar Marschke <elmar.marschke(a)epost.de> >To: suse-security(a)suse.com >CC: AThierer(a)ctl.de, c_peto(a)hotmail.com >Subject: [suse-security] Solved: How to apply IPSec NAT-Traversal Patch to >SuSE8.2-Kernel ? >Date: Thu, 02 Oct 2003 16:41:06 +0200 > >Hi, >special thanks to Andreas and Carl (JJ), due to your hints i solved my >problem. Though i don't have a patched *and* running kernel yet, i >achieved my goal to connect several Private-IP-Subnets through my VPN. >Here's a short summary: > >@Andreas: >Andreas Thierer wrote: > > I also needed NAT-Traversal with FreeSWAN. > > First i wanted to apply the NAT-Traversal-Patch, like you, > > but then i saw, that the X.509-Patch has also an NAT-Traversal- > > functionality. This X.509-Patch is applied to the FreeSWAN- > > paket shipped with SuSE 8.2. >Yes, you're right. I just couldn't believe that it's so simple :-). >Obviously it's not necessary to apply the kernel patch... > > > See >http://www.freeswan.ca/patches/www.strongsec.com/freeswan/install.htm#secti… >..this brought the solution. >Perhaps one will have trouble when trying to connect several Networks that >incidentally use the same private IP-Range, but right now this is not the >case in my setup. > >@Carl: >J J wrote: > > Is your new kernel missing reiserfs.o in the /lib/modules/<kernel > > version>/kernel/fs/reiserfs/ directory? >no, it's existing there. > > > If not then you have probably got a faulty config. >Yes, now i suppose that's the reason, too. Unfortunately i can't imagine >why... Just as you described I did a zcat /proc/config.gz > .config and >then a make xconfig after i patched the kernel. But unfortunately what you >describe in the following lines... > > > You've already patched the kernel so future compiles will give you all > > the Ipsec options that you need. > > Then you should have a configuration > > that's identical to your working configuration but with any changes you > > choose to make. The obvious changes are to switch on Ipsec, the NAT > > traversal and X509 patches... >was not the case, there were no options for ipsec available, before i did >that "strange" makefile targets in .../kernel_modules/zz_freeswan. Is it >possible that patching went wrong although Ret.Code was 0 ? > > > If the build process did make reiserfs.o but you're still getting a > > kernel panic then the problem is probably in the initrd. >I don't think so. I studied mkinitrd -h, think that i did it all correctly >and the same procedure is successful at other occasions. > >Anyway, in further inquiries i found some hints that Kernel-Parameter >CONFIG_REISERFS_FS_POSIX_ACL could be concerned to my problem. In my >xconfig this is displayed black, not grey, but anyway it's not possible to >change it. Another thing that made me wonder: zcat /proc/config.gz > >.config; make xconfig -> save *without any changings* into file .config2 >and quit; then a >diff .config .config2 shows a lot of differences. Does anybody know why >this is so? >Apart from this many thanks to all contributors...:-) >Kind regards >Elmar > > >-- >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 > _________________________________________________________________ On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile

1 0

[suse-security] unsubscription
by Mitica 02 Oct '03

02 Oct '03

---------- Forwarded Message ---------- Subject: [suse-security] unsubscription Date: Mon, 25 Aug 2003 15:36:06 +0300 From: Catalin Nitipir <catalinn(a)breezecom.ro> To: suse-security(a)suse.com > unsubscription -- 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 ------------------------------------------------------- Xnet scaneaza automat toate mesajele impotriva virusilor folosind RAV AntiVirus. Xnet automatically scans all messages for viruses using RAV AntiVirus. Nota: RAV AntiVirus poate sa nu detecteze toti virusii noi sau toate variantele lor. Va rugam sa luati in considerare ca exista un risc de fiecare data cand deschideti fisiere atasate si ca MobiFon nu este responsabila pentru nici un prejudiciu cauzat de virusi. Disclaimer: RAV AntiVirus may not be able to detect all new viruses and variants. Please be aware that there is a risk involved whenever opening e-mail attachments to your computer and that MobiFon is not responsible for any damages caused by viruses. -------------------------------------------------------

1 0

How to apply IPSec NAT-Traversal Patch to SuSE8.2-Kernel ?
by Elmar Marschke 02 Oct '03

02 Oct '03

Hi all, i installed a VPN with a SuSE8.2 2.4.20-4GB kernel and a freeswan_1.99_0.9.23-20 as provided by the 8.2 distribution. Everything including x509-Support is tested and working fine. Now i want to add NAT-Traversal functionality. As written in /u/s/d/p/freeswan/README.SuSE the NAT-Traversal Patches (written by Mathieu Lafon) for the *freeswan-package* are already inserted in the package provided by SuSE. But to get it running one has also to patch the *kernel* with the fswan-nat-t-kernel.diff, they write, and which is provided in the same directory. I applied the patch to my kernel-sources (Return Code=0) and recompiled the kernel: - make oldconfig (perhaps wrong?? don't know what this exactly is doing..) -i took a look in make xconfig and noticed that there were no possibilities to do configuration for IPSec, but at that moment i did'nt care - changed the Makefile's Extraversion Number.. - make dep - make clean - make bzImage - make modules - make modules_install I prepared my bootloader and did mkinitrd for that kernel. Booting with that kernel was ok, but ipsec did'nt start anymore: "ipsec_setup:modprobe: can't locate module ipsec. Kernel appears to lack KLIPS." I booted my old kernel again and according to some mails of this list i took a look into .../kernel_modules/zz_freeswan/Makefile and tried: in that directory: - make insert Result: make xconfig in /usr/src/linux did'nt work anymore. - make kmodule Result: make xconfig didn't work yet. - make klink Result: make xconfig worked again! And it had configuration-options for IPSec!! I configured this -i took all the defaults i found there, the only thing i changed was the IPSec-Stuff- and compiled another kernel exactly as described above (except that i used xconfig instead oldconfig). Every step gave a Return Code of 0. Result when booting this new kernel: "Kernel panic: unresolved symbol reiserfs.o" (which is my boot partition). Question: can anyone give me a hint about the correct way to apply this patch and get a working kernel? *Which* make -steps / targets do i have to take in .../zz_freeswan/ (e.g. what about oldmod?) and perhaps in /usr/src/linux, and **in which order**? Any help would be greatly appreciated.. thnxalot! Kind regards Elmar

1 1

Alternative to openssl/openssh
by Philippe Vogel 02 Oct '03

02 Oct '03

Hello List! Are there any secure alternatives to openssl/openssh? It is no fun to patch these stuff almost every day or week or better said the last time too often! Why then secure communication, if there is too much insecurity in it? Maybe this leads back to telnet! Philippe

3 2

SuSE 7.3
by Philippe Vogel 02 Oct '03

02 Oct '03

Hello! At what date SuSE 7.3 will be discontinued? I want to decide, if I do an upgrade on an old system. Philippe

6 7

Re: [suse-security] SuSE 7.3
by m3047＠inwa.net 02 Oct '03

02 Oct '03

At 1:28 AM 10/2/03, Mathias Homann wrote: >Am Donnerstag, 2. Oktober 2003 01:20 schrieb Roman Drahtmueller: >> (someone) wrote: >> > At what date SuSE 7.3 will be discontinued? >> > I want to decide, if I do an upgrade on an old system. >> >> We're looking at mid November this year for the end of 7.3. > > >With all updates installed, would it be 'safe' to keep a 7.3 box running, or >should it be upgraded? I've still got a SuSE 6.4 box running and on the 'net. Really, it depends on what you use it for, and what you're willing to turn off, firewall, or manually patch. Things get zen after a while.. or else you get hacked I guess. (And I just bought a copy of 8.2. But, that's still too patchy for me to want to "open it up to the world".) -- Fred Morris m3047(a)inwa.net

1 0

Discontinued SuSE Linux Distributions
by Roman Drahtmueller 01 Oct '03

01 Oct '03

I'm also forwarding this to suse-security@, since this is what we do with announcements, too. Thanks, Roman. -----BEGIN PGP SIGNED MESSAGE----- Dear suse-security-announce subscribers and SUSE LINUX users, having provided security-relevant fixes for version 7.2 of our home user product, SuSE Linux, for two years, we would like to inform you that as of today, security fixes for SuSE Linux 7.2 will be discontinued for all architectures. Vulnerabilities found after Oct 1st 2003 will not be fixed any more for SuSE Linux 7.2. By consequence, the SuSE Linux 7.2 distribution directories on our ftp server ftp.suse.com have been moved to the /pub/suse/discontinued/ directory tree structure; the 7.2 directories in the update trees will follow later in October. The discontinuation of SuSE Linux 7.2 enables us to focus on the SUSE LINUX distributions of a newer release date to ensure that our customers can continuously take advantage of the quality that they are used to with SUSE LINUX products. This announcement holds true for SuSE Linux 7.2 only. As usual, SUSE will continue to provide update packages for the following home users distributions: SuSE Linux 7.3 SuSE Linux 8.0 SuSE Linux 8.1 SuSE Linux 8.2 and SUSE LINUX 9.0 for a two-year period after the release of the respective distribution. Please note that the maintenance cycles of SUSE LINUX Enterprise Server products and products based on the SUSE LINUX Enterprise Server operating system are not affected by this announcement. To learn more about SUSE LINUX business products, please visit http://www.suse.com/us/business/products/. If you have any questions regarding this announcement, please do not hesitate to contact the SUSE LINUX security <security(a)suse.de>. Best regards, Roman Drahtmüller, SUSE Security. - - | Roman Drahtmüller <draht(a)suse.de> // "You don't need eyes to see, | SUSE LINUX AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: SuSE Security iQEVAwUBP3tL0ney5gA9JdPZAQF7kgf9HUwDhmKShmj4Qknfm2wu9iqvuCOjKcq+ hCNREA+d7OwRHZacHdpkCXd0uIELBUknLD4q/6cNukRKFB+Td50wpVAaoJVAlGG7 yHmy54vXH7HTcTmPfOonphiusv6XmfTfOgap0yaSt2OoOG4p7TvP5HE16Vgi+HJB kfcWTPfXXit7yoOEYo4zfaaXXCz9WfqvDcdXUOvjmfalhgxmOr3f9/X7KcvhnayQ 4s0+/5hO+Pzzh2ODOaLwv+i4zC2+pDH1w9Ix/+snnjCxZefioG3u/xHaDqGGXTck Rg/y2oNDckNXuAop0B1lu+JdwSc8dSYhXDEenmsMpq2qG3vL13Y2TA== =OopL -----END PGP SIGNATURE-----

1 0

SuSE Security Announcement: openssl (SuSE-SA:2003:043)
by Thomas Biege 01 Oct '03

01 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: openssl Announcement-ID: SuSE-SA:2003:043 Date: Wednesday, Oct 1st 2003 16:12 MET Affected products: 7.2, 7.3, 8.0, 8.1, 8.2, 9.0 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7/8, SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: remote denial-of-service Severity (1-10): 5 SuSE default package: yes Cross References: CAN-2003-0543 CAN-2003-0544 CAN-2003-0545 Content of this advisory: 1) security vulnerability resolved: - problems with ASN.1 encoding - accepting client certificates even if disabled problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - whois - gdm2 - postgresql 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information OpenSSL is an implementation of the Secure Socket Layer (SSL v2/3) and Transport Layer Security (TLS v1) protocol. While checking the openssl implementation with a tool-kit from NISCC several errors were revealed most are ASN.1 encoding issues that causes a remote denial-of-service attack on the server side and possibly lead to remote command execution. There are two problems with ASN.1 encoding that can be triggered either by special ASN.1 encodings or by special ASN.1 tags. In debugging mode public key decoding errors can be ignored but also lead to a crash of the verify code if an invalid public key was received from the client. A mistake in the SSL/TLS protocol handling will make the server accept client certificates even if they are not requested. This bug makes it possible to exploit the bugs mentioned above even if client authentication is disabled. There is not other solution known to this problem then updating to the current version from our FTP servers. To make this update effective, restart all servers using openssl please. 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. Please note that this update includes openssl, openssl-devel and openssl-doc. openssl: Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-0.9.7b-71.i586… 88e30d20d288ecffe1e185b6ccc5099e patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-0.9.7b-71.i586… 68ffad90868b2107e3d82cc8fc50f6b7 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-71.src.r… 1f5a12184b14ac5281f8da50da7deab6 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-19.i586… 20818d3b2d257bcf9258707e2adf8812 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-19.i586… 2fbea6d1b3c19ed67d76337deef05363 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-19.src.r… 24d40081aa2644a336279ecae878c1f3 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-99.i586… a2c35048358d85fffd5a5ab7b58f6683 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-99.i586… 08803c7ac279b8c9ad1dc4aef4146617 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-99.src.r… 8bb653a4f779a125498f47dbaff0dc2f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-86.i386.rpm 671dc039955089f8523064272a4aad49 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-86.i386.pat… 4ae58f8e66b2cc7c2cc936132558ea46 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-86.src.rpm 7577ca638434ebe20406bfab85ec72ad SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssl-0.9.6b-158.i386.rpm 30ba99434b63d09d46cb271fac1bbefa source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-158.src.rpm 3485c804df9a381131462ba97697d6fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssl-0.9.6a-83.i386.rpm d235ef6d8b990bfaadb974c205acdc40 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-83.src.rpm 5a753ed3919767077292f96728de3870 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/sec1/openssl-0.9.6b-90.sparc.r… 29caa7dd281c0891c8655bcd5367f1ca source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-90.src.rpm 6faf5fe6fa004eb5515c1777886c49c9 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssl-0.9.6b-151.ppc.rpm b057f2204c43fdca13fcae041a45e977 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-151.src.rpm 7792ee3de5ef30c66c90a5fe43ee4eb2 openssl-doc: Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-doc-0.9.7b-71.… 4a7d456b67a0456221cf69231270b4bd patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-doc-0.9.7b-71.… 5223616e4b4d8f4bf0c02c63af75106c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-71.src.r… 1f5a12184b14ac5281f8da50da7deab6 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-doc-0.9.6i-19.… fc79cc73f1a9ab5ddfd30cf6ddfb8ddc patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-doc-0.9.6i-19.… 55c3f3afc117c1d3d49ea875057c8d72 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-19.src.r… 24d40081aa2644a336279ecae878c1f3 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-doc-0.9.6g-99.… 0d094066c96a8880845e0775f9e60b73 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-doc-0.9.6g-99.… af8fcb4128569d603a018727eba8dc79 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-99.src.r… 8bb653a4f779a125498f47dbaff0dc2f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/doc4/openssl-doc-0.9.6c-86.i386… c06870e5a8c6ea57471c13fb975c2c9f patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/doc4/openssl-doc-0.9.6c-86.i386… 911c9fd73b10b9db32e60834a82a79ee source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-86.src.rpm 7577ca638434ebe20406bfab85ec72ad SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/doc3/openssl-doc-0.9.6b-158.i38… 119950dc0267c7038c21acf6d875afdd source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-158.src.rpm 3485c804df9a381131462ba97697d6fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/doc3/openssl-doc-0.9.6a-83.i386… 2f664c56f018c857f2f11f2e2634fbfa source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-83.src.rpm 5a753ed3919767077292f96728de3870 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/doc3/openssl-doc-0.9.6b-90.spa… 6cbb149f6a3fb62eb7cc71e817e80426 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-90.src.rpm 6faf5fe6fa004eb5515c1777886c49c9 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/doc3/openssl-doc-0.9.6b-151.ppc.… 3f4235ab75c44e8e07c764ed2e4659da source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-151.src.rpm 7792ee3de5ef30c66c90a5fe43ee4eb2 openssl-devel: Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-devel-0.9.7b-7… 8cadccfaa0eeb50def65bdf1cfdba470 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-devel-0.9.7b-7… c7349b7e87b828ee90d7e0b87b0f5d38 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-71.src.r… 1f5a12184b14ac5281f8da50da7deab6 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-1… 970728b4b4ae97d162a226a51a49c5b4 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-1… f3cde2f53303041001edee7739dc4af1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-19.src.r… 24d40081aa2644a336279ecae878c1f3 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-9… b676506791a1d5ddbc97295443092e4b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-9… a9974f26f6a7280a71228b61b6a861cc source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-99.src.r… 8bb653a4f779a125498f47dbaff0dc2f SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-86.i386… 6ecfb4d3546645282d62e65c3aec04ad patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-86.i386… 1dbd101b9b7619de55d264191465b701 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-86.src.rpm 7577ca638434ebe20406bfab85ec72ad SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/d2/openssl-devel-0.9.6b-158.i38… 0c2b11b0002d077219842e2b8e528af1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-158.src.rpm 3485c804df9a381131462ba97697d6fb SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/d2/openssl-devel-0.9.6a-83.i386… 4c206037061e780fdbc20254cfdc9e17 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-83.src.rpm 5a753ed3919767077292f96728de3870 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/d2/openssl-devel-0.9.6b-90.spa… 40e0b55f40c1dfd110d3494240c2b533 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/openssl-0.9.6b-90.src.rpm 6faf5fe6fa004eb5515c1777886c49c9 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d2/openssl-devel-0.9.6b-151.ppc.… f3a7e90f86c2c095ff3eae5d75a1a3c8 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-151.src.rpm 7792ee3de5ef30c66c90a5fe43ee4eb2 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - gdm2 Due to a bug in GDM it is possible for local users to read any text file on a system by creating a symlink from ~/.xsession-errors. New packages are available on our FTP servers. - whois The client tool whois is vulnerable to several buffer overflows while processing its command-line arguments. In conjunction with using untrusted data from remote sources as input, like using whois in a CGI script and so on, this buffer overflows may be abused to compromise a system. New packages are available on our FTP servers. - postgresql The SQL database server postgresql of version 7.3.x prior 7.3.4 is vulnerable to buffer overflow attacks. New packages will be available soon. ______________________________________________________________________________ 3) 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.0.7 (GNU/Linux) iQEVAwUBP3sLUXey5gA9JdPZAQHR6gf+KcmkRZQ8hrjrFt9vP8SZmZJkO8ZjiVX4 js+qeRyIJCf0juZ5dI+I5FGkoaeifNAnuDPDFrMAwIZXF+tgDaLaQ9/nf6r+vZef Ri5wed4B588E7M0GGsvm3guzGSmkOJnwx+Q6aiFo7Sh98LBHUJ/xF2OerSo6Lz3Q k527BCA/EdF9AqlVKuzDynq9HIUiHhbG8ZqHZCNQJMKwOUFPbnhNoTGc2+i/oMeg 0MHSreVr0N9ThUcCVENe8tjzMqNEuTWKe2mIpcMM0dyz9gY10H1zFn3heEHglsCP xrFYt0mfPf5QNVtk2zq1OykKhgvi5vOdsKQ58LxqsFVBJ3N5xQswKw== =byxR -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de>, SuSE Linux AG, Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- ... bring the pieces back together, we discover communication... - Maynard James Keenan

1 0

New Openssl Vulnerability
by Ferdinand Schmid 01 Oct '03

01 Oct '03

HI, Are SuSE versions of openssl vulnerable to this ASN.1 issue? http://www.kb.cert.org/vuls/id/935264 I understand that SuSE backported the recent patches to 0.9.6 so we may not be affected. However, like Roman said in a previous post - we don't like to guess ;) Thanks, Ferdinand -- Ferdinand Schmid Architectural Energy Corporation Celebrating 21 Years of Improving Building Energy Performance http://www.archenergy.com

2 1

7.3 Kernel Update
by Ulrich Schneider 01 Oct '03

01 Oct '03

Hi ! i´m into updating the Kernel 2.4.10-4GB #1 Mon Nov 5 on a Suse 7.3 System to 2.4.18-279 ... As far as good ... reading Step 4 from http://www.suse.de/de/security/2003_034_kernel.html "The variable INITRD_MODULES .... The variable should contain your scsi adapter (if any) or filesystem driver modules." cat /etc/rc.config | grep INITRD INITRD_MODULES="eepro100 3c90x 3c90x" Shows only the three NIC´s but no scsi adapter or filesystem module. Is it safe to update the kernel? Sorry for being dumb today ... but it confused me quite a litte bit. Thanks Uli

3 3

Traffic analyzing | printing traffic
by BLeonhardt＠analytek.de 01 Oct '03

01 Oct '03

Hi, does any rule allow me to analyze how much traffic is going through my network for printing ? yours, bruno

1 0

Re: [SLE] Re: [suse-security] root login disabled for KDM - SOLVED
by Bob Pearson 01 Oct '03

01 Oct '03

On Wednesday 01 October 2003 7:57 am, Joe Morris (NTM) wrote: > >I have remote login and shutdown disabled via "Control Center->System > >Administration->Login Manager". System UID set to Below 0 and Above > > 65000. "unhidden with every hidden but root (before I had Below 500 and > > had "Selected only" which included "root"). > > Check to make sure /opt/kde3/share/config/kdm/kdmrc is a symlink to > /etc/opt/kde3/share/config/kdm/kdmrc. The control Center edits the > /etc/...file, but kdm reads the opt...file, so these need to be the > same. Often, an update will mv the symlink and install a default kdmrc > in the opt... replacing the one you see in CC. Check it out. Thanks. This was half the solution. It was NOT a symlink. Thanks also to Manfred Hollstein who wrote: --------------------------------------------------------------------------------------------- Make sure to set the following in /etc/opt/kde3/share/config/kdm/kdmrc in section [X-*-Core]: AllowRootLogin=true ------------------------------------------------------------------------------------------- I had multiple (well, two) [X-*-Core] sections but only the last mattered. Setting AllowRootLogin=true and making the symlink fixed the problem. Thanks to all. Regards, Bob Pearson

1 0

AW: [suse-security] root login disabled for KDM (KDE 1.4.1)
by Ulrich Roth 01 Oct '03

01 Oct '03

Hi Bob, > Unable to login to root via KDM. Message is "root logins are > not allowed". This has to do with the configuration of X. In the SuSE support database there is an abstract about this subject. Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth at impact dot de

1 0

SuSE Security Announcement: mysql (SuSE-SA:2003:042)
by krahmer＠suse.de 01 Oct '03

01 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: mysql Announcement-ID: SuSE-SA:2003:042 Date: Wed Oct 1 12:12:38 CEST 2003 Affected products: 7.2, 7.3, 8.0, 8.1, 8.2 SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7, 8 SuSE Linux Office Server UnitedLinux 1.0 Vulnerability Type: remote code execution Severity (1-10): 5 SuSE default package: no Cross References: - Content of this advisory: 1) security vulnerability resolved: Buffer overflow in mysql. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - OpenSSL 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information A remotely exploitable buffer overflow within the authentication code of MySQL has been reported. This allows remote attackers who have access to the 'User' table to execute arbitrary commands as mysql user. The list of affected packages is as follows: mysql, mysql-client, mysql-shared, mysql-bench, mysql-devel, mysql-Max. In this advisory the MD5 sums for the mysql, mysql-shared and mysql-devel packages are listed. To be sure the update takes effect you have to restart the MySQL server by executing the following command as root: /usr/sbin/rcmysql restart 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. i386 Intel Platform: SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-3.23.55-22.i586.… 41e8d3781aeedd2e48837293d261f9e2 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-shared-3.23.55-2… b75bdea7f484305c62415cd7412151af ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-devel-3.23.55-22… 264920dc6e1def4e26253cc3d82f2fc7 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-3.23.55-22.i586.… 82bac86826eb08ccf8c3204a792e0df1 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-shared-3.23.55-2… ea14dd33b2e390009513209e71229cd3 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mysql-devel-3.23.55-22… b8e64deab45bdd05657a5447b4e279eb source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/mysql-3.23.55-22.src.rpm fd33faf5fe7efc9f9c5871db37ea88b4 SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-3.23.52-106.i586… e7488a05d07282bbd8317f834c24f0d4 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-shared-3.23.52-1… e6db8d49932368487a334d803572ed4e ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-devel-3.23.52-10… 9c6c4ab2b8a461ca391a2453d05d9b71 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-3.23.52-106.i586… 37960d363c09a1123c25b11d6a753968 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-shared-3.23.52-1… 77d66503d21447bd1dd8339463c7b25b ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mysql-devel-3.23.52-10… c747e07c307e9619cf04a3e2c8cc369f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/mysql-3.23.52-106.src.r… 952c96bc22740b252e151c27537e5c1b SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-3.23.48-81.i386.rpm 7126396c99deb931dda869fdc8e5e6ef ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-shared-3.23.48-81.i38… 6cfa50d58f7b23201f2056d6097c4161 ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap3/mysql-devel-3.23.48-81.i386… 23d978a491c8a0a0035142276ae9c806 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-3.23.48-81.i386.patch… 49833c754e880fba15e579ad32d6861c ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap2/mysql-shared-3.23.48-81.i38… 3eba782210bf2e3a714616571bea0066 ftp://ftp.suse.com/pub/suse/i386/update/8.0/ap3/mysql-devel-3.23.48-81.i386… 9d6d58e8da20ea06bfd3207c44925190 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/mysql-3.23.48-81.src.rpm bc8db10701bdaee4da9776a6dc49fc29 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap3/mysql-3.23.44-28.i386.rpm f3171ff82e6d3fbf9913cfb58d984602 ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap2/mysql-shared-3.23.44-28.i38… db2fe45728f6073f15c6440538926828 ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap3/mysql-devel-3.23.44-28.i386… 278a0338ed3a6ae65c7328f422f7abfc source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/mysql-3.23.44-28.src.rpm c1076bca4b5a7d750f72811c097e92fa SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap3/mysql-3.23.37-62.i386.rpm 2b5af68cb036119322a8a666fa68046b ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap2/mysql-shared-3.23.37-62.i38… d1f95967eb77ff7b8761ec27795cb740 ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap3/mysql-devel-3.23.37-62.i386… e8cd7dda9473259239458b5e008c6924 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/mysql-3.23.37-62.src.rpm e3c0693bda7d898ffc5bfb8f23478e7e Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap3/mysql-3.23.44-24.sparc.rpm 52a66dfd5f2f330240dab5e59c412ef7 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap2/mysql-shared-3.23.44-24.sp… 6060be5ff51994e0ab73e8afc7ba2f26 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap3/mysql-devel-3.23.44-24.spa… 802c951032a42b1b21f51ab53af502c9 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/mysql-3.23.44-24.src.rpm 350c8fcc5522c08ca9096803cc34dd42 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap3/mysql-3.23.44-32.ppc.rpm 4dfbca3cbc9e9a3f8f36ab19a7bb4093 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap2/mysql-shared-3.23.44-32.ppc.… 068cbab05a37e74b9f57abcae7eb6b64 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap3/mysql-devel-3.23.44-32.ppc.r… c897ad4fa5a724c11efabbecfdd929c4 source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/mysql-3.23.44-32.src.rpm aa219acd13b73c45e2b418e8df03a1ee ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - OpenSSL Critical bugs within the ASN.1 parsing routines have been reported recently. We are currently building new packages and will notify you in a separate advisory when the packages are available. ______________________________________________________________________________ 3) 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.0.7 (GNU/Linux) iQEVAwUBP3q+Jney5gA9JdPZAQEanQf+M0uzKuBuPf7EGBNql8hW5P8XWtVjABiv y7ngIxjah/vACuyTMdPzeMmu+yEdfejCc5jtyYEG0cahxJGpUQOLnJ6jyyDjw+S8 ic+UJ96YZ4j2FKplHaNtGgTpDFUmFtUXg+07vQ76fzfWM8iL1HQKQcFGFuHIauwi 3Ei26HHp8dgRAAVqTzCuEmlOgUkHKTSn4xLbwmdYyDoY9aRtkQ6d7hdN9sOPj7pp p0jlf4I3Xut6fqLJ/4ZbCVI4V1xABG9x+2XagBRAfzauxvLWOfpdrAGRFdX66k14 OvQo58dMxs7pqsubhRtFcYGQROdIjpKLbLSLaLbsypqSOkJrj8ibIQ== =U3Dc -----END PGP SIGNATURE-----

1 0

root login disabled for KDM (KDE 1.4.1)
by Bob Pearson 01 Oct '03

01 Oct '03

Environment: 8.2 Suse Professional i386 (athlon kernel-source-2.4.20.SuSE-100 ) KDE 3.1.4 from SuSE supplementary directory KDM RPM: kdebase3-kdm-3.1.4-34 /etc/passwd entry for root root:x:0:0:Konqi:/root:/bin/bash The name Konqi as root was added with a PNG file for KDM to display, cute little 64x64 pixel 3D dragon that he is. I have remote login and shutdown disabled via "Control Center->System Administration->Login Manager". System UID set to Below 0 and Above 65000. "unhidden with every hidden but root (before I had Below 500 and had "Selected only" which included "root"). Unable to login to root via KDM. Message is "root logins are not allowed". Nothing in /var/log about the attempt but this: Oct 1 06:33:34 cueball resmgr[1227]: accepted connection from user root Oct 1 06:33:34 cueball resmgr[1227]: disconnect from root # cat /etc/pam.d/login #%PAM-1.0 auth requisite pam_unix2.so nullok #set_secrpc auth required pam_securetty.so auth required pam_nologin.so #auth required pam_homecheck.so auth required pam_env.so auth required pam_mail.so account required pam_unix2.so password required pam_pwcheck.so nullok password required pam_unix2.so nullok use_first_pass use_authtok session required pam_unix2.so none # debug or trace session required pam_limits.so I suspect something wrong with my PAM configuration. I did no editing explicitly of these files. There is a /etc/pam.d/xdm but not a /etc/pam.d/kdm "login root" from command line fails and goes away before an error can be detected. "su - root" works. Anyone know what file I have to tweak or what I am doing wrong? TIA for any help. Regards. Bob Pearson -- I am unique and special, just like everyone else.

1 0

SuSE Security Announcement: lsh (SuSE-SA:2003:041)
by krahmer＠suse.de 01 Oct '03

01 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: lsh Announcement-ID: SuSE-SA:2003:041 Date: Wed Oct 1 10:24:45 CEST 2003 Affected products: 8.0, 8.1, 8.2 Vulnerability Type: remote code execution Severity (1-10): 5 SuSE default package: yes Cross References: - Content of this advisory: 1) security vulnerability resolved: Buffer overflow in lsh. problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - node - proftp - OpenSSL 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information LSH is the GNU implementation of SSH and can be seen as an alternative to OpenSSH. Recently various remotely exploitable buffer overflows have been reported in LSH. These allow attackers to execute arbitrary code as root on un-patched systems. LSH is not installed by default on SuSE Linux. An update is therefore only recommended if you run LSH. Maintained SuSE products are not affected by this bug as LSH is not packaged on maintained products such as the Enterprise Server. For the updates to take effect execute the following command as root: /usr/sbin/rclshd restart 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. i386 Intel Platform: SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/lsh-1.5-114.i586.rpm 798f52402cda6c7e1733aed15bf0d9cb patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/lsh-1.5-114.i586.patch… 9308cdb133d2311a9dc4a10bbf613501 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/lsh-1.5-114.src.rpm 1e1b5beac002cf51d1eea0277934a69d SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/lsh-1.4.2-73.i586.rpm b5ff8ba104623fe9a77705154aad92f7 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/lsh-1.4.2-73.i586.patc… 6341acd3fe513921b7123d7c1d98cc43 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/lsh-1.4.2-73.src.rpm 0a2b95e911f8760009ad0d5b2fd7618e SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/lsh-1.3.5-188.i386.rpm bccfd85985bab8a324b25c1b2443bf2b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/lsh-1.3.5-188.i386.patch.r… 8a232720cb0a4b35d0899e9c6a4e80ae source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/lsh-1.3.5-188.src.rpm 8e3e30b134b12400559152bb5c53d0f8 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - node A format string vulnerability has been fixed in the new node packages available on our ftp servers. An update is recommended if you use this package. - proftp A off-by-one buffer overflow has been fixed in the proftp packages for SuSE Linux 7.2 and 7.3. Note that the bug that was fixed is different from the 'ASCII File Transfer Buffer Overrun Vulnerability' (CAN-2003-0831). The proftp packages shipped by SuSE are not affected by CAN-2003-0831. - OpenSSL Critical bugs within the ASN.1 parsing routines have been reported recently. We are currently building new packages and will notify you in a separate advisory when the packages are available. ______________________________________________________________________________ 3) 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.0.7 (GNU/Linux) iQEVAwUBP3qgJHey5gA9JdPZAQEutAf+L935tRS8xmYZFFjUhQdd5MHWOGCanB4I 8WabNy77o6SbztDcskEUUr0+SKjDQjqEEndY4tKFlxCDNWItxJbEYmDtLB2x2CTE dCZSqoJVNxeySWRfYMs8fmC3nEQCgVYgIqhpFhi/VaP89d5/IvITwnDOWOMej0nF pj2emi0cOz62KKSlq64D+uDZJxtMdg0KrVAO15O5TQJvQnze2CkEuWMivvVvmDML jGlTzznhvVey0Czc9LNNK6VPD/i+6zHCM/+XU/1b3Gl4gRAzLjebBsHzjW45bVAu Ed+Z0EPVi/ArzfFJ0P7CcZgnYuTOoqMAJMWagW5O+4pnUpny2aFS/w== =Gv9P -----END PGP SIGNATURE-----

1 0

Re: Re: Re: Re: Re: [suse-security] Dial timeout on isdn router with ip-tables logging
by BLeonhardt＠analytek.de 01 Oct '03

01 Oct '03

I will test / check that -- but I guess he won't hangup anyway ... bruno Keith Roberts <keith(a)topaz5.worldonline.co.uk> schrieb am 01.10.2003 12:00:06: > > > Hmm... > > I'm really not sure what to suggest next here... > > You have got me stumped with this one Bruno. > > > Just a few more thoughts. > > > Does your router have any blocking rules in it? > > If you turn IPTables logging off (not the firewall itself) > > does your ISDN script work correctly? > > > Regards - Keith > > > > > > On Wed, 1 Oct 2003 BLeonhardt(a)analytek.de wrote: > > > > > > > > > > > Good morning ;-) > > > > I am not block all outgoing traffic from the local box just the dns-requests > coming from the box itself - I have bind8 running on the machine. > > All other blocking-rules are in the forward chain ... so if I run win ther > won't be a connection established all 3 min. :-) ... default policy (from the > linux-box) for outgoing connections is allow (accept) ... > > > > bruno > > > > > > Keith Roberts <keith(a)topaz5.worldonline.co.uk> schrieb am 30.09.2003 17:30:55: > > > > > > > > > > > On Tue, 30 Sep 2003 BLeonhardt(a)analytek.de wrote: > > > > > > > > > > > > > > > > > > > > > > > Yes, that's it. > > > > > > > > I don't know why... all possible outgoing traffic has been blocked ( for > > > testing ) but he will not hangup... :-( > > > > > > > > > > That MAY be your problem. > > > > > > I'm NOT using ISDN, but on my dial-up modem connection, when > > > I hit CTRL-C, to kill wvdial, there are a few packets sent > > > out from my modem, to cleanly terminate the dial-in > > > connection. > > > > > > Sometimes my dial-in connection will stay live, if I do NOT > > > finish wvdial in the correct manner. eg CTRL-Z instead of > > > CTRL-C. > > > > > > If you are blocking ALL outgoing packets, this may be why > > > the connection stays open - because the signal to terminate > > > your ISDN connection is not reaching your ISDN service > > > provider. > > > > > > > > > Here's my 56K modem start sequence: > > > > > > topaz:/home/keith # wvdial > > > --> WvDial: Internet dialer version 1.42 > > > --> Initializing modem. > > > --> Sending: AT&F0&C1 > > > AT&F0&C1 > > > OK > > > --> Modem initialized. > > > --> Sending: ATDT1470 0808 9933 030 > > > --> Waiting for carrier. > > > ATDT1470 0808 9933 030 > > > CONNECT 38400 > > > --> Carrier detected. Starting PPP immediately. > > > --> Starting pppd at Tue Sep 30 15:20:53 2003 > > > --> pid of pppd: 1255 > > > --> pppd: Using interface ppp0 > > > --> pppd: local IP address 62.64.219.8 > > > --> pppd: remote IP address 213.120.78.69 > > > --> pppd: primary DNS address 212.74.114.193 > > > --> pppd: secondary DNS address 212.74.112.66 > > > --> pppd: Script /etc/ppp/ip-up run successful > > > --> Default route Ok. > > > --> Nameserver (DNS) Ok. > > > --> Connected... Press Ctrl-C to disconnect > > > > > > [1]+ Stopped wvdial > > > > > > > > > I've just checked this by hitting CTRL-Z. > > > > > > My line is still live! > > > > > > I now have to turn my modem OFF to break the connection. > > > > > > > > > Now, trying to redial I get: > > > > > > > > > topaz:/home/keith # wvdial > > > --> WvDial: Internet dialer version 1.42 > > > --> Cannot open /dev/ttyS1: Device or resource busy > > > --> Cannot open /dev/ttyS1: Device or resource busy > > > --> Cannot open /dev/ttyS1: Device or resource busy > > > > > > Because the wvdial script was not stopped correctly. > > > > > > Now I kill the bash shell in KDE to remove the device lock, > > > and free up the modem! > > > > > > > > > HTH - Keith > > > > > > > > > > > > > > > > >

1 0

Re: [suse-security] Secure Mail Server
by Marc Samendinger 01 Oct '03

01 Oct '03

On Tue, Sep 30, 2003 at 04:24:23PM +0100, João Reis wrote: > Hi to all. Hi João, > I would like to implement a secure Mail server. > > This is an internal mail server and belongs to the network behind the > external firewall. > > I also would like to have a system which permits external users to > connect to the internal mail > server in order to fetch their internal mail or to send their mail > througth this server (POP with SSL and SMTP). ^^^^^^^^^^^^^^^^^^^^^ IMHO this should read "((POP and SMTP) with SSL)" :) And don't forget to use smtp-auth or pop-before-smtp, so you don't end up as an open relay. > João Reis marc

1 0

Re: Re: Re: Re: [suse-security] Dial timeout on isdn router with ip-tables logging
by BLeonhardt＠analytek.de 01 Oct '03

01 Oct '03

Good morning ;-) I am not block all outgoing traffic from the local box just the dns-requests coming from the box itself - I have bind8 running on the machine. All other blocking-rules are in the forward chain ... so if I run win ther won't be a connection established all 3 min. :-) ... default policy (from the linux-box) for outgoing connections is allow (accept) ... bruno Keith Roberts <keith(a)topaz5.worldonline.co.uk> schrieb am 30.09.2003 17:30:55: > > > On Tue, 30 Sep 2003 BLeonhardt(a)analytek.de wrote: > > > > > > > > > > > Yes, that's it. > > > > I don't know why... all possible outgoing traffic has been blocked ( for > testing ) but he will not hangup... :-( > > > > That MAY be your problem. > > I'm NOT using ISDN, but on my dial-up modem connection, when > I hit CTRL-C, to kill wvdial, there are a few packets sent > out from my modem, to cleanly terminate the dial-in > connection. > > Sometimes my dial-in connection will stay live, if I do NOT > finish wvdial in the correct manner. eg CTRL-Z instead of > CTRL-C. > > If you are blocking ALL outgoing packets, this may be why > the connection stays open - because the signal to terminate > your ISDN connection is not reaching your ISDN service > provider. > > > Here's my 56K modem start sequence: > > topaz:/home/keith # wvdial > --> WvDial: Internet dialer version 1.42 > --> Initializing modem. > --> Sending: AT&F0&C1 > AT&F0&C1 > OK > --> Modem initialized. > --> Sending: ATDT1470 0808 9933 030 > --> Waiting for carrier. > ATDT1470 0808 9933 030 > CONNECT 38400 > --> Carrier detected. Starting PPP immediately. > --> Starting pppd at Tue Sep 30 15:20:53 2003 > --> pid of pppd: 1255 > --> pppd: Using interface ppp0 > --> pppd: local IP address 62.64.219.8 > --> pppd: remote IP address 213.120.78.69 > --> pppd: primary DNS address 212.74.114.193 > --> pppd: secondary DNS address 212.74.112.66 > --> pppd: Script /etc/ppp/ip-up run successful > --> Default route Ok. > --> Nameserver (DNS) Ok. > --> Connected... Press Ctrl-C to disconnect > > [1]+ Stopped wvdial > > > I've just checked this by hitting CTRL-Z. > > My line is still live! > > I now have to turn my modem OFF to break the connection. > > > Now, trying to redial I get: > > > topaz:/home/keith # wvdial > --> WvDial: Internet dialer version 1.42 > --> Cannot open /dev/ttyS1: Device or resource busy > --> Cannot open /dev/ttyS1: Device or resource busy > --> Cannot open /dev/ttyS1: Device or resource busy > > Because the wvdial script was not stopped correctly. > > Now I kill the bash shell in KDE to remove the device lock, > and free up the modem! > > > HTH - Keith > > > >

1 0