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
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #18114

Closed (moved)
Open
Created Jan 20, 2016 by teor@teor

Warn when ReachableAddresses restricts connections to relays chosen by others

Tor clients which use one-hop paths to access relays chosen by other clients can't use ReachableAddresses (or similar options) or ClientUseIPv4 0 (#17840 (moved)). If they did, this would deny them access to some relays, potentially impairing functionality or performance.

This affects the following Tor modes:

  • Tor2Web - Introduction Points
  • RSOS - Rendezvous Points

For directory, guard, and bridge connections, clients choose or are configured with accessible relays based on ReachableAddresses / ClientUseIPv4/ClientUseIPv6.

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