Warning
You are viewing an outdated version of this specification. To view the current specification, please click here.
The attacker could attempt to prevent delivery of messages to or from the victim in order to:
An attacker could cause the victims server to exhaust a particular resource (e.g. open TCP connections, CPU, memory, disk storage)
An attacker could send messages which created an unrecoverable "split-brain" state in the cluster such that the victim's servers could no longer derive a consistent view of the chatroom state.
An attacker could convince the victim to accept invalid messages which the victim would then include in their view of the chatroom history. Other servers in the chatroom would reject the invalid messages and potentially reject the victims messages as well since they depended on the invalid messages.
An attacker could try to firewall traffic between the victim's server and some or all of the other servers in the chatroom.
An attacker could send large volumes of messages to a chatroom with the victim making the chatroom unusable.
An attacker could attempt to ban a user from a chatroom with the necessary authorisation.
An attacker could try to send a message claiming to be from the victim without the victim having sent the message in order to:
An attacker could try to alter the contents of an existing message from the victim.
An attacker could try to send a new message purporting to be from the victim with a phony "origin" field.
The attacker could try to send a high volume of solicited or unsolicited messages to the victim in order to:
An attacker could try to send messages to victims who do not wish to receive them.
An attacker could send abusive or threatening messages to the victim
The attacker could try to access message contents or metadata for messages sent by the victim or to the victim that were not intended to reach the attacker in order to:
An attacker could try to expose the message contents or metadata during transmission between the servers.
An attacker could try to convince servers within a chatroom to send messages to a server it controls that was not authorised to be within the chatroom.
An attacker could take control of a server within a chatroom to expose message contents or metadata for messages in that room.
To assist in the development of compatible implementations, the following test values may be useful for verifying the cryptographic event signing code.
The following test vectors all use the 32-byte value given by the following Base64-encoded string as the seed for generating the ed25519 signing key:
SIGNING_KEY_SEED = decode_base64( "YJDBA9Xnr2sVqXD9Vj7XVUnmFZcZrlw8Md7kMW+3XA1" )
In each case, the server name and key ID are as follows:
SERVER_NAME = "domain" KEY_ID = "ed25519:1"
Given an empty JSON object:
{}
The JSON signing algorithm should emit the following signed data:
{ "signatures": { "domain": { "ed25519:1": "K8280/U9SSy9IVtjBuVeLr+HpOB4BQFWbg+UZaADMtTdGYI7Geitb76LTrr5QV/7Xg4ahLwYGYZzuHGZKM5ZAQ" } } }
Given the following JSON object with data values in it:
{ "one": 1, "two": "Two" }
The JSON signing algorithm should emit the following signed JSON:
{ "one": 1, "signatures": { "domain": { "ed25519:1": "KqmLSbO39/Bzb0QIYE82zqLwsA+PDzYIpIRA2sRQ4sL53+sN6/fpNSoqE7BP7vBZhG6kYdD13EIMJpvhJI+6Bw" } }, "two": "Two" }
Given the following minimally-sized event:
{ "event_id": "$0:domain", "origin": "domain", "origin_server_ts": 1000000, "signatures": {}, "type": "X", "unsigned": { "age_ts": 1000000 } }
The event signing algorithm should emit the following signed event:
{ "event_id": "$0:domain", "hashes": { "sha256": "6tJjLpXtggfke8UxFhAKg82QVkJzvKOVOOSjUDK4ZSI" }, "origin": "domain", "origin_server_ts": 1000000, "signatures": { "domain": { "ed25519:1": "2Wptgo4CwmLo/Y8B8qinxApKaCkBG2fjTWB7AbP5Uy+aIbygsSdLOFzvdDjww8zUVKCmI02eP9xtyJxc/cLiBA" } }, "type": "X", "unsigned": { "age_ts": 1000000 } }
Given the following event containing redactable content:
{ "content": { "body": "Here is the message content", }, "event_id": "$0:domain", "origin": "domain", "origin_server_ts": 1000000, "type": "m.room.message", "room_id": "!r:domain", "sender": "@u:domain", "signatures": {}, "unsigned": { "age_ts": 1000000 } }
The event signing algorithm should emit the following signed event:
{ "content": { "body": "Here is the message content", }, "event_id": "$0:domain", "hashes": { "sha256": "onLKD1bGljeBWQhWZ1kaP9SorVmRQNdN5aM2JYU2n/g" }, "origin": "domain", "origin_server_ts": 1000000, "type": "m.room.message", "room_id": "!r:domain", "sender": "@u:domain", "signatures": { "domain": { "ed25519:1": "Wm+VzmOUOz08Ds+0NTWb1d4CZrVsJSikkeRxh6aCcUwu6pNC78FunoD7KNWzqFn241eYHYMGCA5McEiVPdhzBA" } }, "unsigned": { "age_ts": 1000000 } }