#36546: Deprecate django.utils.crypto.constant_time_compare()
-------------------------------------+-------------------------------------
Reporter: Tim Graham | Owner:
Type: | JaeHyuckSa
Cleanup/optimization | Status: new
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* has_patch: 1 => 0
* resolution: fixed =>
* stage: Ready for checkin => Someday/Maybe
* status: closed => new
Comment:
Reopening following revert. See discussion in #36572
> A later first step could be to replace internal usage of
constant_time_compare() with compare_digest()
The deprecation itself needs more consideration
--
Ticket URL: <https://code.djangoproject.com/ticket/36546#comment:12>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198eabb7517-f60f85f5-5db1-4a99-a4ec-cf3f53536710-000000%40eu-central-1.amazonses.com.
