gajim with otr encryption

Monday, April 21. 2008, 02:21
gajim with otrIn the instant messaging world, encryption is a bit of a problem. There is no single standard that all clients share, mostly two methods of encryption are out there: pgp over jabber (as defined in the xmpp standard) and otr.

Most clients only support either otr (pidgin, adium) or pgp (gajim, psi), for a long time I was looking for a solution where both methods work. psi has otr-patches, but they didn't work when I tried them. kopete also has an otr-plugin, but I've not tested that yet.

Today I found that there is an otr-branch of gajim, which is my everyday client, so this would be great. As you can see on the picture, it seems to work on a connection with an ICQ user using pidgin.

I've created some ebuilds in my overlay (the code is stored in bazaar, I've copied the bzr eclass from the desktop effects overlay):
svn co https://svn.hboeck.de/overlay

Trackbacks


Warning: Illegal string offset 'properties' in /home/hanno/websites/blog.hboeck.de/htdocs/include/plugin_api.inc.php on line 1634

Warning: Illegal string offset 'properties' in /home/hanno/websites/blog.hboeck.de/htdocs/include/plugin_api.inc.php on line 1634
OTR in Gajim
Der Jabber-Client Gajim, welcher momentan ausschlißelich GPG-Unterstützung bietet, wird vorraussichtlich ab Version 0.12 OTR-Unterstützung anbieten. Ich freue mich dabei über die zahlreiche Nachfage zur verschlüsselten Kommunikation. Da dies jedoch noch e
Weblog: Fabian Fingerle
Tracked: Jun 05, 00:28
OTR in Gajim schon Heute nutzen
Bereits vor einiger Zeit habe ich berichtet, dass es OTR erst ab dem release 0.12 in gajim geben wird. Ob 0.11.5 oder 0.12 als nächstes stabil released wird ist noch nicht bekannt, jedoch ist in der aktuellen Subversion-Entwicklerfassung gajims OTR unters
Weblog: Fabian Fingerle
Tracked: Jun 05, 00:45

Comments
Display comments as (Linear | Threaded)

Gajim-trunk already supports Encrypted Sessions which is the standardized way to go.
#1 Astro (Link) on 2008-04-21 02:58
Is this a reason not to implement OTR as an additional encryption protocol ?
OTR is necessary to communicate with users on other networks over transports.
It can also be used to communicate with users of other clients which don't support esessions.
There probably won't be one encryption protocol which will be implemented by all clients in the near future. Meanwhile, the more encryption protocols gajim supports the more of its users will be able to communicate securely.
#1.1 Matz on 2008-04-21 04:03
kopete supports gpg encryption out of the box, and there is an otr plugin (net-im/kopete-otr) in the tree
#2 chithanh on 2008-04-21 07:42
Hi!

thanks for using my software. I'm currently preparing a official release of pyotr (which are the python bindings for the OTR library, used in gajim/otr). I'll leave a note here when they're out, you can also subscribe to the RSS feed of the pyotr project.

When the gajim people implemented their plugin interface I'll provide a more clean solution for hijacking their code (and I'll probably release it officially), I guess my current way is quite hackish. Suggestions are welcome, just hit me via mail or jabber :)

Thanks,
Kjell
#3 Kjell Braden (Link) on 2008-04-21 16:59
Hi again!

I released pyotr 0.1 on pyotr.pentabarf.de.

Note that the newest bzr revision (8042) for gajim/otr fixed an issue with ?OTR:[lot of garbage here] shown when talking to purple clients.
#4 Kjell Braden (Link) on 2008-04-22 22:59
The SRC_URI changed, so that the 0.1 ebuild does not work.

It also seems that the OTR-Support is merged into gajim-trunk now.
http://trac.gajim.org/changeset/9602

Anyway. Thanks for the ebuild!
#4.1 anonym on 2008-05-11 16:00
otr support was removed from gajim-trunk:

http://trac.gajim.org/browser/trunk/src/common/gajim.py?rev=9771
#4.1.1 arno nuehm on 2008-06-15 17:19
I know, I've changed the ebuild back to use the bazaar-branch from kjell for now.
#4.1.1.1 Hanno (Link) on 2008-06-15 23:55
last time i tried kopete's pgp-support wasn't working with gajim (but i didn't debug it), kopete's otr worked with gajim-otr, though.

mcabber has otr and pgp.

+++ neingeist
#5 neingeist (Link) on 2008-04-23 17:40
Hi. The ebuild from your overlay is not working anymore. The Bazaar-repo seems to be moved.
#6 anonymous on 2009-02-26 22:57
Fixed, svn up should give you the new ebuild.
#6.1 Hanno (Link) on 2009-03-01 13:23
In Yours ebuild net-im/gajim-9999.ebuild You have

net-im/pyotr but right is net-im/python-otr

http://gajim-otr.pentabarf.de/example-pythonotr.html

Could You include in Yours Overlay this ebuild and improve it if is needed, it works for me.

https://bugs.gentoo.org/show_bug.cgi?id=300634

That this ebuid works, I must patch allways Yours ebuild for Gajim-9999 with

gajim_python-otr
#!/bin/bash



sed -i 's/net-im\/pyotr/net-im\/python-otr/' \

/var/paludis/repositories/hanno/net-im/gajim/gajim-9999.ebuild

Thanks in advance
#7 Smart on 2010-01-13 17:26
Gajim seems to have switched to depend on pygtk >=2.16 (the ebuild depends on >-2.12):

checking for PYGTK... configure: error: Package requirements (gtk+-2.0 >= 2.16.0 pygtk-2.0 >= 2.16.0) were not met:

Requested 'pygtk-2.0 >= 2.16.0' but version of PyGTK is 2.14.1

[...]

Thanks for your efforts.
#8 anonymous on 2010-03-13 12:35
Hi. Me again :-)
update-eix complains for a while that the gajim-9999 uses NEED_PYTHON which will be removed in 1.5 months.

Could you add PYTHON_DEPEND instead to the ebuild? The correct value should be PYTHON_DEPEND="2:2.5". Thanks!
#9 anonymous on 2010-08-09 21:17
There is python-related deprecation-warning for gajim-9999 again:

Deprecation Warning: Usage of python_mod_optimize() in packages not supporting installation
for multiple Python ABIs in EAPI =3 and call python_mod_optimize() with paths having appropriate syntax.
The ebuild needs to be fixed. Please report a bug, if it has not been already reported.
Compilation and optimization of Python modules for CPython 2.7 ...

Thanks.
#10 anonymous on 2011-08-12 20:59

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.