Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
bridgestrap
bridgestrap
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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
  • Anti-censorship
  • bridgestrapbridgestrap
  • Issues
  • #3

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

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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None