Re:JavaScript is now required to sign in to Google
by devy on Wednesday October 31, 2018 @08:08PM
(#18350340)
Yep. Proper password hashing requires per-credential salt, pepper (for all credentials) and a strong algorithm (IV, iterations etc.) Revealing all those information is a leak and arguably making client side hashing less secure (by giving away a lot of parameters for attackers to attack)
Re:JavaScript is now required to sign in to Google
by eropple on Thursday November 01, 2018 @02:01AM
(#18351730)
NIST may say that you should use "peppers" for passwords, but nobody else does.
None of bcrypt, scrypt, or Argon2 use them and are not materially worse for it.
Re:JavaScript is now required to sign in to Google
by devy on Thursday November 01, 2018 @10:55AM
(#18354442)
Yes, adding pepper is a recommendation not a mandatory step. But a lot of sites do, I.E. PagerDuty [1], paired with PBKDF2
as many apps requires to meet FIPS certification or enterprise support on many platforms.[2]
[1]: https://sudo.pagerduty.com/for_engineers/
[2]: https://www.owasp.org/index.php/Password_Storage_Cheat_Sheet
Re:JavaScript is now required to sign in to Google
by totony on Wednesday October 31, 2018 @08:13PM
(#18350377)
Salts are not meant to be secret, nor are the hashing functions. You gain little by hiding them
Re:JavaScript is now required to sign in to Google
by stevewodil on Wednesday October 31, 2018 @08:08PM
(#18350348)
if you're in the position to or are developing an app use argon2!
TLDR don't do that, send passwords over SSL and use a good password hashing algorithm on the server like BCrypt.