Bug #2737
OTR not initing with Bitlbee/IRSSI client app
Status: | Closed | Start date: | 12/09/2013 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | devrandom | % Done: | 0% | |
Category: | - | |||
Target version: | v14 - Armadillo's Agram | |||
Component: |
Description
Here is the OTR message that is causing exception
?OTR,00001,00002,?OTR:AAIRAAAAEJT/231tzn3qQy+2ScTZqOkAAAHSSchTTkePKwLHguy8b7RQSIBRD+Oufv9O6mDg68YPGt8S/gECDBjPiCjT33wRYvZnrSJb39OZqKOkxFa1zqzcSpBSQJQl5psVkb/Z2onQKTh5lylU+VGDiNG7pWe+xjQVrrz+MTUH9LDZ9GYGCZMiOCEs5iQmUiM9uIblHGYge6nGOEkPmiqQveJVqjMhgnYLqeBBqC3ApukqWAd7n6jVd6X6cWMdEGEK8GZNpyRqnvVciQ2MfuJd2Q7bIgVtAB68uOwd0j7nRuSeFrAtJCvwbj5Fcvcsc+RxC5qlwFM3CBcMat0jZKM9kQRn4n0zYbMULyLVU9MWHvwvRsMLDpl9,
Associated revisions
OTR fragment assembly
fixes #2737
History
#1 Updated by n8fr8 about 4 years ago
I think we aren't handling the "fragment" feature correctly:
Fragmentation
Some networks may have a maximum message size that is too small to contain an encoded OTR message. In that event, the sender may choose to split the message into a number of fragments. This section describes the format of the fragments. All OTR version 2 clients must be able to assemble received fragments, but performing fragmentation on outgoing messages is optional.
Transmitting Fragments
If you have information about the maximum size of message you are able to send (the different IM networks have different limits), you can fragment an encoded OTR message as follows:
Start with the OTR message as you would normally transmit it. For example, a Data Message would start with "?OTR:AAED" and end with ".".
Break it up into sufficiently small pieces. Let the number of pieces be (n), and the pieces be piece1,piece2,...,piece[n].
Transmit (n) messages with the following (printf-like) structure (as k runs from 1 to n inclusive):
"?OTR,%hu,%hu,%s," , k , n , piece[k]
#2 Updated by n8fr8 about 4 years ago
- Target version changed from v13 - October Oooya to v14 - Armadillo's Agram
#3 Updated by devrandom almost 4 years ago
- Status changed from New to Resolved
Applied in changeset chatsecureandroid|commit:1e8178fe38207a49361ab9d9e5e50dfa8efe6a4f.
#4 Updated by n8fr8 over 2 years ago
- Status changed from Resolved to Closed