Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Nmap (NASL Wrapper) not generating correct nmap command-line

Subject: Re: Nmap (NASL Wrapper) not generating correct nmap command-line
Date: Fri, 06 Jan 2006 10:22:04 +0100
On Tue Jan 03 2006 at 07:36, Les G wrote:

  I've noticed both with Nesses 2.2.6 and Nessus 3, that under
Debian 3.1 (and also some versions of RHL) that when nmap is chosen as
the port-scanner, and you specify some nmap scanning options, such as
a FIN scan, you still only always get the default SYN scan.

This kind of scan is disabled in "safe checks".
Anyway, running Nessus from Nmap is not a good idea. Current Nmap
versions eat too much memory for each process.
The right way to do it is to run it by hand and import the result
(create the file with nmap -oG your_file your_options)
I would even say that running Nmap is a bad option in any
case. nessus_tcp_scanner is quicker in most circumstances.
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>