Fix: set transport again if falls back in a unecrypted connection #1190
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
In case of falling back in a unencrypted connection, set the transport to OPENVAS_ENCAPS_IP again.
nichtsfrei
approved these changes
Sep 8, 2022
mergify bot
pushed a commit
that referenced
this pull request
Sep 8, 2022
) In case of falling back in a unencrypted connection, set the transport to OPENVAS_ENCAPS_IP again. (cherry picked from commit c4f5a8c)
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:
In case of falling back in a unencrypted connection, set the transport to OPENVAS_ENCAPS_IP (1) again.
Jira: SC-664
Why:
The transport was kept as OPENVAS_ENCAPS_TLScustom (9)
How:
Run an authenticated scan against a windows. The scan config can be a base ScanConfig + smb_login.nasl.
Without the patch the login is not successful, with patch is possible to login agian.
Checklist: