Feature #6840: Upstream our Tor Launcher changes

Feature #6840

Upstream our Tor Launcher changes

Added by intrigeri 2014-03-04 23:44:08 . Updated 2015-05-12 18:46:43 .

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:

Affected tool:

Tor Launcher

Deliverable for:

Description

“The Tor Browser will open after a Tor network connection is established”
etc.

Setting type of work to code for now, since this likely will imply improving our code first.

Subtasks

Bug #7282: Tor Launcher: Don't relabel finish button when not owning Tor.

Rejected

anonym

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

Resolved

100

Related issues

Related to Tails - ~~Feature #5343~~: Tor Launcher	Resolved
Blocked by Tails - ~~Feature #7934~~: Upgrade to Tor 0.2.6.x	Resolved	2014-09-22

History

#1 Updated by intrigeri 2014-03-05 01:44:12

Target version set to Tails_1.0

#2 Updated by intrigeri 2014-03-06 16:38:35

Parent task changed from ~~Feature #6839~~ to ~~Feature #5920~~

#3 Updated by anonym 2014-04-14 15:05:00

Status changed from Confirmed to In Progress

The progress of this process is currently tracked in the following upstream tickets, some with patches:

Tor Launcher’s bridge settings prompt is worded confusingly when there’s no provided bridges (del>Bug #11482
Improve how Tor Launcher handles incomplete translation (del>Bug #11483
Tor Launcher’s bridge settings page doesn’t show the help button when there’s no provided bridges (del>Feature #11484
Tor Launcher should set ClientTransportPlugin according to the bridge list (del>Bug #11512

#4 Updated by intrigeri 2014-04-15 14:04:45

% Done changed from 0 to 10

I’m glad to see progress in this area, congrats! (And thanks to the TBB team for being so open to our suggestions, as it seems to me.)

Given this definitely won’t be done for 1.0, how about formally postponing this to the 1.1 milestone? I propose we turn it into a “Hole in the Roof” if it’s not completed for 1.1, to make it clear that it really should not stay this way much forever. What do you think?

#5 Updated by BitingBird 2014-04-27 12:33:38

https://trac.torproject.org/projects/tor/ticket/11482 is fixed
https://trac.torproject.org/projects/tor/ticket/11483 is fixed
https://trac.torproject.org/projects/tor/ticket/11484 is fixed

https://trac.torproject.org/projects/tor/ticket/11512 seems more complicated.

#6 Updated by anonym 2014-04-29 11:29:33

Target version changed from Tails_1.0 to Tails_1.1

#7 Updated by BitingBird 2014-05-14 14:56:10

Type of work changed from Code to Upstream

#8 Updated by intrigeri 2014-05-15 02:26:12

This task has already been postponed twice. If it is not completed in time for 1.1, I propose we turn it into a Hole in the Roof.

#9 Updated by anonym 2014-05-26 06:16:03

Target version changed from Tails_1.1 to Hole in the Roof

intrigeri wrote:
> This task has already been postponed twice. If it is not completed in time for 1.1, I propose we turn it into a Hole in the Roof.

Agreed. The reason nothing happening for a while is primarily that I’ve been waiting for ~~Bug #7283~~ to be solved in upstream.

#10 Updated by intrigeri 2014-06-10 10:56:16

Category set to Tor configuration

#11 Updated by intrigeri 2014-06-10 10:57:00

Parent task deleted (~~~~Feature #5920~~~~)

#12 Updated by intrigeri 2014-06-10 10:58:01

Parent task set to ~~Feature #6839~~

#13 Updated by intrigeri 2014-09-22 11:34:08

Type of work changed from Upstream to Code

My understanding is that the only open subtask is blocked by us waiting for Tor 0.2.6. anonym, may you please have a look at the upstream..ours log and confirm?

If that’s indeed the case, then I think this ticket doesn’t need to be a hole in the roof anymore. Otherwise, maybe we’re missing a subtask or more.