4 Commits

Author SHA1 Message Date
6d6c74fd32 case 4726 - login lockout per login name and per address
Same as AyaNova: failed logins counted in memory, 10 per login name or 50
per client address within 15 minutes, then 429 for the rest of the window.
Sockeye's login is public (only SSH to the droplet is limited).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 20:12:31 -07:00
f7c1d7c856 case 4710 - 2FA step requires the temp token from the password step
Same fix as AyaNova (raven 141bdeb8): the 2FA step matched the user by temp
token alone and the token was left empty after a 2FA login, so an empty or
missing token skipped the password step. Now an empty or missing temp token is
refused, the token is cleared to null after success, and after 5 wrong codes
the password must be entered again.

Checked on the local server with a temporary user (removed afterwards): no or
empty temp token 401; normal sign in 200; 5 wrong codes then the right code 401;
new password entry 200.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 11:36:45 -07:00
12f095939c case 4670 net10.0 + Asp.Versioning + BouncyCastle.Cryptography 2.7.0 + MailKit 4.x (forced: MimeKit 3.x pulled Portable.BouncyCastle)
sockeye.tests retargeted to net10.0, packages current. Re-sign harness: 1399/1399.
AV0014 suppressed: licence controllers were never versioned under 5.x defaults.
2026-09-23 14:01:40 -07:00
effd96143f 2022-12-16 06:01:23 +00:00