This repository has been archived by the owner on Dec 9, 2020. It is now read-only.
Corrected magic number auth bug with leading characters in MS Teams #58
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
Magic number string comparison was thrown off in MS Teams by user potentially pasting leading/trailing carriage return, etc., modified code to check for "containing" substring instead, while limiting comparison string length (to protect against brute force attempts).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Magic number string comparison was thrown off in MS Teams by user potentially pasting leading/trailing carriage return, etc., modified code to check for "containing" substring instead, while limiting comparison string length (to protect against brute force attempts).
Note: text.Length (comparison string length) limited to 18 to account for possible leading AND trailing characters