this post was submitted on 28 Sep 2022
19 points (100.0% liked)

Matrix

3388 readers
5 users here now

An open network for secure, decentralized communication

founded 5 years ago
MODERATORS
top 10 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 2 years ago (1 children)
[–] [email protected] 2 points 2 years ago

And again in a part that they added to make e2ee more convenient for users that are only security LARPing anyways.

[–] [email protected] 3 points 2 years ago
[–] [email protected] 3 points 2 years ago

@cypherpunks waiting for @fdroidorg to push updates...

[–] [email protected] 3 points 2 years ago (2 children)

How does XMPP with omemo handle these situations?

[–] [email protected] 3 points 2 years ago

@sexy_peach @cypherpunks

I'm a random user but I did hear some discussion on the potential for this kind of vulnerability a while ago in the XMPP Conversations group chat.

OMEMO does not allow access to previous messages when you add a new device. If the message wasn't originally encrypted for the target device, the device will not be able to read it. But the best place to ask this question is in that group chat.

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago) (1 children)

AFAIK they don't exist because OMEMO keys are device and not account specific, so this entire class of attack surface does not exist.

[–] [email protected] 1 points 2 years ago (1 children)

@poVoq @sexy_peach

Isn't matrix also based on session keys?
I think the issue is more about how keys are shared between devices, and access to previous messages granted?

[–] [email protected] 3 points 2 years ago

I am not an expert on the topic, but yes the key sharing seems to be the ultimate source of these issues.

[–] [email protected] 1 points 2 years ago

As far as I am concerned, I use Matrix as a replacement for Slack/Discord/IRC, where I absolutely don't count on e2ee. And Matrix does that really well. For e2ee direct messaging, I use alternatives like Signal or Threema.