Exporting The Plugins Directory?

[Jared M Breland]

Shoot, my apologies everyone.  I realized after I clicked Send that this 
was in response to the wrong message.  Please disregard.

--
Jared Breland                   International Paper
jared.breland at ipaper.com        Information Security
901-419-5077                    http://irm.ipaper.com/


nessus-bounces at list.nessus.org wrote on 11/10/2004 09:40:11 AM:

> 
> There is a ton of detail and sample code available at this site. Perhaps
> this could be used to fine-tune the plugin?
> 
> http://www.appsecinc.com/resources/alerts/oracle/2004-0001/
> 
> --
> Jared  
> 
> 
> On Nov 10, 2004, at 6:08 AM, Pete Vingh wrote:
> 
> > I'm lazy/efficient and only want to update plugins
> > once so that multiple machines can have access to the
> > same plugins.  So, would exporting
> > /usr/local/lib/nessus/plugins to a Nessus box allow
> > the Nessus box to see whatever plugins are in the
> > exported filesystem?  Would that be a sound approach?
> 
> If you're trying to avoid downloading the tarball multiple times over
> the internet, then you could fairly easily store a local copy and
> modify nessus-update-plugins to  point to it instead of nessus.org.
> It's just one variable near the top of the script that would need
> changing.  But, that might not be the problem you're trying to solve
> :-)
> 
> 
> Best regards,
> Erik Stephens
> www.edgeos.com
>                                  Managed Vulnerability Assessment
> Services
> 
> _______________________________________________
> Nessus mailing list
> Nessus at list.nessus.org
> http://mail.nessus.org/mailman/listinfo/nessus
> 
> 
> 
> 
> _______________________________________________
> Nessus mailing list
> Nessus at list.nessus.org
> http://mail.nessus.org/mailman/listinfo/nessus
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nessus.org/pipermail/nessus/attachments/20041110/e7949188/attachment.html