| 2014-05-02 22:01:09 |
William Budington |
bug |
|
|
added bug |
| 2014-06-18 13:27:24 |
Launchpad Janitor |
bitlbee (Ubuntu): status |
New |
Confirmed |
|
| 2014-10-28 07:54:57 |
dx |
bitlbee (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2014-10-28 08:47:03 |
Jelmer Vernooij |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-10-28 14:31:35 |
dx |
description |
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 |
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]
- 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 |
|
| 2014-10-28 14:39:28 |
dx |
description |
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]
- 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 |
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]
- 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 |
|
| 2014-10-28 14:54:16 |
dx |
description |
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]
- 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 |
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]
- 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 / service
- Start irc client, for example irssi
- Connect to bitlbee with "/connect localhost"
- Switch to the autojoined "&bitlbee" channel
- Type "add jabber username@domain password" with appropriate login details (a jabber account in any server will do, gmail also works)
- Type "account jabber on" to connect.
And then either:
1.1 Find an offline contact (type "blist all" in &bitlbee to show them)
1.2 Open a PM window with that contact ("/query contact_name")
1.3 Send two messages to that contact
1.4 Watch it crash (will appear as a disconnection from the server in the irc client)
2.1 Do "set otr_policy manual"
2.2 Open a PM window with an online contact.
2.2 Send at least one message.
3.3 Ask the contact (using some other communication method) if they received anything.
3.1 Keep otr_policy in the default value (or reset it with "set otr_policy opportunistic")
3.2 Send at least two messages to an online contact
3.3 Ask the contact (using some other communication method) if both of them were received.
4.1 Ask the contact (using some other communication method) to send a "/me"-equivalent action
4.2 Watch it crash
[Regression Potential]
- Highly unlikely if only otr.c patches are backported - otr.c is already very very broken.
- Possible but still unlikely if a full upload of 3.2.2-2 is done (the current stable release, which is mostly 3.2.1+otr4-1 with fixes)
- Highly unlikely if the OTR plugin is removed (see below)
- 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]
- Backporting individual otr-related patches is one way to solve the issue, although not my preferred one.
- 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.
- 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 |
|
| 2015-09-29 05:33:06 |
dx |
bug watch added |
|
http://bugs.bitlbee.org/bitlbee/ticket/1109 |
|
| 2015-09-29 05:33:06 |
dx |
bug watch added |
|
http://bugs.bitlbee.org/bitlbee/ticket/1110 |
|
| 2015-09-29 05:33:06 |
dx |
attachment added |
|
Backport bitlbee-plugin-otr bug fixes to 3.2.1+otr4-1 https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/1315550/+attachment/4478209/+files/bitlbee-3.2.1%2Botr4-1-otr-bugfixes.patch |
|
| 2015-09-29 05:33:56 |
dx |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2015-09-29 05:41:35 |
Adam Conrad |
bug task added |
|
bitlbee (Ubuntu Trusty) |
|
| 2015-10-19 06:57:46 |
Timo Jyrinki |
bitlbee (Ubuntu Trusty): status |
New |
In Progress |
|
| 2015-10-19 11:59:03 |
Timo Jyrinki |
bug |
|
|
added subscriber Timo Jyrinki |
| 2015-10-21 16:25:29 |
Chris J Arges |
bitlbee (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-10-21 16:25:31 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-10-21 16:25:36 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2015-10-21 16:25:44 |
Chris J Arges |
tags |
encryption otr |
encryption otr verification-needed |
|
| 2015-10-21 16:30:54 |
Chris J Arges |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2015-10-21 16:58:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/bitlbee |
|
| 2015-10-30 04:14:31 |
Mathew Hodson |
bitlbee (Ubuntu): importance |
Undecided |
Medium |
|
| 2015-10-30 04:14:33 |
Mathew Hodson |
bitlbee (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2015-11-04 19:35:44 |
Timo Jyrinki |
tags |
encryption otr verification-needed |
encryption otr verification-done |
|
| 2015-11-11 20:58:04 |
Launchpad Janitor |
bitlbee (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-11-11 20:58:09 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-11-12 17:41:28 |
Shane Synan |
bug |
|
|
added subscriber Shane Synan |
