Opened 19 months ago

Last modified 6 weeks ago

#24604 new defect

Decorate IPv6 addresses in connection_t->address to avoid ambiguity

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, tor-relay, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: #24403 Points: 2
Reviewer: Sponsor:


Currently, connection_t->address can be in one of three formats:

  • hostname:
  • IPv4:
  • IPv6: 2003::0001

Tor often uses this address with a port like this:

  • hostname:
  • IPv4:
  • IPv6: 2003::0001:1234

The IPv6 case is ambiguous, and we should fix it.

One way of fixing it is to provide a flag if address is an IPv6 literal, and a function to format address and port. (Unfortunately, we can't always decorate IPv6 addresses, because that would cause bugs in other code and in controllers.)

Then we would need to go through every instance of conn->address and find the ones that use a port. This may also require a spec update, like #24603.

Child Tickets

Change History (6)

comment:1 Changed 18 months ago by teor

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

The 0.3.3 freeze deadline has passed, all these children of #24403 belong in 0.3.4

comment:2 Changed 16 months ago by nickm

Keywords: 034-triage-20180328 added

comment:3 Changed 16 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:4 Changed 15 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:5 Changed 6 weeks ago by gaba

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

comment:6 Changed 6 weeks ago by gaba

Sponsor: SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Note: See TracTickets for help on using tickets.