Re: Why s port 111 still open?
On Monday 29 August 2011 13:29:49 Tom H wrote:
> On Mon, Aug 29, 2011 at 5:38 AM, Lisi <email@example.com> wrote:
> > I was under the impression that I had cleansed my system of rpcbind after
> > the security discussion on this list. Today, because I was trying to
> > remove Samba, I ran nmap to see what was going on. Here is the
> > "conversation" I had with Tux just now:
> > lisi@Tux:~$ nmap Tux
> > Starting Nmap 4.62 ( http://nmap.org ) at 2011-08-29 10:31 BST
> > Interesting ports on Tux (192.168.0.2):
> > Not shown: 1711 closed ports
> > PORT STATE SERVICE
> > 22/tcp open ssh
> > 80/tcp open http
> > 111/tcp open rpcbind
> > 6881/tcp open bittorrent-tracker
> > Nmap done: 1 IP address (1 host up) scanned in 0.126 seconds
> > lisi@Tux:~$ which rpcbind
> > lisi@Tux:~$ whereis rpcbind
> > rpcbind:
> > lisi@Tux:~$ locate rpcbind
> > lisi@Tux:~$ find rpcbind
> > find: `rpcbind': No such file or directory
> > lisi@Tux:~$
> CHeck whether the rpcbind or the portmap packages are installed.
I have portmap, but not rpcbind. Would that explain why that port is open? I
seem to have nothing left of rpcbind and its configuration/data files etc.
The other three are open fpr identifiable (by me) reasons. But why is that
rpcbind one still open? The computer has been completely shutdown between
wehn I removed rpcbind and now.