Magic-link tokens were persisted in plaintext, so a database read disclosed usable login/invite tokens. The service now hashes tokens (HMAC-SHA256 when a pepper is configured, else SHA-256 of the high-entropy token) and persists only the hash; the raw token is exposed solely in the registration URL and is re-attached to objects returned to callers. Refs: porchlight-42h Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_last_credential_guard.py | ||
| test_manage_credentials_page.py | ||
| test_manage_password_credential.py | ||
| test_manage_webauthn_credential.py | ||
| test_pages.py | ||
| test_password_login.py | ||
| test_register_magic_link.py | ||
| test_session_deps.py | ||
| test_webauthn_login.py | ||