Nessus
[Top] [All Lists]

RE: plugin 10919

To: <Nessus@list.nessus.org>
Subject: RE: plugin 10919
From: "Scott Pate" <spate@Spohncentral.com>
Date: Tue, 20 Feb 2007 11:53:26 -0600
Cc:
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: Nessus@list.nessus.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>
Sender: nessus-bounces@list.nessus.org
Thread-index: AcdPcVffgsv1xuwxQeGZWF0LJep+DgFhd03g
Thread-topic: plugin 10919
Not sure if this got through the first time:
 
 
 I'm trying to determine the significance of this plugin and how it impacts the report.  I have several reports where this plugin says a "port was open at the beginning of the scan, and is now closed..." but there is still output from other plugins for that port.  If check_ports.nasl determines a port to be closed, do other plugins launch against the port after that, or does nessus consider the port to be closed?
 
Also :
 
Does the plugin determine a port to be closed if it fails to open a tcp socket (in which case the port may not be closed), or if it receives a RST (in which case the port is most definitely closed)? 
 
 
What would be the implications of disabling this plugin? 
 
thanks
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>