From 6e4159bea22a128d38482939a68de3633224a7d9 Mon Sep 17 00:00:00 2001 From: Denis Kasak Date: Thu, 26 May 2022 15:26:22 +0200 Subject: [PATCH] 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. --- .../client-server-api/modules/end_to_end_encryption.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 744e879f..0bed9f5b 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1257,10 +1257,10 @@ the following format: `AuthData` -| Parameter | Type | Description | -| -----------| -----------|--------------------------------------------------------------------------------------------------| -| 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. | +| Parameter | Type | Description | +| -----------| -----------|-----------------------------------------------------------------------------------------------------------------------| +| 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``. The signature is calculated using the process described at Signing JSON. | The `session_data` field in the backups is constructed as follows: