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
  • #17953

Closed (moved)
Open
Opened Dec 29, 2015 by teor@teor

Fallback to resolving localhost when interface searches fail

As described in #17949 (moved) & #17901 (moved), tor needs to know the loopback address.

We can fall back to resolving localhost on systems that don't return any loopback addresses when their interfaces are enumerated.

We need to check that the returned values are standard 127/8 or [::1]. This allows tor to work on non-127.0.0.1 loopback IPv4 systems, and IPv6-only systems, without the security issues inherent in trusting a possibly non-local resolver.

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#17953