Key management APIs #894
Merged
Key management APIs #894
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Extract the key management stuff from the draft e2e branch, in an attempt to make it easier to land
olm isn't specified yet, so we can't link to it.
We're not going to use m.new_device.
api/client-server/keys.yaml
Outdated
| additionalProperties: | ||
| type: integer | ||
| description: |- | ||
| For each key algorighm, the number of unclaimed one-time keys |
NegativeMjark
approved these changes
Apr 20, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd like to try and land the specification for these APIs, not least so that we can stop baking /unstable/ endpoints into clients everywhere. I think they are stable enough now.
FIxes #797