-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Explain about the old password hash wipe in "invalid password" message #47
Labels
Comments
Good point. I'll see if I can add this some time next week. |
Something's still funny with the password wipe. A user reported getting a 500 error when trying to login. The logs show:
Their password field is empty in the database, but the salt is not. |
Fixed. Might have been introduced by my usage of friend. |
swr1bm86
pushed a commit
to swr1bm86/clojars-web
that referenced
this issue
Oct 3, 2015
swr1bm86
pushed a commit
to swr1bm86/clojars-web
that referenced
this issue
Oct 3, 2015
Check for empty password before passing to bcrypt. Otherwise when a user logs in and has a wiped password bcrypt will die. Fixes clojars#47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's no indication on the website that the old salted SHA1 password hashes have been wiped. So users who don't rigorously read the Clojure mailing list, disclojure, twitter etc aren't aware of it. This is causing confusion: someone emailed me asking if logins to the site were broken globally.
When displaying "invalid password" we should link to an explanation like Phil's mailing list announcement and suggest using the "forgot password" feature.
https://groups.google.com/group/clojure/browse_thread/thread/5e0d48d2b82df39b
The text was updated successfully, but these errors were encountered: