Messages delayed using gpg encryption

[Wollschaf]

I'm experiencing problems communicating with encrypted messages between two gajim clients. For Example, user A is writing an encrypted message to user B who is totally unsuspecting of the upcoming event. Now, the following scenarios occur:

* Sometimes, the chat window pops up and the incoming message is noticed. This always works with non-encrypted messages.

* At other times, nothing happens at first. User A is waiting for reply and user B just does not receive the message instantly. If the chat window is already open, nothing happens as well. If chat state notifications are enabled, the message arrives when user A begins typing again. The message also arrives if user A sends another message (the messages then have the same timestamp, but might arrive in wrong order). If user A just waits for reply and otherwise does nothing, the message is delivered somewhere between 30 and 60 seconds after sending. This delay also occurs while being in conversation.

If one of both users uses psi, the encrypted messages are delivered instantly.

Chatlog from user A:

[13:02:22] A: p

[13:02:32] B: ho ho ho

[13:02:43] A: good!

[13:02:55] A: santa?

(pause)

[13:19:35] A: something

[13:20:42] A: something else

Chatlog from user B:

[13:02:22] A: p

[13:02:32] B: ho ho ho

[13:02:55] A: santa?

[13:02:55] A: good!

(pause)

[13:20:30] A: something

[13:21:38] A: something else

Looking at the XML console, the sent message appears instantly at user A, but the console of user B stays empty until the message arrives in the chat window. This might be helpful or not regarding where the console is hooked up.

Both computers are using gpg (GnuPG) 1.4.2 and the same version of gajim (debian unstable 0.9.1-3).

The problem disappears completely if both gajim clients are connected to the server without SSL encryption. (psi has ssl/tls enabled, so this should not be a server problem)

If only one client is connected using SSL connection, the messages sent with this one are most probably (not really sure) also delayed.

[nk]

can you reproduce this behaviour with SVN?

[Wollschaf]

I'm sorry, but I forgot about the issue. I sadly do not have the time to

compile gajim with fresh SVN code.

I still have the problem with 0.10.1-6 from debian unstable, but only using jabber.ccc.de as server. It works perfectly with two jabber.org accounts. Sending to a jabber.org account using jabber.ccc.de as server also introduces the lag, while the other way round the connection is flawless.

So one might assume that the server is the problem - but packet logging with ethereal revealed that the delayed packets are not sent for a long while, and then operation resumes to normal (send packet -> 1-9 sec delay (traffic, decryption) -> receive message). As if finally a timeout occurs...

sending client -> receiving client; Synchronized clocks. Slight lag due to high traffic... huge lag because of the mysterious bug, marked with (!)

[14:54:36] sender: 1 [14:54:36] sender: 1

[14:54:37] sender: 2 [14:54:38] sender: 2

[14:54:38] sender: 3 [14:54:40] sender: 3

[14:54:38] sender: 4 [14:54:42] sender: 4

[14:54:40] sender: 5 [14:55:26] sender: 5 (!)

[14:55:36] sender: 6 [14:55:43] sender: 6

[14:55:36] sender: 7 [14:55:45] sender: 7

[14:55:36] sender: 8 [14:55:56] sender: 8

[14:55:53] sender: 9 [14:55:58] sender: 9

[14:55:54] sender: a [14:56:00] sender: a

[14:55:54] sender: b [14:56:22] sender: b (!)

In one case, typing notification triggered sending of the last missing message. In another case - not. Sending of the missing message is always triggered by sending another one, or sometimes two.

So... I'll keep an eye on this from now on. Sorry again. And thanks.

[nk]

no need to compile anything to use svn. just see downloads on gajim.org on

how to use svn

[Wollschaf]

Silly me. Of course, it's python. No hassle installing many libs, devs,

and fighting with the linker. Certainly a better way to fix bugs.

The problem persists with 0.10.1.3 from SVN today.

[anonymous]

The problem still persists with 0.11.1 (debian testing).

I think the ticket should not be closed therefore?

It doesn't occur with all servers though, I can confirm the problem using the jabber.ccc.de server, while using the mabber.de server I can't see any relevant delay. Maybe it is connected with the jabber server used (jabberd1.4 in the case of jabber.ccc.de, ejabberd in the case of mabber.de)?

I can see delays up to several minutes even.

One more remark, I am *not* using SSL.

thanks florian

[steve-e]

It doesn't occur with all servers though, I can confirm the problem using the jabber.ccc.de server, while using the mabber.de server I can't see any relevant delay. Maybe it is connected with the jabber server used (jabberd1.4 in the case of jabber.ccc.de, ejabberd in the case of mabber.de)?

I don't see anything gajim can do wrong here. Jabber.ccc.de has not been that reliable those days.