On Thu, Jul 25, 2002 at 11:55:59AM +0200, Baumgartner Christoph wrote:
> I had to check 3 dozens of 3COM SuperStack3 4400 switches in our labs.
> To avoid unpleasant reconfigurational work, I enabled 'all but dangerous
> plugins'. I was quite surprised when I saw that Nessus rebooted all the
> boxes during the scanning process. The network did not run properly
> after that (the configuration has not been changed by Nessus).
>
> Could anybody tell me, which plugin is in charge for this unpleasant
> testing behaviour?
The problem is that as long as you start to scan something, you have to
expect the worst. Nessus has builtin options to reduce as much as
possible the amount of bad surprises, but there's no garantee it will
suffice - some vendors dare to sell appliances with a tcp/ip stack which
crashes when two ports are being connected to in less than a minute, or
they implement network services which crash if they don't receive the
exact data they were expecting.
-- Renaud
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
* To subscribe again, send a mail to [EMAIL PROTECTED] with
"subscribe nessus" in the body
