Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OMEMO key issue #1480

Closed
stevenroose opened this Issue Mar 6, 2019 · 2 comments

Comments

Projects
None yet
1 participant
@stevenroose
Copy link

stevenroose commented Mar 6, 2019

2019-03-06

This should definitely not be true. My server forces all OMEMO nodes to be open access. Is there a way to determine which keys are causing this issue?? In the meantime, messages I send to them are not being received.

Another thing: does Converse announce its OMEMO key on login? Or just when the user tries to send an encrypted message?

For clarity: this happens with at least 2 of my contacts. They both can send and receive encrypted messages with me via Conversations. But once they are on Converse, both sending and receiving stops working.

@stevenroose

This comment has been minimized.

Copy link
Author

stevenroose commented Mar 6, 2019

Scrap my last comment. Not resolved with ejabberd key fixes. My contacts are still seeing empty messages.

@stevenroose

This comment has been minimized.

Copy link
Author

stevenroose commented Mar 8, 2019

So this seems to be solved with forcing all OMEMO nodes to be open access. Now it's just those empty messages, I talked about.

@stevenroose stevenroose closed this Mar 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.