July 2000 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement: dhclient
by thomas＠suse.de 11 Jul '00

11 Jul '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: dhclient < 2.0 Date: Tue Jul 11 15:12:22 CEST 2000 Affected SuSE versions: 6.1-6.4 Vulnerability Type: remote root compromise SuSE default package: no Other affected systems: all unix systems using this package ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update it as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description The client side program of the ISC DHCP package, dhclient, does not do quoting of server messages before passing them to /sbin/dhclient-script. This script is executed with root privileges. 2. Impact Dhclient could be tricked by a rogue DHCP server to execute commands as user root. This leads to a remote root compromise of the system using dhclient. 3. Solution Update the package from our FTP server. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: (For SuSE 6.0, please use the 6.1 updates) AXP: 262677203e3b1dada23e65ae60d08264 ftp://ftp.suse.com/pub/suse/axp/update/6.3/n1/dhclient-2.0pl2-3.alpha.rpm 910097426b5771c82abf8f323086b5ba ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/dhclient-2.0pl2-3.alpha.rpm i386: 300a7c8220d3b9f65a2aef3ed4fdb7b3 ftp://ftp.suse.com/pub/suse/i386/update/6.1/n1/dhclient-2.0pl2-3.i386.rpm 7be68cd54e7fd3766b7eb36fc2e854c5 ftp://ftp.suse.com/pub/suse/i386/update/6.2/n1/dhclient-2.0pl2-3.i386.rpm 44fad0cee0cb53627ed7c507077d5d2b ftp://ftp.suse.com/pub/suse/i386/update/6.3/n1/dhclient-2.0pl2-3.i386.rpm 320d4414841e29bd08584fc5d8592d99 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/dhclient-2.0pl2-3.i386.rpm PPC: a8a19501e4821ab6c7b375972eb1e5ce ftp://ftp.suse.com/pub/suse/ppc/update/6.3/n1/dhclient-2.0pl2-3.ppc.rpm b4ea052ba25b10586cc14f6fea5b2d9f ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/dhclient-2.0pl2-3.ppc.rpm ______________________________________________________________________________ You can find updates on our ftp-Server: ftp://ftp.suse.com/pub/suse/i386/update for Intel processors ftp://ftp.suse.com/pub/suse/axp/update for Alpha processors or try the following web pages for a list of mirrors: http://www.suse.de/ftp.html http://www.suse.com/ftp_new.html Our webpage for patches: http://www.suse.de/patches/index.html Our webpage for security announcements: http://www.suse.de/security If you want to report vulnerabilities, please contact security(a)suse.de ______________________________________________________________________________ SuSE has got two free security mailing list services to which any interested party may subscribe: suse-security(a)suse.com - moderated and for general/linux/SuSE security discussions. All SuSE security announcements are sent to this list. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe to the list, send a message to: <suse-security-subscribe(a)suse.com> To remove your address from the list, send a message to: <suse-security-unsubscribe(a)suse.com> Send mail to the following for info and FAQ for this list: <suse-security-info(a)suse.com> <suse-security-faq(a)suse.com> _____________________________________________________________________________ This information is provided freely to everyone interested and may be redistributed provided that it is not altered in any way. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - ------BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12Cg== =pIeS - ------END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOWsm93ey5gA9JdPZAQHseQf9EfascZdwdTCEgeCVELHPYjERcwQeXcb8 nisoW6eXveVVR1FaVpuX/gUeh5u4WNfyBNMuYQV1p7+0gis5f59vFJ7IxFWV/TLm h24/bx7TjufPCCFW16Ye1GWrGb5TIVdC6ORYV4A4BY74sByiKazlFbtT9qAtcAjD kqmbdIFwc1b0rYIREr1WGdwr1tfNVsRUJgKdyAco+miKXGjwM8rGw415A9o1zsrI OjC3sNeDDQi64uEFyODsr/LZpt06HFu0cNif4RbPi2LEd4UTfE2CNj5WGHq7NeEM XFjQ9+fp4/m4mngAsM7/RrlHoNQ09lOdmF7Dj8jWJS4r0c2pKuDzaQ== =ksUb -----END PGP SIGNATURE-----

1 0

makewhatis bug
by Thomas Biege 10 Jul '00

10 Jul '00

Hi, a few days ago a /tmp race condition bug in the makewhatis program was posted on bugtraq. We are NOT vulnerable by this bug, because we use different code, which doesn't touch /tmp in a unsecure way. Bye, Thomas -- Thomas Biege, SuSE GmbH, Schanzaeckerstr. 10, 90443 Nuernberg E@mail: thomas(a)suse.de Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/thomas.pgp | pgp -fka" Key fingerprint = 09 48 F2 FD 81 F7 E7 98 6D C7 36 F1 96 6A 12 47

