Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#31274 closed Cleanup/optimization (fixed)

Use signing infrastructure for session data encoding/decoding.

Reported by: Claude Paroz Owned by: Claude Paroz
Component: contrib.sessions Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no
Pull Requests:12460 merged

Description

The signing infrastructure has dumps and loads utilities to encode and decode data securely. SessionBase should use those instead of handling hash and encoding itself.

Change History (5)

comment:1 by Claude Paroz, 5 years ago

Has patch: set

comment:2 by Mariusz Felisiak, 5 years ago

Owner: changed from nobody to Claude Paroz
Status: newassigned
Summary: Use signing infrastructure for session data encoding/decodingUse signing infrastructure for session data encoding/decoding.
Triage Stage: UnreviewedAccepted

comment:3 by Mariusz Felisiak, 5 years ago

Triage Stage: AcceptedReady for checkin

comment:4 by Mariusz Felisiak <felisiak.mariusz@…>, 5 years ago

Resolution: fixed
Status: assignedclosed

In d4fff711:

Fixed #31274 -- Used signing infrastructure in SessionBase.encode()/decode().

Thanks Mariusz Felisiak and Florian Apolloner for the reviews.

comment:5 by Mariusz Felisiak <felisiak.mariusz@…>, 4 years ago

In 8250145a:

Refs #31274 -- Removed support for the pre-Django 3.1 encoding format of sessions.

Per deprecation timeline.

Note: See TracTickets for help on using tickets.
Back to Top