News for hackers. Stuff that matters.
Re:Password Security The Right Way by tptacek on Wednesday October 24, 2012 @12:58PM (#4693812)
I'm pretty sure your actual bcrypted password doesn't have that cost factor on it.
Re:Password Security The Right Way by AgentConundrum on Wednesday October 24, 2012 @01:06PM (#4693867)
Why not? You'd rather have inferior security than wait a minute and a half[1] to access your accounts?

Shame on you, Thomas! I thought you were a professional!

[1] Based on a remarkably unscientific test I just ran on an Ubuntu 12.04 VM on my laptop. 87.8 seconds.

Re:Password Security The Right Way by MattRogish on Wednesday October 24, 2012 @01:03PM (#4693843)
That's how rails stores it in the database, so trying to be as transparent as possible.
Re:Password Security The Right Way by tptacek on Wednesday October 24, 2012 @01:15PM (#4693912)
It takes 3 minutes to log into your application?
Re:Password Security The Right Way by MattRogish on Wednesday October 24, 2012 @01:56PM (#4694127)
You are absolutely right. This is not our production app (ours is at 12 IIRC) but some internals app I've been playing with.
Re:Password Security The Right Way by tptacek on Wednesday October 24, 2012 @02:00PM (#4694136)
Ok just so you know the default cost factor for bcrypt-ruby is a reasonable choice, and the cost factor you've used here is unreasonable.
Re:Password Security The Right Way by MattRogish on Wednesday October 24, 2012 @02:08PM (#4694182)
Absolutely. Was trying (but failing) to make a joke.
Re:Password Security The Right Way by jgeorge on Wednesday October 24, 2012 @03:36PM (#4694640)
BCrypt 19s are <40s to encrypt here, using Java and not even native code. Certainly not outside the realm of usability for something you don't authenticate against all the time. I wouldn't want that for my screenlock password, but I can still see it being workable.