February 2004 - openSUSE Security - openSUSE Mailing Lists

Postfix pop3 Login problems
by Patrick Nolan 20 Feb '04

20 Feb '04

I just installed SuSE 9.0 with postfix 2.0.14. I can not seem to log in using Outlook. I've been running Postfix on another server for a couple of years now on a red had 7.3 server with courrier IMAP and have had no problems. It is set up with Maildir instead of /var/mail, and was wondering if this might be part of the problem. I am pretty sure qpopper is running on my machine. I haven't been using ssh, I know that I probably should. As when I started working with Linux, there appears to be a central bit of information that I am missing that would make this all be easier. Does 9.0 come with only SSH enabled? And if it does what would be the first thing that I need to do or read to adapt to this change, and to be able to access my email from a windows Outlook client? Thanks, Patrick HYPERLINK "http://www.nappco.com/" \n ISO 9001:2000 Certified Patrick Nolan HYPERLINK "http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=11260+Hempstead+Highway&csz= Houston%2C+TX+77092&country=us" \n11260 Hempstead Highway Houston, TX 77092 HYPERLINK "mailto:pnolan@nappco.com" \npnolan(a)nappco.com HYPERLINK "http://www.nappco.com/" \nwww.nappco.com tel: fax: mobile: 713-688-2521 713-957-4315 713-530-4934 HYPERLINK "http://www.plaxo.com/signature" \nSignature powered by Plaxo HYPERLINK "http://www.plaxo.com/signature" \nWant a signature like this? HYPERLINK "https://www.plaxo.com/add_me?u=21475065754&v0=438582&k0=1249127699" \nAdd me to your address book... --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.590 / Virus Database: 373 - Release Date: 2/16/2004

2 1

SuSEfirewall2 and FW_FORWARD_MASQ
by Ralf Ronneburger 20 Feb '04

20 Feb '04

Hi everyone, I have a setup where I need to forward and masquerade traffic to an internal box from my SuSE 9.0. I use the following: FW_FORWARD_MASQ="0/0,10.0.0.1,tcp,22,22,XXX" where XXX. is my external IP. But with this rule nothing works, I can only connect to the box when I add: FW_MASQ_NETS="10.0.0.1/32" But that opens the whole internet for the internal box. Is there a way to prevent this in SuSEfirewall2 or do I need to add a custom rule? As far as I see it FW_MASQ_NETS can only deal with destination-ports, not with source ports, which is very regrettable. Greetings, Ralf

1 0

Re: [suse-security] How to block MSN using SuSEfirewall2?
by Augusto S Amaya 20 Feb '04

20 Feb '04

Yeah . That´s the best option... IPTABLES! -------------------------------------------------------------- Augusto S Amaya Administrador Certif. Servidores Linux - Dto. de Produccion de Sistemas Perón 407 Conmutador: 6329-0000 Tel/Interno: 4370/4371/4372 Fax: augusto.s.amaya(a)bancogalicia.com.ar http://www.bancogalicia.com.ar Joel Luth <joel(a)luths.net> Para: suse-security(a)suse.com cc: 20/02/2004 03:47 Asunto: Re: [suse-security] How to block MSN using SuSEfirewall2? I imagine you could cron an iptables command (well two, one to accept and then one to deny an hour later). I'm not familiar with SuSEfirewall2, not sure if raw iptables commands are compatible with it. Joel Michael James wrote: > My teenage daughter spends all her time at home chatting on MSN. > It distracts her completely from being civil to her family > and actually concentrating on her homework. > > It's hard to ration because she does (sometimes) > use her computer for study. > If I just turn off her access to the internet > she will appear with some reason she needs to connect. > > How can I turn on a block on MSN > so there is only 1 hour a day it works? > > The house server (Suse8.2 soon to be 9.0) > has the ADSL connection > and runs SuSEfirewall2, NAT, squid, DNS, etc. > > Thanks for any pointers, > michaelj > > PS: The solution need not be very watertight, > I would be delighted if she learned enough > about networks to circumvent it. > -- 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

