A couple of questions about nmap/nessus... 1. Is there any need to recompile nessus if upgrading from nmap3.0 -> 3.2?
2. Is there any way to send command line arguments to nessus that aren't in the GUI (ie. min_parallelism)? 3. What nmap version is recommended? 4. Is nmap the "best" scanning method from within Nessus? If not, which one is? Thanks, Brian > On Thu, Mar 20, 2003 at 03:45:34PM -0800, Phillip Pi wrote: >> Any known problems with the new version and Nessus v2.0? > > It requires g++ to compile and uses libpcap 0.7.1. I've minor gripes : > > - g++ is not installed everywhere > > - libpcap 0.7.1 : I did some testing of libpcap 0.6.x (the "post lbl > libpcap") on Linux, and when you have a great number of processes each > having a different filter on their own pcap filter, in some cases the > wrong packets will go through. I did not test it with libpcap 0.7, so > it might have been fixed, but that was pretty ugly. For the record, > Nessus 1.3.x _had_ libpcap 0.6.x in CVS for a while, and I switched > back to 0.4.x (the True One) because of its instability. I may give a > shot to 0.7.1, but I don't have high hopes. > > > If you have a modern Linux distribution and don't scan too many hosts at > the same time, none of my gripes are an issue. If you try to scan 200 > hosts simultaneously[*], your mileage may vary > > > > -- Renaud > > [*] Fortunately, nmap is too memory hungry to let you do that :) -- Brian Kirsch OLOSEC Network Security Solutions 164 Jefferson Dr. Unit J Menlo Park, CA 94025 Tel: + 1 650.330.1745 Fax: + 1 650.330.1694 Email: [EMAIL PROTECTED] url: http://www.olosec.com
