Commit 1f630610 authored by Tim Graham's avatar Tim Graham
Browse files

[1.5.x] Clarified session replay attack differences with cookie backend.

Backport of 00a0d3de from master
parent 7ebd1001
Loading
Loading
Loading
Loading
+6 −2
Original line number Diff line number Diff line
@@ -154,8 +154,12 @@ and the :setting:`SECRET_KEY` setting.
    integrity of the data (that it is all there and correct), it cannot
    guarantee freshness i.e. that you are being sent back the last thing you
    sent to the client. This means that for some uses of session data, the
    cookie backend might open you up to `replay attacks`_. Cookies will only be
    detected as 'stale' if they are older than your
    cookie backend might open you up to `replay attacks`_. Unlike other session
    backends which keep a server-side record of each session and invalidate it
    when a user logs out, cookie-based sessions are not invalidated when a user
    logs out. Thus if an attacker steals a user's cookie, he can use that
    cookie to login as that user even if the user logs out. Cookies will only
    be detected as 'stale' if they are older than your
    :setting:`SESSION_COOKIE_AGE`.

    **Performance**