Clarify wording of password sending recommendation #87
Conversation
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
2 tasks
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 :
This includes a small improvement in wording in 04-design/02-web-app-checklist/06-digital-identity.md
The recommendation for sending passwords can be read two ways, either as "Always send non-temporary passwords encrypted" or as "Don't send temporary passwords encrypted". This commit clarifies that the former interpretation is the intended one.
Description for the changelog :
Clarify wording of password sending recommendation
Declaration:
Other info :
Thanks for submitting a pull request!
Please make sure you follow our Code of Conduct
and our contributing guidelines
Automated tests are run to check links, markdown and spelling
The pull request must pass these tests before it can be merged