Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

(no subject)

Subject: (no subject)
Date: Mon, 5 Dec 2005 17:10:27 -0000
I have a nessus server running OpenBSD 3.7 (on sparc64) - last month I ran a
couple of test on my hosted web-server, both from my desktop using the
Nessus Console and as a batch job one the OpenBSD server itself (nessus -T
xml -qx .) - it all worked fine.

Since then, I've upgraded the nessus 2.2.2 that came with the OpenBSD
distrib to nessus 2.2.6, and even though the compilation and installation
went absolutely fine, when I run the test again I get the following:

 

[Mon Dec  5 16:57:39 2005][13599] ssh_settings.nasl (process 27839) finished
its job in 0.089 seconds 

[Mon Dec  5 16:57:39 2005][13599] user nessuser : launching labrea.nasl
against [my_host] [25855] 

[Mon Dec  5 16:57:46 2005][13599] labrea.nasl (process 25855) finished its
job in 7.601 seconds 

[Mon Dec  5 16:57:46 2005][13599] user nessuser : launching ping_host.nasl
against [my_host] [26091] 

[Mon Dec  5 16:57:49 2005][13599] ping_host.nasl (process 26091) finished
its job in 3.021 seconds 

[Mon Dec  5 16:57:49 2005][13599] user nessuser : launching
TLD_wildcard.nasl against [my_host] [25923] 

[Mon Dec  5 16:57:49 2005][13599] user nessuser : The remote host
([my_host]) is dead 

[Mon Dec  5 16:57:49 2005][13599] Finished testing [my_host]. Time : 11.23
secs 

[Mon Dec  5 16:57:49 2005][29372] user nessuser : test complete

[Mon Dec  5 16:57:49 2005][29372] user nessuser : Nothing interesting found
- deleting the session 

[Mon Dec  5 16:57:50 2005][29372] Total time to scan all hosts : 13 seconds

 

Now, I know for a fact that the host is not dead, which in my mind is
further confirmed by the fact that labrea.nasl and ping_host.nasl did not
report the problem - I've increased the timeouts in nessusd.conf, but with
no success.

 

Has anybody got an idea of what the problem is, or how I could do some
further investigations?

 

Thanks for the help,

 

Olivier Vigneresse

Hive Ltd

PO Box 206, Rhyl

Denbighshire, LL18 1WY, U.K.

Tel:      +44 (0)7986 00 54 52

Fax:     +44 (01745) 339 802

Email:   Olivier.Vigneresse@hive.uk.com

 

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>