> > 8081/tcp   open        blackice-icecap

> > sure nuf, nmap again shows no 8081.   (8081 is used with popfile,
> > no sure what the name blackice is...)
> >
> > Any i dea why nmap kills popfile?
> 
> Does it?  Not on my box, it doesn't.  Popfile uses 8080, btw.  
> Googling on blackice-icecap came up with this

Well, i think i have it sorted out.

Since i run popfile as a user, I set popfile to 8081 just to get away
from the default (though this was really unnecessary, since i am the
only user).

That's why i had assumed blackice was the "port"  prog for popfile.

Manning nmap:

"Nmap always gives the port's  "well  known"  service  name  (if
any),  number,  state,  and protocol."

So it was just kidding when it called it blackice-icecap.

Also, i found out that nmap by default only probes ports 1-1024 and
those in /etc/services

under the -p option
 The default is to scan all ports
              between 1 and 1024 as well as any ports listed in  the 
services
              file  which  comes  with  nmap.

So, it seems to find all ports, you have to 

nmap -p 1-65535 127.0.0.1

though i probably just missed an "all" switch.

As for the crashing popfile (more man nmap stuff):

 It  should  also  be  noted  that  Nmap has been known to crash certain
       poorly written applications, TCP/IP stacks, and even operating
systems.

So, that's what was going on...

For kicks, i bumped popfile over to 8085, and nmap (default) doesn't
hurt it since 8085 is not in the services file, but nmap "all" does nuke
it.

8085/tcp   open        unknown 

This time, no guess as to the service....

eric



more interesting man nmap info:
-------------------------------------------------
 nmap should be run as root when-
       ever possible (not setuid root, of course).

<snip>

 It  should  also  be  noted  that  Nmap has been known to crash certain
       poorly written applications, TCP/IP stacks, and even operating
systems.
       Nmap  should  never  be run against mission critical systems
unless you
       are prepared to suffer downtime.  We acknowledge  here  that 
Nmap  may
       crash  your  systems  or networks and we disclaim all liability
for any
       damage or problems Nmap could cause.

       Because of the slight risk of crashes and because a few black
hats like
       to  use  Nmap  for reconnaissance prior to attacking systems,
there are
       administrators who become upset and may complain when their 
system  is
       scanned.   Thus,  it  is  often  advisable to request permission
before
       doing even a light scan of a network.

       Nmap should never be run with privileges (eg suid  root)  for 
security
       reasons.



-------------------------------------------------






Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to