Modify ↓

Opened at 2011-10-06T20:44:46Z

Last modified at 2013-08-05T15:30:15Z

#836 new defect

multiple jabber clients on the same account fight over OTR sessions

Reported by: pesco Owned by: pesco
Priority: wishlist Milestone:
Component: OTR Version: 3.0.3
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description

i've been told that this happens, i.e. people have one client at home and one at work. when OTR kicks in the home and work clients fight over who gets to establish the encrypted connection.

i need to try this myself, but reading up a bit on jabber's "resource" system makes it seem like we might just have to differentiate OTR connections by resource (in addition to user/protocol).

is there a reasonable way for the OTR plugin to determine the resource a jabber message is eventually going to be sent to?

Attachments (0)

Change History (2)

comment:1 Changed at 2011-10-06T20:44:58Z by pesco

Component: BitlBee → OTR
Owner: set to pesco

comment:2 Changed at 2013-08-05T15:30:15Z by pesco

This problem is addressed by libotr-4.0.0 (OTR protocol version 3) in the form of "instance tags". See #1004.

Modify Ticket

Action
as new The owner will remain pesco.

Add Comment

E-mail address and name can be saved in the Preferences.

Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.