FS#23709 - [bitlbee] bitlbee is build with otr support compiled in. I think it shouldn't.

Attached to Project: Arch Linux
Opened by Michael Hellwig (the_eye) - Monday, 11 April 2011, 20:04 GMT
Last edited by Gaetan Bisson (vesath) - Friday, 29 April 2011, 15:34 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
bitlbee as it is in archlinux is compiled with otr (end-to-end encryption) support compiled in.
This is, IMO, not optimal as encryption should really happen at the actual end-points of communication, i.e. in the irc-client via e.g. libotr (irssi) or gaim-encryption or whatever.

Also, when one has otr already loaded in irssi and uses that irssi for bitlbee things get ugly because they can't seem to agree on who does the otr-ing ..

Also, bitlbee itself has otr support not compiled in as default, i.e. one explicitly has to enable it, which the arch package maintainer does.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Friday, 29 April 2011, 15:34 GMT
Reason for closing:  Upstream
Additional comments about closing:  The mis-interaction with irssi should be fixed upstream: for non-irssi users, OTR is a feature which should be kept in bitlbee; an AUR package disabling OTR in bitlbee can be used as a temporary fix.
Comment by Greg (dolby) - Monday, 11 April 2011, 20:12 GMT
Unless theres some compeling reason, i am against such a change. A 350kb library dependency is not enough of a reason.
Comment by Gaetan Bisson (vesath) - Monday, 11 April 2011, 20:23 GMT
I see compiling bitlbee against libotr as an additional feature.
Note that it can be disabled for particular connections with the "otr disconnect" command.
Also, many pieces of software only enable very few features by default, and we need to explicitly enable others.

Irssi might provide OTR, but other clients don't; inconsistencies between Irssi and BitlBee regarding OTR should be reported and solved upstream.
Comment by Michael Hellwig (the_eye) - Monday, 11 April 2011, 20:25 GMT
upstream basically said "well don't compile it with otr then" ..
guess an alternative would be to have a bitlbee-no_otr package in aur or something like that (i.e. I could create on aur what I do for myself anyway)
Comment by Gaetan Bisson (vesath) - Monday, 11 April 2011, 20:34 GMT
Regardless of whether we eventually decide to include or exclude OTR from BitlBee, the package with the opposite feature is very welcome to the AUR.
If you are already maintaining it for yourself, I am certain that others would benefit from your uploading it there.

Loading...