Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

Unable to receive OMEMO encrypted messages with fallback #466

Open
kmq opened this issue Apr 25, 2018 · 6 comments
Open

Unable to receive OMEMO encrypted messages with fallback #466

kmq opened this issue Apr 25, 2018 · 6 comments

Comments

@kmq
Copy link

kmq commented Apr 25, 2018

Scenario

An OMEMO encrypted message that includes a fallback is received.

Expected

Zom decrypts the message and ignores the fallback

Actual

Zom shows only the fallback message

I have sent you an OMEMO encrypted message, but your client doesn't
seem to support that.

completely ignoring the encrypted payload.

This makes impossible to communicate with people using the zom.im server, as that server disallows unencrypted communication.

@n8fr8
Copy link
Contributor

n8fr8 commented Apr 25, 2018

Got it. I thought we handled this correctly. Looking into it...

@n8fr8 n8fr8 added this to the Final Spring Sprint milestone Apr 25, 2018
@wiktor-k
Copy link

I'm also experiencing this issue from contacts using Conversations.im

@tiffrobo
Copy link

tiffrobo commented Jun 6, 2018

@iamironrabbit I don't fully understand the ticket. Can you tell me how to test this one, please?

@iamironrabbit
Copy link
Collaborator

In short, test using Conversations.im app. If you can receive messages from Conversations to Zom, then it is fixed. So says the rabbit!

@tiffrobo
Copy link

@iamironrabbit can you test this one, please?

@wiktor-k
Copy link

I tested this with Zom version 15.5.0-RC-2 and the behavior of Zom is very weird: some messages from Conversations are correctly decrypted but some of them still show the fallback ("I sent you an OMEMO..."). It's hard to me to spot the difference why some of them work and some doesn't but the bug is 100% reproducible.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants