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

Workaround for error when fetching notary's own key #6620

Merged
merged 2 commits into from
Jan 6, 2020

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Jan 3, 2020

As a notary server, when we return our own keys, include all of our signing
keys in verify_keys.

This is a workaround for #6596.

(based on #6619)

We already get the Site via the Channel, so there's no need for a dedicated
RequestFactory: we can just use the right constructor.
As a notary server, when we return our own keys, include all of our signing
keys in verify_keys.

This is a workaround for #6596.
@richvdh richvdh requested a review from a team January 3, 2020 11:50
Copy link
Contributor

@babolivier babolivier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@richvdh richvdh merged commit 18674ee into develop Jan 6, 2020
richvdh added a commit that referenced this pull request Jan 7, 2020
This was ill-advised. We can't modify verify_keys here, because the response
object has already been signed by the requested key.

Furthermore, it's somewhat unnecessary because existing versions of Synapse
(which get upset that the notary key isn't present in verify_keys) will fall
back to a direct fetch via `/key/v2/server`.
@richvdh richvdh deleted the rav/keyserver_workaround branch December 1, 2020 12:37
babolivier pushed a commit that referenced this pull request Sep 1, 2021
* commit '18674eebb':
  Workaround for error when fetching notary's own key (#6620)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants