From 9103a0a3980192f78d65f2f9c08f8e6a5d3e726b Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Thu, 16 Apr 2020 14:58:27 -0400 Subject: [PATCH] minor clarifications and corrections --- proposals/1756-cross-signing.md | 4 ++-- proposals/1946-secure_server-side_storage.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/1756-cross-signing.md b/proposals/1756-cross-signing.md index 4b5904bc..de08422a 100644 --- a/proposals/1756-cross-signing.md +++ b/proposals/1756-cross-signing.md @@ -216,7 +216,7 @@ response: } ``` -Similarly, the federation endpoints `POST /user/keys/query` and `POST +Similarly, the federation endpoints `POST /user/keys/query` and `GET /user/devices/{userId}` will include the master and self-signing keys. (It will not include the user-signing key because it is not intended to be visible to other users.) @@ -463,7 +463,7 @@ response: } ``` -Similarly, the federation endpoints `GET /user/keys/query` and `POST +Similarly, the federation endpoints `POST /user/keys/query` and `GET /user/devices/{userId}` will include the new signatures for her own devices or master key, but not signatures made by her user-signing key. diff --git a/proposals/1946-secure_server-side_storage.md b/proposals/1946-secure_server-side_storage.md index fd907e53..3f386d5e 100644 --- a/proposals/1946-secure_server-side_storage.md +++ b/proposals/1946-secure_server-side_storage.md @@ -66,7 +66,7 @@ corresponds to the public key. Encrypted data is stored in the user's account_data using the event type defined by the feature that uses the data. For example, decryption keys for -key backups could be stored under the type `m.megolm_backup.v1.recovery_key`, +key backups could be stored under the type `m.megolm_backup.v1`, or the self-signing key for cross-signing could be stored under the type `m.cross_signing.self_signing`.