Opened 3 years ago

Closed 3 years ago

#20911 closed defect (wontfix)

Why is 0.2.6.10 not a recommended version?

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

Description

There is no 0.2.6 series in recommended versions, but we recommend an 0.2.4, 0.2.5, and 0.2.7.

I've had a fallback operator report that they've patched their relay against TROVE-2016-10-001.

Does this have something to do with debian releases, or is it just a mistake?

Child Tickets

Change History (3)

comment:1 Changed 3 years ago by dgoulet

As far as I can tell, 026 has been removed because of Debian.

Commit b7418c4692e99c854e94e99b23fc20e09bd35286 in dirauth-conf repository removes 026 entirely with the commit message:

Trim versions to what we support in Debian

The Tor LTS pad we worked on few weeks ago describes 026 like so:

===== 0.2.6

 Released 24 March 2015
 Haven't updated since 12 July 2015.

  Debian: Not in debian.
  Ubuntu: It was in Wily Werewolf, which finished support in July 2016.

comment:2 Changed 3 years ago by Sebastian

We don't know of a single distribution that ships an updated 0.2.6.x package. We added 0.2.7 back in because OpenSUSE is on it.

comment:3 Changed 3 years ago by teor

Resolution: wontfix
Status: newclosed

Ok, I asked because an operator patched 0.2.6.10 for themselves.
This doesn't justify recommending that version.

Note: See TracTickets for help on using tickets.