pep/blog.bouah.net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

threat-model: update

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2022-04-14 12:07:36 +02:00
parent 3d2a5a8f38
commit de3c6fad73
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2
1 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
content/posts/thread-model.en.md
View file

@ -109,9 +109,9 @@ isn't very much used. Even though it may also be the case for Dino..
Currently in server logs, a few things can be used to identify a client, such Currently in server logs, a few things can be used to identify a client, such
as the resource string set by the client to something similar to as the resource string set by the client to something similar to
`clientname.random`, or the `disco#info` which lists capabilities of a client. `clientname.randombits`, or the `disco#info` which lists capabilities of a
Both are actually stored on the server for possibly good reasons, but that's client. Both are actually stored on the server for possibly good reasons, but
always more information to identity somebody. that's always more information to identity somebody.
[Conversations]: https://conversations.im [Conversations]: https://conversations.im
[Dino]: https://dino.im [Dino]: https://dino.im
@ -159,12 +159,14 @@ 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 [`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 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 fetching their keys. Dino creates the OMEMO node as [only accessible by
contacts][dino-omemo] (to prevent deanonymization in some types of MUCs). And contacts][dino-omemo] (to prevent deanonymization [in some Prosody
Conversations [doesn't allow sending encrypted messages][conversations-omemo] MUCs][prosody-pep]). And Conversations [doesn't allow sending encrypted
if it doesn't have keys of all participants in a private room. messages][conversations-omemo] if it doesn't have keys of all participants in
a private room.
[`mod_block_strangers`]: https://modules.prosody.im/mod_block_strangers.html [`mod_block_strangers`]: https://modules.prosody.im/mod_block_strangers.html
[dino-omemo]: https://github.com/dino/dino/issues/1139 [dino-omemo]: https://github.com/dino/dino/issues/1139
[prosody-pep]: https://issues.prosody.im/1441
[conversations-omemo]: https://github.com/iNPUTmice/Conversations/issues/3081 [conversations-omemo]: https://github.com/iNPUTmice/Conversations/issues/3081
I am not even talking about OMEMO implementations (using [OMEMO I am not even talking about OMEMO implementations (using [OMEMO