Re:Yahoo discloses hack of 1B accounts
by Dylan16807 on Thursday December 15, 2016 @06:43AM
(#13183918)
That's just a bug. Truncation invalidates the 'stored properly' part of the statement.
[ Parent
| on HN ]
Re:Yahoo discloses hack of 1B accounts
by mannykannot on Thursday December 15, 2016 @07:30AM
(#13184112)
Could you expand on that? I did not think bcrypt was responsible for storing the resultant hash. The limit appears to be in calculating the hash.
Re:Yahoo discloses hack of 1B accounts
by Dylan16807 on Thursday December 15, 2016 @02:09PM
(#13187221)
The original phrasing was "stored properly, (i.e. bcrypt)". That's including the hashing as part of the 'storing'. Bcrypt has a size limit, but a size limit is not the same thing as truncating. It's broken code on the front end that truncates instead of doing something like sha512.
Bcrypt spits out a string, that the caller must store, somewhere. I presume the parent post means that Bcrypt "stores" in its output string a value that, for all practical purposes, varies reliably with the same salt but different plaintext.