📋 refactor: allow paste in confirm field when resetting passwords #2542
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
I've simply commented out the section where paste prevention is defined. Not allowing users to paste passwords makes it harder to use long passwords from password managers that are not browser plugins (e.g. keepass). NIST says it better than me,
NIST SP 800-53B, Section 5.1.1.2, Paragraph 10
https://pages.nist.gov/800-63-3/sp800-63b.html
Change Type
Testing
In the
deploy-compose.yml
file, change theapi
service to build a image locally rather than pullingghcr.io/danny-avila/librechat-dev-api:latest
.Start the containers, ask to reset the password of your user, click the link in the mail you get, and try to paste your password into both fields. Previously you could only paste into the "Password" field, and not the "Confirm password" field.
Checklist
Please delete any irrelevant options.