[jitsi-dev] What needs to be fixed in OTR?


#1

I do not know if it is really relevant to the new stable version email
chain. But it was mentioned that OTR deserves a fix.

Currently I am working with the OTR code. What is it that needs a fix? It
might be worth me doing now.

Thanks,
Mike Schliep


#2

Hi Mike,

There was mention of an issue with state management by the Jitsi plugin
"OTR". It manages OTR state, as does otr4j. As I understand in case of
(or nearing) timeout Jitsi may deviate from otr4j's internal state. This
should be fixed largely - if not fully - at the Jitsi OTR plugin side.
(It's somewhere at the top of the release thread. The explanation is in
an email by George Politis.)

George is most familiar with this issue.

As for me, I've been bothered by a design choice I made while I was
implementing outgoing fragmentation support. I've wanted to fix it but
didn't get to it - and then you started the gOTR implementation :stuck_out_tongue:

I've made the necessary modifications in a separate branch. Have a quick
look at these changes, if they cause a lot of trouble for you, let me know.

* Jitsi: https://github.com/cobratbq/jitsi/compare/otr-simplify
* otr4j: https://github.com/cobratbq/otr4j/compare/otr-simplify

I'll do a quick review tomorrow (or maybe the day after) and then I'll
commit them.

Kind regards,
Danny

···

On 25-11-14 18:53, Michael Schliep wrote:

I do not know if it is really relevant to the new stable version email
chain. But it was mentioned that OTR deserves a fix.

Currently I am working with the OTR code. What is it that needs a fix?
It might be worth me doing now.

Thanks,
Mike Schliep

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


#3

Hello Mike,

I'm aware of one problem that's been described here:

http://lists.jitsi.org/pipermail/dev/2014-November/022544.html

The problem is that sometimes the Jitsi OTR plugin loses track of the
otr4j engine internal state. My plan was to remove the additional state
tracking from the OTR plugin and instead rely entirely on the otr4j
engine internal state. I'd be more than happy to provide help and review
any patches.

Regards,
George

···

On 25/11/2014 18:53, Michael Schliep wrote:

I do not know if it is really relevant to the new stable version email
chain. But it was mentioned that OTR deserves a fix.

Currently I am working with the OTR code. What is it that needs a fix?
It might be worth me doing now.

Thanks,
Mike Schliep

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