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

[Tor Bug Tracker & Wiki]

#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 gk):

 Replying to [comment:3 mcs]:
 > Replying to [comment:2 gk]:
 > > I think the best solution would be to not transmit %OS_VERSION% over
 the wire at all but rather to compute it locally and compare that locally
 with a notice the update.xml contains. Looking at it we could certainly
 encode something in the `buildID` we don't need or we could even make up a
 new element, say `<obsolete/>`, specifying the respective OS and version +
 architecture. But probably there are even better ideas on how to do this
 which I am currently missing.
 >
 > I like your idea.  Since we will already be returning different XML
 update manifests for different OS platforms, we can probably just add
 something like this:
 >
 >   minSupportedOSVersion="10.7"
 >
 > (e.g., for Mac OS when we drop support for 10.6),  Kathy and I will try
 to make the necessary changes next week.

 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"...

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