Since the initial proposal to create a server-side database backend,
made a couple of weeks ago has seemed to have died, I've decided
to integrate it into the nessusd code myself.
The problem is that I can't seem to find where the vulnerability
messages generated by the plugins and scanners are sent to the
client...
As far as I can tell, they may be spawned from the check_threads_input
method in nessusd/utils.c. Can anyone confirm this?
Does this input come from the knowledge base?
What I am looking for is a place in the code where I can find the
plugins that found a security note/hole/warning.
Also, I need to do a similar thing with the open ports.
If anyone knows where I can get the open ports and their
associated vulnerabilites on the server-side, your assistance
is appreciated.
Thanks.
----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: wjh3710@rit.edu
made a couple of weeks ago has seemed to have died, I've decided
to integrate it into the nessusd code myself.
The problem is that I can't seem to find where the vulnerability
messages generated by the plugins and scanners are sent to the
client...
As far as I can tell, they may be spawned from the check_threads_input
method in nessusd/utils.c. Can anyone confirm this?
Does this input come from the knowledge base?
What I am looking for is a place in the code where I can find the
plugins that found a security note/hole/warning.
Also, I need to do a similar thing with the open ports.
If anyone knows where I can get the open ports and their
associated vulnerabilites on the server-side, your assistance
is appreciated.
Thanks.
----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: wjh3710@rit.edu