diff options
| author | Tim Graham <timograham@gmail.com> | 2013-10-02 10:15:18 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-10-02 10:15:18 -0400 |
| commit | 00a0d3de0204f73d3f05ae99548b1e317bfe336b (patch) | |
| tree | b6ff2369b3c2ad6ebf70cde53faf9c8c315be92a /docs/topics | |
| parent | 978e1351a60a0d7b44d367877784109ac01ebc62 (diff) | |
Clarified session replay attack differences with cookie backend.
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/http/sessions.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index e0dafd82f8..b336bf4669 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -163,8 +163,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** |