A long time ago, I posted about an issue where OpenVAS was not loading custom 
plugins.  I could run them with the openvas-nasl command-line tool, but they 
would not appear in GSA as a plugin I could add to a scan config.  At the time, 
I was running OpenVAS 5.  I recently tried to update to OpenVAS 8 and I seem to 
have completely broken my install.
I downloaded the source for all the OpenVAS 8 components, built, and installed 
them.  I migrated the database with openvasmd --migrate, and all was good, 
except I was finding that OpenVAS *still* wasn't loading my custom plugins.  I 
looked in the openvassd.messages log, and it said it was loading them, but when 
I try to make a scan config, they're not in the list of plugins.

I decided to try deleting my tasks.db database and starting over, and 
everything went to hell.

I've done so many things in the last couple days to try to fix it that I can't 
really retrace my steps effectively, but I can tell you what's happening now.

Starting with no tasks.db file and no certificates but with the plugins 
downloaded, I take the following steps:

Run openvas-check-setup, it says there's no CA certificate for the scanner and 
to run openvas-mkcert.  I do that and accept all the default options and the 
certs get built and installed.  Next, openvas-check-setup says to make the 
certs for the manager with openvas-mkcert-client -n -i, I do that, again with 
default options.  Next it says that there's no OpenVAS manager database and to 
run openvasmd --rebuild while the scanner is running.  I run "openvassd", then 
"openvasmd --rebuild".  It only takes about 6 seconds.  Then check setup says 
to create a user, so I do so.  I run openvas-check-setup again, but now there's 
a problem.

It says the number of NVTs in the database is too low and to run openvasmd 
--rebuild while the scanner is running, but it ALSO says that the scanner isn't 
running and that I need to start it, but it actually *is* running.  If I do `ps 
aux | grep openvas` then I can see openvassd is running and Waiting for 
incoming connections.  If I try to run openvasmd --rebuild anyways, it 
immediately returns.  I check the openvasmd.log file, and it says the 
certificate is not trusted and doesn't have a known issuer.  Strange...I run 
openvas-mkcert again and restart openvassd, then try to openvasmd --rebuild 
again.  It returns after a few seconds, and openvas-check-setup still says the 
scanner isn't running and I need to rebuild the database.  I check the 
openvasmd log again and this time, it says "openvas_scanner_read: failed to 
read from server: A TLS packet with unexpected length was received."

I've attached the openvas-check-setup.log file from my last run.

Attachment: openvas-check-setup.log
Description: openvas-check-setup.log

_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to