Opened 8 years ago

Closed 8 years ago

#2937 closed defect (wontfix)

List Tor Browser Bundle versions in the consensus

Reported by: arma Owned by: erinn
Priority: High Milestone: TorBrowserBundle 2.2.x-stable
Component: Applications/Tor bundles/installation Version:
Severity: Keywords:
Cc: nickm, chiiph Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Jake wanted to stick the recommended TBB versions in the Tor consensus, and have Vidalia learn to query Tor about the recommended TBB versions, learn how to know what its current TBB version is, and pop up something for the user if they need to upgrade.

Another option is to ship a simple Thandy with TBB and set up a simple thandy repository that has the TBB versions in it.

How close are we to the thandy solution? If not close, we should probably do some workaround in the mean time.

Child Tickets

Change History (5)

comment:1 Changed 8 years ago by ioerror

Cc: nickm added

comment:2 Changed 8 years ago by ioerror

Cc: chiiph added

Sebastian made a spec change that should clarify that we won't add TBB versions to a few specific fields; there may be already existing areas where we can shove an extra few bytes.

comment:3 Changed 8 years ago by rransom

We will also need to implement #2285 in order to not completely hose users of the current TBBs.

comment:4 Changed 8 years ago by mikeperry

Milestone: TorBrowserBundle 2.2.x-stable
Priority: normalmajor
Summary: Tor Browser Bundle needs a way to learn when it's out of dateList Tor Browser Bundle versions in the consensus
Type: enhancementdefect

I think we need to do one of either this ticket, or #2285 for TBB 2.2.x. We should decide which one is better. See also #3504.

comment:5 Changed 8 years ago by mikeperry

Resolution: wontfix
Status: newclosed

Just spoke with Roger. This option is way harder than going the check.tp.o route. It would require a dirauth upgrade to a new consensus method and voting process. #2285 is the way to go.

Note: See TracTickets for help on using tickets.