Exporting The Plugins Directory?

[Jared M Breland]

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 Breland                 International Paper
jared.breland at ipaper.com      Information Security
901-419-5077                  http://irm.ipaper.com/



                                                                           
             "Erik Stephens"                                               
             <erik at edgeos.com>                                             
             Sent by:                                                   To 
             nessus-bounces at li         "Pete Vingh" <petevingh at yahoo.com>  
             st.nessus.org                                              cc 
                                       nessus at list.nessus.org              
                                                                   Subject 
             11/10/2004 09:24          Re: Exporting The Plugins           
             AM                        Directory?                          
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




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