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. |

| Subject: | Re: Securing nessusd |
|---|---|
| Date: | Thu, 14 Sep 2006 06:31:01 -0400 (EDT) |
On Thu, 14 Sep 2006, Patrick Derwael wrote:
Josh,
My understanding of the nessusd.rules is that this is used to limit the hosts one can scan, not the connection between the NessusWX client and the nessusd daemon. Am I right or wrong here ?
You are correct. Nessus does not have any built in capability to limit who can connect to the daemon. You will need to use a third party application such as tcpwrappers, iptables etc.
-- - Josh _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Securing nessusd, Patrick Derwael |
|---|---|
| Next by Date: | RE: Securing nessusd, Jim Hendrick |
| Previous by Thread: | Re: Securing nessusd, Patrick Derwael |
| Next by Thread: | Re: Securing nessusd, Patrick Derwael |
| Indexes: | [Date] [Thread] [Top] [All Lists] |