On 2/8/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > But set_password will only set a sha1 password. So why would the > global check_password need to check if the algo is 'md5' if > set_password could never use md5?
Django used to use MD5 hashes; that function is in there so that an old installation which was using MD5 can be upgraded and get switched over to SHA1 without needing to manually go through and reset passwords. -- "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 -~----------~----~----~----~------~----~------~--~---
