This document describes the custom API implemented by the Matrix Content Scanner.
An error is returned as JSON responses to the request that caused it, in the following format:
Parameter | Type | Description |
---|---|---|
reason |
str | The machine-readable code for the error. |
info |
str | Additional human-readable information about the error. |
Example:
{
"info": "***VIRUS DETECTED***",
"reason": "MCS_MEDIA_NOT_CLEAN"
}
The error codes used by the Matrix Content Scanner are described below, alongside the HTTP status code of the response for each scenario:
Status Code | Reason | Description |
---|---|---|
400 | MCS_MALFORMED_JSON |
The request body contains malformed JSON. |
400 | MCS_MEDIA_FAILED_TO_DECRYPT |
The server failed to decrypt the encrypted media downloaded from the media repo. |
404 | M_NOT_FOUND |
No route could be found at the given path. |
404 | M_NOT_FOUND |
The requested media was not present in the media repo. |
403 | MCS_MEDIA_NOT_CLEAN |
The server scanned the downloaded media but the antivirus script returned a non-zero exit code. |
403 | MCS_BAD_DECRYPTION |
The provided encrypted_body could not be decrypted, or the encrypted file could not be decrypted. The client should request the public key of the server and then retry (once). |
500 | M_UNKNOWN |
The server experienced an unexpected error. |
502 | MCS_MEDIA_REQUEST_FAILED |
The server failed to request media from the media repo. |
Downloads the media at mxc://{serverName}/{mediaId}
and scans it. If the scan is
successful, the media is sent in the response (identical to the
GET /_matrix/media/v3/download/...
route in the Matrix specification). If the scan is
unsuccessful, an error is sent with the reason MCS_MEDIA_NOT_CLEAN
.
Takes the query parameters described in the Matrix specification.
Downloads a thumbnail of the media at mxc://{serverName}/{mediaId}
and scans it. If the
scan is successful, the media is sent in the response (identical to the
GET /_matrix/media/v3/thumbnail/...
route in the Matrix specification). If the scan is
unsuccessful, an error is sent with the reason MCS_MEDIA_NOT_CLEAN
.
Downloads the media at mxc://{serverName}/{mediaId}
, scans it and
responds with the result of the scan.
Response format:
Parameter | Type | Description |
---|---|---|
clean |
bool | The scan's result: true if the file is clean, false otherwise. |
info |
str | Human-readable information about the result. |
Example:
{
"clean": false,
"info": "***VIRUS DETECTED***"
}
Downloads a specified encrypted file, decrypts it and then behaves identically to the
GET /_matrix/media_proxy/unstable/download/{serverName}/{mediaId}
route.
Request body:
Parameter | Type | Description |
---|---|---|
encrypted_body |
EncryptedBody | An Olm-encrypted version of the request body. See this section for more information. |
file |
EncryptedFile | The metadata (download MXC URL and decryption key) of an encrypted file. Follows the format of the EncryptedFile structure from the Matrix specification. Ignored if encrypted_body is present. |
Example:
{
"file": {
"v": "v2",
"key": {
"alg": "A256CTR",
"ext": true,
"k": "qcHVMSgYg-71CauWBezXI5qkaRb0LuIy-Wx5kIaHMIA",
"key_ops": [
"encrypt",
"decrypt"
],
"kty": "oct"
},
"iv": "X85+XgHN+HEAAAAAAAAAAA",
"hashes": {
"sha256": "5qG4fFnbbVdlAB1Q72JDKwCagV6Dbkx9uds4rSak37c"
},
"url": "mxc://matrix.org/oSTbuSlyZKXvgtbtUsPxRbto"
}
}
Downloads a specified encrypted file, decrypts it and then behaves identically to the
GET /_matrix/media_proxy/unstable/scan/{serverName}/{mediaId}
route.
The request body for this route is the same as for
POST /_matrix/media_proxy/unstable/download_encrypted
.
Responds with a base64 representation of the public key to use to generate the
encrypted_body
parameter of POST requests. See this section for
more information.
Response format:
Parameter | Type | Description |
---|---|---|
public_key |
str | A base64 representation of the public key. |
Example:
{
"public_key": "GdwYYj5Ey9O96FMi4DjIhPhY604RuZg2Om98Kqh+3GE"
}
When processing encrypted attachments, there are two ways to communicate the metadata (i.e. URL and decryption key for the file) to the Matrix Content Scanner.
The first one is by sending it in the request body as shown above. However, this might not provide enough security depending on the infrastructure the Matrix Content Scanner is deployed in. For example if translation from HTTPS to HTTP is done on a separate machine than the one hosting the Matrix Content Scanner, it might be a concern that other pieces of the infrastructure might be able to intercept this traffic and decrypt the attachment.
The second way of communicating encrypted file metadata is to first encrypt it using
libolm's PkEncryption
class. This is done using the public key retrieved from
GET /_matrix/media_proxy/unstable/public_key
and sending the resulting encrypted message
in an encrypted_body
parameter of the request's body. This parameter follows this format:
Parameter | Type | Description |
---|---|---|
ciphertext |
str | The encrypted content. |
mac |
str | The MAC. |
ephemeral |
str | The ephemeral key. |
Example (generated using the body and public key from the previous examples):
{
"encrypted_body": {
"ciphertext": "tED6iNpKcZti+HMZ6t1M+ZlE27IbvF9nojz59dg3jtJHv/9wtH6KiYyaZsVvCNzuwWCjdcxA4PMevZuWnVIEWHArCKdcFJeAvzxzlVtFvlgM5PIiTNtkh8sXIaC7RP5+3s0/aQs9PhuhlJ5nGlS86BZJ56dDwQWS5DO/WPqsTko9lz6//XtZ8ko417vybz81NTNpoADRc8XRntsI1+rmdKkXJtuXTA3d46CCAhLvoJLZlk7xb7IGHADk3eYQ9WTaKQ76/PW1dDo5xQGyXOr+lJByisjkoz4C8i4wRYXnks+d3q6kIndGZgO8s/H7/kfYC052IAlAk3LmYavXaNwXJtnWUCCakTHME154yup8DtmsyuZkC3p3KhSsKAeoxmYvsSf0+p0MinOWB4BgeWwaBaKDKTHbaUKwQzdbZrBXKP+QBdmM9PUrmsTPR2RmWRsPCC3dcmz4rakCZB/Xvwg++xDzpxi3+iJxJ011g1Dfp4sd44U6LJDVZafIoPu7esChYD4o+x4tP4airHueLGpP0rQxPuDZRvklwCRZ5xtzr47fINel2IGrTQEPyNES+lASGr2xeWwBJXBe47OkM0rXZn1HVM6iK3g3HfUT6pFhdI/52ztUf+gOhOhRvTpP079Je9INLApXSu793EQGJpH+ms3ymJ3mfBhEYVVnj8zbczo",
"mac": "nipjbUCnIEw",
"ephemeral": "fk2xOTmttnFDTAORxVQTtIlbsu7O01Oe52+umaOjIiE"
}
}