Added signature verification support for SMB2 client #300
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.
I added the signature verification for SMB2 messages on client side.
Adding the attribute
m_sessionSetupResponseMessagetoSMB2Clientwas a bit lazy, but the easiest method to implement the check without changing to much of the library code. Maybe you have a better approach in mind @TalAloni ?Tests prove that the manipulation of the signature result in the desired behavior (either discarding the invalid message or disconnect from the server).