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

Re: [tor-bugs] #13379 [Tor Browser]: Sign our MAR files

#13379: Sign our MAR files
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  mcs
  mikeperry              |     Status:  needs_review
         Type:  defect   |  Milestone:
     Priority:  major    |    Version:
    Component:  Tor      |   Keywords:  tbb-security, TorBrowserTeam201411R
  Browser                |  Parent ID:
   Resolution:           |
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by mcs):

 Replying to [comment:17 boklm]:
 > The change to add the --createIncrementalMARs command line to
 update_responses looks good.
 >
 > The other changes introduce a single makefile rule to generate the
 incremental mar files and sign them. I am wondering if we should separate
 the incremental mar files generation, and the signature, to allow a
 process like this:
 > - build tor-browser
 > - generate incremental mars
 > - upload sha256sums.incrementals.txt of unsigned mar files
 > - check that sha256sums.txt and sha256sums.incrementals.txt are matching
 > - sign the mar files, update responses xml files and upload

 It would be simple to keep 'incrementals' as a separate Make target.  The
 reason I put everything in one script was to make it less likely that
 things would happen in the wrong order.

 gk or mikeperry:  What do you think?  What will the release process look
 like once we need to sign the MAR files?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13379#comment:19>
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