Re: Unknown service on port 21 and 143 detected via nessus - Next
From: ctt (j1133s_at_yahoo.com)
Date: 06/10/04
- Next message: Tim Haynes: "Re: iptables: forward port from eth0 to 127.0.0.1"
- Previous message: Bill Marcum: "Re: iptables: forward port from eth0 to 127.0.0.1"
- In reply to: Randy Lawrence: "Re: Unknown service on port 21 and 143 detected via nessus - Next"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 10 Jun 2004 10:12:19 -0700
Hi,
If the socket allows sharing, then multiple processes can read/write
to it. Sharing is an option that can be set on a socket (I'm not too
sure if "sharing" is the name of the option since it's been a while
since I've used it).
Try netstat command or look at /proc/net/netstat on Linux.
Also, if you have a kernel rootkit, you may not be able to see the
port being used, just a warning.
Thanks,
Ching Tai
Randy Lawrence <jm@zzzzzzzzzzzz.com> wrote in message news:<OcRxc.7026$n65.5927@newssvr33.news.prodigy.com>...
> Thanks for all the suggestions. lsof is a very interesting command I
> didn't know about.
>
> On a hunch, I tried running netcat on the server to open/listen on port
> 21--and it worked.
>
> When I try this on ports that I know are already open (like 80), netcat
> fails (as expected) because the port is alreaady taken--so I'm guessing
> that port 21 on the server isn't actually open because netcat works.
>
> Is this a bad assumption? I don't know enough about *nix to judge this
> assumption.
- Next message: Tim Haynes: "Re: iptables: forward port from eth0 to 127.0.0.1"
- Previous message: Bill Marcum: "Re: iptables: forward port from eth0 to 127.0.0.1"
- In reply to: Randy Lawrence: "Re: Unknown service on port 21 and 143 detected via nessus - Next"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|