🚀 go-pugleaf

Michael Dwyer <mdwyer@holly.ColoState.EDU> wrote:
: The NCLUG mailing list has reported yet another machine getting 
: hit by a cracker.  It is a very amateur job, if I am any judge.  
: They slip in using some well-known vulnerabilities and explode
: a rootkit.  Update your daemons!  Especially SMAP, SMTP (sendmail),
: HTTPD (Apache) and FTPD (WU-ftpd).  Also, turn off any services
: you aren't using. (ie, SUN NFS daemons scare me.)

Turn off any services you aren't using.
Upgrade nfs-server
(ftp://linux.mathematik.tu-darmstadt.de/pub/linux/people/okir/) if you're
using NFS.  
Use rpc in conjunction with TCP wrappers.
Use TCP wrappers.
Throw away ftp,telnet,rlogin and rsh; replace with ssh.
Read bugtraq.
Make backups.
Explore rootshell.com
Try to crack your own system.
Tighten up passwords.  Run Crack on your password file.
Take to heart the principle of least priviledge.  When configuring a
facility on your network, implement it in the most rigidly secure manner
possible; allow access as needed.
Make backups.
Use ipfwadm / ipchains to deny unneccessary inbound traffic.
Read the Security-HOWTO.
Make backups.
Use nmap (http://www.insecure.org/nmap/index.html) to check for
vulnerabilities in your network.
Make syslog log to your printer or a serial console.

I know this isn't complete....next?