jcast

joined 5 years ago
sorted by: new top controversial old
E2EE vulnerabilities in matrix-js-sdk, matrix-ios-sdk and matrix-android-sdk2: if you use Element or in c/matrix@lemmy.ml
[–] jcast@mastodon.social 1 points 2 years ago

@poVoq @sexy_peach

shared meaning cross-signed

E2EE vulnerabilities in matrix-js-sdk, matrix-ios-sdk and matrix-android-sdk2: if you use Element or in c/matrix@lemmy.ml
[–] jcast@mastodon.social 2 points 2 years ago (2 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?

E2EE vulnerabilities in matrix-js-sdk, matrix-ios-sdk and matrix-android-sdk2: if you use Element or in c/matrix@lemmy.ml
[–] jcast@mastodon.social 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.