Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We should do a better job of explaining homeservers signing requests #498

Open
turt2live opened this issue Jul 9, 2019 · 1 comment
Open
Labels
A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@turt2live
Copy link
Member

Now that we have multiple APIs which can be signed outside of s2s, we should generalize the concept

@turt2live turt2live added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit meta Something that is not a spec change/request and is not related to the build tools labels Jul 9, 2019
@richvdh
Copy link
Member

richvdh commented Jul 6, 2021

For the record, the algorithm used in the IS is the same as that in the S2S API (see https://matrix.org/docs/spec/server_server/r0.1.4#request-authentication). That means that any implementation capable of receiving such requests needs to be capable of retrieving the requesting server's signing keys, which in turn means implementing the federation routing algorithm, complete with SRV lookup.

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@richvdh richvdh added A-S2S Server-to-Server API (federation) and removed meta Something that is not a spec change/request and is not related to the build tools labels Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

No branches or pull requests

2 participants