Bug 348177 - OTR messages cannot be seen in log viewer
Summary: OTR messages cannot be seen in log viewer
Status: RESOLVED DUPLICATE of bug 344144
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: OTR (show other bugs)
Version: 0.9.0
Platform: Other Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-24 13:44 UTC by Franz Schrober
Modified: 2015-05-25 06:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franz Schrober 2015-05-24 13:44:04 UTC
It seems it is not possible to see old messages in the log viewer when they were transported via OTR.

I personally think that end-to-end encryption should be the default mode when communicating. But it is not usable when by default no old messages can be retrieved. I understand that it may be good to stop storing messages when they never, ever should be seen again. But the normal user may still expect to access his/her/its old messages.

I don't want my message service provider to read my messages. But this doesn't make them top secret, only-read-once, destroy in 10 seconds messages

Reproducible: Always

Steps to Reproduce:
1. Start OTR session
2. send some messages
3. open the log viewer through "previous conversations"
4. try to read the old message

Actual Results:  
The messages only appear as "Encrypted message"

Expected Results:  
Message can be read either directly or after pressing something obvious to read it
Comment 1 Franz Schrober 2015-05-24 13:51:37 UTC
Btw. when someone comes with "OTR is only for messages which are very secret and must never be saved": Then please provide a better alternative which is supported by things like kde-telepathy + (at least) kopete and still provides end-to-end encryption.  Some new version for XEP-0027 for example.
Comment 2 Martin Klapetek 2015-05-25 06:53:47 UTC

*** This bug has been marked as a duplicate of bug 344144 ***