List Tor Browser Bundle versions in the consensus

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.

changed milestone to %TorBrowserBundle 2.2.x-stable

added component::applications/tor bundles/installation milestone::TorBrowserBundle 2.2.x-stable owner::erinn priority::high resolution::wontfix status::closed type::defect labels

Trac:
Cc: N/A to nickm

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.

Trac:
Cc: nickm to nickm, chiiph

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

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

Trac:
Summary: Tor Browser Bundle needs a way to learn when it's out of date to List Tor Browser Bundle versions in the consensus
Priority: normal to major
Milestone: N/A to TorBrowserBundle 2.2.x-stable
Type: enhancement to defect

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 (moved) is the way to go.

Trac:
Resolution: N/A to wontfix
Status: new to closed

closed