Email pickup took a while here (I just got the last half-hour's email) so since I mailed the query I have:
Determined that the plugin feed version for scans was Sept 13th (I thought I'd gotten the updating fixed since then, oh well) killed the nessus daemon and restarted it (scans are now identified as using Plugin feed version : 200710031215) Sheesh. Now the addplugin script reports 1320 updated plugins and 888 updated. I need to find the time to dig into this because it had been running fine for about 9 months but since the start of the semester nessus has been a bit flakey, especially with updating. (Note, I'm blaming my wrappers or the environment, not nessus. Last year the server wouldn't update but it seemed to connect with a general lack of memory which has since been remedied.) I take it the Tor plugin is recent which is why it wasn't in my 200709130915 version? Thanks for taking the time. Sorry it was me not working it through enough. Tim Doty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of George A. Theall Sent: Wednesday, October 03, 2007 11:08 AM To: [email protected] Subject: Re: Tor Detection On 10/03/07 12:02, Doty, Timothy T. wrote: > A quick google on Tor detection found > http://www.nessus.org/plugins/index.php?view=single&id=26026 -- but > that plugin doesn't seem to be available to my nessus server? Are your plugin updates working? What does plugin_feed_info.inc, in the plugins directory, contain? Does the problem persist if you rebuild the plugins database ("nessusd -R") and restart Nessus? Do you have a file named tor_server_detect.nasl in the plugins directory? George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
