On Thu, Jun 01, 2006 at 11:18:30AM +0200, Robert Millan wrote:
Sorry, I don't know. However, the big problem here is inability to use nmap
when /etc/resolv.conf is broken.
When this happens, instead of aborting, I think it should just disable
whatever
functionality is associated with
On Wed, May 31, 2006 at 05:45:34PM -0700, Fyodor wrote:
On Tue, May 30, 2006 at 07:59:15PM +0200, Robert Millan wrote:
nmap requires working DNS even when specifiing target by IP:
$ sudo nmap -sS -O 192.168.100.1
Starting Nmap 4.00 ( http://www.insecure.org/nmap/ ) at 2006-05-30
Package: nmap
Version: 4.00-2
Severity: normal
nmap requires working DNS even when specifiing target by IP:
$ sudo nmap -sS -O 192.168.100.1
Starting Nmap 4.00 ( http://www.insecure.org/nmap/ ) at 2006-05-30 19:56 CEST
Unable to determine any DNS servers. Try using --system_dns or specify valid
On Tue, May 30, 2006 at 07:59:15PM +0200, Robert Millan wrote:
nmap requires working DNS even when specifiing target by IP:
$ sudo nmap -sS -O 192.168.100.1
Starting Nmap 4.00 ( http://www.insecure.org/nmap/ ) at 2006-05-30 19:56 CEST
Unable to determine any DNS servers. Try using
4 matches
Mail list logo
