OTR and multiple resources

[neubyi]

• other party is using two clients (both being xmpp-client) with different resource strings, let them be remote-a and remote-b
• remote-a has negative priority, remote-b has positive priority
• i do /otr start on the "general contact" (with a plus sign)
• i receive and decrypt correctly
• when trying to send i see OTR Warning didn't send message, there was no encrypted connection: OTR warning Malformed OTR data message: type
• other party sees ?OTR Error:Malformed OTR data message: type
• other party disconnects remote-a
• /otr info on the generic contact lists two sessions, both in state plain (auth none)
• /otr stop on the generic contact results in error no active session
• the generic contact is green
• /otr start on contact remote-b brings otr session to state: encrypted version 2 (smp initial)
• i can send (and receive) to remote-b
• when trying to send on the (still green) generic contact, i get the above behaviour and the previously working otr session in state encrypted is going to plain again
• the generic contact stays green while remote-b turns red

[hannesm]

thanks for the report!

the negative priority is a bad idea, meant to be for bots. from reading https://tools.ietf.org/html/rfc6121#section-8 I gathered that a negative priority will usually not work nicely (e.g. when sending messages to the bare contact, rather than the bare+resource).

given the deployment of negative priorities (if the issue is related to this), maybe jackline should treat them "normally" (I'm not sure whether this is the actual issue or not, and will need some time to remind myself of the code and branches which are taken if priority is negative)

[TealG]

I have experienced a similar issue when multiple sessions are open to a contact, it happens sometimes that I get this Malformed OTR data message: type error, and then the OTR session restarts.. Seems like this happens when on the left side the list of sessions of the contact is open, it does not happen when the list is hidden and a + sign is shown in front (in both cases sending message to the generic contact not a particular session) Not sure if this issue is specific to the client of the other side, so far I had this issue with 2 contacts using pidgin.