Skip to content
This repository has been archived by the owner on Jul 3, 2020. It is now read-only.

OTRv4? v3? Hmm. #4

Closed
n8fr8 opened this issue Dec 5, 2012 · 4 comments
Closed

OTRv4? v3? Hmm. #4

n8fr8 opened this issue Dec 5, 2012 · 4 comments

Comments

@n8fr8
Copy link

n8fr8 commented Dec 5, 2012

Nathan from Guardian here... we have users starting to request OTRv4 support:

https://twitter.com/Dymaxion/status/276050214878576641

but they may mean "libotr4" which is OTRv3

Any thoughts on how far we are from parity with the latest update of libotr that with otr4j?

@gpolitis
Copy link

gpolitis commented Jan 7, 2013

It's on the todo list, but I'm not sure when it will be done. I was hoping to find some spare time during the holidays to dig a little deeper into this, but that unfortunately that didn't happen.

@devrandom
Copy link

I started on the TLV 8 (extra symmetric key) part of OTRv3 support for otr4j. I have a draft of the API here:

devrandom/ChatSecureAndroid@f4635c2

Any ideas about way to better structure the API? In particular, I wonder if there is a better way to get out the extra data without passing in a list.

@devrandom
Copy link

I've upgraded the API and wrote a draft implementation of the input side:

guardianproject/ChatSecureAndroid#191

@gpolitis
Copy link

The otrV3 branch (adds V3 and fragmentation support) has been merged into master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants