Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #12504
Closed
Open
Created Jul 01, 2014 by Isis Lovecruft@isis

Create BridgeDB config setting for which Pluggable Transports are supported

Currently, there is a list of the "currently supported Pluggable Transports" in bridgedb.strings. This module attribute can be used to change which PTs are listed in the dropdown menu on https://bridges.torproject.org/options, as well as in the list sent out in email responses. Changing this will easily change what both UIs display, however, there still are some sections of BridgeDB's code where the supported PTs are hardcoded.

We need to:

  1. Identify where and why PT method names are hardcoded.
  2. Create a config setting in bridgedb.conf to set this list globally (in the UI, and in code logic).
  3. Get rid of all the hardcoded PT method names in (1) and replace them with the thing from (2).
Assignee
Assign to
Time tracking