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]

losing configuration (listening interface) when updating Nessus3

Subject: losing configuration (listening interface) when updating Nessus3
Date: Sun, 12 Nov 2006 21:28:37 +0100
I need to configure Nessus to listen only on loopback interface and
the only way (afaik) to do it is editing nessusd startup script. Last
time I upgraded from Nessus-3.0.2 to Nessus-3.0.4 I overlooked that
the script was replaced and my Nessus server went accessible from the
outside.

I would like to be able to set listening interface and be sure that
when Nessus is upgraded it keeps this configuration. Would it be
possible to do at least one of the following?

1) adding "noreplace" keyword to startup script in %files section in
   the SPEC file

2) rewriting startup script so it reads adititional nessusd startup
   params from /etc/sysconfig/nessus (if it exists)

3) adding nessusd.conf option that sets interface nessusd will listen
   on

Thank you very much

Martin Mačok
ICT Security Consultant
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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