Opened 8 months ago

Last modified 3 months ago

#24393 new defect

Clients should check IPv4 and IPv6 subnets when choosing circuit paths

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

Description

Currently, clients only check IPv4 subnets when choosing circuit paths. But they should probably also check IPv6 subnets as well.

Once #15518 is fixed, we can make them check both.

Child Tickets

TicketStatusOwnerSummaryComponent
#15518assignedSamdneyTor considers routers in the same IPv6 /16 to be "in the same subnet"Core Tor/Tor

Change History (5)

comment:1 Changed 8 months ago by teor

Parent ID: #7193#24403

#7193 also depends on this.

comment:2 Changed 6 months ago by teor

Milestone: Tor: unspecifiedTor: 0.3.4.x-final

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

comment:3 Changed 4 months ago by nickm

Keywords: 034-triage-20180328 added

comment:4 Changed 4 months ago by nickm

Keywords: 034-removed-20180328 added

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

comment:5 Changed 3 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.

Note: See TracTickets for help on using tickets.