Skip to content
GitLab
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 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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
  • #12872
Closed
Open
Issue created Aug 15, 2014 by Matthew Finkel@sysrqb

Know within which country a bridge is located

This has many uses, but in particular this will allow us to do legacy/trac#12843 (moved). I suggest we not bother rewriting large portions of the code to satisfy this and simply add another attribute to the Bridge class specifying its country. As soon as we have this information we can do more smart things with it (and those can be other smarter tickets).

For simplicity, we can only rely on the the ORPort netblock. This is what the BA checks. In the future, when ORPorts are disableable, we'll need to rely on the addresses in the transport lines, but that can be dealt with later, I think.

Assignee
Assign to
Time tracking