From 7713a0f402667b3e73efc1edcfac22537de64c5d Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 30 Oct 2018 10:05:27 -0400 Subject: [PATCH] snake-case for consistency --- proposals/1219-storing-megolm-keys-serverside.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/1219-storing-megolm-keys-serverside.md b/proposals/1219-storing-megolm-keys-serverside.md index 6fb5c905d..194d50d10 100644 --- a/proposals/1219-storing-megolm-keys-serverside.md +++ b/proposals/1219-storing-megolm-keys-serverside.md @@ -398,8 +398,8 @@ The `session_data` field in the backups is constructed as follows: - `sender_key` (string): base64-encoded device curve25519 key - `sender_claimed_keys` (object): object containing the identity keys for the sending device - - `forwardingCurve25519KeyChain` (array): zero or more curve25519 keys for - devices who forwarded the session key + - `forwarding_curve25519_key_chain` (array): zero or more curve25519 keys + for devices who forwarded the session key - `session_key` (string): base64-encoded (unpadded) session key 2. Generate an ephemeral curve25519 key, and perform an ECDH with the ephemeral key and the backup's public key to generate a shared secret. The public