News for hackers. Stuff that matters.
Re:The Dirty Truth About Web Passwords by ZoFreX on Tuesday December 14, 2010 @02:27PM (#2005380)
I'm not sure what advice to give you. You commonly see advice to outsource your security, to other libraries, the idea being these are more likely to be correct than you. However, there have been some pretty high profile mistakes in common crypto libraries too! If there's anything specific you have in mind, I'd be happy to field questions (and hopefully other HN users will correct me in the event I'm wrong!)
Re:The Dirty Truth About Web Passwords by rahoulb on Tuesday December 14, 2010 @04:09PM (#2005745)
Cheers (that's why I love this place).

At the moment I use Authlogic in Rails, which uses SHA512 by default (SHA512 is built into the Ruby core libs).

But I also notice that it's quite easy to switch to bcrypt (using the bcrypt gem).

Is it worth switching? Or at least using that as my default on new apps?

Re:The Dirty Truth About Web Passwords by ZoFreX on Wednesday December 15, 2010 @04:16AM (#2007539)
What is it being used for, and how is it being used? I'm guessing this is password hashes. Is rails using a unique salt for each password?

Bcrypt is slower than SHA512, in fact it can be made to be very slow. This is actually ideal for password hashes, it doesn't matter if it takes your server 50 milliseconds to calculate a password hash but that would severely slow down an attack.

It is important however that they are being used correctly. Either would be a good solution if properly salted.