Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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.

  • Legacy
  • TracTrac
  • Issues
  • #19838

Closed (moved)
Open
Opened Aug 05, 2016 by Isis Lovecruft@isis

Add dgoulet's obfs4 bridge to Tor Browser's default bridges

After the suggestion to remove #19714 (closed), dgoulet offered an obfs4 bridge as a default TB obfs4 bridge. The other obfs4 bridge operators have told me their bridges are saturated, so, provided that dgoulet's bridge can provide bandwidth similar to the others (see #18113 (moved) for how the round robining doesn't yet take bandwidth into account) then I propose we add it.

@dgoulet Could we get the bridge line for it privately (so that dcf can continue to run tests on how things are blocked)? Or, if you feel like it, you can patch it into Bundle-Data/PTConfigs/bridge_prefs.js in the tor-browser-bundle repo, and give one of the TB team the patch.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#19838