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.
Today I just ran a check of all my open ports with nmap and I found one unkown port open -- port no. 32768. So I tried to check the corresponding application which opened it by the command
netstat -nlp
but even this simply showed a dash in place of the process no. of the process listening on that port. The entry was something like this --
tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN -
Finally I tried fuser to get the process no.--
fuser -n tcp 32768
But it did not return anything at all which implies that that port is not opened by any application. Now how is this possible. How and why is that port open? How can I find out?
Its usually some kind of RPC program which opens such high ports...if not NFS like Amit suggested you might want to check whether you have any other RPC service like NIS running. Still though...I admit it doesnt completely answer why a port should remain open if an app hasnt opened it. I mean..shouldnt NFS(lockd , mountd , portmap...rpcgsvvd...whatever) have been assosciated with it. Or am I missing something???
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.