Nessus
[Top] [All Lists]

Re: Strange Nessus Behavior

To: nessus@list.nessus.org
Subject: Re: Strange Nessus Behavior
From: "George A. Theall" <theall@tenablesecurity.com>
Date: Wed, 20 Dec 2006 20:21:02 -0500
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: nessus@list.nessus.org
In-reply-to: <1276.131.182.26.5.1166634572.squirrel@slashmail.org>
List-archive: <http://mail.nessus.org/pipermail/nessus>
List-help: <mailto:nessus-request@list.nessus.org?subject=help>
List-id: Discussion of Nessus software <nessus.list.nessus.org>
List-post: <mailto:nessus@list.nessus.org>
List-subscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=subscribe>
List-unsubscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=unsubscribe>
References: <4844.131.182.26.5.1166626412.squirrel@slashmail.org> <F9C013D2-E5E1-4E9B-9D36-5DA94FB48B6C@nessus.org> <1276.131.182.26.5.1166634572.squirrel@slashmail.org>
Sender: nessus-bounces@list.nessus.org
User-agent: Thunderbird 1.5.0.8 (X11/20061110)
On Wed, Dec 20, 2006 at 12:09:32PM -0500, Steven Adair wrote:

> I also cannot seem to find
any option to make this a default setting in nessusd.conf to consider the
unscanned ports as closed.  Is there a way to do this?

"unscanned_closed = yes" should work.

Subsequently this brings us to another issue we've had with Nessus as of
late.  Starting a month or so ago when trying to start a scan with an of
the *nix clients it just freezes and nothing happens.

Do you authenticate before trying to start a scan? What if anything is being written to the nessusd.messages logfile? Do you see any packets passing between the server and client? What processes related to nessusd are running?

George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>