Tails

#1 Updated by intrigeri 2017-08-30 13:02:47

• Assignee set to anonym

(It’s Foundations Team’s job, and generally anonym takes care of this area.)

#2 Updated by anonym 2017-08-30 19:31:09

• Target version changed from 2019 to Tails_3.3

We’ll have to migrate to the new Tor Launcher when XUL is deprecated in November.

#5 Updated by intrigeri 2017-11-06 15:48:40

• Target version changed from Tails_3.3 to Tails_3.5

I think we only have to do that in time for when we ship Tor Browser based on ESR 59 so there’s time.

#6 Updated by intrigeri 2017-12-07 12:59:01

• blocks Feature #13244: Core work 2017Q4: Foundations Team added

#7 Updated by anonym 2017-12-07 14:57:26

• Target version changed from Tails_3.5 to Tails_3.6

So I have asked when the stable Tor Browser series will switch to the WebExtension-based Tor Launcher, and got the answer that it “definitely won’t happen in the 7.x series (which means not before we switch to a new ESR)”. source

intrigeri wrote:
> I think we only have to do that in time for when we ship Tor Browser based on ESR 59 so there’s time.

Ack, and ESR 59 is released in March at the same time as Tails 3.6, so we at least got until then (but I wouldn’t be surprised if it’s pushed closer to when ESR 52 is EOL:ed, or even when 59.2 is released in the beginning of July).

#9 Updated by intrigeri 2017-12-12 08:33:18

• related to Feature #8243: Support meek bridges added

#10 Updated by anonym 2017-12-14 17:25:32

• Subject changed from Adapt to new Tor Launcher to Migrate to the Tor Launcher WebExtension

intrigeri wrote:
> I thought this ticket was not primarily about the move to WebExtensions, but rather about the new UI that fetches bridges for the user using meek, which is one of the top priorities of the Tor Browser team currently.

I’ll open a new ticket for that one: Feature #15064

> I don’t know what the release timeline for this change looks like; I doubt it makes it into the Tor Browser we’ll ship in Tails 3.5 but I suggest you check with them.

I’ll do this on Feature #15064.

#11 Updated by intrigeri 2018-01-01 16:45:43

• blocked by deleted (Feature #13244: Core work 2017Q4: Foundations Team)

#12 Updated by intrigeri 2018-01-01 16:45:45

• blocks Feature #13245: Core work 2018Q1: Foundations Team added

#14 Updated by iry 2018-01-03 16:08:56

• related to Feature #15144: Consider migrating from Tor Launcher to anon-connection-wizard added

#17 Updated by anonym 2018-02-02 14:27:34

• Target version changed from Tails_3.6 to Tails_3.7

If I attend Tor Dev (Rome, March 2018) I hope to get some clarifications. I’ll definitely no look at this ticket before that.

#19 Updated by intrigeri 2018-02-20 08:31:23

• Target version changed from Tails_3.7 to Tails_3.9
• Parent task set to Feature #15023

Hi anonym,

while reading the proposed plan for meek (Feature #8243#note-28) I’ve looked for a ticket about supporting moat and ended up here.

anonym wrote:
> intrigeri wrote:
> > I thought this ticket was not primarily about the move to WebExtensions, but rather about the new UI that fetches bridges for the user using meek, which is one of the top priorities of the Tor Browser team currently.
>
> I’ll open a new ticket for that one: Feature #15064
>
> > I don’t know what the release timeline for this change looks like; I doubt it makes it into the Tor Browser we’ll ship in Tails 3.5 but I suggest you check with them.
>
> I’ll do this on Feature #15064.

Looks like the confusion is back. Feature #15064 was repurposed to a subset of what it was meant to be and we’re back to square one: we have no ticket that tracks moat support => created Feature #15331.

This very ticket is solely about the migration away from XUL, which should happen with the move to Firefox ESR60, so I’m reparenting this ticket. Our plan is to work on this in July and August.

#20 Updated by intrigeri 2018-02-20 08:36:31

• blocked by deleted (Feature #13245: Core work 2018Q1: Foundations Team)

#21 Updated by intrigeri 2018-02-20 08:36:35

• blocks Feature #15334: Core work 2018Q3: Foundations Team added

#22 Updated by intrigeri 2018-03-22 07:20:59

• Subject changed from Migrate to the Tor Launcher WebExtension to Migrate to Tor Launcher compatible with Firefox ESR60

The Tor Browser team has no clear plan wrt. how to do this yet. One option is to turn their extensions into “system add-ons” that would be allowed to keep using APIs that are not available anymore to regular add-ons.

#23 Updated by intrigeri 2018-04-27 10:22:01

• Description updated

(Added link to upstream ticket.)

#24 Updated by intrigeri 2018-06-26 17:22:38

• Assignee changed from anonym to intrigeri

We’ll decide on Feature #15531 how we’ll handle this.

#25 Updated by intrigeri 2018-06-27 09:44:57

• Priority changed from Normal to High

#26 Updated by intrigeri 2018-07-01 11:47:31

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 10
• Feature Branch set to feature/15023-tor-browser-8

Tor Launcher seems to work just fine, when tested manually, on our topic branch. Next step: make the relevant test scenarios pass. And then I’ll reassign to sajolida for updating the doc if needed.

#29 Updated by intrigeri 2018-07-03 16:16:07

• related to Bug #15709: Deal with Tor Launcher being integrated into Tor Browser 9.0 and Firefox 68esr possibly removing support for XUL/XPCOM extensions added

#30 Updated by intrigeri 2018-07-03 16:17:03

• Status changed from In Progress to Resolved
• Assignee deleted (intrigeri)
• % Done changed from 10 to 100

intrigeri wrote:
> One the relevant test suite scenarios pass, we’ll be done here.

They do pass!

> I’ll file another ticket to handle things whenever the XUL extension becomes a thing of the past, which will happen sooner or later.