Possible bug

[<datawar () usa net>]

Happy new year to everyone ...
 
Platform tested: Linux kernel 2.0.36 and glibc 
 
I don't know if this problem exists in any other OS. As making a change to my /etc/services file to be more specific:
 
test         945/tcp        # This is a test
 
The port can be replaced with any port < 1024 (as this is the max scan default port number) as long as its not used by 
any other service.
 
Then I activated this port with a random service.
 
i.e. cat a random file
add to your /etc/inetd.conf
 
test     stream     tcp     nowait     root     /bin/cat     cat /etc/test.txt
 
Now when I tried to use the -F flag with nmap 
(-F fast scan. Only scans ports in /etc/services, a la strobe(1).)

That's what happened:

[root@DataWaR /]# nmap -v -F 127.0.0.1

Starting nmap V. 2.02 by Fyodor (fyodor () dhp com, www.insecure.org/nmap/)

No scantype specified, assuming vanilla tcp connect() scan. Use -sP if you really don't want to portscan (and just want 
to see what hosts are up).

Host localhost (127.0.0.1) appears to be up ... good.

Initiating TCP connect() scan against localhost (127.0.0.1)

State mismatch!!@ -1

QUITTING!



I am not sure if that is a bug because Fyodor may mean that this scanning mode is performed according to a normal 
/etc/services file.




____________________________________________________________________
Get free e-mail and a permanent address at http://www.netaddress.com/?N=1