#23818: Make v3 single onion services retry failed connections with a 3-hop path -------------------------------------------------+------------------------- Reporter: teor | Owner: teor Type: defect | Status: | needs_review Priority: Medium | Milestone: Tor: | 0.4.2.x-final Component: Core Tor/Tor | Version: Tor: | 0.2.9.3-alpha Severity: Normal | Resolution: Keywords: consider-backport-after-0421-alpha, | Actual Points: 0.2 029-backport-maybe-not, 035-backport, | 040-baclport, 041-backport, v3-onion-service- | feature-parity, prop224, tor-hs, single- | onion, ipv6, network-team-roadmap-august | Parent ID: #23493 | Points: 1 Reviewer: | Sponsor: | Sponsor27-must -------------------------------------------------+------------------------- Changes (by teor):
* status: assigned => needs_review * keywords: v3-onion-service-feature-parity, prop224, tor-hs, single-onion, ipv6, network-team-roadmap-august => consider-backport-after-0421-alpha, 029-backport-maybe-not, 035-backport, 040-baclport, 041-backport, v3-onion-service-feature- parity, prop224, tor-hs, single-onion, ipv6, network-team-roadmap- august * version: => Tor: 0.2.9.3-alpha * actualpoints: => 0.2 Comment: It turns out that there is actually an identical bug in v2 and v3 onion services, from the original v2 implementation in 0.2.9.3-alpha. Here are the PRs for the fix: * 0.2.9: https://github.com/torproject/tor/pull/1255 * v2 fix * 0.3.5: https://github.com/torproject/tor/pull/1256 * v3 fix * master: https://github.com/torproject/tor/pull/1257 * comment fix I don't know how far we should backport this fix. It's a reachability fix. I think we should backport to 0.3.5, I'm not sure if we should worry about 0.2.9. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23818#comment:23> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs