1f349/dendrite
4
0
Fork 0
mirror of https://github.com/1f349/dendrite.git synced 2024-11-09 22:42:58 +00:00
Code Issues Packages Projects Releases Wiki Activity
de78eab63a
dendrite/keyserver
History
Brian Meek de78eab63a
Add race testing to tests, and fix a few small race conditions in the tests (#2587) 
* Add race testing to tests, and fix a few small race conditions in the tests

* Enable run-sytest on MacOS

* Remove deadlock detecting mutex, per code review feedback

* Remove autoformatting related changes and a closure that is not needed

* Adjust to importing nats client as 'natsclient'

Signed-off-by: Brian Meek <brian@hntlabs.com>

* Clarify the use of gooseMutex to proect goose internal state

Signed-off-by: Brian Meek <brian@hntlabs.com>

* Remove no longer needed mutex for guarding goose

Signed-off-by: Brian Meek <brian@hntlabs.com>
2022-08-05 09:19:33 +01:00
..
api Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
consumers Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
internal Fix syncapi shared users query & device lists (#2614) 2022-08-03 18:35:17 +02:00
inthttp Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
producers Remove eduserver (#2306) 2022-03-29 14:14:35 +02:00
storage Add race testing to tests, and fix a few small race conditions in the tests (#2587) 2022-08-05 09:19:33 +01:00
types Remove sarama/saramajetstream dependencies (#2138) 2022-02-04 13:08:13 +00:00
keyserver.go Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
README.md Add boilerplate for key server APIs (#1196) 2020-07-13 16:02:35 +01:00

README.md

Key Server

This is an internal component which manages E2E keys from clients. It handles all the Key Management APIs with the exception of /keys/changes which is handled by Sync API. This component is designed to shard by user ID.

Keys are uploaded and stored in this component, and key changes are emitted to a Kafka topic for downstream components such as Sync API.

Internal APIs

  • PerformUploadKeys stores identity keys and one-time public keys for given user(s).
  • PerformClaimKeys acquires one-time public keys for given user(s). This may involve outbound federation calls.
  • QueryKeys returns identity keys for given user(s). This may involve outbound federation calls. This component may then cache federated identity keys to avoid repeatedly hitting remote servers.
  • A topic which emits identity keys every time there is a change (addition or deletion).

### Endpoint mappings

  • Client API maps /keys/upload to PerformUploadKeys.
  • Client API maps /keys/query to QueryKeys.
  • Client API maps /keys/claim to PerformClaimKeys.
  • Federation API maps /user/keys/query to QueryKeys.
  • Federation API maps /user/keys/claim to PerformClaimKeys.
  • Sync API maps /keys/changes to consuming from the Kafka topic.