Opened 4 years ago

Last modified 3 years ago

#21000 new enhancement

Make chutney select different options depending on the tor version

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:


Some versions of tor have bugs that chutney needs to work around, for example, #20996 requires tor versions <= to set UseMicrodescriptors 0 when setting ClientUseIPv4 0.

But we want to test newer versions without this workaround, so we need some kind of versioning feature. (Or test alternatives, where we report more than just pass or failure - but I think that's a different ticket.)

Child Tickets

Change History (5)

comment:1 Changed 4 years ago by teor

Parent ID: #21001

comment:2 Changed 3 years ago by teor

I've already implemented a few conditional substitutions, like the one for ServerDNSResolvConfFile and nearby code. It wouldn't be hard to make them depend on the tor version.

comment:3 Changed 3 years ago by teor

Parent ID: #21001

One way to do this for #21001 is to create new md-networks in chutney, and make newer versions of tor use them.

comment:4 Changed 3 years ago by teor

Owner: teor deleted
Status: newassigned

Disowning tickets I don't intend to work on in the next 6 months.

comment:5 Changed 3 years ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

Note: See TracTickets for help on using tickets.