2e380f0f18
it seems to be possible that only one of them ends up to be cached. when this was the case, the missing one was not fetched via federation, and clients then failed to validate cross-signed devices. Signed-off-by: Jonas Jelten <jj@sft.lol>
2 lines
129 B
Plaintext
2 lines
129 B
Plaintext
Fix fetching of E2E cross signing keys over federation when only one of the master key and device signing key is cached already.
|