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: Tue, 03 Jan 2006 20:09:40 -0500
On Tue, Jan 03, 2006 at 05:36:38PM +1100, 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.  Running a "ps
-ef" reveals that nmap is always invoked with the same command-line
options.  Basically, changing the nmap scan options in the Nessus client
has no effect.
...
This does not
seem to happen running under SUSE.

Excuse me if these seem like silly questions but...

  o Have you cross-referenced the pid(s) that you see in the
    ps output with the pids reported by nessusd when it
    launches nmap.nasl (ie, in nessusd.messages)?

  o Have you checked whether the commandline ps reports is being
    truncated because it would otherwise exceed the screen size?

  o Have you verified whether nmap is indeed always doing a SYN
    scan by, say, doing a packet capture?

  o Do you have a script named nmap that's being called by
    nessusd instead of nmap itself?

  o Have you verified that you have a current and valid
    version of nmap.nasl?

George
-- 
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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