Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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.

  • Legacy
  • TracTrac
  • Issues
  • #1104

Closed (moved)
Open
Opened Sep 24, 2009 by Sebastian Hahn@sebastian

We should have an option that disables connections to bridge auth and fallback

] I meant UpdateBridgesFromAuthority 0 ] Or does that not prevent connections to the Authority? ] If it doesn't, I think we should have some config option that means "never talk to the bridge authority". Else it's easier to spot that someone is trying to use Tor arma] right. we've never really solved that part of the problem. i figured i'd do it once somebody blocks it. arma] whether tor decides to go to the bridge authority directly depends on a couple of things.

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#1104