2
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Dec 2024
2 points (100.0% liked)
SimpleX Chat
586 readers
1 users here now
Community of SimpleX Chat users โ managed by the team.
SimpleX Chat is the first chat platform that is 100% private by design โ it has no user identifiers of any kind and no access to your connections graph โ it's a more private design than any alternative we know of.
Please ask any questions and make feature suggestions. Your ideas and criticism are very welcome!
https://github.com/simplex-chat/simplex-chat
founded 2 years ago
MODERATORS
Not sure which docs you are looking at, but my preferred description for this part is SMP
The previous message already pointed out the main point - communication happens via queues our clients knows to belong to the destination, and these queues are temporary. This means even if an attacker determines the queue belongs to a specific person it can be changed and even then it does not reveal who is the other contact using the queue.
A few more bits to consider:
So there are IDs but hopefully they are not useful for an attacker.
Now to answer your question. There are IDs but for a message to be delivered to the wrong person the following would need to happen
Caveats - the client app must be well implemented and NEVER reuse keys. Likewise the server must not reuse queue IDs.
I think I got my assumptions right. When in doubt check the 2nd link for a long step by step description of the protocol