Re: db_services bug?

[Tod Beardsley <todb () planb-security net>]

Seems to work for me under normal circumstances. Need to run
msfconsole as root of course to get UDP scan. This was on r12995.

msf auxiliary(ssh_login) > db_nmap -T4 -ff -sU 192.168.145.50 -p 5353
[*] Nmap: Starting Nmap 5.51SVN ( http://nmap.org ) at 2011-06-21 10:17 CDT
[*] Nmap: Nmap scan report for dbsrv (192.168.145.50)
[*] Nmap: Host is up (0.00053s latency).
[*] Nmap: PORT     STATE SERVICE
[*] Nmap: 5353/udp open  zeroconf
[*] Nmap: MAC Address: 00:0C:29:A5:9E:F3 (VMware)
[*] Nmap: Nmap done: 1 IP address (1 host up) scanned in 0.31 seconds
msf auxiliary(ssh_login) > db_services

Services
========

host            port  proto  name      state  info
----            ----  -----  ----      -----  ----
192.168.145.50  5353  udp    zeroconf  open

msf auxiliary(ssh_login) >



On Tue, Jun 21, 2011 at 9:05 AM, Scott McClellan <Scott.McClellan () tn gov> wrote:
> I'm running the 3.8.0-dev version of Metasploit (rev 12980), updated
> yesterday.  My database had no hosts in it.  I ran db_nmap -T4 -ff -sU on my
> target.  I then ran db_services, but the only value in the proto column was
> tcp.  I know that my target has open UDP ports.  I'm using the Postgresql
> database, with msfconsole.  I'm running Metasploit from within BackTrack 5.
>
> Has anyone else seen this behavior?
> _______________________________________________
> https://mail.metasploit.com/mailman/listinfo/framework
_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework