Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 315
    • Issues 315
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #17953
Closed
Open
Created Dec 29, 2015 by teor@teor

Fallback to resolving localhost when interface searches fail

As described in legacy/trac#17949 (moved) & legacy/trac#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
Time tracking