Thanks for all your help. That'll teach me to hack shell scripts at 3:30 on a Friday afternoon... ;-) Quoting and escaping causes issues... Anyway, it appears that I can continue to use the 2.2.0 with the new update method until I can successfully compile the new binaries (2.2.2).
Another question I had was this: In the future can I "activate" my existing code by purchasing a subscription so that scanners will begin downloading the 0 day feed without the need to modify the script? Or do subscribers need to use the new nessus-fetch script? Actually, if nessus-fetch will compile correctly this will soon become a non-issue. It just means modifying the update cron job on each of my scanners. Regards, Luke -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Renaud Deraison Sent: Friday, December 10, 2004 3:31 PM To: [EMAIL PROTECTED] Subject: Re: Problems compiling Nessus 2.2.1 on Solaris On Fri, Dec 10, 2004 at 03:20:14PM -0500, Luke Youngblood wrote: > This is what part of my nessus-update-plugins script looks like now: > > location="http://plugins.nessus.org/get.php\?f\=all-2.0.tar.gz [...] > location_md5="http://plugins.nessus.org/get.php\?f\=all-2.0.tar.gz.md5 [...] > location_sig="http://plugins.nessus.org/get.php\?f\=all-2.0.sig [...] You don't need to escape anything. ie: location="http://plugins.nessus.org/get.php?f=all-2.0.tar.gz&u=..."; location_md5="http://plugins.nessus.org/get.php?f=all-2.0.tar.gz.md5&u=..."; location_sig="http://plugins.nessus.org/get.php?f=all-2.0.sig&u=...."; -- Renaud _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
