-
Notifications
You must be signed in to change notification settings - Fork 24
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
Comments
Try Psi+ 1.4.1299 or newer please. |
@kssytsrk: Can you look this ticket? |
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? |
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: |
When we are on a protected MUC Room, after an OMEMO discussion with several people, if we are the last people (alone):
When we send a message:
-> Impossible to disable OMEMO (icon is in grey)
Linked to:
The text was updated successfully, but these errors were encountered: