Fix init nvticache init. #459
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jjnicola
force-pushed
the
dont-init-plugins
branch
from
4575387
to
4b85ddd
Compare
Add a new function to initialize the nvticache without loading the plugins.
jjnicola
force-pushed
the
dont-init-plugins
branch
from
4b85ddd
to
bea2837
Compare
bjoernricks
approved these changes
Mar 5, 2020
With PR #458 I avoid to load plugins when a scan starts, since the plugins load up must be done calling openvas with --update-nvt-feed option. During this plugins load at the init of openvas, it was also done the nvticache init, necessary for the scan. With this PR, I split the function and now I openvas can init the nvticache when a new start scan, but without loading up the plugins. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a new function to initialize the nvticache without loading the plugins.