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: | setting up auto fetch of plugins on updated version |
|---|---|
| Date: | Thu, 23 Mar 2006 12:36:51 -0500 |
Hi all, This is my first post here so please go easy on me. I have a number of questions: Has the IP address changed where nessus-fetch connects to to retrieve plugins between versions? I installed nessus a while ago at home (2.2.4) and recently at work (2.2.5) which I have now updated to 2.2.7. I'm behind a firewall at work and since I couldn't find the IP nessus connects to I observed nessus-fetch at home with netstat connecting to 66.240.11.101. Based on this I created a firewall rule at work to allow https to this IP but nessus could not connect. This was with version 2.2.5. I got this error suggesting that the IP should be right as www.nessus.orgtranslates to 66.240.11.101 nessus-fetch --plugins Could not open connection to www.nessus.org - Operation now in progress Then I tried --check: /usr/local/bin/nessus-fetch --check nessus-fetch is not configured to receive a direct plugin feed Now this version was registered manually so I figured that's the reason for the message. I couldn't find anything in the conf file where it may be configured to receive a direct plugin therefore I decided to upgrade as the new version was available anyway. I uninstalled v2.2.5 leaving the configuration files alone (which may have been a mistake in hindsight) and installed v2.2.7 which I tried to register with the firewall rule in place but got this: nessus-fetch --register xxxx-xxxx..... could not connect to plugins.nessus.org - Operation now in progress plugins.nessus.org translates to 66.240.11.107 and I also found a reference in the mail archives that https to 66.240.11.107 worked for someone else. My firewall rule will be updated with the .107 address in a day or two. Will this IP work for plugins and registration? Do I have to configure nessus somewhere else to receive direct plugins since the previous install was not? Sorry about the length. Thanks in advance.
_______________________________________________ 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: custom nessusrc being overwritten, George A. Theall |
|---|---|
| Next by Date: | Re: setting up auto fetch of plugins on updated version, Renaud Deraison |
| Previous by Thread: | custom nessusrc being overwritten, R. Brockway |
| Next by Thread: | Re: setting up auto fetch of plugins on updated version, Renaud Deraison |
| Indexes: | [Date] [Thread] [Top] [All Lists] |