6c70ac8eef
Self-contained docker-compose harness that exercises the new bootstrap
branch against a real Continuwuity homeserver. Three tests:
1. fresh bot → bootstrap fires, /keys/query returns master + ssk
with UNPADDED base64 keyids, current device is signed by the
new SSK
2. second startup with same crypto store → bootstrap is skipped
3. MATRIX_RECOVERY_KEY set → existing verify_with_recovery_key path
takes precedence, no new bootstrap
Run via:
docker compose -f tests/e2e/matrix_xsign_bootstrap/docker-compose.yml up -d
python tests/e2e/matrix_xsign_bootstrap/test_bootstrap.py
docker compose -f tests/e2e/matrix_xsign_bootstrap/docker-compose.yml down -v
The test mirrors the bootstrap snippet from matrix.py inline so it can
run without importing the full hermes gateway and its deps. Skipped
automatically when mautrix isn't installed or the homeserver is
unreachable.
All three pass against ghcr.io/continuwuity/continuwuity:latest
(Continuwuity 0.5.7). The unpadded-keyid assertion is the load-bearing
one — it's exactly the property the PR's bootstrap path provides that
the hand-rolled `base64.b64encode().decode()` scripts get wrong.
1.8 KiB
Matrix cross-signing bootstrap — E2E test
Self-contained end-to-end test for the auto-bootstrap behavior added in
gateway/platforms/matrix.py. Spins up a real Continuwuity homeserver
in Docker, registers a fresh bot, runs the patched bootstrap path
against it, and asserts:
- Cross-signing keys get published with unpadded base64 keyids (the bug this PR fixes — padded keyids are silently rejected by matrix-rust-sdk in Element).
- On a second startup with the same crypto store, bootstrap is skipped.
- When
MATRIX_RECOVERY_KEYis set, the existing recovery-key path takes precedence and no fresh bootstrap happens.
Run
# from repo root
docker compose -f tests/e2e/matrix_xsign_bootstrap/docker-compose.yml up -d
python tests/e2e/matrix_xsign_bootstrap/test_bootstrap.py
docker compose -f tests/e2e/matrix_xsign_bootstrap/docker-compose.yml down -v
The down -v step removes the persistent volume so the next run gets
a fresh homeserver — important because Continuwuity's one-time admin
registration token is only valid before the first user is created.
Port
The compose binds Continuwuity to 127.0.0.1:26167 by default. Override
with HOMESERVER_HOST_PORT=NNNNN docker compose up -d if that port is
busy locally.
What the test exercises
The test mirrors the bootstrap snippet from
gateway/platforms/matrix.py (the "if MATRIX_RECOVERY_KEY else
get_own_cross_signing_public_keys / generate_recovery_key" branch)
inline so it runs without importing the entire hermes gateway and its
many dependencies. If the source diverges from what's in
_connect_with_bootstrap, this test must be updated to match. A
small price for not requiring the full hermes-agent runtime in CI.
Skipped when
mautrixPython package is not installed- The homeserver isn't reachable at
$E2E_MATRIX_HS(defaulthttp://127.0.0.1:26167)