From 8efd9e53d3606a9b94bbf123180376261d9b234e Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Tue, 7 Jun 2022 11:47:40 -0600 Subject: [PATCH] Remove incorrect example --- content/client-server-api/modules/end_to_end_encryption.md | 4 +--- 1 file changed, 1 insertion(+), 3 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 abeae27a..e2d65102 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1626,9 +1626,7 @@ messages. When a client is updating a Megolm session (room key) in its store, the client MUST ensure: -* that the updated session data comes from a trusted source, where a trusted source - could be the signatures on the session or those from the user's session key backup; - and +* that the updated session data comes from a trusted source. * that the new session key has a lower message index than the existing session key. #### Protocol definitions