Opened 15 years ago

Closed 15 years ago

Last modified 11 years ago

#2895 closed defect (fixed)

OTR status does not update after switch between different "real" contacts of a metacontact

Reported by: anonymous Owned by: nobody
Milestone: Adium X 1.0 Component: Adium Core
Version: Severity: normal
Keywords: Cc:
Patch Status:


If you have a chat window open talking to one identify (i.e. "real" contact) of a metacontact and double-click the metacontact in your buddy list, AdiumX presents you with popup menus in the message window to choose which identity to send your next message to. If you pick a new identity, the OTR status is not updated, and messages sent to the new identity are sent using the OTR state of the old identity.

Example: Alice starts talking with Bob over AIM using OTR encryption. Alice double-clicks Bob's metacontact in her buddy list and sends a message to him over a Jabber account. Alice sends the message encrypted, even though an encrypted chat probably wasn't active between Alice-jabber and Bob-jabber.

Adium 0.88 changed the behavior of things slightly. Now, when Alice switches to Jabber, she would send the message /unencrypted/ even though the GUI would indicate that OTR was still enabled. Since Alice could send unencrypted data but think the connection was secure, I'm assigning the bug "major" severity.

Change History (3)

comment:1 Changed 15 years ago by Chris Forsythe

Milestone: Adium X 1.1
Severity: majornormal

Do *not* set the severity on tickets.

comment:2 Changed 15 years ago by Evan Schoenberg

Milestone: Adium X 1.1Adium X 1.0
Resolution: fixed
Status: newclosed

Already fixed in 1.0svn.

comment:3 Changed 11 years ago by Zachary West

Component: OTRAdium Core

Removing 'OTR' component.

Note: See TracTickets for help on using tickets.