search

cmeng-git / atalk-android

xmpp/jabber client for android
Apache License 2.0
155 stars 56 forks source link

OTR message from another OTR-instance received. #208

Closed cmeng-git closed 5 months ago

cmeng-git commented 5 months ago

I attached a screen shot of the problem I am having with of the record. They still come in like this with OTR enabled

Whispered Message from another OTR-instance received

Screenshot_20240120_002342_c0nnectPRO

cmeng-git commented 5 months ago

What you observed is actually the OTR V3 implementation limitation. OTR protocol implementation generates and uses a unique key for handshake for each new OTR session initiated; and this key is only valid for this session.

Once an OTR session is completed; both parties must end the current OTR session before start another new OTR session. If only one of the parties ended the OTR session, then starts/enables another OTR session. Any OTR messages sent to previously setup OTR session will show the error message as shown in your comment.

To avoid seeing the problem, both parties must end and start a new OTR sessions; or go back to he previously setup OTR session. This is the inherited limitations of the OTR V3 implementations.

For message encrypted session, user is advised to use OMEMO instead. Many of the new chat client implementation has dropped support of OTR. For users wish to continue using OTR, he/she must understand and bear with the OTR V3 protocol limintation.

cmeng-git commented 5 months ago

Observation is OTR normal or limitations.