fix(matrix): keep startup bootstrap conservative

This commit is contained in:
Gustavo Madeira Santana
2026-04-15 11:09:14 -04:00
parent f3a15b0b52
commit 28d2aac87b
4 changed files with 3 additions and 3 deletions

View File

@@ -146,6 +146,7 @@ Docs: https://docs.openclaw.ai
- Media/store: honor configured agent media limits when saving generated media and persisting outbound reply media, so the store no longer hard-stops those flows at 5 MB before the configured limit applies. (#66229) Thanks @neeravmakwana and @vincentkoc.
- Plugins/setup-entry: preserve separate setup-entry secrets exports when loading bundled setup-runtime channels, so setup-mode flows keep the channel secret contract for split plugin + secrets entrypoints. (#66261) Thanks @hxy91819.
- CLI/update: prune stale packaged `dist` chunks after npm upgrades, verify installed package inventory, and keep downgrade/update verification working across older releases. (#66959) Thanks @obviyus.
- Matrix/E2EE: keep startup bootstrap conservative for passwordless token-auth bots, still attempt the guarded repair pass without requiring `channels.matrix.password`, and document the remaining password-UIA limitation. (#66228) Thanks @SARAMALI15792.
## 2026.4.12

View File

@@ -613,7 +613,8 @@ if you want a shorter or longer retry window.
Startup also performs a conservative crypto bootstrap pass automatically.
That pass tries to reuse the current secret storage and cross-signing identity first, and avoids resetting cross-signing unless you run an explicit bootstrap repair flow.
If startup finds broken bootstrap state and `channels.matrix.password` is configured, OpenClaw can attempt a stricter repair path.
If startup still finds broken bootstrap state, OpenClaw can attempt a guarded repair path even when `channels.matrix.password` is not configured.
If the homeserver requires password-based UIA for that repair, OpenClaw logs a warning and keeps startup non-fatal instead of aborting the bot.
If the current device is already owner-signed, OpenClaw preserves that identity instead of resetting it automatically.
See [Matrix migration](/install/migrating-matrix) for the full upgrade flow, limits, recovery commands, and common migration messages.

View File

@@ -1280,7 +1280,6 @@ describe("MatrixClient crypto bootstrapping", () => {
expect(bootstrapSpy).toHaveBeenCalledTimes(1);
expect((bootstrapSpy.mock.calls as unknown[][])[0]?.[1] ?? {}).toEqual({
allowAutomaticCrossSigningReset: false,
allowSecretStorageRecreateWithoutRecoveryKey: true,
});
});

View File

@@ -139,7 +139,6 @@ export type MatrixVerificationBootstrapResult = {
const MATRIX_INITIAL_CRYPTO_BOOTSTRAP_OPTIONS = {
allowAutomaticCrossSigningReset: false,
allowSecretStorageRecreateWithoutRecoveryKey: true,
} satisfies MatrixCryptoBootstrapOptions;
const MATRIX_AUTOMATIC_REPAIR_BOOTSTRAP_OPTIONS = {