Nmap Development mailing list archives

port order in 5.00-2


From: Miguel Rozsas <miguel () rozsas eng br>
Date: Wed, 18 Nov 2009 12:17:07 -0200

Hi,

I am using nmap 5.00-2 in Ubuntu and 4.75 in opensuse.
Both versions doesn't respect the order of ports using the -p flag,
even using the -r (don't randomize) flag.

nmap -r -p T:7894,8945,1234,5678 -PN localhost

Starting Nmap 5.00 ( http://nmap.org ) at 2009-11-18 12:04 BRST
Warning: Hostname localhost resolves to 2 IPs. Using 127.0.0.1.
Interesting ports on localhost (127.0.0.1):
PORT     STATE  SERVICE
1234/tcp closed hotline
5678/tcp closed unknown
7894/tcp closed unknown
8945/tcp closed unknown

Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds

The order specified was 7894,8945,1234,5678 but the scanning order was
1234,5678,7894,8945.

This could be a problem when using nmap to trigger firewall actions
that are based on the strict order of hits, i.e. port knocking.


---------------------
Miguel A. Rozsas
"Teoria é quando você sabe tudo mas nada funciona.
Prática é quando tudo funciona mas ninguém sabe o porquê.
Neste caso, juntamos a teoria à prática: Nada funciona e ninguém sabe o porquê!"
Albert Einsten
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/

Current thread: