I know this is not critical (after all, it works fine), but I also don't see why hard-code something that could be configurable (especially that contrib apps should be as flexible as possible, IMHO). I've implemented this for myself anyway[1], but this probably could be improved.
On 20 Wrz, 13:20, Russell Keith-Magee <[email protected]> wrote: > contrib.auth currently supports MD5, SHA1 and crypt, which IMHO covers > all the important bases. If you think there is an obvious candidate > that is missing, I think I'd rather see us add specific support for > that algorithm rather than a pluggable interface. Well, there's entire SHA-2 family, PBKDF2 (and other KDFs, like bcrypt or scrypt); and in near future, SHA-3. Having pluggable interface would simplify adding new algorithms and possibly removing those kept for backwards compatibility in the future. Thanks for the reply. [1]: http://bitbucket.org/piotrlegnica/django-trunk-patches/src/tip/auth-password-algorithms.patch --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
