It is advisable to use FQDN with regards to the plugin downloads if at all
possible. It may become necessary in the future to add additional resources
for downloads via multiple download sites and for the purposes of redundancy
in multiple download locations (a failover location with a different IP
already exists). In such a case, a fixed IP might fail. Also if the site
is moved to a new address space entirely, this would also cause the firewall
rule to fail. As Nessus and Tenable grow, changes in address space are
likely.
Regards,
Daniel Bowman - Director of Support & MIS
Tenable Network Security
http://www.tenablesecurity.com/
________________________________
From: nessus-bounces@list.nessus.org [mailto:nessus-bounces@list.nessus.org]
On Behalf Of Michael Chapman
Sent: Friday, March 24, 2006 5:34 PM
To: nessus@list.nessus.org
Subject: Re: setting up auto fetch of plugins on updated version
On 3/23/06, Renaud Deraison <deraison@nessus.org> wrote:
On Mar 23, 2006, at 12:36 PM, Michael Chapman wrote:
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?
Yes, this is were the plugins are downloaded from. If you are a
customer, then another hostname/IP is used for the plugins downloads
(plugins-customers.nessus.org <http://plugins-customers.nessus.org> )
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