1 0

weird seccheck-0.9-35 behaviour
by Peter Nixon 08 Jul '00

08 Jul '00

Can someone tell me why "/usr/lib/secchk/security-control.sh daily" would be doing strange things... (See ps list below) I am using seccheck-0.9-35 on SuSE 6.4 with all available security options and updates. This machine also runs squid,sendmail,smtpd,AVP and BIND Any help would be appreciated ~ # ps afx PID TTY STAT TIME COMMAND 1 ? S 0:09 init [2] 2 ? SW 0:00 [kflushd] 3 ? SW 0:47 [kupdate] 4 ? SW 0:00 [kpiod] 5 ? SW 0:21 [kswapd] 6 ? SW 0:00 [md_thread] 9 ? SW 0:00 [khubd] 100 ? S 0:28 /usr/sbin/scanlogd 106 ? S 0:22 /usr/sbin/syslogd 110 ? S 0:00 /usr/sbin/klogd -c 1 137 ? S 0:22 /usr/sbin/named -u named -g named 146 ? S 0:00 /usr/sbin/atd 152 ? S 0:00 /usr/sbin/gpm -t ps2 -m /dev/mouse 156 ? S 0:03 /usr/sbin/inetd 178 ? S 0:00 /bin/su - mail -c /usr/sbin/smtp-virus 191 ? S 0:48 \_ perl /usr/sbin/smtp-virus 5689 ? S 0:00 \_ sh -c /usr/local/avp/AvpLinux /var/spool/smtpd/incoming/smtpdvI0vSs >> /var/tmp/smtpdvI0vSs.191/scanlog 5690 ? R 0:00 \_ /usr/local/avp/AvpLinux /var/spool/smtpd/incoming/smtpdvI0vSs 183 ? S 0:02 /usr/sbin/smtpfwdd -u mail -g daemon -d /var/spool/smtpd/scanned 187 ? S 0:00 /usr/sbin/sendmail -q30m -om 199 ? S 0:00 /usr/sbin/squid -sYD 200 ? S 3:05 \_ (squid) -sYD 202 ? S 0:00 \_ (dnsserver) 203 ? S 0:00 \_ (dnsserver) 204 ? S 0:00 \_ (dnsserver) 205 ? S 0:00 \_ (dnsserver) 206 ? S 0:00 \_ (dnsserver) 207 ? S 0:00 \_ (smb_auth) -W sydney -U 192.168.1.2 208 ? S 0:00 \_ (smb_auth) -W sydney -U 192.168.1.2 209 ? S 0:00 \_ (smb_auth) -W sydney -U 192.168.1.2 210 ? S 0:00 \_ (smb_auth) -W sydney -U 192.168.1.2 211 ? S 0:00 \_ (smb_auth) -W sydney -U 192.168.1.2 232 ? S 0:00 \_ (unlinkd) 218 ? S 0:05 /usr/sbin/sshd 5535 ? S 0:00 \_ /usr/sbin/sshd 5537 pts/0 S 0:00 | \_ -bash 5551 pts/0 S 0:00 | \_ su -l 5552 pts/0 S 0:00 | \_ -bash 5598 pts/0 S 0:00 | \_ tail -f /var/log/mail 5614 ? S 0:00 \_ /usr/sbin/sshd 5619 pts/1 S 0:00 \_ -bash 5634 pts/1 S 0:00 \_ su -l 5636 pts/1 S 0:00 \_ -bash 5687 pts/1 R 0:00 \_ ps afx 224 ? SL 0:10 /usr/sbin/xntpd 228 ? S 0:00 /usr/sbin/cron 10746 ? S 0:00 \_ /USR/SBIN/CRON 10751 ? Z 0:00 | \_ [sh <defunct>] 30084 ? S 0:00 \_ /USR/SBIN/CRON 30089 ? Z 0:00 | \_ [sh <defunct>] 16903 ? S 0:00 \_ /USR/SBIN/CRON 16908 ? Z 0:00 | \_ [sh <defunct>] 3658 ? S 0:00 \_ /USR/SBIN/CRON 3663 ? Z 0:00 | \_ [sh <defunct>] 24186 ? S 0:00 \_ /USR/SBIN/CRON 24193 ? Z 0:00 | \_ [sh <defunct>] 26574 ? S 0:00 \_ /USR/SBIN/CRON 26578 ? Z 0:00 | \_ [sh <defunct>] 5069 ? S 0:00 \_ /USR/SBIN/CRON 5074 ? Z 0:00 | \_ [sh <defunct>] 17645 ? S 0:00 \_ /USR/SBIN/CRON 17650 ? Z 0:00 | \_ [sh <defunct>] 3506 ? S 0:00 \_ /USR/SBIN/CRON 3511 ? Z 0:00 | \_ [sh <defunct>] 21891 ? S 0:00 \_ /USR/SBIN/CRON 21896 ? Z 0:00 | \_ [sh <defunct>] 8195 ? S 0:00 \_ /USR/SBIN/CRON 8200 ? Z 0:00 | \_ [sh <defunct>] 25729 ? S 0:00 \_ /USR/SBIN/CRON 25734 ? Z 0:00 \_ [sh <defunct>] 246 tty1 S 0:00 login -- root 309 tty1 S 0:00 \_ -bash 247 tty2 S 0:00 /sbin/mingetty tty2 248 tty3 S 0:00 /sbin/mingetty tty3 249 tty4 S 0:00 /sbin/mingetty tty4 250 tty5 S 0:00 /sbin/mingetty tty5 251 tty6 S 0:00 /sbin/mingetty tty6 10752 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 10762 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 10764 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 10766 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 10799 ? S 0:00 \_ /bin/csh -f -s 10800 ? R 4106:34 \_ manpath -q 30090 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 30094 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 30101 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 30102 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 30137 ? S 0:00 \_ /bin/csh -f -s 30138 ? R 2680:25 \_ manpath -q 16909 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 16913 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 16919 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 16920 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 16955 ? S 0:00 \_ /bin/csh -f -s 16956 ? R 1968:21 \_ manpath -q 3664 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 3668 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 3674 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 3676 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 3711 ? S 0:00 \_ /bin/csh -f -s 3712 ? R 1492:58 \_ manpath -q 24194 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 24198 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 24206 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 24207 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 24241 ? S 0:00 \_ /bin/csh -f -s 24242 ? R 1137:23 \_ manpath -q 26579 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh monthly & 26583 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh monthly 26586 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh monthly 26590 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 26627 ? S 0:00 \_ /bin/csh -f -s 26628 ? R 1089:38 \_ manpath -q 5075 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 5079 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 5080 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 5087 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 5122 ? S 0:00 \_ /bin/csh -f -s 5123 ? R 890:09 \_ manpath -q 17651 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 17656 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 17659 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 17665 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 17699 ? S 0:00 \_ /bin/csh -f -s 17700 ? R 684:55 \_ manpath -q 3512 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 3516 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 3522 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 3524 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 3559 ? S 0:00 \_ /bin/csh -f -s 3560 ? R 508:29 \_ manpath -q 21897 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 21902 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 21907 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 21908 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 21944 ? S 0:00 \_ /bin/csh -f -s 21945 ? R 349:59 \_ manpath -q 8201 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 8205 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 8212 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 8213 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 8248 ? S 0:00 \_ /bin/csh -f -s 8249 ? R 207:28 \_ manpath -q 25735 ? S 0:00 /bin/sh -c test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 25740 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 25746 ? S 0:00 \_ sh /usr/lib/secchk/security-control.sh daily 25747 ? S 0:00 \_ /bin/sh /usr/lib/secchk/security-daily.sh 25783 ? S 0:00 \_ /bin/csh -f -s 25784 ? R 77:43 \_ manpath -q _______________________________________________________________ Peter Nixon Systems Engineer Jigsaw Technology Pty Ltd URL: http://www.jigsaw.com.au Address: 21 Boomerang Place Seven Hills NSW 2147 Australia Phone: 02 9672 4222 Fax: 02 9672 4211 Email: peter(a)jigsaw.com.au _______________________________________________________________

