Opened 7 years ago

Last modified 2 years ago

#4904 new defect

tor-resolve falsely says can't resolve if answer is 127.0.0.1

Reported by: arma Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: dns tor-client tor-resolve needs-insight
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

$ tor-resolve localhost.seul.org
Jan 14 18:52:47.884 [warn] Got SOCKS5 status response '4': host is unreachable

In my logs I have

Jan 14 18:52:47.884 [info] connection_edge_process_relay_cell_not_open(): Got a resolve with answer 127.0.0.1.  Rejecting.

Trying to connect to 127.0.0.1 over Tor is a poor move. But knowing that a given address resolves to it? I can imagine situations where you'd want that info, rather than being told that the address doesn't resolve.

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by arma

This isn't a straightforward bug. If the user is using tor-resolve as a wrapper in e.g. torsocks, with plans to connect to the address it responds, we want to say it failed. If the user is actually wanting to know what the dns server says, we want to answer correctly. Hm.

comment:2 Changed 7 years ago by nickm

Keywords: dns added
Milestone: Tor: unspecified

Unless this is actually hurting something, I'd like to hold off on this until we do a big DNS revision; we have a lot of DNS issues to solve, and this is far from the most important.

comment:3 Changed 7 years ago by nickm

Keywords: tor-client added

comment:4 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:5 Changed 2 years ago by nickm

Keywords: tor-resolve needs-insight added
Priority: MediumLow
Severity: Normal
Note: See TracTickets for help on using tickets.