element-hq / element-hq/synapse

Report suspicious login attempts

Open
#4,556 0 comments 0 reactions 0 assignees View on GitHub
T-Enhancement z-feature z-p2
Dominant language
Python
Stars
4.6k
Forks
600
Avg merge
5d 6h
Merged PRs (30d)
46

Description

This issue has been migrated from [#4556](https://github.com/matrix-org/synapse/issues/4556).

---

**Description:** Most services seem to implement this to alert users to break-ins. We should consider at least support sending a notification and optionally locking the account until verified through email or another medium.

It's not a major problem if people don't re-use passwords, but it happens.

To break this down further, I'd like to propose having different levels of security ranging from just checking if the user has signed in from a different region, to checking if the users IP address has changed. This would be useful for people who want a paranoid mode.

In terms of spec, this would require the concept of an account being "locked" as well as an `account_data` type which could store the security level required to trigger a lock. I've mentioned it in synapse first because a server-level alert only (not locking the account) config option would require no spec changes.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.