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> |
|---|---|---|
| ||
| Previous by Date: | Export/Import Policies with Nessus Windows, Steve_Mullen |
|---|---|
| Next by Date: | Starting CGI Abuses scans on a subsite, Steven Haryanto |
| Previous by Thread: | Export/Import Policies with Nessus Windows, Steve_Mullen |
| Next by Thread: | Re: losing configuration (listening interface) when updating Nessus3, Renaud Deraison |
| Indexes: | [Date] [Thread] [Top] [All Lists] |