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] Protected MUC Room problem, if alone -> OMEMO is forcing: *** [OMEMO] Unable to build any sessions, the message was not sent #57

Closed
Neustradamus opened this issue Jan 8, 2020 · 4 comments · Fixed by #106

Comments

@Neustradamus
Copy link
Contributor

Neustradamus commented Jan 8, 2020

When we are on a protected MUC Room, after an OMEMO discussion with several people, if we are the last people (alone):

  • OMEMO icon: Grey "OMEMO is not available for this contact"

When we send a message:

  • *** [OMEMO] Unable to build any sessions, the message was not sent

-> Impossible to disable OMEMO (icon is in grey)

Linked to:

@tehnick
Copy link
Member

tehnick commented May 26, 2020

Try Psi+ 1.4.1299 or newer please.

@Neustradamus
Copy link
Contributor Author

@kssytsrk: Can you look this ticket?

@kssytsrk
Copy link
Contributor

Can reproduce on Psi+ 1.5.1551 (2021-08-16) / FreeBSD 13.0, but isn't this expected behavior? I don't think it'd be troublesome to implement OMEMO-encrypting the message using sender's own key, just not sure if it's needed/conforming to the XEP (here, for example, it is specified that the messages should be encrypted using the recipients' keys and the keys of sender's other devices). Have you tested this with any other clients (Gajim, Dino, Conversations?), do they implement this?

@Neustradamus
Copy link
Contributor Author

I have done a new ticket, now we are not "OMEMO forced" with last commits from @nullobsi and @stigger (thanks) but the problem is always here when the last try to send an OMEMO message in MUC Room (and the error is now showed for myself OMEMO messages that were not showed before, invisible).

Linked to:

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

Successfully merging a pull request may close this issue.

3 participants