offtopic: startup item / daemon / chron
by J Fischer - UIA 20 Feb '04

20 Feb '04

Hi there, This is a newb question. I've found it hard to phrase appropriate queries about it for web / usenet searches and hope someone can set me straight. I want to create an action on bootup that starts our site search engine. They tell you how to get it running as a daemon from the shell and I am stuck on how to get this to happen everytime the machine boots. I've tried the bootup and chron sections of webmin but my syntax doesn't work. The search engine needs to be invoked from a specific directory so the command structure would be like this: change directory to xyz ./command and parameters any advice appreciated joel

3 2

RE: [suse-security] How to block MSN using SuSEfirewall2?
by Ray Leach 20 Feb '04

20 Feb '04

On Fri, 2004-02-20 at 09:19, Abacus Infomail wrote: > Ray, > > Unless there's a reason not to..... > > Why not post it to the list for all to see..... > > I for one would welcome such a critter as I prepare for the same thing at > our Bible School. > OK, here it is ... I do not use SuSEFirewall2, I rather use my own custom shell script, but you an add these rules to the susefirewall2_custom file (whatever it is called) with a little modification. In the archive are the following files, and this is where I put them: File My Location (change if you want to) ftpallowedinternal /etc/firewall nightftpallowed /etc/firewall iptables-firewall.rules /etc/firewall switchftp.sh /etc/firewall crontab.txt in yer crontab ... rc.d.firewall.sh /etc/rc.d with a link in rc3.d and rc5.d If you put the files in a different directory, just check inside them and change the patch as necessary (just in rc.d.firewall.sh and switchftp.sh) ... Enjoy! Ray > <snip> > > Michael James wrote: > > > > > My teenage daughter spends all her time at home chatting on MSN. > > > It distracts her completely from being civil to her family > > > and actually concentrating on her homework. > > > > > > It's hard to ration because she does (sometimes) > > > use her computer for study. > > > If I just turn off her access to the internet > > > she will appear with some reason she needs to connect. > > > > > > How can I turn on a block on MSN > > > so there is only 1 hour a day it works? > > > > > > The house server (Suse8.2 soon to be 9.0) > > > has the ADSL connection > > > and runs SuSEfirewall2, NAT, squid, DNS, etc. > > > > > > Thanks for any pointers, > > > michaelj > > > > > > PS: The solution need not be very watertight, > > > I would be delighted if she learned enough > > > about networks to circumvent it. > > > -- -- Raymond Leach <raymondl(a)knowledgefactory.co.za> Network Support Specialist http://www.knowledgefactory.co.za "lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import" Key fingerprint = 7209 A695 9EE0 E971 A9AD 00EE 8757 EE47 F06F FB28 --

1 0

hi
by wiersig-ml＠dns.glamus.de 20 Feb '04

20 Feb '04

that's funny

2 1

Re: [suse-security] Off Topic : Lost GB in a Dual Boot System ?!
by remote 20 Feb '04

20 Feb '04

Hi Christian, thanks for the reply. I think I have the solution by now. When I bought the notebook, it came only with the Windows Recovery CD, so I suspect that the missing 6 GB are some sort of inaccessible system backup where a fresh Windows is stored in case you want/have to use the Recovery CD. I posted my question in some other forums, and they agree with my theory. Also, a friend of mine, who has a similar system, is also missing around 6 GB, and WinXP is the only OS on his system. Sucks, hm ? Right now, I am considering reinstalling both OS from scratch (I have a normal WinXP that I could use), but frankly, I don´t have the time and inclination to do so. I was aware of the "Marketing Accounting" of hard drive capacity, though, never that that was my problem. You´re right though, I wonder, why they don´t do it with RAM ? Thanks, Jörg PS : Regarding the my real name, I signed the last mail with it, I just use this address to distinguish list mails from my normal mail.:)

