Hi Ron,
could you tell me how many access points does #11026 plug-in currently
detects?
Thank you
Amy
--------------------------------------------------
From: "Ron Gula" <rgula@tenablesecurity.com>
Sent: Tuesday, March 18, 2008 12:08 PM
To: <nessus@list.nessus.org>
Subject: Re: Verifying latest plugins
Doug V wrote:
Hello Ron,
Doug V wrote:
I am using Fedora 8 with the latest non-beta versions of Nessus and the
Nessus Client installed. I was wondering if there was a command that I
could run to force Nessus to update its plugins or to show the date of
the last update. When I run /opt/nessus/bin/nessus-fetch --check I do
get the "nessus-fetch is properly configured to receive a Registered
feed" response, and in nessusd.conf the auto_update option is set to
"yes", but I would like to verify myself that the latest plugins are
installed.
rgula at tenablesecurity wrote:
If you are on Linux, you can always do an ls -lt | more while in the
/opt/nessus/lib/nessus/plugins directory and look at the time on the
last file. This should
give you some indication of when the last update was.
I entered that command in that directory on Marc 17th, and almost every
single plugin file is dated 2008-01-02. The last few files are:
-r-xr-xr-x 1 root root 66480 2007-06-26 11:52 find_service.nes
-r-xr-xr-x 1 root root 35648 2007-06-26 11:52
nessus_tcp_scanner.nes
-r-xr-xr-x 1 root root 8998 2007-06-26 11:52 ssl_ciphers.nes
-r-xr-xr-x 1 root root 16609 2007-06-26 11:52 synscan.nes
-rw-r--r-- 1 root root 75776 2007-05-04 09:20
compliance_check_windows_file_content.nbin
Is this normal? I have been online several times with the Nessus service
running this month (March 2008). Shouldn't the files date from then and
not last January and last year? It doesn't seem that the auto-update is
working even though I registered.
How can I force an update? Thank you for your time.
Hi Doug,
It looks like your registration process either never happened, had
an error, is being prevented by a proxy or some other reason.
When you get an update, the NASLs won't necessarily have today's
date on them, but they won't be as old as 2008-01-02 either.
I suggest re-registering and paying close attention to any logs
or error messages to see what the issue is.
Ron Gula
Tenable Network Security
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
