Edenyard wrote: > > /usr/sbin/syslogd > /usr/sbin/klogd -c 3 The logging daemons that leave messages for you (probably in /var/log/messages).
> /usr/sbin/inetd The daemon that controls most of the network servers. > /usr/sbin/sshd Secure shell daemon. > /usr/sbin/lpd Print daemon. > /usr/sbin/crond -l10 > /usr/sbin/atd -b 15 -l 1 Daemons used to schedule things for automatic execution. > Lines without # in inetd.conf are: > time, ftp, telnet, comsat, shell, login, ntalk, finger > auth, netbios-ns, netbios-nmbd Wow, you've got a whole heap of services running. > So - should I be changing (removing, deleting...) anything, > based on what you can see here? Definitely!! My recommendation is to turn them all off (except for any you *really* need). You probably need none of them. For example, even if you want to use ftp to connect to remote systems, you do not need that ftp server -- your ftp client will connect just fine (as long as there is an ftp server on the remote system). If you decide to leave some of these services running and expose them to the internet, it is very important to keep up-to-date with security and/or to firewall your system. There is no disagreement between Steve and me on this. If you are exposing services to the internet, you must take security seriously. There should be no doubt. Crackers are scanning for systems like yours. I think you said that you have a Slackware system. If so, your servers are probably being turned on in /etc/rc.d/rc.inet2. You can edit this file (using #'s to stop sections being executed) or you can stop the entire file from being executed by renaming it. > Also, where could I read more (generally) about what all these > items are? You probably have a comprehensive NET-?-HOWTO somewhere. Have a look in /usr/doc on your system or in the /docs directory on the installation CDrom. Cheers, Steven
