#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:
 Severity:  Minor         |     Resolution:
 Keywords:  easy, ipv6    |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
Changes (by teor):

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


 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

 > 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"


 > 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: <https://trac.torproject.org/projects/tor/ticket/25784#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to