Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bridgestrap bridgestrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • bridgestrapbridgestrap
  • Issues
  • #3

Closed
Open
Created Oct 02, 2020 by Philipp Winter@phwReporter

Be more efficient when testing bridges

There's room to make bridgestrap more efficient when it tests bridge lines. Roger helpfully suggested the following:

  • Reuse Tor's data directory. (Bridgestrap currently deletes it after a test).
  • Consider running a single Tor client and use SETCONF to test different bridges.
  • If we can fetch the bridge's descriptor, we know that 1) we can establish a handshake and 2) the bridge knows its address. If we do a full bootstrap instead, we also learn if the bridge can properly fetch and serve directory information too.
Assignee
Assign to
Time tracking