#21346: Clients with NoIPv4Traffic should only choose IPv6-supporting Exits -------------------------------------------------+------------------------- Reporter: teor | Owner: neel Type: defect | Status: | assigned Priority: Medium | Milestone: Tor: | unspecified Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: ipv6, 031-deferred-20170425, | Actual Points: 032-unreached | Parent ID: #21311 | Points: 0.5 Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by teor): Replying to [comment:9 neel]: > Thank you again. > > Sorry to ask you one more time, but I have a few more questions: > > 1. Is `connection_ap_attach_pending()` the stream attachment code? Yes. > 2. Would it be okay to use `node_has_ipv6_addr()` or `node_has_ipv6_orport()` along with checking for `!ap_conn->entry_cfg.ipv4_traffic` to see if a node has IPv6 support? If so, would `node_has_ipv6_addr()` suffice or would I need `node_has_ipv6_orport()`? No, these functions check for an IPv6 ORPort. You need to check for an IPv6 exit policy that allows exiting to the port in the request. When building a circuit, use exit_policy_is_general_exit(), but add a "sa_family_t family" argument to it for IPv6. It should look a bit like policy_is_reject_star(). When attaching a stream, use compare_tor_addr_to_node_policy() with a NULL address for a domain, or the IPv6 address. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21346#comment:10> 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