[OTR-dev] OTR support for Gajim

Chris Ballinger chrisballinger at gmail.com
Thu Aug 18 13:45:31 EDT 2011


I implemented libotr for iPhone in under a day so I'd say it's not
particularly difficult.

https://github.com/chrisballinger/Off-the-Record-iOS/blob/master/Off%20the%20Record/OTRCodec.m

Basically you just need to implement that structure OtrlMessageAppOps and
all of those static functions need to be modified to work with how Gajim
does its stuff. Then just follow the readme for how to encode/decodes
messages, or look at the bottom of my file for how I did it.

On Thu, Aug 18, 2011 at 8:16 AM, Aaron Toponce <aaron.toponce at gmail.com>wrote:

> According to http://trac.gajim.org/wiki/OTR, the OTR API is crap, and
> implementing it into a project seems to be somewhat of a chore. I would
> like to see OTR support built into Gajim, but it appears to be a deadend.
> As the article states, you can see the code he ripped out from the commit
> message here: http://trac.gajim.org/changeset/ef7496ee5eb2/.
>
> Thankfully, it appears that Gajim will be supporting a plugin architecture,
> and an OTR plugin looks likely. See http://gajim-otr.pentabarf.de/.
> Currently, the only end-to-end encryption for Gajim, is using OpenPGP keys,
> which digitally sign every message, which isn't optimal.
>
> So, is OTR v4 being worked on? Is the claim that the current API sucks
> accurate? It seems other projects, such as Pidgin and Bitlbee have
> implemented OTR just fine, so maybe the core devs either have issues with
> the Gajim code, or the OTR code that was written just sucked.
>
> Thoughts?
>
> --
> . o .   o . o   . . o   o . .   . o .
> . . o   . o o   o . o   . o o   . . o
> o o o   . o .   . o o   o o .   o o o
>
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20110818/5ba81d81/attachment.html>


More information about the OTR-dev mailing list