I'm running the following Solaris 8 version of nessus with the latest
plugings download last week on the September 8:
The problem that I see is that when I run a scan to a server that has IPSEC
configured and the ip address of the nessus server is not in the trusted
host file and I'm scanning 1-65535 port, I had the protocol tracer running.
It take round 3hr to get to the 3% scanned after 36hr it is at the port
range of 65500/65535. I have top running on the Unix box that has my nessus
server on and the nessud is running several and one is at 95.04% and the
scan never completes.

# ./nessusd -d
This is Nessus 2.0.9 for SunOS 5.8
compiled with gcc version 3.3.2
Current setup :
        Experimental session-saving    : enabled
        Experimental KB saving         : enabled
        Thread manager                 : fork
        nasl                           : 2.0.9
        libnessus                      : 2.0.9
        SSL support                    : enabled
        SSL is used for client / server communication
        Running as euid                : 0
I start a scan on a single ip address and have the following setup :
Nessus Console [Version 1.4.4] Ready
SSL library initialized
New encryption key was generated
DBG-02: ConnectionHandlerMain(): user='tester', password='tester',
auth_type=0, server='10.77.101.17', port=1241
Connecting to server 10.77.101.17 (port 1241) using TLSv1 encrypted
connection...
SSL connection using DES-CBC3-SHA
Using < NTP/1.2 >
Connection with the server [10.77.101.17] established.
2407 plugins loaded
132 preferences received
0 rules received

_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to