Bug #3992
OTR is not working
| Status: | Resolved | Start date: | 01/24/2015 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: | n8fr8 | % Done: | 100% | |
| Category: | - | |||
| Target version: | v14.2 bug fix update! | |||
| Component: |
Description
OTR doesnt seem to work....
After first install it seems to work after that nothing tried between 14.0.6 and 14.0.6.... 14.0.6 and 14.0.4....14.0.6 and pidgin with otr... all through latest version of prosody.
I also noticed that if I open a chat from 14.0.6 to pidgin and i start texting unencrypted it takes up to a minute to deliver the messages from pidgin to 14.0.6 its works fine.
Chatsecure runs on CM10.
Subtasks
History
#1 Updated by n8fr8 about 3 years ago
- Status changed from New to In Progress
- Assignee set to n8fr8
- Target version set to v14 - Armadillo's Agram
We've made a number of fixes on the OTR front, so keep us posted if this problem continues. You may need to close and restart any open chats you have first. Another thing to try is to do a fresh install of the app, to ensure your key is not corrupted somehow.
As for delays in messaging sending, we've made no changes there, so it is likely related to network congestion and latency.
#2 Updated by hans about 3 years ago
I just saw a weird one-sided delay between jabber.org/ChatSecure and limun.org/Gajim. I was also sending messages between Gajim and Pidgin at the same time. The messages from limun.org/Gajim to jabber.org/ChatSecure were arriving in less than 10 seconds but the messages from jabber.org/ChatSecure to limun.org/Gajim did not seem to arrive. Then after a minute or two, all the messages from jabber.org/ChatSecure arrived.
This came after I had initiated an OTR session between the two, then rebooted the device with ChatSecure on it. Then sending a message from Gajim to ChatSecure dumped an "unreadable encrypted message" stacktrace, then Gajim dumped four of those and refreshed:
[10:56:20 PM] [OTR] We received the following OTR error message from gptest@jabber.org/ChatSecure-20bbf32c: [You sent me an unreadable encrypted message] [10:56:21 PM] [OTR] We received the following OTR error message from gptest@jabber.org/ChatSecure-20bbf32c: [You sent me an unreadable encrypted message] [10:56:21 PM] [OTR] We received the following OTR error message from gptest@jabber.org/ChatSecure-20bbf32c: [You sent me an unreadable encrypted message] [10:56:21 PM] [OTR] We received the following OTR error message from gptest@jabber.org/ChatSecure-20bbf32c: [You sent me an unreadable encrypted message] [10:56:22 PM] [OTR] Private conversation with gptest@jabber.org/ChatSecure-20bbf32c refreshed.
That's when gajim could sent to chatsecure but the cs to gajim were delayed.
Here's a debug logcat:
https://gist.github.com/eighthave/c6deb99eb0198f0283f1
#3 Updated by n8fr8 over 2 years ago
- Target version changed from v14 - Armadillo's Agram to v14.2 bug fix update!
#4 Updated by n8fr8 over 2 years ago
- Status changed from In Progress to Resolved
Going to mark this resolved, since we have implemented multiple fixes on this front. Primarily, mixed case usernames caused problems, along with some OTR session state bugs. We will see once the v14.2 release goes out.