[tbb-bugs] #13047 [Tor Browser]: Updater should not send Kernel and GTK version

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Sep 15 20:34:10 UTC 2014

#13047: Updater should not send Kernel and GTK version
     Reporter:  gk       |      Owner:  tbb-team
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Tor      |    Version:
  Browser                |   Keywords:  tbb-firefox-patch
   Resolution:           |  ,TorBrowserTeam201409
Actual Points:           |  Parent ID:
       Points:           |

Comment (by mcs):

 Replying to [comment:4 gk]:
 > I wonder how we should handle things if we want to drop support just for
 32bit systems. (See: https://lists.torproject.org/pipermail/tor-
 talk/2014-September/034728.html for my idea) That plan has IMO a bunch of
 advantages and not much disadvantages compared to the "Let's move to 10.7
 as minimum proposal"...

 I think we will be able to detect the difference because of the presence
 of the %BUILD_TARGET% component within our update URL (we do not plan to
 remove that component).  In TB 4.0a2 that component turns into this:
 I think it will turn into the following in a 64-bit build (we will need to
 test to be 100% sure):
 Then we just need to modify boklm's tb-update-response script to return a
 "end of life" XML response if _64 is missing.  In the simplest case, that
 can look like:
 <?xml version="1.0"?>
     <update unsupported="true" detailsURL="..." />
 The detailsURL should point to a helpful page that tells people they need
 to stop using Tor Browser on their outdated systems.

 Also worth noting: Google is apparently dropping their 32-bit Mac builds:
 (or rather, they are switching from 32 to 64 like we may do).

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13047#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

More information about the tbb-bugs mailing list