Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




nmap-dev logo Nmap Development mailing list archives

Re: Can i tell nmap what to log and what not?
From: Ron <iago () valhallalegends com>
Date: Fri, 07 Jan 2005 08:00:07 -0600

If you know what ports are going to be open before hand, then you can use the -p option on nmap (nmap -p 1-80,135,137). However, if you know which ports are going to be open, that rather defeats the purpose of a portscan.
Martin Contento wrote:

Hi, i frequently use nmap to scan for certain open ports in my dorm.
It works very well, but parsing the logs is really slow because it's
full of "filtered" entries that don't interesnt me anyway.
Is there a way to tell nmap to "only log open ports"?
To avoid the obvious reply: i know man grep ;P

Thanks in advance

Martin

---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to nmap-dev-help () insecure org . List archive: http://seclists.org





---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to nmap-dev-help () insecure org . List archive: http://seclists.org



  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]