On 2/8/07, TR <[EMAIL PROTECTED]> wrote: > Which would be right, if you couldn't use a broken hash algorithm to > login without the right password, but something that just generates > the same hash - in other words, knowing the hash (poking at the db, > SQL injection, anything) you don't need the password. It's like > storing a clear text password, and you wouldn't argue that's a good > idea, no?
Well, the important thing here is that in order to take over a user's account by generating a hash collision, an attacker has to know *in advance* the hash to generate the collision for. And if your attacker has enough access to get that information out of your database, I don't really see how choosing a different hash algorithm could help you out -- if the attacker can retrieve password hashes, it's likely she no longer needs to generate collisions in order to impersonate people (and, since the DB entries contain the salt used to generate the hash, a standard dictionary attack is likely to be a much more efficient use of the attacker's resources if she does need to do that). -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
