Opened 5 years ago

Last modified 3 years ago

#18674 new defect

Tor rejects [::]/8 and [::]/127 explicitly, but the latter is sometimes eliminated

Reported by: Sebastian Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Trivial Keywords: tor-relay exit-policy ipv6
Cc: teor Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I suspect the rules that try to eliminate duplicates are at play here. I figured this out while trying to add tests for some getinfo exit-policy queries.

Child Tickets

Change History (6)

comment:1 Changed 5 years ago by nickm

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

ISTR we talked about this for a long time on IRC. I don't see this as must-fix for 0.2.8, or must-fix at all. Please comment if you disagree.

comment:2 Changed 4 years ago by teor

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

Milestone renamed

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

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:5 Changed 3 years ago by nickm

Keywords: tor-relay exit-policy ipv6 added
Priority: MediumLow
Severity: NormalTrivial

comment:6 Changed 3 years ago by teor

I suggest we make sure they are eliminated as much as possible. There's no reason to have them in the same list, when there are no intervening IPv6 allow rules.

Note: See TracTickets for help on using tickets.