[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #18904 [Applications/Tor Browser]: Mac OS: meek-http-helper profile not updated

#18904: Mac OS: meek-http-helper profile not updated
--------------------------------------------+------------------------------
 Reporter:  mcs                             |          Owner:  mcs
     Type:  defect                          |         Status:
 Priority:  Medium                          |  needs_information
Component:  Applications/Tor Browser        |      Milestone:
 Severity:  Normal                          |        Version:
 Keywords:  ff45-esr, TorBrowserTeam201605  |     Resolution:
Parent ID:                                  |  Actual Points:
 Reviewer:                                  |         Points:
                                            |        Sponsor:
--------------------------------------------+------------------------------
Changes (by mcs):

 * status:  assigned => needs_information


Comment:

 Kathy and I have been thinking about how best to handle this. We need some
 kind of "versioning" for the meek-http-helper browser profile, but we
 would rather not add a manual maintenance step to the release process
 (e.g., "If any of the files that will be part of the meek-http-helper
 browser profile have changed since the last release, change the contents
 of meek-profile-version.txt").

 gk, dcf: What do you think of the idea of generating a checksum and
 storing that in a file? Here is how it could work:
 1. During the Tor Browser gitian-based bundling step, we would generate a
 checksum that uniquely identifies the contents of the meek-http-helper
 profile template and place it in the template, e.g., as meek-profile-
 sha256sum.txt. We could do this by creating a sorted sha256sums file and
 then calculating a checksum of that file.
 2. The meek-client-torbrowser code would compare the contents of the meek-
 profile-sha256sum.txt that is part of the browser bundle (the template)
 with the profile that is in use (the user's copy). If the contents are
 different, the meek-client-torbrowser code would remove the entire profile
 and create a new one from the template.

 Comments?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18904#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs