I wrote a quick off-list reply to this last night, but thought it might be worth pointing out parts of it publicly as well so anyone who searches the archives with similar problems will spot this:
1. Django does still support plain old unsalted md5 passwords for login (for backwards compatibility reasons), but the first time a user successfully logs in it'll be transparently converted and re-stored as a salted SHA1. Disabling that is a minor change in Django's auth code, and is one approach. 2. But a better approach would probably be a custom auth backend; this would let you continue to use all the features of Django's authentication system, while checking credentials directly against the legacy database for maximum compatibility. Auth backends aren't terribly hard to write, and the documentation makes it pretty clear what needs to be done: http://www.djangoproject.com/documentation/authentication/#other-authentication-sources -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
