Closed rye closed 3 years ago
Still need to test this by completely shutting everything down and booting a fresh instance on the master
branch, then upgrading to this to ensure that the migration procedures are all working properly.
I'll do that tonight, then test the migration.
No, this won't work at all.
The greenbone/openvas repository no longer contains any daemonization code (so, we can't run a server and connect to it from GVMD anymore).
It appears we need to use ospd-openvas
, per this comment.
I think the migration plan is now going to be to add ospd-openvas
to the openvas container and have that control openvas instead.
And yes, per https://github.com/greenbone/openvas/blob/master/INSTALL.md, we now have
The scanner module does not run as a service as before any more. gvmd can act as a client and control the scanner through the
OSPD-OpenVAS
module. The actual user interfaces (for example GSA or GVM-Tools) will only interact with gvmd and/or ospd-openvas, not the scanner. You can launch openvas to upload the plugins in redis using the following command:openvas -u
but ospd-openvas will do the update automatically each time a new feed is detected.
Constituting a major version upgrade, this PR contains the required changes to build the new versions of OpenVAS.