Opened 7 years ago

Closed 7 years ago

#6934 closed defect (fixed)

TBB-stable should contain 0.2.3.x

Reported by: rransom Owned by: erinn
Priority: High Milestone:
Component: Applications/Tor bundles/installation Version:
Severity: Keywords:
Cc: mikeperry, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor 0.2.3.x-rc is a stable release branch, and it will never receive ‘enough’ testing as part of a TBB because the TBB alpha series includes (a) Vidalia 0.3.x-alpha with its bloated Marble network map that no one should use or trust, and (b) versions of Firefox that should not be trusted for anonymity (even when they haven't been remotely exploitable for months). Tor 0.2.2.x is no longer receiving fixes for ‘minor’ security bugs such as #6710 (and TBB still makes it easy for users to turn themselves into bridges and relays). It's time to start shipping a safe version of Tor with a tolerably safe browser.

Child Tickets

Change History (2)

comment:1 Changed 7 years ago by erinn

Cc: mikeperry nickm added

TBB alpha does not have Vidalia alpha in it and stable TBBs aren't going to ship with 0.2.3.x until either it is released as a stable series or nickm tells me they should. Can you elaborate more on the Firefox complaint though? Does this mean you think the Firefox ESR releases are safer than the normal Firefox stable releases? If so, why?

Adding nickm and mikeperry to Cc.

comment:2 Changed 7 years ago by arma

Resolution: fixed
Status: newclosed

I think we're doing ok here, in that we have tor 0.2.3 with stable other-components in the alpha tbb.

The major remaining sticking point for calling tor 0.2.3 stable, and changing the stable tbb to use tor 0.2.3, is to make sure that the stable-vidalia we have in tbb-alpha doesn't have any show-stopping bugs (like not handling microdescriptors right). But that's not this bug.

Note: See TracTickets for help on using tickets.