Improve log message for WMI connect failed or missing WMI support. #670
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
The message suggest that the connect failed can be produce because missing WMI support.
ArnoStiefvater
approved these changes
Mar 9, 2021
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.
What:
Both, a WMI connect failed or the WMI stub function return NULL.
The message suggest that the connect failed can be produce because
missing WMI support.
Why:
To let now the user that the libopenvas_wmiclient is missing. See openvas-smb
How:
Build the scanner from scratch, but remove/rename the openvas-smb libs, so you don't have WMI support. Run a scan and check the log.
Checklist: