** Description changed: The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems in the OTR negotiation phase. These problems have been fixed in the nightlies for bitlbee. Relevant tickets are: http://bugs.bitlbee.org/bitlbee/ticket/1109 http://bugs.bitlbee.org/bitlbee/ticket/1110 - - [Impact] + [Impact] - BitlBee crashes when sending messages to contacts with no previous otr context (offline contacts, or contacts that weren't talked to before) - BitlBee silently drops all unmodified messages when opportunistic otr is enabled, which is the default mode - Receiving a /me from a remote contact crashes BitlBee. [Test Case] - Start bitlbee daemon, connect with irc client, type "add jabber username@domain password" with appropriate login details And then either: - Find an offline contact, send two messages, watch it crash (will appear as a disconnection from the server in the irc client) - Do "set otr_policy manual" and send messages to an online contact. Ask the contact if they received anything. - Keep otr_policy in the default value (or reset it with "set otr_policy opportunistic"), and send two messages to an online contact. Ask the contact if both of them were received. - Ask the contact to send a "/me"-equivalent action, watch it crash + + [Regression Potential] + + - Unlikely. The patches apply mostly to otr.c, which is already very + very broken. + + - These have been tested and worked perfectly for all the users that + complained about it so far in our channel (roughly 50 of them), who were + told to switch to the nightly apt repo, and this turned out to be more + stable. + + [Other Info] + + - A full upload of 3.2.2-2 would be the easiest way to solve it. It's + stable, and the otr patches in 3.2.1+otr4-1 are the biggest part of it. + + - Backporting individual otr-related patches is also possible, if you + don't really like that thing. + + - Removing the OTR plugin package will also get rid of the issues, + probably the safest option, but with a functionality loss. This will + require changing the version string to not say "otr4", as this is + misleading - without changing that, it will not be an effective way to + solve our tech support headache in #bitlbee
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315550 Title: Current 14.04 bitlbee build using broken OTR (fixed in nightlies) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/1315550/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
