Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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 01: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.
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.
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?