3 2

Having problem with LPD after running harden_suse
by Fred A. Miller 07 Jul '00

07 Jul '00

> Hi2all > > Bo, when running harden_suse if you did answered 'Yes' on question 6, that > can cause that problem you have (the same happend here, 'lpr' dont work, and > reinstalling dont solve the problem). The question is: "Do you want strong > permissions on user homedirs, limits and umask?" > > Run harden_suse again, answering 'No' in this question 6, and lpr will work > again. > I did got this problem, and this was tested 2/3 times, in two diferent SuSe > 6.4 (1 desktop, 1 laptop) allways behaving like this. > > Personally i'm using it like this: harden_suse y y y y n n y y n y 'Did as suggested, and "nada." I think the harden script messed things up big time the first time I ran it. The error I get now is: Your printer job (testpg.ps) was not printed because it was not linked to the original file 'Don't have a clue what to do about this. Fred -- ----/ / _ Fred A. Miller ---/ / (_)__ __ ____ __ Systems Administrator --/ /__/ / _ \/ // /\ \/ / Cornell Univ. Press Services -/____/_/_//_/\_,_/ /_/\_\ fm(a)cupserv.org

1 0

Re: [suse-security] telnet as a root on a suse 6.3 suse server
by Stefan Suurmeijer 07 Jul '00

