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.

Sign up for GitHub

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

Jump to bottom

OMEMO doesn't work with Dukgo and possibly other servers #607

Closed
chrisballinger opened this issue Nov 23, 2016 · 2 comments
Closed

OMEMO doesn't work with Dukgo and possibly other servers #607

chrisballinger opened this issue Nov 23, 2016 · 2 comments
Labels
Bug
Milestone
4.0

Comments

@chrisballinger
Copy link
Member

This may be due to a broken PEP implementation because they run an old version of Prosody. Conversations has code to detect broken PEP implementations, but there's not really a reliable way to test if it's broken. I reached out to Dukgo to see if they could update their server, which might improve the issue.

If this remains a problem we may want to reconsider the default server options.
@chrisballinger chrisballinger added this to the 4.0 milestone Nov 23, 2016
@asiamov
Copy link

asiamov commented Nov 23, 2016

This is also the case for jabber.de.
Own OMEMO fingerprint is visible on both sides but the conversation can only be encrypted with OTR.

@chrisballinger
Copy link
Member Author

@asiamov This is fixed in beta 49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
4.0
Development

No branches or pull requests
2 participants
@chrisballinger @asiamov