Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

e2e: ensure we have both master and self-signing key #8455

Merged
merged 3 commits into from
Oct 26, 2020
Merged

e2e: ensure we have both master and self-signing key #8455

merged 3 commits into from
Oct 26, 2020

Commits on Oct 17, 2020

  1. e2e: ensure we have both master and self-signing key 

    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>
    @TheJJ
    TheJJ committed Oct 17, 2020
    Configuration menu
    Copy the full SHA
    e9097e5 View commit details
    Browse the repository at this point in the history

Commits on Oct 26, 2020

  1. Merge remote-tracking branch 'github/develop' into federation-fetch-c… 

    …rossigning-keypair
    @TheJJ
    TheJJ committed Oct 26, 2020
    Configuration menu
    Copy the full SHA
    2e7e764 View commit details
    Browse the repository at this point in the history

  2. e2e: clarify the need for a federation request for e2e keys

    @TheJJ
    TheJJ committed Oct 26, 2020
    Configuration menu
    Copy the full SHA
    198e787 View commit details
    Browse the repository at this point in the history