Refs #36546 -- Replaced usage of constant_time_compare() with hmac.compare_digest(). #20358
+21
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trac ticket number
ticket-36546
Branch description
This PR addresses the first phase of cleanup for ticket-36546 by refactoring Django's internal codebase.
The existing wrapper function
django.utils.crypto.constant_time_compare()is redundant for internal Django use. It was also usingforce_byteswhich not needed .This change replaces all internal calls with
secrets.compare_digest().constant_time_compare()function remains untouched to maintain backwards compatibility for external libraries that rely on its current type-coercion behavior (as discussed following the revert in ticket-36572).Checklist
mainbranch.