@robkelk: "This change happened in July of 2012"
@TvT Rivals: You didn't post the salt along with the hash. You have to assume that if you're compromised, the salt and the hash are both compromised, because they're stored in the same location. (Well, unless you have a salt microservice, and then God help you.) Salts are still a great idea, as they prevent any kind of rainbow table attack ??. I am curious why you didn't choose one of the stock solutions today like bcrypt or scrypt. The bcrypt algorithm is designed to be configurably slow so the cracking difficulty level can be increased along with Moore's Law. The scrypt approach is similar, but it also uses a lot of memory so that one cannot simply parallelize into Mordor.
I think I have some reviews I've emailed to Geth that I could post.
And finally, I wrote and deployed an entirely new version of SectionHide -- this time called HideSection. Hopefully this will work better for everyone; let me know if you have any problems. I already found one, but I filed a bug on VisualEditor and patched the CSS.
-- ∇×V
@TvT Rivals: You didn't post the salt along with the hash. You have to assume that if you're compromised, the salt and the hash are both compromised, because they're stored in the same location. (Well, unless you have a salt microservice, and then God help you.) Salts are still a great idea, as they prevent any kind of rainbow table attack ??. I am curious why you didn't choose one of the stock solutions today like bcrypt or scrypt. The bcrypt algorithm is designed to be configurably slow so the cracking difficulty level can be increased along with Moore's Law. The scrypt approach is similar, but it also uses a lot of memory so that one cannot simply parallelize into Mordor.
I think I have some reviews I've emailed to Geth that I could post.
And finally, I wrote and deployed an entirely new version of SectionHide -- this time called HideSection. Hopefully this will work better for everyone; let me know if you have any problems. I already found one, but I filed a bug on VisualEditor and patched the CSS.
-- ∇×V