You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you please check whether or not BeagleIM & SiskinIM are affected of the OMEMO change as described in https://monal.im/blog/omemo-is-broken-in-general-across-the-ecosystem/ ? Daniel Gultsch from Conversations do seem to have made the change as well.
From what I understood of this discussion still using non-12byte IV will render OMEMO not working on those clients.
The text was updated successfully, but these errors were encountered:
This issue is already fixed in the master branch of TigaseSwiftOMEMO ( tigase/MartinOMEMO@628db2a ) and the fix will be part of the next releases of BeagleIM and SiskinIM.
Hi!
Can you please check whether or not BeagleIM & SiskinIM are affected of the OMEMO change as described in https://monal.im/blog/omemo-is-broken-in-general-across-the-ecosystem/ ? Daniel Gultsch from Conversations do seem to have made the change as well.
From what I understood of this discussion still using non-12byte IV will render OMEMO not working on those clients.
The text was updated successfully, but these errors were encountered: