[Django] #28660: Remove CryptPasswordHasher

9 views
Skip to first unread message

Django

unread,
Sep 30, 2017, 5:50:53 AM9/30/17
to django-...@googlegroups.com
#28660: Remove CryptPasswordHasher
-------------------------------------+-------------------------------------
Reporter: Mads | Owner: nobody
Jensen |
Type: | Status: new
Cleanup/optimization |
Component: | Version: master
contrib.auth | Keywords: hasher crypt
Severity: Normal | password
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
It's not documented, and is no longer included in any default settings,
and the doc string says it may not be available on all platforms. There's
a single test in `tests/auth_tests/test_hashers.py` for it.

--
Ticket URL: <https://code.djangoproject.com/ticket/28660>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Sep 30, 2017, 8:20:43 AM9/30/17
to django-...@googlegroups.com
#28660: Remove CryptPasswordHasher
-------------------------------------+-------------------------------------
Reporter: Mads Jensen | Owner: Uman
Type: | Shahzad
Cleanup/optimization | Status: assigned
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: hasher crypt | Triage Stage:
password | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Uman Shahzad):

* owner: nobody => Uman Shahzad
* status: new => assigned


--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:1>

Django

unread,
Sep 30, 2017, 8:44:08 AM9/30/17
to django-...@googlegroups.com
#28660: Remove CryptPasswordHasher
-------------------------------------+-------------------------------------

Reporter: Mads Jensen | Owner: Uman
Type: | Shahzad
Cleanup/optimization | Status: assigned
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: hasher crypt | Triage Stage:
password | Unreviewed
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Uman Shahzad):

* has_patch: 0 => 1


--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:2>

Django

unread,
Sep 30, 2017, 10:14:36 AM9/30/17
to django-...@googlegroups.com
#28660: Remove CryptPasswordHasher
-------------------------------------+-------------------------------------

Reporter: Mads Jensen | Owner: Uman
Type: | Shahzad
Cleanup/optimization | Status: assigned
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: hasher crypt | Triage Stage:
password | Unreviewed
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Aymeric Augustin):

It is documented here:
https://docs.djangoproject.com/en/1.11/topics/auth/passwords/#included-
hashers

I'm not seeing a pressing reason to remove this hasher, which may be used
for compatibility with existing password databases.

If there's a decision to remove it, that should go through a deprecation
path.

--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:3>

Django

unread,
Sep 30, 2017, 2:23:01 PM9/30/17
to django-...@googlegroups.com
#28660: Remove CryptPasswordHasher
-------------------------------------+-------------------------------------

Reporter: Mads Jensen | Owner: Uman
Type: | Shahzad
Cleanup/optimization | Status: closed
Component: contrib.auth | Version: master
Severity: Normal | Resolution: wontfix

Keywords: hasher crypt | Triage Stage:
password | Unreviewed
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

* status: assigned => closed
* resolution: => wontfix


Comment:

I agree -- unless a discussion on the DevelopersMailingList yields a
consensus that the original use case in #3316 in obsolete, this hasher
doesn't have much maintenance cost and it's better for there to be a
canonical implementation rather than requiring users to implement it
themselves.

--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:4>

Reply all
Reply to author
Forward
0 new messages