Re:Password Hijacking Security Incident and Response
by wulczer on Wednesday January 09, 2013 @04:35PM
(#5033660)
I just gave django.contrib.auth.tokens a read and shared my opinion on it :)
I wouldn't roll my own password reset feature if I can just take the builtin one from Django, which is what I did.
Re:Password Hijacking Security Incident and Response
by tptacek on Wednesday January 09, 2013 @04:41PM
(#5033702)
The good thing about taking your web stack's password reset feature, if it has one, is that you're probably going to find out quickly if there's a bug discovered in it.
Note though that that's not the case for 3rd-party password reset libraries or, more likely, the all-purpose security library that provides it. I'd be very wary about using a 3rd party library for password reset unless they've got a credible for story for it having been reviewed.
Django: Good.
3rd Party Library: Less Good
Just Using A Random Token: Good
Cryptography: You Will Perish In Flames
Re:Password Hijacking Security Incident and Response
by thibaut_barrere on Wednesday January 09, 2013 @06:51PM
(#5034332)
Does Devise [1] qualifies as a properly reviewed 3rd Party Library, to your knowledge?
Asking this since it's probably the most widely used authentication gem in Rails etc...
Personally, I have this particular bit of appsec down cold, and if I was building a new app, I wouldn't even think about it: I'd use a random token and save it in the database.