Yup, starting portmap opens port 111/tcp. should i block this port using iptables?
--- Spider <[EMAIL PROTECTED]> wrote: > begin quote > On Thu, 13 Mar 2003 22:40:25 +0800 > Pius Lee <[EMAIL PROTECTED]> wrote: > > use "lsof -i" instead of nmap and you can know what it is that > does > what, instead of knowing something is open. > > but, "fam" (file alteration monitor) speeds up the listing of files > + > updates of them if you have KDE or Gnome, and that in turn starts > Portmap (the sunrpc client) > > > //Spider > > > > Hi, I recently used nmap to portscan my machine from another pc > and > > found that i've got the following ports open: > > > > 22 (ssh) > > 25 (smtp) > > 113 (pop-3) > > > > I don't see port 25 or 113 open, but why does nmap list them as > so? > > Blocking the ports with iptables would probably solve the problem, > but > > > > to get to the root of it, would tracking the daemons responsible > for > > opening them be a better solution? How should I go about doing it > > then? > > > > > -- > begin .signature > This is a .signature virus! Please copy me into your .signature! > See Microsoft KB Article Q265230 for more information. > end > -- [EMAIL PROTECTED] mailing list
