Opened 3 years ago

Last modified 21 months ago

#18721 new enhancement

Define accessors for connection_t's address fields

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: refactoring tor-relay tor-client technical-debt intro
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

In #18460, we noted that connection_t's address fields are confusing.

we should open a ticket to add comments explaining the real story of what's going on above in the code, and that we also open a ticket to define a few accessor functions to provide tor_addr_t and string representations of the final target address, proxy-or-final, or whatever other things we actually need.

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by teor

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

Milestone renamed

comment:2 Changed 2 years 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:3 Changed 22 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:4 Changed 21 months ago by nickm

Keywords: refactoring tor-relay tor-client technical-debt intro added
Note: See TracTickets for help on using tickets.