Commit Graph

9 Commits

Author SHA1 Message Date
a843bd3132 case 4711 - JWT signing key generated by the server; AYANOVA_JWT_SECRET removed
The LAN/IIS and Linux templates shipped a placeholder secret printed in the
manual, and installs that kept it signed logins with a public key; any setting
also invited short or reused values (security review F1). The setting is now
ignored (one warning at boot if still present): the server generates a key once
(48 random bytes) into jwt-signing.key in the data folder (beside the app if
there is none; owner-only on Linux) and reuses it, so sign-ins also survive a
restart where the server used to make a new key each boot (standalone, Linux
desktop). If the file cannot be used, a temporary key is used for that run.

Templates and dev launch configs drop the setting; manual updated (key page
rewritten, setting steps removed from install pages); changelog line.

Checked locally: token forged with the old placeholder 401; key file created
and reused after restart (old token 200); auth and 2FA tests pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 12:01:08 -07:00
52ccc3fe5e 2024-05-22 18:40:30 +00:00
6126fe977b case 4377 FIRST REAL CODE COMMIT SINCE APRIL 2023 2023-11-02 20:40:49 +00:00
d560e4ef5a increased config.json commandtimeout to 300 seconds to support erasing HUGE size db
also more subscription licensing support
2022-08-19 23:45:48 +00:00
6363f444cc 2021-12-10 01:05:57 +00:00
116e1647ac 2021-12-09 18:57:30 +00:00
881195bb25 2021-12-09 17:42:08 +00:00
ad1073e1a6 2021-12-09 01:29:55 +00:00
3f11e06220 2021-12-08 00:08:02 +00:00