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
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #33299

Closed (moved)
Open
Opened Feb 13, 2020 by Philipp Winter@phw

Remove retired pluggable transports from BridgeDB

BridgeDB still hands out obfs3, ScrambleSuit, and FTE bridges. Tor Browser no longer supports FTE (see #29319 (moved)), so we should remove it. I suggest also removing obfs3 and ScrambleSuit because these transports don't offer anything that obfs4 doesn't already provide.

As of today, BridgeDB knows about 1,316 bridges. Among these:

  • 31 support FTE. 29 of these wouldn't be handed out because they also support obfs4 (see #28655 (moved)). The remaining two bridges run FTE/obfs3 and ScrambleSuit/obfs3/FTE.

  • 34 support ScrambleSuit. 32 of these also support obfs4 and only two don't. Instead, they run obfs3/ScrambleSuit and ScrambleSuit/obfs3/FTE.

  • 106 support obfs3. Only seven of these don't support obfs4.

Considering the above, I think it's safe to retire FTE, ScrambleSuit, and obfs3.

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