Feature #15397

Document meek bridges

Added by sajolida 2018-03-12 15:52:34 . Updated 2020-04-06 18:07:56 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Tor configuration
Target version:
Start date:
2018-03-12
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Tor Launcher
Deliverable for:

Description

I’m seeing now that Feature #8243 will be in 3.6.

We should at least update the list of transports in https://tails.boum.org/doc/first_steps/startup_options/bridge_mode/.

Subtasks

Related issues

Blocked by Tails - Feature #8825: Provide default bridges Confirmed 2015-01-30

History

#1 Updated by sajolida 2018-03-12 15:55:04

  • Assignee changed from sajolida to anonym
  • QA Check set to Info Needed

anonym: I tried to used meek in Tails 3.6~rc1 but failed to understand how to do it.

From Tor Launcher in Tails, there is no drop down list from which to select meek.

I tried to input directly the configuration line for meek-amazon from https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-Data/PTConfigs/bridge_prefs.js but I get “missing pluggable transport - 0.0.2.0:2” when trying to connect.

#2 Updated by bertagaz 2018-03-12 16:26:03

sajolida wrote:
> anonym: I tried to used meek in Tails 3.6~rc1 but failed to understand how to do it.
>
> From Tor Launcher in Tails, there is no drop down list from which to select meek.

There’s a discussion on Feature #8825 about shipping the default bridges or not.

> I tried to input directly the configuration line for meek-amazon from https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-Data/PTConfigs/bridge_prefs.js but I get “missing pluggable transport - 0.0.2.0:2” when trying to connect.

We’re shipping the meek_lite PT variant, so when you’re configuring the bridge, you need to change the line taken from bridge_prefs.js and replace meek by meek_lite at the beginning of it, otherwise it won’t work.

#3 Updated by sajolida 2018-03-12 17:49:55

#4 Updated by sajolida 2018-03-12 17:50:41

  • Assignee changed from anonym to sajolida
  • Target version deleted (Tails_3.6)
  • QA Check deleted (Info Needed)

Actually, from the discussion on Feature #8825 we should wait until we provide default bridges in Tails.

Right now, if people want to use meek in Tails they have to copy the default bridges from the Tor Browser config and use the meek_lite transport:

meek_lite 0.0.2.0:2 B9E7141C594AF25699E0079C1F0146F409495296 url=https://d2cly7j4zqgua7.cloudfront.net/ front=a0.awsstatic.com
meek_lite 0.0.2.0:3 97700DFE9F483596DDA6264C4D7DF7641E1E39CE url=https://meek.azureedge.net/ front=ajax.aspnetcdn.com

#5 Updated by intrigeri 2018-03-14 10:55:18

> Actually, from the discussion on Feature #8825 we should wait until we provide default bridges in Tails.

Right :)

Sorry I was not clear enough in Feature #14680#note-5.

#6 Updated by sajolida 2018-03-15 16:59:24

You were clear! I just didn’t see it in time :(

#7 Updated by sajolida 2020-04-06 18:07:56

  • Assignee deleted (sajolida)