On Sat, May 01, 2004 at 03:48:15PM -0500, Tarek W Moussa, ISO wrote: > I am using NessusWX as a client, just in case it makes a > difference for any of the questions. > > 1) Why does selecting "Enable Non-DoS" from the plugin list leave some > checks in the DoS category active? > > Example: Abyss httpd crash is disabled, but Annex DoS is still enabled
Take this with a grain of salt since I don't use NessusWX, but from reading the source it looks like NessusWX only disables plugins in the ACT_DENIAL category when you select "Enable Non-DoS". The unix-based nessus GUI has a similar setting (Enable all but dangerous plugins) that actually disables those in ACT_DESTRUCTIVE_ATTACK and ACT_KILL_HOST categories as well as ACT_DENIAL. In short, it looks like NessusWX takes a fairly narrow view regarding what constitutes a DoS. As for the two plugins you mention, abyss_dos.nasl is classified as ACT_DENIAL since it only crashes the web service while annex_dos.nasl is ACT_KILL_HOST since it will take down the entire annex TS rather than just its web server. > 3) I have a question about the overlap between safe-checks and the DoS > category: is it the difference between a chance of crashing vs. > definitely crashing? What is the dividing line? safe_checks causes the server to disable dangerous plugins (ACT_DENIAL, ACT_DESTRUCTIVE_ATTACK, and ACT_KILL_HOST) *and* causes several plugins to rely on just the banner in determining whether a vulnerability exists. Also, safe_checks can be set either in the client or the server configuration file; setting it on the server side overrides any client-side setting. George -- [EMAIL PROTECTED]
pgp00000.pgp
Description: PGP signature
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
