Describe the bug
I am in an OMEMO-encrypted MUC where one participant is using Siskin IM. A 1-1 message works both ways between them and me, but all their MUC messages appear as unencrypted to both of my clients (Dino and Conversations). Two other participants in the MUC (who are using Dino, Conversations, and some other clients) report being able to read the messages.
To Reproduce
Steps to reproduce the behavior:
Certain MUC participant sends a message
Shows as "I sent you an OMEMO encrypted message but your client doesn’t seem to support that." (in Dino)
Expected behavior
I should be able to read the message
Screenshots
N/A
Details (please complete the following information):
Siskin Version: siskin v6.4
iOS version: iOS 14.4
iPhone model: iphone 8
Additional context
Side note, it looks every link except for the docs link in the Support section of the README is broken. They all redirect to https://tigase.net/ for me.
Let me know if there's any other info that would be helpful.
Unknown commented 3 years ago
Just to add onto this: in Siskin IM, if I go to "Room Details" for an encrypted MUC and set "Encryption" to OMEMO, then messages do not send at all.
So if "Encryption" is set to "None," messages sent to the encrypted MUC are readable by other clients, but not encrypted. If "Encryption" is set to "OMEMO," the messages do not send.
Details
Siskin version 6.4
iOS 14.7.1
iPhone SE
Unknown commented 3 years ago
@cpif global settings encryption is set to OMEMO?
Unknown commented 3 years ago
There is no such thing as "encrypted MUC". Encryption with OMEMO works only for "members-only" MUC rooms - if enabled for not members-only room it may reject sending messages and that is expected.
Describe the bug I am in an OMEMO-encrypted MUC where one participant is using Siskin IM. A 1-1 message works both ways between them and me, but all their MUC messages appear as unencrypted to both of my clients (Dino and Conversations). Two other participants in the MUC (who are using Dino, Conversations, and some other clients) report being able to read the messages.
To Reproduce Steps to reproduce the behavior:
Expected behavior I should be able to read the message
Screenshots N/A
Details (please complete the following information):
Additional context Side note, it looks every link except for the docs link in the Support section of the README is broken. They all redirect to https://tigase.net/ for me.
Let me know if there's any other info that would be helpful.