Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suggestion: do not demonstrate storing a password in plain text #4

Closed
kardianos opened this issue Apr 12, 2017 · 3 comments
Closed
Milestone

Comments

@kardianos
Copy link

Examples should often take extra steps to be correct. When demonstrating how to display an error message to the user:
https://github.com/Checkmarx/Go-SCP/blob/c3471ef24a7c2ca6a769457783f43c60712f087a/authentication-password-management/communicating-authentication-data.md

The password check is apparently stored in plain text. I would recommend returning fields called PasswordHash and Salt then doing some fake calls to verify that against the given password in the example.

@PauloASilva
Copy link
Collaborator

Hi @kardianos,
I do agree with your suggestion: including/returning names like PasswordHash and Salt makes sense to get readers as familiar with them as they are with common username and password ones.

We would be glad to accept a Pull Request from you, following the suggested approach, otherwise we will put it on our changes queue for the next release.

Thanks for sharing,
Paulo

@PauloASilva PauloASilva added this to the v1.1 milestone Apr 13, 2017
@Jack64
Copy link

Jack64 commented Apr 29, 2017

@kardianos @PauloASilva adjusted #31 to include a fix for this issue. Let me know if you think that's sufficiently clear or requires additional remarks.

@kardianos
Copy link
Author

I find salt would give it more flavor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants