Bug 161581 - OTR contact authentication over MSN fails; Kopete splits message as too long
Summary: OTR contact authentication over MSN fails; Kopete splits message as too long
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Zanetti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-04 00:45 UTC by makosoft
Modified: 2008-06-24 08:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description makosoft 2008-05-04 00:45:38 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 4.2.3 (Gentoo 4.2.3 p1.0) 
OS:                Linux

When using the Kopete OTR plugin over MSN, authenticating a contact doesn't work. After both sides enter the shared secret, Kopete displays a message saying that the message is too long and asking if it should be split into two parts. No matter which choice is made, the authentication doesn't work. (It doesn't matter which side initiates the authentication.)

Kopete should let libotr split the message itself in this case, but looking at the Kopete OTR plugin this doesn't currently appear to be supported.

libotr version is 3.1.0, and Kopete was updated from svn trunk earlier today. The user I'm connecting to is using the Pidgin OTR plugin, version 3.1.0, on Pidgin 2.3.1.
Comment 1 Michael Zanetti 2008-06-15 21:54:29 UTC
fixed in rev. 820925
Comment 2 makosoft 2008-06-21 14:48:06 UTC
Hmmm... out of interest, why is the maximum message size set to 650 for Jabber? The libotr documentation seems to suggest that Jabber doesn't have a maximum message size and doesn't need fragmentation, as does the comment in otrlchatinterface.cpp:max_message_size. That's actually quite a low message size limit, too.
Comment 3 Michael Zanetti 2008-06-24 08:53:03 UTC
corrected. thanks!