Improve cookie authentication tokens#805
Merged
Merged
Conversation
…factor-bounded HMAC-SHA256 tokens
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Replace the token generation in CookieAuthenticator with a new token format. The previous token format had weaknesses that could be used to create an authentication bypass if encrypted cookies were not used.
The
legacyTokensoption provides backwards compatibility for existing tokens, and gives application developers a path to disable legacy token support, which will become the default in a future minor release.Thanks to Gilles Bedel for reporting this issue through the security mailing list.