Nmap Announce mailing list archives
Re: Possible bug
From: "HD Moore" <hdmoore () usa net>
Date: Sat, 2 Jan 1999 12:42:38 -0600
I could not reproduce the bug described. SuSe 5.2 / Libc5 / 2.0.36 + Solar Diz's secure linux patch Maybe this only affects users with glibc? I tried using every type of TCP scan with the same effects. -- shell paste -- Starting nmap V. 2.02 by Fyodor (fyodor () dhp com, www.insecure.org/nmap/) Host localhost (127.0.0.1) appears to be up ... good. Initiating TCP connect() scan against localhost (127.0.0.1) Adding TCP port 23 (state Open). Adding TCP port 53 (state Open). Adding TCP port 945 (state Open). Adding TCP port 80 (state Open). Adding TCP port 21 (state Open). The TCP connect scan took 0 seconds to scan 112 ports. Interesting ports on localhost (127.0.0.1): Port State Protocol Service 21 open tcp ftp 23 open tcp telnet 53 open tcp domain 80 open tcp www 945 open tcp test Nmap run completed -- 1 IP address (1 host up) scanned in 1 second shadowbox:/root/nlog # uname -a Linux shadowbox 2.0.36 #1 Sun Dec 6 21:49:45 CST 1998 i586 unknown -- end shell paste --
Current thread:
- Possible bug datawar (Jan 02)
- <Possible follow-ups>
- Re: Possible bug HD Moore (Jan 02)