diff options
author | Richard van der Hoff <1389908+richvdh@users.noreply.github.com> | 2020-01-08 13:24:10 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-01-08 13:24:10 +0000 |
commit | 573fee759cbd76fca93bf90783cd013a11b9b4e5 (patch) | |
tree | be32aacfaee4f55a5e16798393ce0c1dba8b98dd /test_postgresql.sh | |
parent | Fixup changelog (diff) | |
download | synapse-573fee759cbd76fca93bf90783cd013a11b9b4e5.tar.xz |
Back out ill-advised notary server hackery (#6657)
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`. Also: more tests for fetching keys via perspectives: it would be nice if we actually tested when our fetcher can't talk to our notary impl.
Diffstat (limited to 'test_postgresql.sh')
0 files changed, 0 insertions, 0 deletions