Opened 13 months ago

Last modified 4 months ago

#31908 new enhancement

Unify meaning of routerset NULL and routerset "" to avoid recurrence of #31495

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

Description

From #31611:

Avoid configuration types where NULL and "" mean different things. We would have to add a new routerset type meaning "all routers", (maybe, "*"?) and have that be the default for EntryNodes. [We probably could not make NULL mean the same as "" for all cases, since there are lots of string-valued configuration types.]

Child Tickets

Change History (4)

comment:1 Changed 9 months ago by nickm

Keywords: 043-deferred added

All 0.4.3.x tickets without 043-must, 043-should, or 043-can are about to be deferred.

comment:2 Changed 9 months ago by nickm

Milestone: Tor: 0.4.3.x-finalTor: 0.4.4.x-final

comment:3 Changed 9 months ago by gaba

Sponsor: Sponsor31-can

No more sponsor 31. All this tickets remained open after sponsor 31 ended.

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