Update ADR 0041: sign-in failures are counted per email and IP #439
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amaurycoudr/chess-project#439
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
MR !546 (closes #436) changed the sign-in failure counter from lowercased email alone to email and IP together, so strangers can no longer lock a Player out. The owner accepted the trade-off: guesses at one email spread over many IPs are now limited to 5 per IP (each IP still capped by the per-IP limit of 20).
ADR 0041 (
docs/adr/0041-rate-limits-are-in-memory-counters-in-the-api.md) no longer matches the code:signInFailuresPerEmailAndIp(RATE_LIMIT_SIGN_IN_FAILURES_PER_EMAIL_AND_IP).Also refresh the stale "per-email limits" comments in
deploy/compose.preview.yamlandscripts/assign-dev-rate-limits.sh, and check that no deployed environment still sets the oldRATE_LIMIT_SIGN_IN_FAILURES_PER_EMAILvariable (it now falls back silently to the default).mentioned in commit fe9f2e3bbb8c9c7f21fad05879afbe9f7de459de
mentioned in merge request !549
mentioned in commit c182f1ebb7ee782f49f26e730a4f25c8e6dd35bc
mentioned in commit
697b60f837mentioned in commit
56cc57afdc