Opened 5 years ago

Last modified 9 months ago

#7961 new defect

Publish transports that bind on IPv6 addresses

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-bridge, pt, ipv6 anticensorship needs-spec refactor easy
Cc: Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:

Description

Currently, pt_get_extra_info_descriptor_string() uses router_pick_published_address() to retrieve our external IP address so that it can write it in our extra-info descriptor along with the TCP port that our transport listens on.

The bad news are that router_pick_published_address() only returns IPv4 addresses, and we will probably have to refactor it, or do something like this:
https://gitweb.torproject.org/tor.git/blob/ebf30613ea41bbed3340851e839da9b7db4351c5:/src/or/router.c#l1775
for IPv6 addresses.

Not sure if this can get in 0.2.4.x. I guess it depends on how quickly we implement it, and how complex the changes are going to be.

Child Tickets

Change History (6)

comment:1 Changed 4 years ago by nickm

Keywords: ipv6 added

comment:2 Changed 4 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:3 Changed 15 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 14 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 9 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 9 months ago by nickm

Keywords: anticensorship needs-spec refactor easy added
Points: 3
Severity: Normal
Note: See TracTickets for help on using tickets.