From fc793557f8d7e0a71ff671fb97b86d4529910e43 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 12 Nov 2019 10:48:38 -0500 Subject: [PATCH] make the default key event an object --- proposals/1946-secure_server-side_storage.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/proposals/1946-secure_server-side_storage.md b/proposals/1946-secure_server-side_storage.md index aa4fd8f91..fd907e535 100644 --- a/proposals/1946-secure_server-side_storage.md +++ b/proposals/1946-secure_server-side_storage.md @@ -49,10 +49,11 @@ A key with ID `abcdefg` is stored in `m.secret_storage.key.abcdefg` ``` A key can be marked as the "default" key by setting the user's account_data -with event type `m.secret_storage.default_key` to the ID of the key. The -default key will be used to encrypt all secrets that the user would expect to -be available on all their clients. Unless the user specifies otherwise, -clients will try to use the default key to decrypt secrets. +with event type `m.secret_storage.default_key` to an object that has the ID of +the key as its `key` property. The default key will be used to encrypt all +secrets that the user would expect to be available on all their clients. +Unless the user specifies otherwise, clients will try to use the default key to +decrypt secrets. Clients MUST ensure that the key is trusted before using it to encrypt secrets. One way to do that is to have the client that creates the key sign the key