Opened 2 years ago

Last modified 15 months ago

#27722 new defect

rust protover doesn't canonicalize adjacent and overlapping ranges

Reported by: cyberpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: rust, protover, 035-deferred-20190115, 041-proposed, 033-unreached-backport
Cc: nickm Actual Points:
Parent ID: #27190 Points:
Reviewer: Sponsor:


protover.c accepts both "Foo=1-3,4-5" and "Foo=1-3,2-5" and then canonicalizes them into "Foo=1-5" with contract_protocol_list(). Rust rejects the 2nd one as malformed.

Child Tickets

Change History (5)

comment:1 Changed 22 months ago by nickm

Keywords: 035-deferred-20190115 041-proposed added
Milestone: Tor: 0.3.5.x-finalTor: unspecified

Marking a number of 0.3.5 tickets as possible, maybe even a good idea, for later. Possibly backportable, some of them. But not currently things to do as part of 0.3.5 stabilization.

comment:2 Changed 20 months ago by teor

Keywords: 033-backport removed

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

comment:3 Changed 20 months ago by teor

Keywords: 033-backport-unreached added

Hmm, I guess they should still get 033-backport-unreached

comment:4 Changed 17 months ago by nickm

Keywords: 034-backport removed

Removing 034-backport from all open tickets: 034 has reached EOL.

comment:5 Changed 15 months ago by teor

Keywords: 033-unreached-backport added; 033-backport-unreached removed

Fix 033-unreached-backport spelling.

Note: See TracTickets for help on using tickets.