From 3d2a5a8f385cfce456719a1f2f8f5998eca9cc7f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Thu, 14 Apr 2022 12:02:47 +0200 Subject: [PATCH] threat-model: update MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- content/posts/thread-model.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/thread-model.en.md b/content/posts/thread-model.en.md index 45f6323..38974e9 100644 --- a/content/posts/thread-model.en.md +++ b/content/posts/thread-model.en.md @@ -159,7 +159,7 @@ Interactions with OMEMO between non-contacts is a mess. Some servers have the [`mod_block_strangers`] module deployed as an anti-spam measure: when a user from such a server joins a private room, non-contacts will be prevented from fetching their keys. Dino creates the OMEMO node as [only accessible by -contacts][dino-omemo] (in an effort to prevent enumeration attacks). And +contacts][dino-omemo] (to prevent deanonymization in some types of MUCs). And Conversations [doesn't allow sending encrypted messages][conversations-omemo] if it doesn't have keys of all participants in a private room.