Bug #7283

Use upstream solution for Tor Launcher: Set ClientTransportPlugin according to the bridge entries

Added by anonym 2014-05-26 06:11:43 . Updated 2015-05-12 18:46:16 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Tor configuration
Target version:
Tails_1.4
Start date:
2014-05-26
Due date:
% Done:

100%

Feature Branch:
feature/8925-tor-0.2.6
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Tor Launcher
Deliverable for:

Description

Commit 75f76d4 in our Tor Launcher Git repo is part of our delta against upstream.

Upstream has chosen a different approach than us: https://trac.torproject.org/projects/tor/ticket/11512

We should wait until this have been implemented by upstream, but if it takes too long we may consider writing a patch.

Subtasks

Related issues

Related to Tails - Feature #7087: Do not bundle Tor Launcher in the main Tails Git repository Resolved 2014-04-15
Blocked by Tails - Feature #7934: Upgrade to Tor 0.2.6.x Resolved 2014-09-22

History

#1 Updated by anonym 2014-06-12 17:08:14

Bad news, see upstream bug.

They decided to go with backporting a Tor 0.2.6.x feature (current implementation of Tor ticket Feature #8402 into the Tor 0.2.4.22 they ship in TBB 3.6.2. I doubt moving the delta from Tor Launcher to Tor is a wise decision for us, maintenance wise, so we may have to live with our current Tor Launcher delta until Tor 0.2.6.x goes stable.

#2 Updated by intrigeri 2014-06-13 03:48:02

> They decided to go with backporting a Tor 0.2.6.x feature (current implementation of
> Tor ticket Feature #8402 into the Tor
> 0.2.4.22 they ship in TBB 3.6.2.

Wow. I’d be surprised that something that TBB will ship anyway could not be sneaked into 0.2.5. I suggest asking Nick about it, if the TBB team hasn’t already tried.

> I doubt moving the delta from Tor Launcher to Tor is a wise decision for us, maintenance wise, so we may have to live with our current Tor Launcher delta until Tor 0.2.6.x goes stable.

That’s acceptable, since it gives us a good enough warranty that we can drop the delta at some point.

#3 Updated by intrigeri 2014-09-22 11:31:46

#4 Updated by BitingBird 2015-01-07 16:30:36

  • Affected tool set to Tor Launcher

#5 Updated by intrigeri 2015-02-28 09:25:00

  • Subject changed from Tor Launcher: Set ClientTransportPlugin according to the bridge entries to Use upstream solution for Tor Launcher: Set ClientTransportPlugin according to the bridge entries
  • Type of work changed from Wait to Code

(The fact this ticket is blocked by Tor 0.2.6 is already expressed by a ticket relationship.)

#6 Updated by Tails 2015-03-11 00:59:43

  • Status changed from Confirmed to In Progress

Applied in changeset commit:30f8c35fdf2d38c0065d7ccc4f5707de7fa17504.

#7 Updated by anonym 2015-03-11 01:17:17

  • Target version changed from Hole in the Roof to Tails_1.3.2
  • % Done changed from 0 to 50
  • Feature Branch set to feature/8925-tor-0.2.6

#8 Updated by intrigeri 2015-03-15 10:36:08

  • Target version changed from Tails_1.3.2 to Tails_1.4

I doubt that we’ll want to upgrade to Tor 0.2.6 in a point-release => postponing to Tails 1.4.

#9 Updated by intrigeri 2015-03-16 10:30:35

  • related to Feature #7087: Do not bundle Tor Launcher in the main Tails Git repository added

#10 Updated by Tails 2015-03-17 11:11:07

Applied in changeset commit:3710b2c913c883e2be2adfdd5c4b99c87e3ed5af.

#11 Updated by anonym 2015-04-29 11:48:08

  • Assignee deleted (anonym)
  • QA Check set to Ready for QA

#12 Updated by intrigeri 2015-05-01 10:00:12

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:e88f3b27b295e745eb31af186fc48879bc4a1ca0.

#13 Updated by BitingBird 2015-05-01 10:13:10

  • QA Check changed from Ready for QA to Pass

#14 Updated by BitingBird 2015-05-12 18:46:16

  • Status changed from Fix committed to Resolved