Update from code changes: token version and salt entropy fix - #24
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: token version and salt entropy fix#24mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Documents the challenge token construction version (
v: 1), the Argon2id salt entropy fix, and the clarification that bothargonProfiletiers currently share the same tuning.Changes
vfield to the challenge token payload table and explained fail-closed behavior for unknown versionsinvalid-tokenwarning reason to cover unknown construction versions'mobile'and'standard'Argon2id profiles currently resolve to the same parameters, and why picking a tier now is safeContext
Ribaunt v0.2.6 strengthens challenge entropy to 16 random bytes, embeds a
v: 1construction version in every token so future changes cannot break in-flight tokens, and keeps legacy tokens verifying. Both Argon2id profile tiers intentionally share the same conservative tuning for now.ribaunt/ribaunt#25