Yeah, but I want to automate everything (except for reviewing the results). So I doing everything on the cmd line. So I'm doing something like
/opt/nessus/bin/nessus -T nessus -xq localhost 1241 admin secret /tmp/targets.txt /tmp/report.nessus And it doesn't handle hypens in /tmp/targets.txt. At least I haven't been able to convince it to do so. /tmp/targets.txt is generated from a script. John Ron Gula wrote: > John Gray wrote: > >> One issue that I've run into with something like this, is that I can't >> find a way escape hyphens in host names in the target list to nesses. >> So the names with hyphens are interpreted as ranges. >> >> I see I can build a .nessus file that'll handle the issue. But its a >> lot more work to build the .nessus file from my host list. One could >> just use IPs, except I'm scanning some named virtual hosts, which >> require using the name. >> >> I really want to have a cron job that runs at, say, 4 am, that does my >> scan. And this is the hold up. >> > > The Nessus Client allows you to specify a file that contains hosts. > > Ron Gula > Tenable Network Security > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus > > -- John Gray [EMAIL PROTECTED] AgoraNet, Inc. (302) 224-2475 314 E. Main Street, Suite 1 (302) 224-2552 (fax) Newark, De 19711 http://www.agora-net.com _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
