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

Closed (moved)
Open
Opened Jan 28, 2015 by weasel (Peter Palfrader)@weasel

tor-resolve should better handle .onion addresses

In https://bugs.debian.org/776454, Russell Coker asks for a slight modification of tor-resolve's behavior wrt .onion addresses:

$ tor-resolve zp7zwyd5t3aju57m.onion Jan 28 17:38:42.055 [warn] Got SOCKS5 status response '4': host is unreachable Jan 28 17:38:42.055 [warn] zp7zwyd5t3aju57m.onion is a hidden service; those don't have IP addresses. To connect to a hidden service, you need to send the hostname to Tor; we suggest an application that uses SOCKS 4a.

The above output is informative, but not particularly useful for the case of scripts.

https://www.howtoforge.com/anonymous-ssh-sessions-with-tor

The above web site gives an example of how to use tor which btraks when used with .onion addresses. One way to solve this would be for tor-resolve to give "zp7zwyd5t3aju57m.onion" on stdout and the warning message on stderr, that would inform users but work in the desired manner with scripts.

A small change to tor-resolve will make it work better with existing documented practice and make it work with future use for .onion addresses in cases where admins only care about non-onion addresses now.

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