Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #28627
Closed (moved) (moved)
Open
Issue created Nov 27, 2018 by Trac@tracbot

[torsocks] AAAA replies from tor not handled

As reported on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895903:

Tor now returns IPv6 addresses when hostnames are resolved, but torsocks cannot handle this case.

To reproduce:

torsocks -d nc v6.ipv6-test.com 80

'' This makes it tricky to use torsocks on domains that will resolve to an AAAA only causing the program to abort with no error message.''

Indeed, in

int socks5_send_resolve_request(const char *hostname, struct connection *conn)

I see:

/* By default we use IPv4 address. */
msg.atyp = SOCKS5_ATYP_DOMAIN;

(I've tested it from the command line with torsocks 2.3.0, and it does not work, while using TBB it works fine.)

I'm not sure if this issue is also related to this bug: https://trac.torproject.org/projects/tor/ticket/25295

Trac:
Username: u

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking