>113 auth - I removed auth from inetd.conf, where else can it be called
If you remove this from inetd.conf the super server will not invoke the
daemon so dont worry about it, the only other way to start the daemon, is to
start it as standalone by adding a startup script for it to the appropriate
Quote:>587 submission - I have no idea what this is, does anyone?
Quote:>98 Linuxconf - I know this one, but would like to keep Linuxconf running.
>it possible to close the port for external connections?
you can use ipchains to deny any external access to this port. Check out the
man pages for ipchains for information on how to do this. (You do have
ipchains don't you?)
Quote:>How big is the security risk, is it possible to connect from linuxconf on
another box to my
>new one easily?
Yep, do not under any circumstances leave this port open for external
access, if you do it's an open invitation to crackers/script kiddies
everywhere to hack your system. You can check out vunerabilities in
realation to linuxconf at www.securityfocus.com
Also check out the following web pages in relation to armouring LINUX
systems which I found it useful:
Also if your running Red Hat Linux 6 or above there are perl scripts which
will do a really good job at hardening your system further. I think the
site is www.bastillelinux.org if I'm wrong however you can download it from
Hope this helps,