Re: Hydra & Portscanning XP

On Wed Apr 27 2005 at 18:01, George A. Theall wrote:

> > I have found that portscanning Widows XP SP2 systems that
> > have the built-in firewall enabled is extremely slow using
> > both Nessus built-in portscanner

nessus_tcp_scanner was muc more aggressive in 2.2.3. Did you see any
differences?

> > and Nmap when they are in default configurations. It is possible to
> > make Nmap return results in a reasonable time without seeming to loose
> > accuracy by setting --max_rtt_timeout to e.g. 50 instead
> > of the default 9000.

If you select Nessus "auto" timing, you'll get a more reasonable
value.
However, I suggest once again that you run Nmap independantly with any
option you want, then import the results.
If you scan a whole network, this will be much more efficient. IIRC,
Fyodor explained on this list that the latest versions were optimized
for this.

> I'm not aware of anything, but perhaps Michel or Renaud will
> step in with a more authoritative answer.

We disabled the aggressive timing options in safe checks. 
When safe checks is not set, nessus_tcp_scanner uses more aggressive
values and all Nmap options are available.
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus