Opened 6 months ago

Last modified 2 months ago

#33383 new defect

Do we actually need the orconn_ext_or_id_map?

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 044-deferred
Cc: phw, cohosh Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

So apparently we have this structure, orconn_ext_or_id_map, where we map from ext_orport identifiers to the corresponding orconn objects ... but nothing in our code (outside of the unit tests) actually looks anything up in this map.

I can't remember -- is this a feature that we were planning to do something with if transports needed it in the future? Or is this just dead code?

Found while working on #33368.

Child Tickets

Change History (1)

comment:1 Changed 2 months ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Note: See TracTickets for help on using tickets.