When you try to run both openvas and nessus on the same system (I have to because I develop autonessus which supports both) they both claim the same pot. Both deamons have the -p opetion which allows you to configure the port they listen on, but htis cannot be set via /etc/conf.d/nessusd.conf or /etc/conf.d/openvasd.conf Reproducible: Always Steps to Reproduce: 1. Install openvas 2. Install nessus 3. start nessusd 4. start openvasd 5. Openvasd fails because port is busy Actual Results: 5. Openvasd fails because port is busy Expected Results: Port should be configurable, but isn't
I have attached my custom config and init files for openvas-server. The openvasd Port is now configurable and the stop function has a timeout if openvasd never finishes. Maybe a start-stop-daemon --stop --quit --retry $[TIMEOUT} --exec /usr/sbin/openvasd would do the same, but I dont like the black magic of start-stop-daemon. ;) Maybe the files are worth a newconfd "${FILESDIR}/openvasd.confd" openvasd newinitd "${FILESDIR}/openvasd.initd" openvasd in the ebuild. Take a look.
Created attachment 211790 [details] openvasd init file
Created attachment 211792 [details] openvasd conf.d file
Hi, this blog looks pretty good explained about OpenVAS. I installed OpenVAS on Debian (Raid Systems)(SERVER) nd trying to scan by giving the localhost address or any remote systems… The problem is the report which is getting as an output from openvas is only regarding PORT’s, i just wanted to know is it possible to scan based on application installed in the remote systems or is it possible to scan specific files which i needed to scan respectively. please provide me the best solution for it, waiting for the earliest response. my mail id: avinashvbhat@gmail.com Thanking you, Avinash Bhat
openvas-server removed
I just gave away maintenance of openvas. I'm aware this is an ancient bug, but I also don't think this is even worth fixing, the use case of running both openvas and nessus *at the same time* simply doesn't look very legit.