M-
I was not aware that it was default, immutable behaviour. I tried
creating a second '.rc' file that I specified on the command line and it
works fine, thanks for the tip. Manually adding each plugin as needed
is fine with me because I'm only scanning for 2-4 types of
vulnerabilities at once so minor modifications now and then are cool.
-erich
M. Velasquez wrote:
Erich,
I thought this was the default behaviour.
I created a separaten '.rc' file and specify that on the commandline
when I do a scan (that way the .nessurc file may get updated. but not
the one I use for scanning). Of course, now you have to manually add
each pluginid to your '.rc' file.
Hope this helps
M
Erich Weiler wrote:
I have a problem that I was hoping someone would have some insight on:
I run nessus via command line by cron a few times daily to scan some
of our local subnets. I then parse the output with a script I have to
accomplish some other tasks.
Basically, right now, I only want to scan for the new Microsoft PnP
vulnerbaility. So, in my .nessusrc file, I have only 2 plugins, 19407
and 19408, set to "yes". I also have a bunch of rules set in the
rules section.
All goes well for a while. Then I run the "nessus_update_plugins"
cron job at midnight, and new plugins are downloaded. Next time I
scan again, it finds tons of stuff that I didn't ask it to search
for. I look at the .nessusrc file, and there are like 20 plugins at
the bottom of the plugin list set to "yes"! I assume these are the
newly downloaded plugins, but I don't want them to be set to "yes"
automatically. Also, it looks like my RULES were removed.
Anyone else seen this? Is my only option not to update the plugins?
Or is there a way around it?
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
