You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 795a7b0
Browse filesBrowse the repository at this point in the historyBrowse files
Key backup from Settings works for every login; 4-digit PINs behind a server-side lockout (0.5.0) (#283)
* Key backup: works from Settings for every login, 4-digit PINs behind a server-side lockout
- Settings, restore and key reset send the Bearer session (passkey, CoinPay
and phone sessions have no cookie, so backup silently 401'd).
- PINs may be 4-12 digits. GET /api/auth/key-backup no longer returns the
encrypted keys; restore is POST {pin}, checked against the scrypt hash with
5 tries then 15 min, doubling to 24 h. Backups must use the account PIN.
- Changing a verifiable PIN needs the current one; the server backup is
re-encrypted with the new PIN.
- Legacy backups (no verifiable hash) still restore; the client registers the
PIN once it decrypts, upgrading them.
- DELETE /api/auth/key-backup exists now (Complete Key Reset called it).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Release 0.5.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments