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 [email protected] http://mail.nessus.org/mailman/listinfo/nessus
