Re: nmap 5.21, OS X 10.6.2 - doesn't work as root

[Walt Scrivens <walts () gate net>]

Both were built from source, and the 5.21 was probably built with 10.6.2.

Compiling for 32-bit as
./configure CFLAGS="-m32" CXXFLAGS="-m32" LDFLAGS="-m32"
does work, so it looks like the problem is back :-(

Starting Nmap 5.30BETA1 ( http://nmap.org ) at 2010-04-13 20:04 EDT
Warning: File ./nmap-services exists, but Nmap is using /usr/local/share/nmap/nmap-services for security and 
consistency reasons.  set NMAPDIR=. to give priority to files in your local directory (may affect the other data files 
too).
Initiating Connect Scan at 20:04
Scanning 192.168.1.149 [1000 ports]
Discovered open port 139/tcp on 192.168.1.149
Discovered open port 135/tcp on 192.168.1.149
Discovered open port 445/tcp on 192.168.1.149
Discovered open port 554/tcp on 192.168.1.149
Discovered open port 5357/tcp on 192.168.1.149
Discovered open port 2869/tcp on 192.168.1.149
Discovered open port 10243/tcp on 192.168.1.149
Completed Connect Scan at 20:04, 11.55s elapsed (1000 total ports)
Nmap scan report for 192.168.1.149
Host is up (0.012s latency).
Scanned at 2010-04-13 20:04:04 EDT for 11s
Not shown: 993 filtered ports
PORT      STATE SERVICE
135/tcp   open  msrpc
139/tcp   open  netbios-ssn
445/tcp   open  microsoft-ds
554/tcp   open  rtsp
2869/tcp  open  unknown
5357/tcp  open  unknown
10243/tcp open  unknown

Read data files from: /usr/local/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 11.74 seconds


Walt

On Apr 13, 2010, at 1:37 PM, David Fifield wrote:

> Is the 5.21 from a binary package and the 5.30 built from source? (Or
> was the 5.21 perhaps built under 10.6.2 before you upgraded?) This might
> be a problem with building in 64-bit mode that went away in 10.6.2 but
> might be back in 10.6.3. Patrik reported that rebuilding with -m32
> solved the problem, as described in this post:
>
> http://seclists.org/nmap-dev/2009/q4/365
>
> Does it work for you with -m32? Does the binary package from the .dmg
> work?
>
> Note that there are two different problems happening in this thread.
> What Walt and Patrik have seen (and I can reproduce) is a hang (which is
> ocurring inside pcap_next). What Daniel reported in
> http://seclists.org/nmap-dev/2010/q1/1199 is a failure of ARP scan, not
> a hang. I believe these are separate.
>
> David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/