07 Jul '00

On Fri, 7 Jul 2000, S.G. Zijl wrote: > On Fri, 7 Jul 2000, Francesco Masiello wrote: > > > I must be able to telnet from a terminal (not a console) as a root without > > using su. > > In solaris i could do that editing /etc/default/login file,but i can't find > > it on this > > Operating System. > > How can i do ? > > Thanks > > The /etc/securetty file defines on which devices root can log in. > I think he means he wants to login from a remote terminal. A big security NO-NO, but if you still want to you can set ROOT_LOGIN_REMOTE in /etc/rc.config to yes. Stefan

1 0

unsubscibe
by Florian Koch 07 Jul '00

07 Jul '00

unsubscribe suse-security(a)suse.com koch(a)agua.de

2 1

Re: [suse-security] partitions & mail system
by Marco Schöling 06 Jul '00

06 Jul '00

Hi, I wonder if this is a SECURITY mailing list? Partitioning is either a question for a beginner mailing list - or- if it IS a security related question, the information given in the mail is everything else but enough to answer. Regards, Marco Schoeling >>> Nikolai Dahlem <n_dahlem(a)gmx.net> 07/06/00 11:53am >>> Hi, I am currently setting up a mail-/webserver and I wondered what would be a good way to partition my disk. I'm also seeking for a smtp-pop mailsys with support for multiple domains, thought about using exim-mysql-qpopper [qpopper path for using mysql database for auth and virtual domain support]. Anyone tried this yet or has other suggestions ? Nikolai --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

6 5

identd and SuSE firewall
by Martin Jackson 06 Jul '00

06 Jul '00

Hello, I have just finished setting up a firewall configuration on SuSE 6.4 where I have no TCP services explicitly enabled - the string is blank. Yet for some reason, when I run nmap on that port, it says it is in unfiltered status. What does that mean? Why is it showing up in the nmap scan at all if I didn't enable it? Thanks for any help/advice. -- Martin Jackson: mhjacks(a)nwa.quik.com ========================================= This Message Brought to You by SuSE Linux

2 1

partitions & mail system
by Nikolai Dahlem 06 Jul '00

06 Jul '00

Hi, I am currently setting up a mail-/webserver and I wondered what would be a good way to partition my disk. I'm also seeking for a smtp-pop mailsys with support for multiple domains, thought about using exim-mysql-qpopper [qpopper path for using mysql database for auth and virtual domain support]. Anyone tried this yet or has other suggestions ? Nikolai

1 0

Help, Having problem with LPD after running harden_suse
by Bo Jacobsen 05 Jul '00

05 Jul '00

After running the script harden_suse, LPD returns the following error: Unable to print "name of file to print" when ever I print from a win pc (through Samba) or using the lpr command locally. I have tried the following without any luck: 1. Running the undo_harden_suse. The script runs without any complaints, but the error is stil there. 2. Uninstall LPD, reboot and installing LPD again. As my system is otherwise running without any problems (with or without harden_suse) I would like to know if anyone has any solution to this problem, besides reinstalling the whole system. The printer is a HP IIIP printer connected to an Accton printserver on the network. I have used apsfilter/SETUP to first create a remote printer and thereafter a prefilter that bypasses data to the remote printer. Everything worked perfectly before I ran harden_suse (I also have a "clone" linux host on which I have not run suse_harden. On this machine everything works OK, so it's not just a setup problem). I can still print to the remote printer created, even through Samba, but not from any of the Ascii, LP and RAW printers (that are spooled). If I invoke lpq -Praw it displays the file to be printed in maybe 1 second and then it's gone so it's actually spooled but just not printed. I could maybe live with printing through the remote printer if it was not for the problem that LPD is not spooling print jobs to remote, and the win clients therefor locks completely while printing. I'm running Suse Linux 6.4. Thanks in advance Bo Jacobsen bjc(a)image.dk

2 1