Re: Disable service identification

Waiting doesn't fix it.  I confirmed this by letting one of them sit over 
night.  In the morning, I could still not telnet or ftp to it.

Do you recall if xaudio has ever been a problem with Nessus?

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


Le Thu, 12 Jul 2007 15:39:56 -0400,
"Pete Duffin" <pduffin@blabbernet.net> a écrit :

> It doesn't actually crash, any existing connections remain just fine.

Established connections are not handled by inetd.

> However, no new connections can be established.

Do you have any log message about inetd disabling failing or looping 
services?

> The only way to fix it is to restart inetd.

Or wait for a while (5 min)
Or send SIGHUP to inetd

I suppose...

> I have confirmed that the identify services portion is the culprit

Probably not.

> I have disabled all of the service detection plugins, and it doesn't
> break.

Yes, of course. And the Nessus report will be useless.

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