Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #10183

Closed (moved)
(moved)
Open
Created Nov 18, 2013 by Roger Dingledine@arma

Get bridgedb back to using bulkexitlist

bridgedb uses bulkexitlist to recognize when a user is coming from a Tor exit, so it's harder to enumerate the address-based pool just by coming through Tor.

But we have varied over the past year which list we use, since the main bulkexitlist was flaky.

When I was last the maintainer for bridgedb, I had a cron running on moria1 to generate an exitlist, and I had bridgedb fetch it via wget periodically. Are we still doing that, or did we move to something else? Now that the new check seems more stable, we should consider moving back to the main source.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking