Fix logic in xfr ReadMsg + add test #1649
Merged
Conversation
This file contains hidden or 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
|
your rational makes sense |
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.
Hi!
This fixes a possible bug where a xfr client can skip tsig validation if the server doesn't respond with a tsig.
Say I setup an xfr client with a tsig provider. If it connects to a server which doesn't implement tsig, but that server can perform a transfer without adding the tsig to the response then the current logic will skip validation.
m.IsTsig() && t.tsigProvider()is going to look for the tsig in the message, see none and consider the transfer valid, but I think the client should be checking the signature since the tsig provider is configured on the client.