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: Discrepancies regarding feeding nmap data to Nessus 3.2 beta (3.1.4)

Subject: Re: Discrepancies regarding feeding nmap data to Nessus 3.2 beta (3.1.4)
Date: Fri, 21 Sep 2007 14:42:56 -0400
On 09/21/07 02:59, Knut Hellebø wrote:

I think I may have found the answer. When feeding the targetnames to 
nessus from a targetfile, I have constructed a file consisting of eight 
hosts per line, all followed by a comma (for readability reasons). 
Nessus apparently reads the file just fine, but I noticed some double 
commas, ",,", in the "Target(s):" line. All hosts immediately following 
",," are not being tested. 

Ok.

It seems that only the first 80 characters in
each line in the targefile is significant. Is my targetfile badly built 
or is this a bug in nessus ?

You're talking about after fixing the problem you noted above, right?

I'm not aware of any limitation in line lengths in general. Which client 
are you using (name, platform, version)?  What does nessusd.messages 
show when you start a new scan?


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>