prosolis 1adcd05dc7 cross-signing: persist the bot's identity instead of reminting it every start ...

Both session paths called GenerateAndUploadCrossSigningKeys unconditionally on
every start. That published a fresh cross-signing identity each time the bot
restarted, so every user's client saw the bot's verification break and had to
re-verify it. The freshly-minted recovery key was only ever logged, never kept,
so the identity couldn't be recovered either.

bootstrapCrossSigning now mints once, persists the recovery key to
DATA_DIR/cross_signing.json (0600), and on later starts reuses the stored
identity untouched. Two escape hatches, both normally unset:
CROSS_SIGNING_REGENERATE=1 forces exactly one remint (every user must then
re-verify), and CROSS_SIGNING_RECOVERY_KEY imports an identity created before
the bot persisted its own key.

Shared by the appservice and masdevice paths, which had drifted into two copies
of the same block.

2026-07-09 18:53:23 -07:00

..

appservice.go

cross-signing: persist the bot's identity instead of reminting it every start

2026-07-09 18:53:23 -07:00

client.go

cross-signing: persist the bot's identity instead of reminting it every start

2026-07-09 18:53:23 -07:00

crosssigning_test.go

cross-signing: persist the bot's identity instead of reminting it every start

2026-07-09 18:53:23 -07:00

crosssigning.go

cross-signing: persist the bot's identity instead of reminting it every start

2026-07-09 18:53:23 -07:00

dispatch.go

Honor IGNORED_BOTS env var: global sender ignore at dispatch

2026-06-05 19:26:49 -07:00

masauth.go

Add appservice auth mode behind AUTH_MODE; land device grant

2026-07-03 17:11:58 -07:00

session.go

appservice: start presence heartbeat before plugin init so bot shows online from boot

2026-07-04 10:36:44 -07:00