#22053: Failed to launch Tor Browser: Server provided a downgrade: '7.0a3' ----------------------------------------------+------------------------- Reporter: Digitalcourage | Owner: yawning Type: defect | Status: closed Priority: Medium | Milestone: Component: Applications/Tor Browser Sandbox | Version: Severity: Normal | Resolution: wontfix Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ----------------------------------------------+------------------------- Changes (by yawning):
* status: needs_information => closed * resolution: => wontfix Comment: > Yes, I had installed the hardened TBB. As for my sandboxed-tor-browser, I think the version is 0.0.3, but I can check it only later (give me 12 hours). Per the 0.0.5 release notes: {{{ * (< 0.0.4) Will not correctly transition to the alpha channel. Sorry. The bundle may or may not be rendered non-functional by the transition update, I don't have a good way to test the Tor Browser auto update infrastructure with updates that haven't been released yet. * (>= 0.0.4) When `sandboxed-tor-browser` is launched, it will detect the `hardened` bundle and force a reinstall. This will eradicate the existing bundle directory obliterating user customization, bookmarks, and downloads (unless the download directory is overridden). A warning dialog box is displayed prior to booting the user back to the installation screen. }}} > Frankly, I had assumed it would update itself, too. That's something for future improvement perhaps, if I can figure out a good way to do it. Closing, since there's nothing I can do about "there is code that assumes that channels never go away deployed, that people try to use to update a deprecated bundle". -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22053#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs