docs: add password-strength cross-service contract - #296
Merged
Conversation
dargmuesli
changed the title
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
1 participant
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.
Documents the password strength policy that
vibetypeandpostgraphilemust both implement identically, with no code shared between them. Writing this down surfaced two real gaps, now fixed in maevsi/vibetype#2374 and maevsi/postgraphile#40:accountPasswordResetwasn't checked server-side at all, and the 12-character minimum was only enforced client-side. The policy's length floor was lowered to 8 (NIST SP 800-63B's own minimum) since sqitch already enforces exactly that across all three password-setting functions, making a separate server-side length check redundant.