1 0

SUSE Security Announcement: Linux Kernel (SuSE-SA:2004:005)
by thomas＠suse.de 20 Feb '04

20 Feb '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: Linux Kernel Announcement-ID: SuSE-SA:2004:005 Date: Wednesday, Feb. 18th 2004 23:05 MET Affected products: 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: local privilege escalation Severity (1-10): 6 SUSE default package: yes Cross References: CAN-2004-0003 CAN-2004-0010 CAN-2004-0077 CAN-2004-0075 Content of this advisory: 1) security vulnerability resolved: - do_mremap: insecure memory page management - several local denial-of-service attacks problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - netpbm - zebra - susehelp - mod_gzip - mod_auth_shadow - mod_python - mutt - mailman - clamav - XFree86/xf86 - libxml2 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Another bug in the Kernel's do_mremap() function, which is unrelated to the bug fixed in SuSE-SA:2004:001, was found by Paul Starzetz. The do_mremap() function of the Linux Kernel is used to manage Virtual Memory Areas (VMAs) which includes moving, removing and resizing of memory areas. To remove old memory areas do_mremap() uses the function du_munmap() without checking the return value. By forcing do_munmap() to return an error the memory management of a process can be tricked into moving page table entries from one VMA to another. The destination VMA may be protected by a different ACL which enables a local attacker to gain write access to previous read-only pages. The result will be local root access to the system. Additionally to the bug mentioned above some other bugs were fixed (depending on architecture) that can cause local denial-of-service conditions: - Vicam USB driver: CAN-2004-0075 + denial-of-service due to problem while copying data from user to kernel space - Direct Render Infrastructure: CAN-2004-0003 + denial-of-service due to integer overflow + needs r128 card and console to be exploited - ncpfs/ncp_lookup: CAN-2004-0010 + buffer overflow with the probability to gain root - execve(): + malformed elf binaries can lead to a local denial-of-service attack 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, you decide if the paragraph is needed for you or not. Please read through all of the steps down to the end. 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 to complete successfully. **** Step 1: Determine the needed kernel type Please use the following command to find the kernel type that is installed on your system: rpm -qf /boot/vmlinuz The following options are possible (disregarding the version and build number following the name, separated by the "-" character): k_deflt # default kernel, good for most systems. k_i386 # ke 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 **** Step 2: Download the package for your system Please download the kernel RPM package for your distribution with the name starting as indicated by Step 1. The list of all kernel rpm packages is appended below. Note: The kernel-source package does not contain any binary kernel in bootable form. Instead, it contains the sources that the binary kernel rpm packages are made 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 these 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 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 applied. If you run SUSE LINUX 8.1 and haven't applied the previous kernel update (SUSE-SA:2003:034), AND use 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 being 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 have a 7.x system, you must now run the command lilo as root to initialize the lilo bootloader for your system. Then proceed to the next step. If you run a SUSE LINUX 8.x or a SLES8 system, there are two options: Depending on your software configuration, you have 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 applied to 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 are complete, then reboot using the command shutdown -r now or init 6 Your system should now shut down and reboot with the new kernel. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. There is no workaround known. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, to apply the update use the command "rpm -Fhv file.rpm". Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Due to unfinished functional evaluation testing the 8.0 kernel will be released within the next few days. Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-192.i58… ecfbe03e394832b72a3b9c82eb126064 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-192.src.… 1bd070771a5dd094aa08cf38b1a044b9 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-192.i586.… c00538019717f0eb2c50d67468daf0ec source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-192.src.rpm 9f8882b0c598e160382640c0b0764239 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp4G-2.4.21-192.i58… aac234b34178e1027f0295efc0e59b21 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp4G-2.4.21-192.src.… 618f890d3802b98b08f69e99c608f88d ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_um-2.4.21-192.i586.r… ac6b4b271bdb7db1c6e906d30feeb509 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_um-2.4.21-192.src.rpm 73abafe183680051e36b0e06044dfaf1 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-192.i5… 90e0a63318e67e4d80bbf599e092a9e9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-192.src… 34871bc1783b214eb1abf1a3b08f7b08 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-1… 2cb5ef97c015d72a911c2a99b6517e09 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-19… 24933c7c1adf988494e98fd8da7895a9 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-105.i58… 1782b12abf777cea56e3093a6afd77d3 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-105.src.… 1851210f8db7acd6f0396a774032128e ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-105.i5… 63a528e967ea95c94357cbdb24b539fc source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-105.src… 52497095cbf87ec168d0c7babb3ee416 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-105.i586… 3743e2d1f856541b9baf2c5f629a7ee6 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-105.src.r… 502677799b511df2491cb87c9c35b997 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-105.i586.… d0711272b2d4de9a32b86ae83ae6a3e0 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-105.src.rpm bb323ee3ca8654d9f547a0ba3d2ad430 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… 2e9eef765ef10fcdfb17d96f6042ecdb source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.Su… 2251c37b3ead38d341ca3fc1558f23ba SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-189.i58… 268986c15003f47539f97847ca0a71ba source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-189.src.… 19a256181b4ccf094db7a1af53a286cf ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-189.i5… d673923c542d3b0cd7f383f33b8a1818 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-189.src… 96e3687da59d0e79246df6e385f0443d ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_psmp-2.4.21-189.i586… 165f881a57d953eeb078b82ff5c1c745 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_psmp-2.4.21-189.src.r… 21fa38976e6dedbaa11e1a699b539021 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_smp-2.4.21-189.i586.… e7126b41226074c4bed437e374055e9c source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_smp-2.4.21-189.src.rpm ed4457abe00add59dd62185bfd560ec0 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-1… 5e6d14000e873c83916871a284e34032 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kernel-source-2.4.21-18… a42879b3e259630f0ffcc48e72b67385 Opteron x86_64 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-201… f751f7c38b66fef72497cd20efe93e6d source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-201.sr… 7e4a005094d9db401fcff09edf02f8e3 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-201.x… 460119617de7678ca0e81cd9cdc1b07d source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-201.src.… 54408250c4c6876d65b9e07c3633e355 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… afb38f0f8bb015110be9aab42536961f source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… d8bd2b7a61dea7e3166acf11f4bc35e0 ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - netpbm Some tools in the netpbm suite create files in an insecure manner that can lead to local privilege escalation. New packages are available on our FTP servers. - zebra Local users can send malicious netlink messages that cause denial-of-service conditions in zebra. New packages are available on our FTP servers. - susehelp The susehelp package for SuSE Linux 9.0 contained CGI scripts which allowed remote attackers to execute arbitrary commands as wwwrun user. Additionally, certain ACL entries have been added to deny execution of the susehelp CGI scripts from remote. If you update your susehelp package manually, you have to invoke the SuSEconfig command as root afterwards. You also have to restart the HTTP server for the new ACLs to take effect. New packages are available on our FTP servers. - mod_gzip (apache-contrib) The apache module mod_gzip is vulnerable to remote code execution while running in debug-mode. We do not ship this module in debug-mode but future versions will include the fix. Additionally the mod_gzip code was audited to fix more possibly security related bugs. New packages are available on our FTP servers. - mod_auth_shadow (apache-contrib) This apache module ignores account expiration dates. The update will be released together with mod_gzip. New packages are available on our FTP servers. - mod_python A remote denial-of-service attack can be triggered against the Apache web server by sending a specific query string that is processed by mod_python. New packages will be available soon. - mutt The popular email client mutt is vulnerable to a remote denial-of-service attack and maybe remote command execution. The bug can be triggered by malformed messages that overflow an internal buffer. New packages will be available soon. - mailman A remote denial-of-service attack can be triggered in mailman 2.0.x (CAN-2003-0991). New packages will be available soon. - clamav A remote denial-of-service attack can be triggered in the anti-virus scanner. New packages will be available soon. - XFree86/xf86 Several buffer overflows in the font-alias handling code can lead to local root access. Packages are built and are being tested at the moment. - libxml2 Two buffer overflows in the URI code can lead to remote system compromise. 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) iQEVAwUBQDPkWXey5gA9JdPZAQHTmgf9EqfmibSJX/PQNWghrb2qySy38n0zvyYT 5xPhPNyodcb4zAEMj3etKmyptoYnCne9CLCToJEGhqh7LwkK2KIJHXAXwwG046of vEi6Fzj+7UUPedg0mm+r/AxEyneTw8T1Wmp6K+fjYH8PRqjssrL/l1LqOgah4x7y VMJNdJzm9h/qMYXXtXZRjdX8Za+IWWja2R7Ly3suurivwEHI3zTxvxPsvNSbg9GW XnCFUI2Md4zfUi+dWwC+gTHePiHZWIOd+cgR2yIs4PN7sgtTd08iZr+ht0dQtSPz 5OjVxFcjcOwXM2/CwvD9rLoLXMsRULht/KSDsul1YuGkf8e7zat/Zg== =32A9 -----END PGP SIGNATURE-----

