Re: [tor-bugs] #25784 [Core Tor/Tor]: Misleading error message when asking for IPv6 in a network with no IPv6-capable exits

[Tor Bug Tracker & Wiki]

#25784: Misleading error message when asking for IPv6 in a network with no
IPv6-capable exits
--+
 Reporter:  pastly|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.2.9.1-alpha
 Severity:  Minor | Resolution:
 Keywords:  easy, ipv6|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * version:  Tor: 0.3.2.10 => Tor: 0.2.9.1-alpha
 * milestone:  Tor: 0.3.5.x-final => Tor: unspecified


Comment:

 Replying to [ticket:25784 pastly]:
 > As you can see, I'm talking myself out of this being a bug and it just
 being me screwing things up for myself. I was encouraged to make a ticket
 though, so here we are.

 We should fix this error message eventually.

 I think it was introduced back in 0.2.8 or 0.2.9 with IPv6Only and
 OnionTrafficOnly.

 > If rewriting the error message is the solution, maybe after fixing the
 "fulfil" typo

 It's a variant spelling, which we tolerate in Tor. You can thank the
 British Empire for your confusion. Or people who insist there is one right
 way to spell.

 > we should add "It's also possible we couldn't find any exits supporting
 the IP version you want to use"

 +1

 > I'm picking 0.3.5.x-final just because I've been told you have to pick a
 milestone or else your tickets generally fall through the cracks. :)

 The new rule is that everything goes in "Tor: unspecified".

 If you want to rescue a ticket from "Tor: unspecified", take ownership of
 it, do it, and assign it to the current release.

 (Paid staff don't spend more than half a day on things until we all agree
 it's on the roadmap. But volunteers can do whatever we like.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25784 [Core Tor/Tor]: Misleading error message when asking for IPv6 in a network with no IPv6-capable exits

[Tor Bug Tracker & Wiki]

#25784: Misleading error message when asking for IPv6 in a network with no
IPv6-capable exits
--+
 Reporter:  pastly|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.2.10
 Severity:  Minor |   Keywords:  easy, ipv6
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I created a small test Tor network. 3 authorities, 7 relays, 3 exits.
 Great.

 I didn't set `IPv6Exit 1` on any of the exits.

 I had a client try to request `::1` over this Tor network on a hand
 crafted circuit (it makes sense to ask an exit to connect to localhost
 when this is all local ... trust me). I got the following confusing error
 message on the client.

 > [warn] I'm about to ask a node for a connection that I am telling it to
 fulfil with neither IPv4 nor IPv6. That's not going to work. Did you
 perhaps ask for an IPv6 address on an IPv4Only port, or vice versa?

 I think it's important to point out (again) that I was hand crafting these
 circuits and was not considering IPv6 support. That said, I don't know
 what Tor would do if I let it make the circuit for me and it couldn't find
 an IPv6-supporting exit.

 As you can see, I'm talking myself out of this being a bug and it just
 being me screwing things up for myself. I was encouraged to make a ticket
 though, so here we are.

 If rewriting the error message is the solution, maybe after fixing the
 "fulfil" typo, we should add "It's also possible we couldn't find any
 exits supporting the IP version you want to use"

 I'm picking 0.3.5.x-final just because I've been told you have to pick a
 milestone or else your tickets generally fall through the cracks. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs