[OTR-users] Bug with auto-connection logic

[Byrd, Brendan]

The logic for sending and receiving encrypted and unencrypted messages
isn't automatic in all cases.  For example, the "The following message
received from XXXX was not encrypted" messages from the system don't
spawn a private connection.  The biggest issue with these messages is
that they are considered system messages, not chat messages, so the
window doesn't blink or alert you in any way.  Therefore, entire
conversations get missed because OTR isn't doing the job of establishing
the connection right away. 

 

Here's the behavior of OTR in all of the scenarios (first person is the
sender):

 

E-E - Both parties are encrypted, so there is no problem

U-E - This gives out the "not encrypted" message described above and
does NOT auto connect

E-U - This gives out the "not expecting an encrypted message" and does
auto connect

U-U - Both parties are unencrypted, so there is no problem (except for
the unencryption)

 

Furthermore, the reason why these problems happen also has to do with
actions that don't trigger OTR automatically, even with the
"Automatically initiate private conversations" option turned on.
Certain actions don't do anything automatically, like:

 

Open new chat window - Does NOT auto connect (it may say Private, but
does NOT tell the other side)

Close chat window - Does auto disconnect (naturally), but does NOT tell
the other side

Remote side logs off - Does NOT auto disconnects

Remote side logs on - Does NOT auto connect

 

These desyncing problems are what cause the above issues in the first
place.  Both should be tackled, but the latter would help out a lot in
fixing the former.

 

Making OTR work automatically when you tell it to work automatically
would make conversations painless.  As it is now, this "missing entire
conversations" bug is causing a lot of grief.

 

--
Brendan Byrd <byrd.b at insightcom.com <mailto:byrd.b at insightcom.com> >
System Integration Analyst (NOC Developer)

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20101213/80ef2fdf/attachment.html>