#34804: legacy_algorithm = 'sha1' removed in django4.0 but new algorithm is
hardcoded
-------------------------------------+-------------------------------------
Reporter: Awais Qureshi | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 4.2
Severity: Normal | Resolution: invalid
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: => invalid
Comment:
`signing.dumps()` uses the default `Singer` algorithm, i.e. `SHA256` (as
documented). I'm not sure why you want to force unsafe `SHA1`, but you can
do this by using `TimestampSigner(algorithm="sha1")` in your code.
--
Ticket URL: <https://code.djangoproject.com/ticket/34804#comment:3>
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/0107018a45f624b5-c2cdf93a-4969-453d-87ff-395ee05b91bd-000000%40eu-central-1.amazonses.com.
