feat(#551): switch read_room to room.messages() for e2ee decryption, add UTD sentinel, update docs
This commit is contained in:
parent
f51402a867
commit
78317b9cac
2 changed files with 46 additions and 16 deletions
|
|
@ -119,8 +119,15 @@ Initial rollout settings:
|
|||
engage). The absent
|
||||
`yes_i_am_very_very_sure_…_open_registration_…` flag keeps the
|
||||
server closed to anyone without the token.
|
||||
- `allow_encryption = false` per operator call; E2EE re-enabling is
|
||||
deferred to a follow-up.
|
||||
- `allow_encryption = true` — E2EE enabled. Agent clients use the
|
||||
`e2e-encryption` feature of `matrix-sdk`; crypto keys are stored in
|
||||
the per-agent sqlite store under the state dir and persist across
|
||||
restarts (lost on `--purge`). `read_room` decrypts via
|
||||
`room.messages()` — UTD events surface as `event_type =
|
||||
"m.room.encrypted"` with `body = "[unable to decrypt]"`.
|
||||
Cross-signing and automatic key backup are not enabled for the first
|
||||
pass: static bearer-token bot accounts can't bootstrap cross-signing
|
||||
without MSC3967.
|
||||
|
||||
## Hive Matrix Space
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue