[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17662 [Quality Assurance and Testing]: Have a test to check that Tor Browser updater is working
#17662: Have a test to check that Tor Browser updater is working
------------------------------------------------+-----------------------
Reporter: boklm | Owner: boklm
Type: task | Status: new
Priority: Medium | Milestone:
Component: Quality Assurance and Testing | Version:
Severity: Normal | Resolution:
Keywords: tbb-testcase, TorBrowserTeam201512 | Actual Points:
Parent ID: | Points:
Sponsor: |
------------------------------------------------+-----------------------
Comment (by mcs):
Replying to [comment:3 boklm]:
> This might work for testing the updater in nightly builds where we
always use the same version. But for release builds it is more difficult
as it requires a full rebuild to change the version number.
I do not understand all of the testing constraints, but I think you are
right: it is difficult to test updates using a release build that uses a
new version number.
> ...
> So it looks like the accepted mar channels can be changed at run time,
but I'm not sure what this refers to exactly. Do you know if this could
allow us to change at run time the certificate used to verify the update?
The channel indicates what kind of release is being updated (e.g., alpha,
beta, or stable release). The certificate is embedded in the browser
binary though; see toolkit/mozapps/update/updater/Makefile.in. We could
embed different certificates in our nightly builds like Mozilla does, but
that won't solve the testing problem for release builds.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17662#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