Bug #244
OTR should lock to a specific XMPP resource
| Status: | Closed | Start date: | 08/10/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | devrandom | % Done: | 0% | |
| Category: | - | |||
| Target version: | v12 - March Mantra | |||
| Component: |
Description
Session gets confused if a new resource of the peer comes online and we start talking to it in the middle of an OTR conversation.
Related issues
Associated revisions
Lock to a specific resource during an OTR session.
Fixes #244
Put back OTR lock to presence
fixes #244
History
#1 Updated by devrandom over 5 years ago
- Subject changed from OTR with multiple presences is wonky to OTR should lock to a specific XMPP resource
- Description updated (diff)
- Assignee set to devrandom
- Target version set to v10 - June Jaunts
#2 Updated by devrandom over 5 years ago
- Status changed from New to Resolved
#3 Updated by J over 5 years ago
Is this a feature of libotr4? Or GP magic?
#4 Updated by devrandom over 5 years ago
We implemented what Pidgin does - specify the destination resource for message sending once OTR negotiation starts.
This is not OTR v3 / libotr4. We should implement that too. It drops incoming messages destined for other presences. That's useful if the server broadcasts messages to all presences.
#5 Updated by devrandom over 5 years ago
Created issue #331 for that.
#6 Updated by n8fr8 about 5 years ago
- Target version changed from v10 - June Jaunts to v11 - January Judo
#7 Updated by n8fr8 almost 5 years ago
- Target version changed from v11 - January Judo to v12 - March Mantra
#8 Updated by devrandom over 4 years ago
Hi n8fr8,
Commit c7b61f3 reverted changes to XmppAddress and broke this fix. Please let me know what was the thinking behind that.
#9 Updated by devrandom over 4 years ago
- Status changed from Resolved to In Progress
#10 Updated by devrandom over 4 years ago
- Status changed from In Progress to Resolved
#11 Updated by n8fr8 about 4 years ago
- Status changed from Resolved to Closed