No description

Find a file

Pim Kunis c42fc7c350 Implement client send message endpoint Fix state res and authorization to handle missing state_keys		2021-08-31 16:32:04 +02:00
config	Restructure code base	2021-08-06 23:14:27 +02:00
keys	Add function to sign event	2021-08-05 13:30:46 +02:00
lib	Implement client send message endpoint	2021-08-31 16:32:04 +02:00
priv/repo	Implement client send message endpoint	2021-08-31 16:32:04 +02:00
test	Restructure code base	2021-08-06 23:14:27 +02:00
.dialyzer_ignore.exs	Add dialyzer dependency	2021-08-18 23:22:04 +02:00
.formatter.exs	Init git repo	2021-06-22 14:09:25 +02:00
.gitignore	Add function to sign event	2021-08-05 13:30:46 +02:00
.tool-versions	Add function to sign event	2021-08-05 13:30:46 +02:00
LICENSE	Create LICENSE	2021-07-23 22:18:25 +00:00
mix.exs	Split Identifier struct into seperate types	2021-08-19 16:31:03 +02:00
mix.lock	Add dialyzer dependency	2021-08-18 23:22:04 +02:00
psql.sh	Add schemas and functions to query signing keys from servers	2021-08-13 00:45:07 +02:00
README.md	Update README.md	2021-08-27 16:21:32 +00:00

Matrix homeserver

This is my attempt at creating a Matrix homeserver in Elixir. Currently it is in a very early stage.

Noteworthy contributions

lib/matrix_server/state_resolution.ex: Implementation of version 2 of the Matrix state resolution algorithm.
lib/matrix_server/state_resolution/authorization.ex: Implementation of authorization rules for the state resolution algorithm.
lib/matrix_server/room_server.ex: A GenServer that holds and manages the state of a room.

Generate the server's ed25519 keys by executing ssh-keygen -t ed25519 -f keys/id_ed25519 -N ""

Here, implemented and some unimplemented features are listed.

TODO: list implemented endpoints

State resolution: functional, but very memory-intensive and with high database usage. For now it is sufficient, but snapshots should be used in the future. See: State Resolution v2 for the Hopelessly Unmathematical, State Resolution: Reloaded and Room Version 2.
Authorization rules (Room version 1)
Homeserver authentication using signing keys (4.1 Request Authentication)
Client authentication (5.1 Using access tokens)

Resolving server names (but works for local development) (3.1 Resolving server names)
Checks when receiving events via federation (i.e. valid format, signature check and hash check) (6.1 Checks performed on receipt of a PDU)
Federation of events