On 3 October 2007 (Wed), James Bennett wrote: > So don't use set_password(), and avoid any built-in views which try to > hash things.
That's not all. I won't be able to use check_password(), which also calls get_hexdigest(). And I'll have to reimplement ModelBackend because of that, and possibly some other things. And I'll have to tweak admin interface to make password changing work. I'd really like to see some cleaner and simpler solution. > And make sure your stakeholders are OK with the security > implications of storing passwords in plain text. Actually, this is exactly what they want, so I guess it can't be helped. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
