Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #28706
Closed
Open
Issue created Dec 03, 2018 by juga@jugaMaintainer

Maybe implement resolving destination domain using Tor's RESOLVE and ADDRMAP events

In legacy/trac#28458 (moved) the domain of the destination was being resolved locally to check whether and exit policy allows to exit to the IP, which had 2 problems:

  • in the case that the destination is a CDN, the IP resolved locally would be different to the IP resolved by the exit.
  • it was returning the first IP found, without checking whether the scanner supported IPv6. The correct way would be to resolve the domain via Tor itself using RESOLVE and ADDRMAP events with that exit. While there are not too many circuits that fails (because the policy doesn't allow to exit to the destination IP), this is not a priority
Assignee
Assign to
Time tracking