#33793: Check for PASSWORD_HASHERS
-------------------------------------+-------------------------------------
Reporter: Francisco Couzo | Owner: nobody
Type: New feature | Status: closed
Component: Core (System | Version:
checks) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
Django keeps "weak" password hashers for support with legacy systems and
[https://docs.djangoproject.com/en/stable/topics/testing/overview
/#password-hashing speeding up the tests]. Moreover they are not enabled
by [https://docs.djangoproject.com/en/stable/ref/settings/#password-
hashers default], so you must add them explicitly to the
`PASSWORD_HASHERS`. Folks that do this should be aware of their weakness.
IMO there is not need for a new system check.
You can start a discussion on DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/33793#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701818507c33c-d51bef27-672d-48d9-9f87-6d3c32f195a1-000000%40eu-central-1.amazonses.com.
