Feature #5479

Bridge support

Added by Tails 2013-07-18 07:41:40 . Updated 2018-04-08 16:47:24 .

Status:
Resolved
Priority:
Normal
Assignee:
anonym
Category:
Tor configuration
Target version:
Start date:
2013-07-25
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Starter:
0
Affected tool:
Deliverable for:

Description


Subtasks

Feature #6192: bridge dialog at Vidalia startup Duplicate

0

Feature #5920: Tor bridges support: complete phase one Resolved

100

Feature #6839: Tor bridges support: complete phase two Resolved anonym

100


Related issues

Related to Tails - Bug #6986: Repeated prompt for simple vs. complex Tor configuration Duplicate 2014-03-29
Related to Tails - Bug #6985: Allows configuring unworkable combination of outbound port filtering + obfsproxy Resolved 2014-03-28
Related to Tails - Bug #6893: Skip the first screen of Tor Launcher Duplicate 2014-03-10

History

#1 Updated by intrigeri 2013-07-19 01:54:23

  • Type of work set to Code

Type of work: Code

#2 Updated by intrigeri 2013-12-08 14:33:12

  • Assignee set to anonym
  • Starter set to No

#3 Updated by intrigeri 2014-03-29 09:20:30

  • related to Bug #6986: Repeated prompt for simple vs. complex Tor configuration added

#4 Updated by intrigeri 2014-03-29 09:22:10

  • related to Bug #6985: Allows configuring unworkable combination of outbound port filtering + obfsproxy added

#5 Updated by intrigeri 2014-03-30 14:51:05

  • related to Bug #6893: Skip the first screen of Tor Launcher added

#6 Updated by BitingBird 2014-04-27 12:28:36

  • Subject changed from bridge support to Bridge support
  • Status changed from Confirmed to In Progress

#7 Updated by anonym 2014-04-29 11:29:26

  • Target version changed from Tails_1.0 to Tails_1.1

#8 Updated by intrigeri 2014-05-28 10:56:35

  • Category set to Tor configuration

#9 Updated by anonym 2014-06-12 16:38:18

  • Target version deleted (Tails_1.1)

Dropping target version, Feature #5920 is the goal of 1.1 w.r.t. bridges support.

#10 Updated by BitingBird 2015-08-25 13:57:16

  • Status changed from In Progress to Resolved

Marking as resolved, since all children tickets are. If it’s wrong, please reopen and clarify the next thing to do :)