Disable 'Bit 0x20' mixed case option in dns resolve of libevent2 driver to make it working like other drivers #1366
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
…er to make it working like other drivers
|
Interesting, didn't know about this. Kind of a pity, but there seems to be no way around it other than a server white list. |
s-ludwig
added a commit
that referenced
this pull request
Jan 8, 2016
Disable 'Bit 0x20' mixed case option in dns resolve of libevent2 driver to make it working like other drivers
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.
I found that not all DNS servers support the 'Bit 0x20' security mechanism (randomize query names to avoid hacking responses).
Libevent2 enables it by default(all other drivers do not enable it) and sometimes fail on resolveHost(), so it is better to disable it by default to avoid such problems.