OTR on the desktop (as opposed to Android) has started acted up again.
It automatically enables itself upon starting a conversation and I
have to click on the lock icon in the chat window to stop it.
Yes, that's correct. The expected default behaviour is for the OTR to start
automatically when possible.
If one wants though, he could either disable OTR with the respective Contact
from Secure chat -> uncheck Enable private conversations or
he could uncheck Secure chat -> "Automatically start private conversations
with Contact/All Contacts".
However, with the second/third option one would not prevent others to start
OTR with him, but he will stop attaching the so called "otr whitespace tags"
to every message he sends. The semantics of these "whitespace tags" are
expressing the desire of the sender to establish an encrypted session with
the remote party.
Thank you very much, Marin!
time, that same contact send me a message and I receive it in Gmail
chat on the desktop or Hangouts on Android but it's encrypted there
and I cannot read it.
Do you know whether the remote party is also logged in the latest Jitsi's
desktop? If yes then this is probably a bug.
If not, however, then this behaviour is expected. As we know, your contact
had previously established otr session with you. Most of the instant
messengers out there (including Adium, Pidgin and Jitsi before the update)
do not support establishing separate OTR sessions for separete jids of the
same contact. This means that if your contact has changed his outgoing jid
for some reason then he would have encrypted the message with the previously
established session keys and your Andoid device would not be able to read
I hope this clears things up a bit.
If you have any further questions feel free to ask
Please let me bother you a bit more with that.
I read the following at
2014/1/17 Marin Dzhigarov <email@example.com>:
This all having been said, the "multiple logins" problem is one that's
been bothering us for a really long time, and I'm happy to say that
we've now got someone working on fixing exactly that issue. It won't be
in the (imminent) 3.2.0 release, but will almost certainly be in v4.
I went to https://otr.cypherpunks.ca and read the following excerpt of
news published on September 4th, 2012:
pidgin-otr 4.0.0 and libotr 4.0.0 released
The long-awaited version 4.0.0 of pidgin-otr and libotr are finally here!
The main new features in 4.0.0:
- The plugin now supports multiple OTR conversations with the same
buddy who is logged in at multiple locations. In this case, a new OTR
menu will appear, which allows you to select which session an outgoing
message is intended for. Note that concurrent SMP authentications with
the same buddy who is logged in multiple times is not yet supported
(starting a second authentication will end the first).
libotr API changes:
- instance tags, to support multiple simultaneous logins
What does that mean?