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.
Unknown commented 5 years ago
This issue is already fixed in the master branch of TigaseSwiftOMEMO ( tigase/tigase-swift-omemo@628db2afe4042477971676be59555a96a5c7d024 ) and the fix will be part of the next releases of BeagleIM and SiskinIM.
Unknown commented 5 years ago
Oh, great! Then I think this issue can be closed... :-)
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.