Re: [Django] #37078: Change default algorithm of salted_hmac() from SHA-1 to SHA-256

1 view
Skip to first unread message

Django

unread,
10:17 AM (11 hours ago) 10:17 AM
to django-...@googlegroups.com
#37078: Change default algorithm of salted_hmac() from SHA-1 to SHA-256
--------------------------------------+------------------------------------
Reporter: Denny Biasiolli | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: security, crypto | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Denny Biasiolli):

I'd be happy to help, but do you have suggestions about the steps I need
to take to fix this?
My PR with the fix (without the deprecation) was here:
https://github.com/django/django/pull/21190
--
Ticket URL: <https://code.djangoproject.com/ticket/37078#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
10:32 AM (11 hours ago) 10:32 AM
to django-...@googlegroups.com
#37078: Change default algorithm of salted_hmac() from SHA-1 to SHA-256
--------------------------------------+------------------------------------
Reporter: Denny Biasiolli | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: security, crypto | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Jacob Walls):

Sure thing, and thanks for the offer.

1. Set yourself in the owner field here on this ticket.
2. Check the [https://docs.djangoproject.com/en/dev/internals/contributing
/writing-code/submitting-patches/#deprecating-a-feature deprecation guide]
for places to add documentation.
3. I assume you will need to do something like change the default value
for the argument to a `NOT_PROVIDED` sentinel, check for it, and issue the
warning and fall back to SHA-1.
--
Ticket URL: <https://code.djangoproject.com/ticket/37078#comment:7>

Django

unread,
11:05 AM (11 hours ago) 11:05 AM
to django-...@googlegroups.com
#37078: Change default algorithm of salted_hmac() from SHA-1 to SHA-256
-------------------------------------+-------------------------------------
Reporter: Denny Biasiolli | Owner: Denny
Type: | Biasiolli
Cleanup/optimization | Status: assigned
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: security, crypto | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Denny Biasiolli):

* owner: (none) => Denny Biasiolli
* status: new => assigned

--
Ticket URL: <https://code.djangoproject.com/ticket/37078#comment:8>

Django

unread,
1:53 PM (8 hours ago) 1:53 PM
to django-...@googlegroups.com
#37078: Change default algorithm of salted_hmac() from SHA-1 to SHA-256
-------------------------------------+-------------------------------------
Reporter: Denny Biasiolli | Owner: Denny
Type: | Biasiolli
Cleanup/optimization | Status: assigned
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: security, crypto | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Denny Biasiolli):

* has_patch: 0 => 1

--
Ticket URL: <https://code.djangoproject.com/ticket/37078#comment:9>
Reply all
Reply to author
Forward
0 new messages