...this can not be a real solution for corporate networks with only one centralized http-proxy. (maybe for home users ?)
> hi, > > On Fri, 2004-12-10 at 12:33, Davide Messana wrote: > > When I run the command nessus-update-plugins -vv I get the following > > message: > > + /usr/local/bin/nessus-fetch --plugins-md5 > > An unknown HTTP error occured (http error code: 404) > > Could not retrieve the plugins MD5 > > Aborting > > i notice that if your proxy's traffic is upstreamed to another proxy, > you may encoutered this error message. > Setting the proxy variable in your $prefix/etc/nessus/nessus-fetch.rc to > the proxy that directly talks to www.nessus.org should do the trick. > > tan > > _______________________________________________ > Nessus mailing list > [EMAIL PROTECTED] > http://mail.nessus.org/mailman/listinfo/nessus > -- NCSISU Non Certified Security Information Systems User GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail +++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++ _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
