"Work around" for IPv6 Crash and Evasion Tracking issues #39
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
"Work around" for IPv6 Crash.
"Work around" for IPv6 Crash.
Only activate evasion tracking during failed username/password and not for requests without auth header or hash expired, else there's high probability it will end up in evasion period when a browser sends lots of requests at once.
Nazar78
changed the title
|
Sorry, upon further testing and some reading, it seems triggering the evasive tracking only at nc=00000001 is useless because it's easily bypassed by the client. Closing this PR for now. |
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.
"Work around" for IPv6 Crash:
Opened the issue for the IPv6 Crash here #38.
Evasion Tracking:
Only activate evasion tracking during failed username/password and not for requests without auth header or hash expired, else there's high probability it will end up in evasion period when a browser sends lots of requests at once.