Fix: Unwrap SSL socket before closing transport socket. #737
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.
Unwrap the SSL socket before closing the underlying transport socket instead of just closing SSL socket, to avoid yielding a "The TLS connection was non-properly terminated" warning in gvmd.log on disconnect.
What:
Performing proper disconnect of a TLS connection to skip log warnings from
gvmd
.Why:
TLSConnection
uses a transport socket and TLS socket wrapped on top of it. When disconnecting, the TLS socket was simply closed. Such behavior caused a log warning on thegvmd
side:How:
In the change, on disconnect,
unwrap()
is called first on the TLS socket that closes it and returns the underlying transport socket, then the underlying socket can be closed normally and no warning from thegvmd
server is generated.I tested it using following snippet and observing tail of
gvmd.log
:Checklist:
gvmd
to be tested)