[telepathy] [Bug 344556] New: OTR is stopped without notifying the other end when conversation is closed
Raimar Sandner
disp.reg.bugs.kde at typename.de
Wed Feb 25 14:14:22 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=344556
Bug ID: 344556
Summary: OTR is stopped without notifying the other end when
conversation is closed
Product: telepathy
Version: 0.9.0
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: OTR
Assignee: kde-telepathy-bugs at kde.org
Reporter: disp.reg.bugs.kde at typename.de
CC: zieminn at gmail.com
First of all I was very excited to see OTR support in telepathy, thank you!
However at the moment there is a big issue with the conversation flow (at least
for my typical use case).
Because the OTR session is closed when the chat window is closed, new messages
which arrive are unreadable, and I have to ask my correspondent to send them
again after the OTR session is refreshed.
Actually I don't know if the issue lies with telepathy or with the other
clients. Anyhow, the OTR session should be closed properly, so that the other
end knows new messages cannot be encrypted within the same session anymore.
Alternatively (maybe as a configurable option) the OTR session should be kept
open when closing the chat window. This is how most other clients work at the
moment, I guess.
Reproducible: Always
Steps to Reproduce:
(tested with Adium or kopete on the other end):
1. initiate an otr session, exchange some messages
2. close the chat window
3. your correspondent sends you a new message
Actual Results:
The messages belong to the old OTR session and are unreadable because they
cannot be decrypted on my end.
Expected Results:
Messages are decrypted within the previos OTR session, which would have to be
kept open for this purpose. Alternatively, properly close the old OTR session,
so that a new one has to be established by the sender.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kde-telepathy-bugs
mailing list