-
Notifications
You must be signed in to change notification settings - Fork 9
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
Store hashes of passwords #9
Comments
@gragland let me know if you want to see this implemented. I might be able to work on it. |
Hey there, I'm not sure I understand the point of adding any kind of security here, as this is only meant to be used when prototyping and the code of this library isn't really intended to be a good example of a production auth system (which would look very different and hashing would happen on the server). Maybe you can clarify your reasoning? |
@gragland I understand that this library is for prototyping, and a production-level security is not needed. However, storing plain passwords might really damage your reputation. In my case, that surprised me, and not in a good way. Perhaps, consider setting expectations clearly that the password will be stored unhashed when using fake-auth (on the registration form or as a pop-up). |
And by the way, it's really easy to use hashes (even with salt and multiple rounds). There is this library called
this produces something like
I think any eng would appreciate this little security measure in fake-auth. |
Store hashes of passwords instead of the original passwords. Optionally, apply salt to it.
Context
Currently, passwords seem to be stored in its original form in Local Storage under
auth-db-fa5
key:This sets a bad example. I think it's much better to implement simple logic of using hashes instead (perhaps even including salt, but not necessary).
The text was updated successfully, but these errors were encountered: