diff options
| author | S7evinK <2353100+S7evinK@users.noreply.github.com> | 2022-02-09 13:11:43 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-09 13:11:43 +0100 |
| commit | ac25065a54149117761e7a1b471a9b742f920ebc (patch) | |
| tree | 40a523aa914fc3c51cc47a62c32c4c18468be48f /sytest-whitelist | |
| parent | cf447dd52a0015c2c5b10813ed11e59a3712607e (diff) | |
Fix sytest `uploading signed devices gets propagated over federation` (#2162)
* Remove unneeded logging
* Add MasterKey & SelfSigningKey to update
Avoid panic if signatures are not present
* Add passing test
* Revert "Add MasterKey & SelfSigningKey to update"
This reverts commit 2c81b34884be8b5b875a33420c0f985b578d3fb8.
* Send MasterKey & SelfSigningKey with update
* Debugging
* Remove delete() so we also query signingkeys
Diffstat (limited to 'sytest-whitelist')
| -rw-r--r-- | sytest-whitelist | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sytest-whitelist b/sytest-whitelist index c6ce1daa..04b1bbf3 100644 --- a/sytest-whitelist +++ b/sytest-whitelist @@ -591,3 +591,4 @@ Can receive redactions from regular users over federation in room version 9 Forward extremities remain so even after the next events are populated as outliers If a device list update goes missing, the server resyncs on the next one uploading self-signing key notifies over federation +uploading signed devices gets propagated over federation |