fix(auth): a hold-out moves a reset on only by its own time, and a reset lives 30 days at most

Browse source

The reading of the full reading's fixes found that every refusal at the
address's ceiling moved a reset to 72 hours after it (A1): someone who
knows only the address kept the owner's own reset from ever taking effect
with one burst every three days, and kept a forgotten one alive (A2).

Now a hold-out that begins before a reset takes effect moves it on only by
the time it holds the owner out and no hold-out counted before did
(account_reset.heldOutUntil, under a row lock), so the owner gets 72 hours
outside hold-outs in total; and every reset not carried out lapses 30 days
after it was asked (resetLivesAtMost), whatever moved it, besides a week
after it took effect.

Migration (module, Learn's and Todo's servers, Learn's device schema):
ALTER TABLE "account_reset" ADD COLUMN "heldOutUntil" timestamp without
time zone; nullable, existing rows counted from now on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

...

This commit is contained in:

Tizian 「ティツィアーン」 2026-10-21 15:50:29 +02:00

parent a72b96d628

commit 274b796faa

Signed by: raisondetredev

GPG key ID: 07F6FCF405488B64

1 changed files with 41748 additions and 65 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4334

packages/halkyon_base_server/migrations/20261021134802955-reset-hold-outs/definition.json Normal file

View file

File diff suppressed because it is too large Load diff