In current django >= 0.95 logout() simply removes the user object id from a running session. Thus, if the browser stays open and somebody else log in, they get access to all session bound data of the previous user.
http://www.djangoproject.com/documentation/sessions/#clearing-the-session-table states the opposite. As this change in behaviour is not documented in the regular docs and even not tracked in http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges This might have severe security implications for several sites who upgraded their django framework after 0.90. Just thought this could be of interest to anybody Boris PS: Would be pleased to get an answer to my authenticate() question sometime :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
