Re: Disable service identification

It doesn't actually crash, any existing connections remain just fine. 
However, no new connections can be established.  This relates to just about 
all the services in inetd.conf, but of course the most troublesome are ftp 
and telnet.  The only way to fix it is to restart inetd.

I have confirmed that the identify services portion is the culprit as I have 
disabled all of the service detection plugins, and it doesn't break.  Right 
now I am scanning per port listed in inetd.conf to see if I can figure out 
which one is the problem.

----- Original Message ----- 
From: "Michel Arboi" <mikhail@nessus.org>
To: "Pete Duffin" <pduffin@blabbernet.net>
Cc: <nessus@list.nessus.org>
Sent: Thursday, July 12, 2007 3:09 PM
Subject: Re: Disable service identification


Le Thu, 12 Jul 2007 14:48:30 -0400,
"Pete Duffin" <pduffin@blabbernet.net> a écrit :

> Can anyone tell me how I go about disabling service detection?

By not running Nessus. Nearly all tests rely on service detection.

> trying to figure out why nessus is crashing all of our solaris 8
> boxes

Does inetd really crashes or are the ports disabled for a couple of
minutes?

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus