Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm just curious why inetd is listening on a port? Here's the output of netstat -ap:
tcp 0 0 *:988 *:* LISTEN 812/inetd
I guess I found what I was looking for - it listens and tranfers incoming connections to the services listed in /etc/services...is that right? If so, why are other services listening on their own? If it's the only service listening according to a portscan with nmap is it alright to shut it down? What surprises me is that nmap couldn't identify it. Isn't it common enough to be a known process?
Thanks for any help.
Last edited by Vincent_Vega; 09-16-2004 at 12:15 AM.
Thanks for that info but I'm looking at INETD. I have ident disabled and just about everything else but inetd is still coming up as an unknown process when I nmap my computer. I tracked it down to see what the process was which was simple enough but now I'm just trying to figure out what the story is behind it and if I shoud keep it running.
It's not inetd that listens to port 988. It's a service that it is started from inetd. Check /etc/inetd.conf to see what services are started from it and disable the ones you don't need
You're right. I went in, commented it all out, what very few I had remaining, restarted inetd and nmap shows nothing.
Are there any processes that must run?
Basically, you can run daemons as standalone eg httpd, sshd or you can run them via (x)inetd.
Loosely speaking, high traffic daemons run on their own, low traffic ones are called by (x)inetd, which listens on their behalf.
There are exceptions eg sshd.
Standalone daemons have their own stop/start controls, the others are controlled by the files in eg /etc/xinetd.d. Just set disable to yes for any you don't want (that are in xinetd area).
Some distros still use (older) inetd daemon, others use the newer xinetd.
HTH
I'm using Slack 9.1 so I have inetd. I just commented out the ones I didn't want and that seemed to do it. I just expected something listed in inetd by default to be identified by nmap. That's sort of where the confusion came in but I think I'm understanding it all now.
Thanks for the posts. Any other information about this that I should know?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.