Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
    • A
      Anti-censorship
  • Pluggable Transports
  • trac
  • Issues
  • #29296

Closed
Open
Opened Feb 01, 2019 by Cecylia Bocovich@cohoshOwner

Look into alternatives for distributing bridge info to clients

The traditional way of distributing bridge information is to give bridge IP/connection information through BridgeDB and add that information to the Tor Browser configuration.

Snowflake and meek handle "bridge" information differently at the client side, and we might like to consider a broader application of the Snowflake/broker style of distributing bridges. To do so, we should look into what changes we need to make at the client side to make this distribution easier.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/anti-censorship/pluggable-transports/trac#29296