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]

Re: Disable service identification

Subject: Re: Disable service identification
Date: Sat, 14 Jul 2007 10:57:04 +0300
Le Fri, 13 Jul 2007 17:47:36 -0400,
"Pete Duffin" <pduffin@blabbernet.net> a écrit :

I reproduced the state where inetd doesn't allow telnet, ftp, etc...
I checked the console as well as the messages log and found nothing,
other than an xaudio error message.

That's odd. inetd should only disable the failing service, not the
other ones. And the manual clearly says that the "broken" service
should be enabled again after 10 minutes.
But I still don't believe that Nessus could kill inetd, mainly because
inetd does nothing special with the incoming connections. It does not
read data from them.

You should increase those two paramaters. 
e.g. run inetd with -r 2000 60 instead of the default -r 40 60

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

<Prev in Thread] Current Thread [Next in Thread>