Explain what is meant by Signed JSON.

The explanation is copied from another place for consistency. There's
now a link to the Signing JSON section of the spec.
This commit is contained in:
Denis Kasak 2022-05-26 15:26:22 +02:00
parent 73a7c7e70c
commit 6e4159bea2

View file

@ -1257,10 +1257,10 @@ the following format:
`AuthData` `AuthData`
| Parameter | Type | Description | | Parameter | Type | Description |
| -----------| -----------|--------------------------------------------------------------------------------------------------| | -----------| -----------|-----------------------------------------------------------------------------------------------------------------------|
| public_key | string | **Required.** The curve25519 public key used to encrypt the backups, encoded in unpadded base64. | | public_key | string | **Required.** The curve25519 public key used to encrypt the backups, encoded in unpadded base64. |
| signatures | Signatures | Optional. Signatures of the ``auth_data``, as Signed JSON. | | signatures | Signatures | *Optional.* Signatures of the ``auth_data``. The signature is calculated using the process described at Signing JSON. |
The `session_data` field in the backups is constructed as follows: The `session_data` field in the backups is constructed as follows: