News for hackers. Stuff that matters.
Re:The scrypt parameters by eropple on Thursday December 28, 2017 @10:05AM (#16022325)
I don't see how that'd be the case. An attacker who has visibility into the client that has the salt can already see the plaintext password. And an attacker on the service side of things can see the salt anyway, it's in the database.
Re:The scrypt parameters by Buge on Thursday December 28, 2017 @04:24PM (#16025008)
>An attacker who has visibility into the client that has the salt can already see the plaintext password.

There is no way for the server to distinguish a legitimate user trying to login from an attacker trying to hack someone. So if the salt is sent to a legitimate client, the salt will also be sent to attackers.

I'm not sure if sending the salt to attackers is really a vulnerability though.

Re:The scrypt parameters by jedisct1 on Thursday December 28, 2017 @10:13AM (#16022358)
An attacker that would have the ability to impersonate the server could precompute a rainbow table for a given salt, and send that salt to the client.

OTOH, without client-side prehashing, an attacker that has the ability to impersonate the server doesn't have to precompute anything in order to collect all passwords.

Re:The scrypt parameters by Franciscouzo on Thursday December 28, 2017 @10:53AM (#16022659)
If an attacker is able to impersonate the server, then it is also able to ask the client for the password by modifying the Javascript sent.
Re:The scrypt parameters by jedisct1 on Thursday December 28, 2017 @11:11AM (#16022836)
All clients are not web browsers, but sure.