case 4710 - 2FA step requires the temp token from the password step
The 2FA step matched the user by temp token alone, and the token was left empty after a successful 2FA login (null right after turning 2FA on), so an empty or missing token skipped the password step (security review F5). Now: an empty or missing temp token is refused before the lookup; the token is cleared to null after success; after 5 wrong codes the token is cleared, so the password must be entered again (counted in memory per user). Changelog: general security notice for self-hosted upgrades, and the one behaviour change users can see. SECURITY-REVIEW.md: F5 fixed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -14,8 +14,11 @@ IN PROGRESS
|
||||
|
||||
**WARNING:** this release contains changes that will require a **pre upgrade step** on all Windows and Linux network platforms from the normal upgrade process you may be accustomed to. Be sure to follow our [upgrade instructions](ops-upgrade.md) and the **pre upgrade step** for your platform for this particular upgrade from version 8.2.4 (or older) to version 8.3.0 (or newer).
|
||||
|
||||
**IMPORTANT:** this release includes important security improvements along with the move to .NET 10. We recommend upgrading self-hosted installations to 8.3.0 promptly.
|
||||
|
||||
**Changed**
|
||||
|
||||
- Server: after several incorrect two-factor authentication codes, the password must be entered again before another code can be tried.
|
||||
- Server: updated to use .NET 10.x LTS from previously used .NET 8.x LTS. .NET 8.x reaches end of support in November 2026. With this update to .NET 10.x come performance and security gains.
|
||||
- Server: all 3rd party components used by the AyaNova server have been upgraded to their most recent release versions to use with .NET 10.x. This improves performance, stability and security for each component used.
|
||||
- Server: the report rendering system now uses the smaller and faster "Chrome headless shell" browser instead of the full Chrome browser. It is downloaded into a `report-browser` folder under the AyaNova data folder instead of the program folder, so it is no longer removed by an upgrade. There will be a longer than normal delay the _first time_ a report is rendered after upgrading while AyaNova automatically downloads the new report rendering browser. Any old `Chrome` and `ChromeHeadlessShell` folders in the AyaNova program folder are no longer used and can be removed.
|
||||
|
||||
Reference in New Issue
Block a user