[jitsi-dev] OTR support for transport channels with limited sized messages?


#1

Hi,

I've been trying out OTR for the IRC implementation and it currently
does not work :-(. Cause for this is the limited message size that IRC
allows, because of the implementation specification. It says to use a
buffer of 512 bytes of memory for a command/message buffer. Because of
this some larger OTR messages won't make it through in one piece.

According to the OTR spec it is possible to split up OTR messages in
several smaller portions. Receiving partial message must be supported,
but creating them is optional, IIRC.

Is there a mechanism by which I can tell OTR to use at most x
bytes/chars for a message? (For this particular protocol that is.)

Danny


#2

Hello Danny,

The OTR protocol mandates that all OTR version 2 and 3 clients must be
able to assemble received fragments, but performing fragmentation on
outgoing messages is optional.

Jitsi uses the otr4j library that, while it complies with the spec in
the sense that it assembles fragments, it does not offer outgoing
message fragmentation. It would be nice to have that but it's not in our
immediate plans list for the time being.

Cheers,
George

ยทยทยท

On Sun, Aug 10, 2014 at 11:40:02PM +0200, Danny van Heumen wrote:

Hi,

I've been trying out OTR for the IRC implementation and it currently
does not work :-(. Cause for this is the limited message size that IRC
allows, because of the implementation specification. It says to use a
buffer of 512 bytes of memory for a command/message buffer. Because of
this some larger OTR messages won't make it through in one piece.

According to the OTR spec it is possible to split up OTR messages in
several smaller portions. Receiving partial message must be supported,
but creating them is optional, IIRC.

Is there a mechanism by which I can tell OTR to use at most x
bytes/chars for a message? (For this particular protocol that is.)

Danny

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev