T
finnandClaude Opus 5.5 7ac4e6c3a7 Handle sessions on password change correctly
remove_user_sessions() got the user id as except_id, so the exception
never matched. On an own password change the result was correct only
by accident. When an admin changed another user's password, the admin
session got a new id, but the old entry stayed valid in the store.

- New Session.regenerate(): keeps the data under a new id and removes
  the old store entry.
- change_password() handles the sessions: on an own password change it
  regenerates the current session and ends all other sessions of the
  user (except_id is now the session id). When an admin changes another
  user's password, the admin session stays untouched and all sessions
  of that user end.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 17:48:03 +00:00
2020-04-13 08:31:44 +02:00
2020-04-13 08:31:44 +02:00
2020-04-13 08:31:44 +02:00
2026-10-19 18:53:59 +02:00
2026-10-21 09:06:51 +00:00
2026-10-19 18:53:59 +02:00
2020-04-13 08:31:44 +02:00

MAX

A small little program to manage emails.

The proxy should add X-Real-IP to get a better logging.

Setup

Requirements: Docker, Make

Start with make run-dev

Configuration

  • MAX_ORIGIN (required in production): The public origin of MAX, e.g. https://max.finn.st
S
Description
No description provided
Readme MIT
1.2 MiB
0 Stars 1 Watchers 0 Forks
Languages
Python 70.9%
HTML 19.8%
CSS 4.4%
Dockerfile 2.9%
Shell 1%
Other 1%