11 12

Off Topic : Lost GB in a Dual Boot System ?!
by remote 19 Feb '04

19 Feb '04

Hi ! I know this is entirely off topic, but maybe somebody is kind and knowledgable enough to help me anyway :) I recently installed SuSE 9.0 Prof. on a Compaq Presario B1011 laptop which came with Windows XP (Home) already preinstalled. The installation went without a glitch (except for some trouble with the graphics and sound cards, and the fact that the modem is only a softmodem :() but when it came to partitioning the hard drive, the installation routine told me that I could only create a 4GB partition for SuSE and that I should defragment the drive under Windows (NTFS) to obtain a bigger partition. I continued the installation, and after some days, defragmented the drive under Windows. Using yast2, I then reduced the Windows Partition in size to 26 GB and created another partition for SuSE, which works just fine. However, Windows now tells me that its own partition only has 20 GB, and when, under SuSE, I cd into the Windows partition and then type df, it says the same. The yast partitioning tool however, insists that the Windows partition is actually 26 GB in size. Adding up the results of the df command for all partitions accessible in SuSE, I end up with just over 30 GB, while yast says (and I know the notebook came with a 40 GB hdd) the drive has a capacity of 37 GB. My question is : Where are these missing 7 GB, and how can I get them back for Windows ? Any help would be appreciated ! Bye, Jörg

2 1

Securing internet access from a WiFi network via login
by J. Theriault 19 Feb '04

19 Feb '04

I am wondering if anyone can help me, I am trying to setup a small limited-use wireless network (web/ftp/email only) and I am trying to find the best way to limit unauthorized access to the Internet from the wireless network. WEP is not an option - I do not want to have to change any settings on a client and I want more than WEP can offer. What I would like to know is; is it possible to set up a proxy server for web/ftp/email using SuSE 8.1 Pro (or higher) that could also issue (expiring) usernames/passwords for many temporary users and force them to login before allowing them access to the Internet? Or, to put it in less words, I need: - A way to keep people off the Internet unless they are allowed. - A way to stop users from accessing services other than http/ftp/imap/pop/smtp. - A way to block certain sites. - An "easy" way to create temporary usernames/passwords for Internet access and to expire them. So, if anyone has ANY information that could help, even if it's just to "RTFM for xyz software and go away", I would greatly appreciate it. Thanks, J. Theriault administrator(a)raven-computer.de -- ~From RFC 1925; ~ (3) With sufficient thrust, pigs fly just fine. However, this is ~ not necessarily a good idea. It is hard to be sure where they ~ are going to land, and it could be dangerous sitting under them ~ as they fly overhead.

3 2